Slashdot Mirror
NetBSD v3.0 Released
FullMetalAlchemist writes "After six release candidates, the NetBSD project has finally released a gold version of a major mile stone; v3.0. I'm looking forward to this release a good deal. If I wanted to, I could build our entire office infrastructure on it thanks to Xen. Major Changes can be found on the NetBSD website, and there are several ways to get the release. Get downloading!"
Hrrmph. As a loyal VAX owner, I need to note that it seems that although NetBSD claims to support some gawd-awful high number of architectures...many are left behind to basically fend for themselves.
Just because NetBSD v3 is out, doesn't mean it runs on anything except a few of the common Intel/PPC chips.
It would be nice to be able to complete a full VAX build without some bizarre GCC error forcing me to go look for a workaround.
VAX 4-ever!
Two, we hardly knew thee.
Some settling may occur during posting.
I can install NetBSD on my, oh, (picks obscure platform) VAX, and have xen run multiple virtual vaxes?
try { do() || do_not(); } catch (JediException err) { yoda(err); }
maybe you shouldnt?
and you can go back to using your poorly ported system or trolling other forums...
idiot.
Due: rxplain, plese?
Netcraft surrenders...
No WPA support, very little support for 802.11g devices, and a lot of missing things as compared with other modern OSes (a current, working DRI implementation and support for ACPI suspend/resume would both be very nice)... this is a pretty disappointing release.
I've always liked NetBSD for being very cleanly implemented, but the way things have been going lately, I might wind up having to switch to FreeBSD or *shudder* Linux for some upcoming projects.
Congratulations for a new release of a great OS!
I'm compiling it on my toaster right now!
I am trolling
This is an obvious troll, not the real release notes, the author was so sloppy he/she even referred to OpenBSD instead of NetBSD...
okay, that was a joke.
Anyone got any?
posting comment to remove moderation of grandparent
Read Epic the first RPG novel.
I've run OpenBSD and FreeBSD but what compelling reason would there be for me to run this variant? Riddle me this, is it worth my time installing this on a test box?
It's ok. You'll be remembered in the way of bash.org quotation.
"I'm a well-wisher, in that I don't wish you any specific harm."
I use one based off the VMS engine that drives yours, & after 10++ years of development & patch releases from its VMS underpinnings in design?
It rocks... & we ALL know what it is & have used it most likely: A form of Windows, based off its NT 3.x-3.5x-4.x-2000/XP heritage ->
Windows Server 2003 SP #1 fully hotfix patched as of the date of this post is the best of the lot & most current.
That's what I've truly got to say for it.
Well, also that it's what windows should always have been imo, & I've used it since Windows 3.0 & coded from 3.11 onwards to today as well.
This version just runs stable for months on end uptime (not counting reboots for drivers/various installs etc.) & runs on tons of different hardware & with it, so, I can do what I am doing as I post this - watch T.V. via Win32 USB, listen to tunes (via a software I wrote that does MP3), & post to you all on the internet.
So, that type of ability, to do that? I used to see it in movies in the Win16 days & say "Hmmm, must be UNIX"...
This is what makes it so great, besides being reliable, secure (the way I do it @ least), & run so many softwares + hardwares:
This final product release (lately) of Windows NT-based OS!
And, Years of mistakes, time in redo/rethink + rebuild, & rinse, wash, + repeat a few times in multiples of 3 imo on Microsoft's part no doubt @ the expense of many people's time - imo, the one thing mnney can't buy you more of, & thus, the most valuable.
Plus, the tools for software development for Win32? Heh... huge amounts & varied. Delphi being my fav, but, using VB.NET, VB6, SQL extensively in SQLServer on the job.
RAD Tools all, they're fantastic imo, & I come out of the drop-thru single function instance code days of the 1980's - trust me, lol, today's tools are a wicked bigtime improvement, as well as what comes out of them by comparison to those days of the dinosaurs...
APK
P.S.=> VAX port dead? Heh, man, not really... NT = VAX @ the OS core design level (via Mr. Dave Cutler). Same OS designer built this one, only better: FAR MORE POWERFUL DUE TO FLEXIBILITY IN TODAY'S COMPUTING ENVIRONS FROM THE HOME DESKTOP/LAPTOP, TO THE OFFICE, TO THE SERVERS & THE REST OF THE WORLD with VAX underpinnings & a Win32 Shell we code on - Windows Server 2003 is a look @ the future & the future IS now, because it does exactly whatever needs doing on a computer, more & thus better vs. all the other OS out there! It used to be Multi-CPU family capable, but not what it was if it even still is... I only use it on X86 everywhere I go... apk
Microsoft fucking sux0r!
Does it run Linux?
(sorry, it's Christmas so the posting volume is low, and I had to get it in because I've got 'owt else better to do!)
What exactly does one do w/a Dreamcast running BSD anyways?
"I see a vacant seat," replied the Ghost, "in the poor chimney-corner, and a crutch without an owner, carefully preserved. If these shadows remain unaltered by the Future, *BSD will die."
"No, no," said Scrooge. "Oh, no, kind Spirit! say it will be spared."
"If these shadows remain unaltered by the Future, none other of my race," returned the Ghost, "will find him here. What then? If it be like to die, it had better do it, and decrease the surplus operating system population."
Scrooge hung his head to hear his own words quoted by the Spirit, and was overcome with penitence and grief. It was sad to see any operating system die, even one so obviously flawed and useless as *BSD.
God bless us, every one.
One great thing about netbsd is the possibility of handheld netbsd. Find out more Here. Some people have tried using it on flash cards with great success, a good choice if that is the case is 256mb's to get the full effect. Handheld BSD is great though, give it a try.
Didn't we all concede right on this very site that BSD is dead? *ducks*
"Of course it runs NetBSD" - the old saw, it seems. But I think that NetBSD is falling down in this regard. Many ports don't work properly, or haven't been updated in ages. Mailing lists lie dormant, waiting for attention, such as SBMips (BroadCom Sybyte MIPS) - in spite of Wasabi Systems (which is basically the commercial arm of NetBSD) having a press release about Broadcom support back in 2002, not much is being done in extending NetBSD to the CPUs used in consumer-grade equipment like Linksys routers. It's not even available for a fee: Wasabi doesn't have it in their development products and doesn't plan to. Linux is clearly quite far out in front in this regard.
And it's not only MIPS: VAX ports are stale as well, from what I see here. This is sad. I like the idea of portability, and I like NetBSD - but I don't find that it lives up to its repuation in portability. Yes, someday I'll shut up and work on ports to the platforms I care, but in the meantime I am using Linux on the Broadcom CPUs and finding I enjoy it..almost too much to bother with NetBSD.
Damn shame mods didn't think this an insightful question.
I'd sure like to see some bsd folks take a stab at answering it.
Mod me down with all of your hatred and your journey towards the dark side will be complete!
Linux is a kernel. NetBSD is an operating system.
When Linux runs on a platform, most of the time it means an incredibly stripped-down variant that has almost no features runs on the platform. In addition, no support is thrown in to port the rest of the operating system (e.g. userland, applications, etc.).
When NetBSD runs on a platform, most of the time it means the default NetBSD userland, kernel, and everything else in the source repository will run on the platform. In addition, NetBSD tends to be careful about incorporating new features (Linux had support for hot-swappable CPUs at one point...).
Isn't it??
Reality is nothing but a collective hunch.
thanks for the great christmas present. however, like when mum bought me a C64 game for my speccy back
in the day, I'm sure this present will also have a nasty habit of not working on my Sparc5 , my Amiga
and my Acorn. Older NetBSD did fulfill its promise of being VERY multiplatform..but now it has a distinct rotten odour of a x86 platform admirer
You'd install NetBSD on all the hardware that [Open|Free]BSD doesn't support.
Then you go back and install NetBSD on the rest to standardize, where there isn't a compelling reason to use the others. For instance, you might want to keep OpenBSD on the external firewall(s).
I have a special place in my heart for NetBSD. I once was living poor, and was given a small, mips based computer. The only modern OS I could run was NetBSD, and it ran great! Never crashed and was well documented enough for me to figure out whatever I wanted to do.
;) In this day and age, with distros like Ubuntu and Linspire, even my mom can run linux, let alonse a lowly Windows Admin. Being able to setup and run NetBSD restores my geeky feeling of supiority!
Here are some reasons you might want to try it out:
1. Geeky history lesson. In my mind there was a golden age of geekiness going on during the 70s and early 80s centered around the creation of BSD. Reading the many stories in the Jargon File gives you an idea of the times. NetBSD is a decendent of that OS and those times. Using it gave me a taste of times I would love to visit if I ever had a time machine. Geeky!
2. It is simple. Install a basic machine and look at the process list. On my 1.6 machine there would be maybe 5 lines. Interesting to see how little an OS needs to be useful.
3. It is something new to learn. I love tinkering and learning new things. Instead of a train set, I have a network of old and/or unusual computers. Not an x86 in the bunch. NetBSD and linux power most of it.
4. You can me more of an elitest
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 *BSD at this point in time. For all practical purposes, *BSD is dead.
Fact: *BSD is dying
if you were cool you could install NetBSD on your Dreamcast and SSH into your Xbox
A Sega Dreamcast console out of the box supports only dial-up. An Ethernet card for the Dreamcast costs more than the Dreamcast itself.