Slashdot Mirror
NetBSD Goodies: 2.0 RC1 Tagged, New pkgsrc Branch
jschauma writes "The NetBSD Releng Team has announced that the first Release Candidate for NetBSD 2.0 (ie NetBSD-2.0_RC1) has been tagged. This is a major milestone in the much anticipated release of NetBSD 2.0: from now on, any pullups must address some form of show-stopping issue to even be considered. The NetBSD Project encourages all users to test the binary snapshots that will soon be available on the release engineering ftp server. If no pullups are necessary, then the 2.0 release should
occur around the middle of October. Any fixes resulting in pullups will cause a second RC cycle to begin and add approximately 1-2 weeks more to the timeline."
Further, "The NetBSD Packages team announced that a new
pkgsrc-2004Q3 branch was created, and the freeze on committing to the pkgsrc trunk is now over. This branch, which includes a total of 4959
actively-maintained and supported packages, deprecates the last stable pkgsrc
branch (pkgsrc-2004Q2); all maintenance will take place on this new pkgsrc-2004Q3 branch. Please see our online documentation of the NetBSD Packages Collection for details."
I'll be really interested to see what NetBSD 2.0 is like. It seems like FreeBSD gets all of the attention (and all of the user base); I myself use FreeBSD on my laptop. However, there are some benchmarks that place NetBSD above FreeBSD, and you certainly can't beat the hardware support! Imagine... I could put it on my SPARC and be in the exact same environment as I have on my x86 laptop!
As you could with FreeBSD, OpenBSD, and Linux I"m pretty sure. IIRC the point of constantly porting the NetBSD kernel is to make sure the code is flexible and robust and doesn't build-up any system dependent kludges. I'd consider the platform independence as a sign of good design rather than as a goal.
Your CPU is not doing anything else, at least do something.
For those of you that don't know, NetBSD 2.0 is going to be _awesome_
::cough:: ::cough:: ;) [mods, it's a joke])
I run -current on 3 machines (x86,sparc32,sparc64) and it's just cool. One of the features that come to mind (really don't think it's in 1.6.2) is FFS2 (FFS being their file system)
SMP is still being worked on, I don't know about the status of the i386 port, but for sparc64, SMP is to the point where the kernel will spin up that second CPU.
(Of course, we never paid a developer full time to hack SMP
Error 407 - No creative sig found
I have a few 2.0_BETA machines doing NAT and running squid - I rebuilt one after the ipf 4.1.3 update (couple of weeks ago-ish) and NAT stopped working properly - for example, a webpage that pushed the user through from http to https would never get to the https page. The was other odd brokenness with NAT too, but this one stood out for the users :/
I moved the machine back to a build a couple weeks before that, before the 4.1.3 update - no problems so far. (Nothing else changed on the machines, though I did try a squid update to the latest in pkgsrc, no help). ipfstat looks fine, too...
I can't really help debug this with this machine as I need it working working 100% of the time. However if anyone has suggestions, I will consider them.
Having said that, the 2.0_BETA machines I have at home (running a build with 4.1.3 in it) do not have this problem. Quite odd.
Note, when I say "rebuild" above I am keeping userland and kernel in sync (crucial when something like ipf is updated anyway), plus etcupdate-ing.
I want to see the new logo already. They announced the contest about six months ago... how long does it take to choose a logo, even with open source bureaucracy? :)
Here is the Changelog from 1.6 to 2.0
I you want an evolution of FreeBSD that really makes steps forward instead of adding a pile of hacks on old code, try DragonflyBSD iinstead.
{{.sig}}
Is it just me, or is there something afoot here?
OpenBSD releases a new version every 6 months, like clockwork and uses the $ from selling the CDs to further the development. Of course, it it freely downloadable from a bazillion sites. May, November, May, November. Then both FreeBSD and NetBSD are on the edges of releases that may cause some to try them instead of OpenBSD. Is there jealousy, or enmity or evil going on?
This sounds silly, but hey, the big boys time their releases and we all know how microsoft and cisco announce vaporware that knocks off sales until the small start-up goes under.
Maybe this should go under Conspiracy
Facts:
1. NetBSD 2.0 is descended from Berkeley's CSRG.
2. NetBSD 2.0 runs ALL the time.
3. The purpose of NetBSD 2.0 is to flip out and kill people.
I heard that there was this server running NetBSD 2.0 at an ISP. And when some dude tried installing Windows the NetBSD box killed the whole datacenter. My friend Mark said that he saw NetBSD 2.0 totally uppercut some kid just because the kid ran OpenBSD.
Has anyone else noticed that the three major BSD variants are all going to have major releases within about two weeks of each other?
FreeBSD 5.3 is scheduled for a Oct 17 release. NetBSD 2.0 is scheduled for a mid-October release. OpenBSD 3.6 is scheduled for a Nov 1 release.
Hmmm?
(S(SKK)(SKK))(S(SKK)(SKK))
One more crippling bombshell hit the already beleaguered *BSD community when IDC confirmed that *BSD market share has dropped yet again, now down to less than a fraction of 1 percent of all servers. Coming on the heels of a recent Netcraft survey which plainly states that *BSD has lost more market share, this news serves to reinforce what we've known all along. *BSD is collapsing in complete disarray, as fittingly exemplified by failing dead last in the recent Sys Admin comprehensive networking test.
You don't need to be the Amazing Kreskin to predict *BSD's future. The hand writing is on the wall: *BSD faces a bleak future. In fact there won't be any future at all for *BSD because *BSD is dying. Things are looking very bad for *BSD. As many of us are already aware, *BSD continues to lose market share. Red ink flows like a river of blood.
FreeBSD is the most endangered of them all, having lost 93% of its core developers. The sudden and unpleasant departures of long time FreeBSD developers Jordan Hubbard and Mike Smith only serve to underscore the point more clearly. There can no longer be any doubt: FreeBSD is dying.
Let's keep to the facts and look at the numbers.
OpenBSD leader Theo states that there are 7000 users of OpenBSD. How many users of NetBSD are there? Let's see. The number of OpenBSD versus NetBSD posts on Usenet is roughly in ratio of 5 to 1. Therefore there are about 7000/5 = 1400 NetBSD users. BSD/OS posts on Usenet are about half of the volume of NetBSD posts. Therefore there are about 700 users of BSD/OS. A recent article put FreeBSD at about 80 percent of the *BSD market. Therefore there are (7000+1400+700)*4 = 36400 FreeBSD users. This is consistent with the number of FreeBSD Usenet posts.
Due to the troubles of Walnut Creek, abysmal sales and so on, FreeBSD went out of business and was taken over by BSDI who sell another troubled OS. Now BSDI is also dead, its corpse turned over to yet another charnel house.
All major surveys show that *BSD has steadily declined in market share. *BSD is very sick and its long term survival prospects are very dim. If *BSD is to survive at all it will be among OS dilettante dabblers. *BSD continues to decay. Nothing short of a miracle could save it at this point in time. For all practical purposes, *BSD is dead.
Fact: NetBSD is dying
NetBSD does it again. After the original Internet2 Land Speed Record set in 2004 May 3 was broken, NetBSD shines again: researchers at the Swedish University Network (SUNET) have broken once more the Internet2 Land Speed Record, using the upcoming version, NetBSD 2.0.
The new records are 124.935 Pbmps in a single stream (was 69.073 Pbmps), and 122.367 Pbmps in multiple streams. NetBSD was used once more due to the "scalability of its TCP code".
More information about this record including the NetBSD configuration can be found here for single stream and here for multiple streams. And here is the website of the Internet2 Land Speed Record (I2-LSR) competition.
There was some nasty NFS glitch n RC2, which led to RC3.
- Hubert