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!"

15 of 132 comments (clear)

  1. The VAX port stopped working a long time ago by Anonymous Coward · · Score: 4, Interesting

    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!

    1. Re:The VAX port stopped working a long time ago by SillyNickName4me · · Score: 4, Interesting

      Heh, the last version that actually builds and works correctly on my VAX is 1.4

    2. Re:The VAX port stopped working a long time ago by mnemonic_ · · Score: 1, Interesting

      ...doesn't mean it runs on anything except a few of the common Intel/PPC chip

      In other words, it runs on 90% of their users' computers, and the developer time on those architectures was well-spent. Sorry, but pandering to hobbyist users of obscure hardware (yes, today it is) is a waste. In a world of finite resources, tasks must be prioritized. By releasing first for x86, the NetBSD devs demonstrate their sanity by working on the software that would benefit the most users. Today, VAX doesn't matter, so why should they support it at all?

    3. Re:The VAX port stopped working a long time ago by possible · · Score: 5, Interesting
      Why does VAX need to be supported?

      Because porting to non x86 architectures forces you to fix bugs. If the code is faulty, it may work for 99% of the x86 users, but crash for the remaining 1% of x86 users. But since none of the developers can reproduce the problem, it's a case of "I dunno, works on my machine, I'm not going to spend time looking for it". Whereas on other architectures, incorrect code may fail 100% of the time due to aligment, different exception handling, etc.

      NetBSD doesn't just suck on VAX. It sucks on ppc (aka, Macs) too. And up til recently it sucked badly on amd64. Most of NetBSD's "supported architectures" haven't worked for years, because they often cross-build instead of doing native builds.

    4. Re:The VAX port stopped working a long time ago by SillyNickName4me · · Score: 4, Interesting

      Hmm... just wondering, if I post what version each of the obscure pieces of hardware I have lying around manages to run, will all of those posts get a +5 interesting moderation?

      Anyway, its a vaxstation 3100 m20 with 16mb ram and monochrome graphics with a local (scsi) disk for swap and temp storage, it is netbooted. When trying to run 1.5 or 1.6 and build a world, the machine just hangs after some 2 days of work. 1.4 finishes building a world but it takes forever to do so (actually, something like 7 or 8 days). I never tried 2.x and current however, maybe I should when I can be bothered to connect it again and setup mopd on some machine here.

    5. Re:The VAX port stopped working a long time ago by Anonymous Coward · · Score: 0, Interesting

      because they're engaged in fraud. it isn't just the vax port that is broken.

    6. Re:The VAX port stopped working a long time ago by c9a9t · · Score: 2, Interesting

      I just downloaded macppccd-3.0.iso hoping it would be an improvement over 2.1 but the 3.0 cd doesn't even boot on my b&w G3.

      Perhaps they should consider timely complete release notes for each architecture? I don't think 2.1 macppc release notes and errata have yet appeared...

      Meanwhile, much as I love BSD (preferably FreeBSD) on i386 I haven't found it terribly useful on powerpc. If it weren't for Debian my macs would have to run mac os.

    7. Re:The VAX port stopped working a long time ago by Anonymous Coward · · Score: 1, Interesting

      OpenBSD has very decent macppc support, I ran it on a B&W g3 until I gave it away.

  2. So, does this mean by ch-chuck · · Score: 1, Interesting

    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); }
  3. Screenshots of graphical installer by Anonymous Coward · · Score: 1, Interesting

    Anyone got any?

  4. Re:I'm underwhelmed. by Anonymous Coward · · Score: 0, Interesting

    A server os that works on dreamcast. Duh.

  5. Re:I'm underwhelmed. by xwin · · Score: 2, Interesting

    Exactly. It is just about the only thing that runs on my Qube. The OS is actually pretty good, easy to use and secure. Very good server OS to run on mips hardware.

  6. does it fulfill portability promises? by drwho · · Score: 3, Interesting

    "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.

  7. Re:Hmmm, the other BSD by ci4 · · Score: 2, Interesting

    I was about to say the same. It started with my laptop - OpenBSD not supporting the modem part of a Xircom combo cardbus adapter, FreeBSD completely failing even to begin installation - and that's the whole sequence of them between 4.4 and 5.3 (haven't tried since). NetBSD (1.6 at the time) ran first time and the Xircom got me connected to the ISP first time. Since then I have it running permanently on some five machines in the office doing various In(ter|tra)net serving and desktop duties; only one box is running FreeBSD (6.0 currently) because NetBSD's INSTALL kernel (at least) did not find the RAID part of a HighPoint card; FreeBSD did - I wanted it mirrored and setting up RaidFrame on a boot disk was a bit over what I wanted to do quickly... Anyway, I carried on adding additional software on that box via source ports; this has been mostly succesful, but nowhere as smooth as is normally with pkgsrc. I do run two or three OpenBSD firewalls (including several at customer sites), but generally performance issues have stopped me from other deployment.

    NetBSD performance has been excelent recently; BTW I run -current on all but one system (that one follows the latest release, therefore will get 3.0 this Wednesday).

    I also maintain some five Solaris(mostly 10/11) systems - the latest Express with the ZFS id awesome!

    Haven't touched the L*x thing for some three years now - don't start me on it...

  8. Reasons To Run NetBSD by Anonymous Coward · · Score: 1, Interesting

    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.

    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 ;) 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!