Slashdot Mirror
FreeBSD 7.0 Release Now Available
cperciva writes "The first release from the new 7-STABLE branch of FreeBSD development, has been released. FreeBSD 7.0 brings with it many new features including support for ZFS, journaled filesystems, and SCTP, as well as dramatic improvements in performance and SMP scalability. In addition to being available from 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."
Hmm. The time I tried to install FreeBSD, the installer choked on my hardware. I tried two different dell desktops. Part of the problem was an inability to deal with a USB keyboard. I hope that has been fixed, and I plan to try FreeBSD again, some day. I'll stick with a more common OS, for now.
A cat can't teach a dog to bark.
It's actually pretty stable. Having said that, there are some issues surrounding it. For starters, FreeBSD 7.0 uses ZFS ported from version 6, whereas Solaris now has ZFS pegged at version 10. There have been numerous enhancements made to ZFS in v10 which aren't in v6. It remains to be seen how the FreeBSD implementation catches up to the Solaris implementation. There is an upgrade command in ZFS that can upgrade the file system to the new version - but no idea how this will work in future FreeBSD versions yet. Secondly, ZFS runs better on 64bit - so using the 32-bit i386 release is not recommended. Thirdly, you need quite a large clump of memory - over 1GB and preferably 2GB or more. It is recommended to tune some kernel memory parameters to ensure that ZFS doesn't cause your system to panic. ZFS seems to like munching on memory in an attempt to scale. Otherwise ZFS is really good and very stable - perfect for use in a file server. Just don't build your file server on old 32-bit hardware, and make sure you have plenty of RAM.
READY.
PRINT ""+-0
FreeBSD hasn't wanted journaling filesystems for years, since we've had softupdates which solve many of the same problems but with half the writes. The recent gjournal plugin to the GEOM system is a block-level journal. In other words, it handles all writes to a device, whether or not the overlying filesystem supports journaling. Journaled FAT anyone?
I just said journal a lot, didn't I?
Dewey, what part of this looks like authorities should be involved?
Is when FreeBSD and wine will start to care about each other.
Damn_registrars has no butt-hole. Damn_registrars has no use for a butt-hole.
My feedback as an user of "current" Linux distros.
.0 release of distros.
- I found the same sysinstall that I saw 4+years ago when I last tried installing Freebsd.
- I found that the official way to configure is to generate the config file template using 'Xorg -configure' and then hand editing the xorg.conf config file!!!!
- I found that the standard install still installs TWM and doesn't even ask for KDE/GNOME (I know you need to install the packages *after* the install, and yes I know I can use sysinstall) and you are dropped to a text login after install.
- I found that my amd64 cpu with the nvidia integrated card doesn't have an nvidia driver. And the default nv driver can't make use out of DDC to configure my brand new widescreen LCD monitor.
- I found that my mouse pointer is invisible in X.
Now, before other start, please understand why I am saying this - I know Freebsd has a different approach to building a distro. I also know that reasons like prop. drivers are not its fault. I also accept that I probably am facing some system specific issue inherent in any
My point here is simply to let how a typical user who thought of migrating to Freebsd thinks. I for one, value using my relatively new hardware to the fullest, so I am going back to Ubuntu.
I still have tremendous regards for Freebsd as a server. I have found them to be much more stable than any current Linux distro, and capable of much more punishment too.