Some comments on FreeBSD 5.2 usage
I personally manage several FreeBSD 5.2-CURRENT instances, and here are my experiences.
FreeBSD 5.x contains many new features and technologies. Currently, it’s clear that 5.2-CURRENT is more stable and has better performance than 5.2(.1)-RELEASE. Therefore, if you are looking to install a new (of course, and ONLY if you choose the 5.x series!) computer, the best solution would be 5-CURRENT.
Before FreeBSD 5.2-RELEASE, a dynamically linked root became the default. This meant a drastically reduced / space requirement. Personally, I would suggest 128M for your / slice, and if you can use a smaller one, do so because this will place the swap slice closer to the outside tracks, and hence give better performance. If possible, split your swap across multiple disks.
Running SoftUpdates with sysinstall does not seem to be a wise idea. During install, all file systems are mounted asynchronously, and therefore, no SoftUpdates is actually needed during install. You may want to turn it on after your first boot. In my experience, disabling SoftUpdates in sysinstall’s newfs option will increase the possibility of success.
Do not install anything until it is necessary! FreeBSD’s ports tree updates much faster than its base code because third-party developers update their software from time to time. COMPAT_4X? Only when it asks you to do so! Personally speaking, I do a pkg_delete -a right after a brand-new minimum installation, and then pkg, resync my src tree and ports tree, and then install everything from ports.
Previously, Zend’s products were released only for FreeBSD 4.x and you needed to have COMPAT_4X enabled in your /etc/make.conf in order to make them run. However, fortunately, a few days ago they released a FreeBSD 5 binary version. This change will permit us to run PHP applications much faster and more securely, because COMPAT_4X brings not only compatibility, but also security issues :-)
Currently, even -O2 is not officially supported for compiling kernels and world. So, do not add these options unless you are ready to submit backtraces as well as patches to address them.
READ UPDATING carefully. This is necessary for tracking -CURRENT, and a good habit if you track -STABLE. Before you start your make world kernel build, DO REVIEW IT!!
On SMP/HTT machines, using ULE as your scheduler will give a great performance gain.
You need libmap.conf! Map all libc_r related calls to libthread, or you will be unhappy because mixing thread libraries will kill you silently :-)
在线阅读本文并参与讨论 delphij's Chaos blog.delphij.net/posts/2004/03/some-comments-o/