NetBSD 1.5 released
Leto2 writes "I'm happy to see NetBSD has released version 1.5 of their OS. NetBSD-1.5 currently runs on about 20 platforms, with an additional 10 avaliable as experimental. Get it from your local mirror today!"
← Back to Stories (view on slashdot.org)
> BFD
Yes, it is big deal indeed. NetBSD project doesn't release new version every day. NetBSD 1.4 was announced in May 1999.
And the changes are well worth new number. Soft updates in FFS, full featured RAID implementation, LFS improvements, Kerberos V and more cryptography support integrated (and available outside US as well), NFS lockd, IPv6 and various performance and reliability enhancements to name only a few.
Why wasn't this on the front page?
Holy shit! That is funny! But how does it work? It's linked to Windows libraries, which I don't think use the same namespace or calling convention (win32 uses pascal)
Oh well, I wanted to wait for at least 1.5.1 anyway to get the bugs shaken down. 1.4.0 nipped me with bizarre crashes, so I don't leap onto new branches like I useta.
I just hope this time they included my one-line quirk table patch for my CD drive! grrr
What is that supposed to mean?
This is a _fair_ question. The recent releases of FreeBSD, OpenBSD and NetBSD (1.4.3) all got the front page. Why didn't 1.5?
(8-DCS)
I've been running NetBSD on a Mac G4 cube for more than a month now. It's schweeeet. With XFree86 4 (Tsubai's patches, not integrated yet unfortunately), GNOME and Mozilla, it really is a complete desktop environment. And have I mentioned that I run exactly the same software (yah, yah, so it's recompiled) on an Alpha, a Shark (ARM-based), a Celery, a SPARC and a WorkPad Z50? You can't beat true platform-independence. </speech> (Posting this from a cube right now.)
BTW, you can buy 1.5 CDs (and toys) at http://www.wasabisystems.com ...
jm
True. But if you read all the m68k specific NetBSD stuff you'll find that its a hardware issue. Yup, the clock that the system "knows" runs funny over time while on; apparently its behavior is improved or resynched to some other clock through long down times and/or frequent reboots. Suggested fix: sync to a network clock.