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 ;)
Incorrect conclusion. Going by these comments, very few slashdot readers use NetBSD. In fact, I'm willing to bet that the majority of the slashdot GNU/hippies that rant on and on against Microsoft and fawn over Linux are all too happy to activate their Windows XP and click about in their MSIE. I make this judgment from the complete dearth of technical information in slashdot comment pages.
Of course, this is quite hypocritical of me as here I am adding no useful technical information. In all honesty, I've never had the chance to use NetBSD for any significant task. I know (and love) FreeBSD and OpenBSD inside and out I've only put NetBSD on esoteric machines that don't run the other BSDs quite as well (really old Macs and Sparcs).
Anyway, congratulations to the NetBSD folks. The next time I need to do something useful with strange hardware, I know where to look.
Give it a try. It really doesn't matter what kind of machine you have, as long as it's 32 bit and supports an Memory Mapping Unit, it should work ;)
Success is as dangerous as failure, hope as hollow as fear.
Well, I'm surprised by the figures I read here. I use netBSD since september last year and it's been a good experience ever since. It gave me what I was looking for on Linux, a small footprint after the installation and I guess that's not what linux is about anymore, hence the 5-7 CD-set on most of the distributions. Burning just another set of iso's just to give another linux-flavour a try isn't my idea of efficiency. But hey, we all have fat pipes and fat systems, haven't we? So who cares about a small footprint and a 5 iso download? Well, I do... In the meantime I'll be happy with my netBSD bootfloppy and a ftp-install to match.
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."
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.