NetBSD 2.0RC2 Released 56
An anonymous reader writes "NetBSD 2.0 RC2 has been released. Get it using sup or ftp from one of the mirror sites. NetBSD is used to routinely set transmission-speed records, and is widely considered to be the cleanest of the BSDs. NetBSD is widely portable."
Cleanest? (Score:3, Interesting)
Re:Cleanest? (Score:3, Informative)
Re:Cleanest? (Score:2, Informative)
What exactly does NetBSD lack that FreeBSD has?
usb stack: check (FreeBSD borrowed it)
SMP : check (getting much better fast)
RAIDframe: check (FreeBSD killed it on 5.x)
Kernel assisted threading (Scheduler Activations) : check (works better than FreeBSD's KSE btw)
FFSv2 : check
Sendmail and postfix in base: check
veirexec : check (FreeBSD doesn't have it)
pkgsrsc: check (works on FreeBSD too)
rcNG : check (FreeBSD borrowed it)
arrogant developers: nope, FreeBSD does though, phk@, des@ and some more.
cro
Re:Cleanest? (Score:5, Informative)
Options for software RAID on FreeBSD 5 right now: vinum (old and crufty these days), gvinum (GEOM version of vinum), gmirror/gstripe (standalone GEOM RAID-1 and 0 modules), ataraid, ccd (old and crummy, seems mainly an experiment in GEOM porting). Was there a compelling reason to keep RAIDframe?
"Kernel assisted threading (Scheduler Activations) : check (works better than FreeBSD's KSE btw)"
References? I'd be especially interested in a MySQL super-smack benchmark on a decent SMP system.
"FFSv2 : check"
With snapshots? Obtained from: FreeBSD?
"Sendmail and postfix in base: check"
Great, now I get two mail daemons I don't like instead of just one. At least syspkg makes them easy to avoid
"veirexec : check (FreeBSD doesn't have it)"
whatexec?
"arrogant developers: nope"
Just the users, huh?
Re:Cleanest? (Score:5, Informative)
However, where they differ is the maintainability. FreeBSD has portupgrade, which doesn't seem to exist in the NetBSD ports world. Portupgrade, although not a perfect port management tool, is damn near close to perfect
Having a ports tree is nice, all the BSD's have that, but having a tool that can intelligently upgrade your existing packages without having to remove and recompile 1/2 your installed packages (try a "make update" sometime on NetBSD, you'll see), is a must.
As well, updating NetBSD from source has always been an exercise in frustration for me. Most of the time, after updating, I can no longer rebuild the userland. It's always some small problem or other, but it's still a far stretch from FreeBSD-STABLE which has broken maybe 3-4 times in the 5 years I've worked with it.
Stability of desktop apps seems to be a bit of an issue for me as well. Mozilla in particular (Linux emulated, and native) core dumps on me on a weekly basis. This was with the pre-RC 2.0 beta's though, so they might have worked that issue out. I imagine it can't be threading related, because KDE seemed very solid, and never gave me grief.
After all this, I still trust NetBSD as a firewall which it has performed perfectly for me for years now. It's also the only OS that I find works well on non i386 hardware. Everything in the Linux world I've tried for Sparc (not Sparc64) has been crap compared to NetBSD in terms of stability. As well, 68k support (Older macs, and older HP workstations) on NetBSD is top notch, and very usable. I actually had a Quadra 610 mac (33Mhz, 24 meg ram, 250 meg SCSI-2 hdd) running apache, php, postgresql and bind 8, and it was still surprisingly fast, and even more amazingly fit well within that tiny hard drive.
NetBSD can give your older oddball hardware new life. The scalability factor that they push is not only impressive upwardly, but downwardly as well. Can you imagine any Linux distro working well on 25Mhz machines with 250 meg drives? Me neither. When they finally come out with a tool for netbsd like portupgrade, and 2.0 gets a minor revision number, I'll be there with my desktop systems.
Re:Cleanest? (Score:2)
I understand the upgrade procedure, the problem is the source breaks quite consistently. I would say that 7 times out of 10 updating my source tree will induce some breakage that is only fixed by whacking the entire tree and re-downloading.
Re:Cleanest? (Score:2)
My work life is spent helping people code ASP.NET pages for a municipality, and I have to say that any organization with money seems more inclined to throw bigger hardware at a performance issue rather than spend any amount of time profiling the applications. We have monster boxes running bad web applications that could be served from really tiny boxe
Re:Cleanest? (Score:5, Informative)
In this sense we can think of cleanliness and portability as things that imply the other, though it would be quite a different thing to interpret this particular kind of cleanliness as anything but that; it wouldn't be safe to assume on those grounds alone that the code would be faster/more efficient or be more feature rich/powerful, which I'm thinking some people might want to extrapolate. It's not beyond reason, however, and, as the author points out, there are speed records involved, so its possible that these things are related somehow (but not necessarily).
Re:Cleanest? (Score:2)
Why is out-of-the-box, desktop-ness a low priority for netbsd, while it is so stressed for Linux? Seems like a 'clean' system would more easily be achieved with a 'clean' OS...
I just wish I had an Ubuntu-like netbsd system using those sweet ports system.
Re:Cleanest? (Score:2)
That said, I think NetBSD has a few problems on the desktop.
1. People ignore NetBSD. Probably about 90% of the world is x86, and FreeBSD seems to rule the roost for x86 BSD. Although I really like NetBSD, I often grab for my FBSD mini-iso on x86 before NetBSD. Other BSD users show up in the form of the "OMG Sekure!" crowd, who gravitate to OpenBSD. So, the platforms left are no
Re:Cleanest? (Score:1, Insightful)
Re:Cleanest? (Score:3, Insightful)
DANGER (Score:3, Funny)
Replying to this post may result in flames no matter what your position.
I know which BSD is the cleanest. I'm just not going to say it here...
Re:Cleanest? (Score:2, Interesting)
It is much more friendly (well less intimidating) than OpenBSD's although I do have reservations about it, such as it not storeing any options you set at install time, and not booting with RC_CONFIGURED=false by default to alert you to the fact you need to set options.
Re:Cleanest? (Score:4, Interesting)
I dont know about portability but OpenBSD was forked from NetBSD, and has been changed less since and audited more.
But if you mean 'original' by clean, the earlier versions of either would be cleaner.
Re:Cleanest? (Score:2)
free from dirt or pollution
free from contamination or disease
UNADULTERATED, PURE
In some meanings it means original, in others it means without the unwanted 'pollution' or bugs.
So a more thoroughly audited code would be cleaner than 'better designed' which isnt too different between netbsd and openbsd in this case. Theres some very buggy software out there that was designed well, but not implemented properly.
And the most thoroughly washed and cleaned up BSD, is openbsd althoug
Re:Cleanest? (Score:2, Insightful)
Comment removed (Score:5, Funny)
Re:uh huh (Score:1)
i just got a bit enthusiastic, that's all.
you really showed them netbsd users how good linux is.
What say we have a group mass masturbation session?
NetBSD portability vs Linux (Score:3, Insightful)
It depends of what you are talking. Linux is just the kernel, NetBSD is a compete OS. You have to pick up a Linux distro and compare its portability to NetNSD.
NetBSD builds for more than 50 architectures from the same source tree, fully supporting cross-building of the entire system (it's as simple as running a shell script).
It has the same distribution layout for all the supported architectures, and the same installation system for most of them. It has machine independant
Re:NetBSD portability vs Linux (Score:1)
Re:NetBSD portability vs Linux (Score:1, Informative)
alpha, arm, arm26, cris, h8300, i386, ia64, m32r, m68k, mips, parisc, ppc, ppc64, s390, sh, sh64, sparc, sparc64, v850, x86-64
NetBSD supports:
alpha, arm, arm26, i386, m68k, mips, ns32k, parisc, ppc, sh, sh64, sparc, sparc64, vax, x86-64
Actually, I count 20 for Linux vs 15 for NetBSD.
Re:NetBSD portability vs Linux (Score:1)
Re:uh huh (Score:4, Funny)
I don't mean an N-Gage. I mean the damn taco I just bought from Taco Bell.
I accidentally dropped a NetBSD CD into the Taco Bell bag, and when I pulled out my taco, there was a bash prompt on the tortilla shell.
Get With it Already (Score:2, Offtopic)
actually, RC3 is tagged (Score:4, Informative)
Status of SMP support? (Score:2)
I know that SMP has been present in -current, at least for architectures like Alpha (and others?), for several years. My impression is that 2.0 is intended to be the first release where SMP is a real priority. I have been a longtime FreeBSD user and have watched their progress (and struggles) as the state of the art has moved from SMP in the 4.x kernels into the 5.x kernels where they are trying to squash down the BGL. How doe
Re:Status of SMP support? (Score:1)
The complexity of the SMP code in FreeBSD 5.3 was what I was talking about. IMHO, the FreeBSD hackers have been working very hard to move forward with fine-grained locking and my main worry is that they're making such a complicated system that it's going to be hard to continue moving forward with it.
I am really interested to see what Matt comes up with in DragonFly and have read a lot of the design info that he has posted as well as taken a look at a fair amount of his source code
Re:Status of SMP support? (Score:2)
I don't think the way DragonFly does SMP is best for everything.
The problem is that the DF kernel has a great deal less freedom to do what it likes with threads. This may ultimately give DF the advantage bec
Re:Status of SMP support? (Score:2)
Ran just fine, including full SMP support. Didn't note any real performance difference between FreeBSD 4 and NetBSD.
But the NetBSD tree is still supported, and FreeBSD has dropped Alpha support. It's probably a good thing, too, seeing as how I could never get 5.1 or 5.2 to install on that machine.
yay threading (Score:1)
I don't know much about SMP programming, but that threading has to be really up to par. I've been looking forward to 2.0, even though I have only a uniprocessor box, so that I can recompile Apache to use threads rather than prefork.
Cleanest OS (Score:2, Interesting)