Slashdot Mirror
FreeBSD 6.4 Released
hmallett writes "FreeBSD 6.4-RELEASE, the fifth release from the 6-STABLE branch of FreeBSD development, is now available. In addition to being hosted at many FTP sites, ISO images can be downloaded via the BitTorrent tracker, or for users of earlier FreeBSD releases, FreeBSD Update can be used to perform a binary upgrade."
No one really cares about 6.4. The people who really, really, care about stability might decide to run 6.4, but most of the stability-conscious people will just run 6-STABLE and not care about releases. The people who want new features are running 7.0 or 7-STABLE and are waiting for 7.1. The people on the cutting edge are running 8-CURRENT.
I am TheRaven on Soylent News
ZFS memory problems are on 32bit architectures. It was developed for 64bit and it needs some room. Some hard limits on 32bit platforms need to be tweaked so it fits. Use a 64bit system with zfs.
Samba is optimized for the linux network stack and you need different options for your FreeBSD6. Seems to work better with FreeBSD7. I d wish the developer wouldnt assume that everything works like on their local linux box.
Actually, stability-conscious people will be running either RELENG_6_4 or RELENG_7_1 (once 7.1 is complete). You may call them the super-stability-conscious people. :) -STABLE branches just refer to the ABI being stable, but they are still development branches. They do tend to be more stable then CURRENT since the code must survive CURRENT for an amount of time before being merged into STABLE.
Personally, I run 7-STABLE (RELENG_7) on all my systems with HEAD in a VM or two.
Sometimes it's because you're running critical shit. Sometimes it's because you're running critical shit and the last person with reboot experience retired 10 years ago.
Do you even lift?
These aren't the 'roids you're looking for.
However, without a good virtualization solution there is no way.
This doesn't directly address your problem with VMWare, but FreeBSD's self-virtualization (aka "jails") is outstanding. Our standard deployment now is to build a beefy server with a minimal install, then use jails (via "ezjail") to carve it into multiple production servers. When the system starts to slow, we shuffle the jails around to different hardware as appropriate.
The only thing I dislike about jails today, in practice, is that each can only be assigned one IPv4 address. The new virtualized network stack should allow multiple IPv4 and IPv6 addresses per jail but it's not available on -STABLE yet. Once that's in place, FreeBSD jails will be the perfect virtual server arrangement for our workload.
Again, that doesn't help you if you're needing to run Windows or Linux VMs (although you can make a jail based on, say, Debian running on the native FreeBSD kernel's emulation layer), but it's extremely useful for consolidating multiple servers onto a machine.
Dewey, what part of this looks like authorities should be involved?