Home > NetBSD > NetBSD 2.0 Release Engineering Process has begun

NetBSD 2.0 Release Engineering Process has begun

  Submitted by Jan Schaumann NetBSD 19 Comments

James Chacon of the NetBSD Release Engineering team has announced that the Release Engineering process for the much awaited NetBSD 2.0 release has begun. At this time, the expected final release is scheduled for the end
of May 2004. See James’ message to the netbsd-announce
mailinglist for details.

About The Author

Eugenia Loli

Ex-programmer, ex-editor in chief at OSNews.com, now a visual artist/filmmaker.

Follow me on Twitter @EugeniaLoli

19 Comments

  1. 2004-03-29 7:46 am
    Anonymous

    Beta testing ;) , to help us making this the best release ever!

  2. 2004-03-29 7:53 am
    Anonymous

    By the looks of things, it probably will be ;)

  3. 2004-03-29 8:12 am
    Anonymous

    One thing I’d very keen to use is the kernel smbfs support:

    http://www.netbsd.org/Changes/changes-2.0.html#kernel

    It was imported from FreeBSD ;) .

    If I’m going to start to use/test the 2.0 I should start from here, right ?

    ftp://releng.netbsd.org/pub/NetBSD-daily/current/

  4. 2004-03-29 8:13 am
    Anonymous

    Feeling very eager to get it. surprised that it supports more than 50 arch… Great work NetBSD Team!!!.

  5. 2004-03-29 9:18 am
    Anonymous

    “The current tentative schedule shows an expected final release in late May 2004.”

    How long has it been since 1.6 was released? I have the impression that 1.6.1 and 1.6.2 were maintenance releases with few new features introduced. Anyway, there seems to be LOTS of changes planned from 1.6 to 2.0.

    Not many changes in Sysinst, though. I mean, it gets the job done but it looks a bit, well, ascetic. But I suppose that’s just something you learn when you port software between many machine architectures: keep it simple, functional, and efficient. 😉

  6. 2004-03-29 9:39 am
    Anonymous

    How long has it been since 1.6 was released?

    More than one year and a half. 1.6 was released in September

    2002.

  7. 2004-03-29 11:21 am
    Anonymous

    If I’m going to start to use/test the 2.0 I should start from here, right?

  • 2004-03-29 11:25 am
    Anonymous

    How long has it been since 1.6 was released? I have the impression that 1.6.1 and 1.6.2 were maintenance releases with few new features introduced.

    That’s right, the changes to netbsd-release branches (e.g. netbsd-1-6) are kept to a minimum, to provide a stable system that is not a moving target. The webpage http://www.netbsd.org/Releases/release-map.html contains information about the differences between formal releases, -release, -current, etc.

  • 2004-03-29 11:25 am
    Anonymous

    How long has it been since 1.6 was released? I have the impression that 1.6.1 and 1.6.2 were maintenance releases with few new features introduced.

    Yes, 1.6.[12] were maintenance releases only.

    -current now and 1.6.2 are very very different. I just want to note that 2.0 is not, um, er, an increment from 1.6.2. 2.0 is result of contiguous work that started immediately after 1.6.0 was branched (so 2.0 is not something that builds on 1.6.0, either).

    Anyway, there seems to be LOTS of changes planned from 1.6 to 2.0.

    Well, if they have been hacking on it for almost two years, there should be LOTS of changes.

    Not many changes in Sysinst, though.

    Actually there have been lots and lots of changes to sysinst, they haven’t just been that remarkable to be noted on the major CHANGES list. Still, sysinst is as ascetic as in 1.6. It just is more stable. And IIRC the partitioning stuff has improved, and the usability in general.

    But I wouldn’t want it any other way. It is a bit hard to use a hi-color graphical whizz bang installer over serial console.

    (Just building -current with 2.0A version at the moment…)

  • 2004-03-29 12:02 pm
    Anonymous

    did usb wi(4) show up? will it?

  • 2004-03-29 3:09 pm
    Anonymous

    Wasn’t there a change in 2.0 release in regards to threading and the scheduler? Could somone point me to that information? thanks in advanced.

  • 2004-03-29 3:21 pm
    Anonymous

    2.0 will introduce kernel support for a POSIX threads interface in the base system, based on Scheduler Activations, a M:N threading implementation.

    See Nathan Williams’s paper about it:

    http://web.mit.edu/nathanw/www/usenix/freenix-sa/freenix-sa.html

  • 2004-03-29 5:33 pm
    Anonymous

    I have _never_ been able to connect to the http://www.netbsd.org or http://www.us.netbsd.org website. This is something that has bothered me since I installed slackware 9.1 (current). I can connect from gentoo and winxp on a seperate machine, but on this one I simply get “Waiting for http://www.netbsd.org...” in firefox and “Request sent” in links.

    Anyone have any ideas? I am using the exact same nameservers on all systems, and all systems share the same connection. I am able to connect to the www mirror at http://www.au.netbsd.org perfectly fine, and I have no trouble whatsoever with _any_ other site.

    Im out of ideas as to what configuration differences could lead to this behavior.

  • 2004-03-29 5:39 pm
    Anonymous

    >There are so many remote vulnerabilities in it, and the components of NetBSD

    Really ? Well, if so its the same that Linux and other *BSD’s

    use so we better remove those OS’s as well, just in case MS

    may use it against anyone !??

    I think you should read:

    http://www.netbsd.org/Goals/ , it is not just intended to

    be a Desktop OS for everyone. (though it works nicely for that as well once set up properly.)

    I’m also wondering what plays not great together ? It works like a charm here.

  • 2004-03-29 5:58 pm
    Anonymous

    It could be that Firefox and other Netscape-derived browsers (Netscape Navigator, Mozilla, etc.) connect to their own DNS servers. Try “lynx http://www.netbsd.org” to see if you can connect. If it does, then the problem lies with Firefox.

  • 2004-03-29 6:07 pm
    Anonymous

    Thank you for your comments Anonymous, but I had stated that I get the same results with Links (an advanced? version of lynx) ;)

    I realize this is all OT, so I appologize if that offends anyone!

  • 2004-03-29 8:57 pm
    Anonymous

    Please fix sparc64 support, it is VERY buggy.

  • 2004-03-30 7:06 am
    Anonymous

    yeeehaaa … macppc has issues too, but somehow I guess it will only be fixed if you _do_ it or at least spent some effort on bug reporting :O

    PS:NetBSD(current) is really great, it makes my mac fly if it does not crash ;)

  • 2004-03-30 6:44 pm
    Anonymous

    I have NetBSD 1.6.2 runing on a powernotebooks laptop. It runs really good. I use it as a desktop OS. I am really impressed with the quality of NetBSD.