Slashdot Mirror


NetBSD 1.6.2 Released

kairi writes "NetBSD 1.6.2 has just been released, supporting over 40 architectures. See the release announcement! Be sure to use one of the many mirrors when you grab your ISO!" MobyTurbo adds "A preliminary source of bittorrents has been announced on the NetBSD users mailing list."

34 comments

  1. I DON'T LIKE WHITE GUYZ by Anonymous Coward · · Score: -1, Troll

    LOL !!!!???
    a galapagos tortoise wearing a scarf just SuCkeD My CoCK OMG!!!
    ??? PROFIT

    ps big ups to gnaa omg

  2. Coping with NetBSD's Loss by Anonymous Coward · · Score: -1, Flamebait
    Although it is true that BSD is dying, there are some helpful steps you can take ease your sorrow:
    • deal with the inevitable.
    • grieve for your loss.
    • move on.
    Never let your emotions get mixed up with something as silly as a computer operating system. It isn't healthy. So BSD fails. Big whoop. Deal with it and move on. Hope this helps.
  3. WARNING - REMOTE ROOT IN BSD - PATCH NOW! by Anonymous Coward · · Score: -1, Troll

    CERT SecAD NBSD4536A746
    Advisory: Olfactory disturbance during *BSD use
    Affected: NetBSD all versions
    FreeBSD all versions
    OpenBSD all versions
    Description: The dead corpse of a *BSD operating system emits a foul, disgusting smell which reduces the
    productivity of the users.
    Recommended activities: - use nose plugs
    - removal of *BSD operating system, replace with Linux or Windows XP

  4. Dedication by JustinXB · · Score: 5, Interesting
    http://netbsd.org/Releases/formal-1.6/NetBSD-1.6.2 .html

    "Dedication
    The NetBSD Foundation would like to dedicate the NetBSD 1.6.2 release to the memory of Erik Reid, who went missing and is presumed dead in a sailing accident on 18 February 2004. Erik's contributions to NetBSD included work on support for SGI MIPS R4000, integrating XFree86 Direct Rendering Interface (DRI), and managing the build lab. His death came as a shock, and he will be greatly missed by all of us. May he rest in peace. "

    Just thought I'd point it out.

  5. Truly an American Icon by Anonymous Coward · · Score: -1, Troll

    -insert witty reference to this situation being ironic because *BSD is also dead-

  6. Geez by Anonymous Coward · · Score: 1, Funny
    Just when I finally got around to getting all of
    1.6.1 downloaded (on dialup) and installed on my
    laptop, this happens.


    NetBSD Rules!

    1. Re:Geez by TruffleGuy · · Score: 1

      Ya they seem to keep poping new versions out as soon as I get one downloaded.

      --
      i am we todd did... i am sofa king we todd did
    2. Re:Geez by Endive4Ever · · Score: 5, Interesting

      I just installed 1.6.1 on my four-way PPro box (IBM PC Server 704) but have discovered I'm going to need to build NetBSD-current to get SMP support for it. I was hoping they'd finally merged SMP into the release branch, but maybe that's a 1.7 thing. This is a minor incremental release.

      Being as I have a well-maintained near-complete mirror of the 'distfiles' source tarballs for the Pkgsrc tree local now ('make mirror-distfile' is your friend for overnight bandwidth burning), I can't see ever moving to any other OS for main use. I have all the source for everything for almost any type of box I put into service.

      --
      ---
    3. Re:Geez by bccomm · · Score: 5, Informative

      I'd go with -current anyway, there are more features in it, and it's generally more widely-used by the community.

      PS: I believe the next NetBSD formal release will be 2.0. It will have kernel threads, SMP, ACPI, and all that other good stuff. (:

      -Bruce

    4. Re:Geez by kivaapina · · Score: 2, Informative

      SMP will never go to 1.6 branch. You have to wait for 2.0 or use current. If you don't like to build current you can download it from releng.netbsd.org.

    5. Re:Geez by krog · · Score: 1, Funny

      Considering the speed at which NetBSD releases come out, you must be rocking 1200 baud!

      -krog, NetBSD user since 1.1 (about 40 years ago)

  7. Tell me... :) by molnarcs · · Score: 2
    I've been using FreeBSD for some time, but I'm curious about NET, especially using it on the desktop. Any experience with it?

    Also, 40 platforms are great, but what are the differences in their support? I suppose NetBSD has some sort of port system as well. Is there a detailed list of what ports work on a specific architecture (I'm especially interested in PDAs, and in NetBSD as an OPIE replacement)?

    Anyhow congrats to the the kings of portability :) Also, there is this interesting newsbit if you scroll down in the release announcment:
    Pkgsrc included in Bluewall GNU/Linux (27 Feb) (top) Bluewall GNU/Linux has announced the release of a Linux distribution that includes the NetBSD pkgsrc distribution. One of the goals of the NetBSD Project's pkgsrc distribution is to be portable to other operating systems and we are pleased to see someone take advantage of that.
    So, is there going to be a linux distro with something similar to ports (as I said, I only have experience with FreeBSD ports, and only assume here that pkgsrc is something similar). ps - not interested in portage until it doesn't handle dependencies when you remove packages as well...
    1. Re:Tell me... :) by saintlupus · · Score: 4, Informative

      So, is there going to be a linux distro with something similar to ports (as I said, I only have experience with FreeBSD ports, and only assume here that pkgsrc is something similar).

      Yes, there is. Pkgsrc is remarkably similar to what Free and OpenBSD call Ports. It also works on a lot of OSes, including Linux, Irix, and (I think) Solaris.

      Check out the NetBSD page for info. It's pretty cool stuff.

      --saint

    2. Re:Tell me... :) by Anonymovs+Coward · · Score: 2, Informative
      I suppose NetBSD has some sort of port system as well.

      Weird that you ask that, since you answer it a few lines later. It's pkgsrc, thus called because "port" is NetBSD's term for a separate architecture on which it runs. Pkgsrc originally came from FreeBSD's ports system.

    3. Re:Tell me... :) by codemachine · · Score: 1

      Yeah, NetBSD uses pkgsrc instead of ports because ports isn't portible enough to run on 40 architectures, whereas pkgsrc is.

      Ironic that ports isn't portible enough...

    4. Re:Tell me... :) by pschmied · · Score: 4, Informative

      I really like NetBSD as a desktop OS. NetBSD's clean approach means that they often get cool new drivers and features before anyone else, including linux. Cases in point: IPv6 and USB Visor support, IIRC.

      Pkgsrc is a nice evolution of the ports. It has some neat additional features like a security audit.

      I've said it before: NetBSD gets a bum reputation as being only for obscure hardware. Not so! People alway make the connection that FreeBSD==server, OpenBSD==security and NetBSD==suitable for toaster. I'd posit that NetBSD should be considered for desktops.

      So, give it a shot on your desktops. I think you'll like it.

      -Peter

  8. Mac68K build-from-scratch in emulation? by MarcQuadra · · Score: 3, Interesting

    Alright, I've got a hankering to build 1.6.2 from scratch for my Mac Quadra (25MHz 68040), but I KNOW building the whole thing would take weeks.

    Is there an emulator for my x86 box that would allow me to get this done faster? BasiliskII can emulate my Mac much faster than it really is.

    I'm sure this is a problem on a lot of the 40 architectures, some of them are way old and limited to the sub-100MHz range. Cross-compiling seems like a hairy mess.

    Also, is there a way to build the whole distribution via gcc-3.3.x? I'd like to see how well it performs against the gcc2-built system I used a while ago.

    --
    "Sometimes, I think Trent just needs a cup of hot chocolate and a blankie." -Tori Amos on Nine Inch Nails
    1. Re:Mac68K build-from-scratch in emulation? by JustinXB · · Score: 3, Interesting

      You can cross-compile anything with NetBSD. I've never done, there are some instructions on the website though.

    2. Re:Mac68K build-from-scratch in emulation? by saintlupus · · Score: 3, Interesting

      Alright, I've got a hankering to build 1.6.2 from scratch for my Mac Quadra (25MHz 68040), but I KNOW building the whole thing would take weeks.

      It's really not all that bad. The first Unix box I ever had was a Quadra 700 running NetBSD -- the code base is _really_ tight. You could probably build the whole thing from scratch in a couple of days.

      I know, that might sound like a lot, but it's a hell of a lot faster than a Sparc IPC can compile gcc from source. Don't ask me why I know that.

      --saint

    3. Re:Mac68K build-from-scratch in emulation? by bccomm · · Score: 5, Informative
      Alright, I've got a hankering to build 1.6.2 from scratch for my Mac Quadra (25MHz 68040), but I KNOW building the whole thing would take weeks. Is there an emulator for my x86 box that would allow me to get this done faster? BasiliskII can emulate my Mac much faster than it really is. I'm sure this is a problem on a lot of the 40 architectures, some of them are way old and limited to the sub-100MHz range. Cross-compiling seems like a hairy mess.
      You should be able to cross-compile the entire distribuiton from your x86 box using the build.sh frontend. It seems like it would be messy to build it and copy it over, but it's actually quite easy. The alternative would be to *not* build it yourself and instead just install the binary distribution---there really aren't many benefits of compiling it unless you need a custom kernel or -current sources.
      Also, is there a way to build the whole distribution via gcc-3.3.x? I'd like to see how well it performs against the gcc2-built system I used a while ago.
      The 1.6.x releases use gcc-2.95 for the basis of the toolchain. If you want to try gcc-3.3.x, this may be another reason to look at -current (just yesterday they updated gcc to v3.3.3). Current may be a better choice anyway: its faster, more feature-rich (think native threads), and more widely-used by the community.

      -Bruce
    4. Re:Mac68K build-from-scratch in emulation? by Permission+Denied · · Score: 3, Interesting
      Cross-compiling seems like a hairy mess.

      Cross-compiling not so bad.

      I did exactly this for a slew of old Macs that I turned into useful machines by putting Linux on them. Compiling a 2.2 series Linux kernel would take a few days on the machines themselves, so I set up a cross-compiler on a fast machine.

      The Linux kernel was easy to compile and move over, but userspace things were more difficult to compile as they tried to link to the wrong libraries (or perhaps the problem was that "make install" would never work since the library would end up in /lib on target machine and needed to be configured as such, but it needed to be in /opt/mac-cross/lib on cross compiler machine). Most documentation for setting up cross compilation is aimed at OS/compiler/embedded developers who build mostly static binaries and don't need to compile and link large sources with dependencies like gtk, so I don't know if many people do this.

      I don't remember how I solved this (maybe chroot + hard links + copying stuff from target) so it must not have been too difficult. NetBSD has an nice integrated build system for everything, so this should be much easier for you (Linux was a third choice, NetBSD and OpenBSD had problems on those machines).

      Go ahead and set up the cross compiler. It will take some reading and tweaking, but you'll save time in the end. I, at least, think it's far more elegant than using an emulator. Good luck.

    5. Re:Mac68K build-from-scratch in emulation? by T-Punkt · · Score: 3, Interesting

      > I'm sure this is a problem on a lot of the 40 architectures, some of them are way old and limited
      > to the sub-100MHz range
      Nowadays the release binaries for most platforms except i386 are crosscompiled.

      > Cross-compiling seems like a hairy mess.
      Not with NetBSD (well, most platforms. There may be a few, which are not using the build.sh system).

      Since the NetBSD build process bootstraps by building first a set of tools (make, binutils, compilers etc) and then uses this set to build the system.All you need is a bourne-shell compatible shell and a C/C++ compiler.That's why you can use a - say - solaris/sparc system to compile NetBSD/pmax.See the file BUILDING in the top directory of the source tree.

    6. Re:Mac68K build-from-scratch in emulation? by ChristTrekker · · Score: 1

      I was about to download the 1.6.2 tarballs to update my SE/30. I also wanted to update my gcc installation to 3.3.x for compiling MySQL and some other tools. How stable is -current? Perhaps I should look at that instead.

    7. Re:Mac68K build-from-scratch in emulation? by bccomm · · Score: 1

      -current is usually very reliable. I would suggest that you install a binary snapshot from ftp://releng.netbsd.org first, just to be sure

      -Bruce

    8. Re:Mac68K build-from-scratch in emulation? by ChristTrekker · · Score: 1

      As of right now, it seems the last successful mac68k build was the one on March 3. So that's the snapshot I'd want to download. Is there a list of changes from 1.6.2 posted somewhere, so I can see if this is something I want to do, based on new features/fixes? Or is that something that's only provided with releases?

    9. Re:Mac68K build-from-scratch in emulation? by bccomm · · Score: 1

      I don't believe they make changelogs for current builds. For a general overview of new features, and possibly some insight as to how much work this will be, look at the NetBSD guide, specifically section 2. You may also want to browse the mailing list archives for gotchas.

    10. Re:Mac68K build-from-scratch in emulation? by ChristTrekker · · Score: 1

      I'm subscribed to the mac68k list. Maybe I will ask there if anyone else uses -current and what their experience is.

  9. What's the point? by Anonymous Coward · · Score: -1, Offtopic

    Open source and the BSD license in general are easy models to adopt when banding together to protest the unethical practices of Microsoft, but why give software away for free ALWAYS and FOREVER? Maybe you are a follower? Maybe you want to grow a long beard and be dirty? Does it REALLY make sense?

  10. What We Can Learn From BSD by Anonymous Coward · · Score: -1, Offtopic

    What We Can Learn From BSD
    By Chinese Karma Whore, Version 1.0

    Everyone knows about BSD's failure and imminent demise. As we pore over the history of BSD, we'll uncover a story of fatal mistakes, poor priorities, and personal rivalry, and we'll learn what mistakes to avoid so as to save Linux from a similarly grisly fate.

    Let's not be overly morbid and give BSD credit for its early successes. In the 1970s, Ken Thompson and Bill Joy both made significant contributions to the computing world on the BSD platform. In the 80s, DARPA saw BSD as the premiere open platform, and, after initial successes with the 4.1BSD product, gave the BSD company a 2 year contract.

    These early triumphs would soon be forgotten in a series of internal conflicts that would mar BSD's progress. In 1992, AT&T filed suit against Berkeley Software, claiming that proprietary code agreements had been haphazardly violated. In the same year, BSD filed countersuit, reciprocating bad intentions and fueling internal rivalry. While AT&T and Berkeley Software lawyers battled in court, lead developers of various BSD distributions quarreled on Usenet. In 1995, Theo de Raadt, one of the founders of the NetBSD project, formed his own rival distribution, OpenBSD, as the result of a quarrel that he documents on his website. Mr. de Raadt's stubborn arrogance was later seen in his clash with Darren Reed, which resulted in the expulsion of IPF from the OpenBSD distribution.

    As personal rivalries took precedence over a quality product, BSD's codebase became worse and worse. As we all know, incompatibilities between each BSD distribution make code sharing an arduous task. Research conducted at MIT found BSD's filesystem implementation to be "very poorly performing." Even BSD's acclaimed TCP/IP stack has lagged behind, according to this study.

    Problems with BSD's codebase were compounded by fundamental flaws in the BSD design approach. As argued by Eric Raymond in his watershed essay, The Cathedral and the Bazaar, rapid, decentralized development models are inherently superior to slow, centralized ones in software development. BSD developers never heeded Mr. Raymond's lesson and insisted that centralized models lead to 'cleaner code.' Don't believe their hype - BSD's development model has significantly impaired its progress. Any achievements that BSD managed to make were nullified by the BSD license, which allows corporations and coders alike to reap profits without reciprocating the goodwill of open-source. Fortunately, Linux is not prone to this exploitation, as it is licensed under the GPL.

    The failure of BSD culminated in the resignation of Jordan Hubbard and Michael Smith from the FreeBSD core team. They both believed that FreeBSD had long lost its earlier vitality. Like an empire in decline, BSD had become bureaucratic and stagnant. As Linux gains market share and as BSD sinks deeper into the mire of decay, their parting addresses will resound as fitting eulogies to BSD's demise.

  11. Let's Google Bomb BSD by Anonymous Coward · · Score: -1, Offtopic
  12. SO DOES THIS MEAN *BSD IS FINALLY DEAD FOR GOOD??? by Anonymous Coward · · Score: -1, Troll
  13. Workstation Hardware? by lateefj · · Score: 2

    I am planning on developing some QT applications and using netbsd for the os. I was leaning twards a AMD dual atholon but was wondering if anybody had recommendations for soemthing else (say 64 bit)?

    Links to where to buy would be cool also :)
    THanks.

    --
    Pedro For President!
  14. bittorrent by grbeattie · · Score: 1

    torrents are available for a number of single architecture ISOs and some package and multi-boot ISOs from here.

  15. :P by ChristTrekker · · Score: 0, Offtopic

    2004-03-02 16:26:29 NetBSD 1.6.2 (bsd,news) (rejected)

    No, I'm not bitter. Just confused about slashdot's schizophrenia. But that's nothing new.