Slashdot Mirror
NetBSD 1.6.1 Release Process Has Begun
jschauma writes "The NetBSD Project is pleased to announce that NetBSD 1.6.1 has been branched
and the release engineering process has begun. NetBSD 1.6.1 is a maintenance
(or patch) release for users of NetBSD 1.6, not to be confused with
NetBSD-current (which will become the next major release). As a patch release, it is not branched off the head of the CVS source tree, but instead includes all security fixes and patches applied to the 1.6 branch. A complete list of changes since 1.6 is available in src/doc/CHANGES-1.6.1 of
the branch, which can be checked out by passing the -rnetbsd-1-6-PATCH001-RC1 flag to the cvs command: cvs -rnetbsd-1-6-PATCH001-RC1 co src.
Details on the release cycle and status information is available from www.netbsd.org/releng/releng-1.6.html."
Hearken unto me, O children of Slashdot:
End your torture at the hands of lesser OSes; try NetBSD today! (or whenever 1.6.1 is properly released ;)
In the above, it should read 'NetBSD 1.6.1 has been tagged', not branched. Sorry for the confusion.
-- "Tradition is the illusion of permanence."
Or 64bit. Like the NetBSD/alpha-, NetBSD/sh5-, NetBSD/sparc64- or NetBSD/x86_64-Ports.
-- "Tradition is the illusion of permanence."
Guess all the NetBSD users out there are too busy at work
to bother making any postings here. Oh well, for them, I'll
write this:
NetBSD Rulz!!!!!
People tend to think of NetBSD as only good for obscure architectures and not for any serious systems. In my experience this is far from true.
/usr/pkg for package placement, making it very clear what is built from pkgsrc or installed as a package. This leaves /usr/local available for you for packages build and installed outside of the package system.
My experience with NetBSD has actually only been with i386 platforms, and I've been very impressed. It is actually my preferred UNIX (over Open/FreeBSD, Linux, Solaris). I find the default install to be nice and minimal, and the packaging system layout to be very clean and effective.
I like the way NetBSD uses
Upgrades of NetBSD are also very smooth, both binary and source, with security patches released nearly instantly.
A lot of the innovation in the BSD's is actually originated by NetBSD (which has a team of excellent developers), then incorporated in by the other BSD's, taking much of the credit from their less popular counterpart.
Anyways, after that rant, give it a try, you won't be disappointed!
In my computing experience, I have used NetBSD, FreeBSD, and OpenBSD. I can't stand FreeBSD's installation process. I always end up going in a loop with assigning disks or labels. The ports collection works most of the time, but is damn annoying when it doesn't. OpenBSD's installation is fine, but post-install it's a pain getting everything up to the point of functionality. NetBSD strikes a good balance between the two, with the purely text-based installer but also a functional post-install.
I am also happy knowing that all my non-SMP servers can be running the same OS, no matter if they are Intel, MIPS, SPARC, Alpha, VAX, or otherwise. Hardware age doesn't matter, either. I use an old 486DX with 32MB of RAM as a DNS/DHCP/SMTP/IMAP/LDAP server for a network, and it handles the load beautifully.
I remember I once had an errant Perl script that kept on spawning itself, sucked all the available memory, and pegged the CPU load average to around 70. It was slow, but I managed to log in, kill all the Perl scripts, and everything returned to normal instantly. No crash, no fallout. I'd like to see Windoze 2000 (or even Linux) do that!
As another anecdote from my work at my school, I have a professor who, while on our FreeBSD 4.6.2 server, forgot to grep for nfsd in an awk script when he was trying to kill and restart NFS. This killed all the processes on the server, and left it without init, basically in an unusable state. I can recall doing that in NetBSD, and it appears that there is a kernel function that checks that init is still running and will respawn it if it dies, and then place the machine in single-user mode. I would still have had to run over to the science building and get things going again, but our uptime would have been preserved, and I would have been able to do administrative work immediately.
It's a pity that NetBSD doesn't have more users than it does. It has got to be one of the most capable open-source OSs, and I certainly prefer it over some commercial UNIXs such as AIX.
"After all, you have no option to just install the parts that you need!"
.rpm without gnome-libs. Thus, I have to include bloat and yet another package to watch carefully in regards to possible security vulnerabilities.
.rpm (which naturally, is needed by the GiMP itself), and compile and install the GiMP myself. Hey - look! No need for Gnome libs!
No, on most distributions of Linux, you do *not* have that option. Everything is so freakin' interdependant for absolutely no god damned reason.
Take RedHat. I want the GiMP. Great. Or not - RH insists I need their 'gnome-libs' package. I dislike Gnome with a passion, but that's neither here nor there.
I can't install the gimp
Or, I could go an alternate route. I could simply install the GTK
The problem is, compiling from source defeats the purpose of binary distribution. Ease of use and installation is immediately thrown out the window. Easy upgrading is gone as well.
So, you can either play along and install crap you don't want or need, or waste days of post-install time compiling everything from source.
NetBSD apparently doesn't have this problem. Good for them, I think I'll be sending them some cash for a disc or two in the near future.