Slashdot Mirror

← Back to Stories (view on slashdot.org)

NetBSD Status Report for Oct- Dec '04 Published

Posted by timothy on from the letter-from-summer-camp dept.

Enrique writes "The NetBSD Foundation has published its fourth quarterly status report, covering the months October through December of 2004. Among many other things, this status report covers the publication of the new NetBSD Logo, the new pkgsrc branch, the new NetBSD/iyonix port and of course the release of NetBSD 2.0."

27 comments

  1. New logo by compass46 · · Score: 1

    Is it just me or does anyone else when they see the new NetBSD logo have the urge to go sailing for the America's Cup?

    1. Re:New logo by Anonymous Coward · · Score: 1, Funny

      it's just you, really :)

    2. Re:New logo by BossMC · · Score: 1

      Is it just me or does anyone else when they see the new NetBSD logo have the urge to go sailing for the America's Cup?

      Despite being somewhat of a sailor, I don't share your point of view. I think the NetBSD logo looks more like a pool cue that was rubbed on the table so much that it caught fire. Either way, I think they could have done better.

      Note: This comment isn't offtopic, because the logo is mentioned in the report.

  2. NetBSD has OpenPAM now by TilJ · · Score: 4, Informative

    It seemed like a throwaway line in the status report, and didn't really have any details attached to it. NetBSD getting PAM is big news though -- some of the flame wars between the BSDAuth folks and the PAM folks in the NetBSD community were legendary for their ability to burn unsuspecting posters.

    I found some information at a livejournal posting, but I haven't been able to dig much else up.

    --
    "The purpose of argument is to change the nature of truth." -- Bene Gesserit Precept
    1. Re:NetBSD has OpenPAM now by Homology · · Score: 3, Interesting
      NetBSD getting PAM is big news though -- some of the flame wars between the BSDAuth folks and the PAM folks in the NetBSD community were legendary for their ability to burn unsuspecting posters.

      PAM has had a some exploits. The latest OpenSSH (portable, not OpenbSD) exploit was in the PAM code.

  3. pkgsrc by archen · · Score: 3, Interesting

    According to the report, pkgsrc is now supported in DragonflyBSD. So is DragonFly going to use pkgsrc, ports, or cook up their own solution? I'd guess that since DragonFly is free to be rather experimental that they'll try something new, but I'm sure they'll need to use something else in the mean time.

    1. Re:pkgsrc by Anonymous Coward · · Score: 3, Interesting

      Last time I checked, the Dragonfly folks were planning to cook up their own packaging system. It's sort of a necessity with the way their VFS system is going to work. I figure that they'll end up with something like ports+portupgrade (but smoother operating) with support for multiple versions of programs/libraries being installed at the same time.

    2. Re:pkgsrc by compass46 · · Score: 4, Informative

      Other way around, pkgsrc supports DragonFly. Just as pkgsrc supports FreeBSD but that doesn't imply FreeBSD supports pkgsrc.

      And someone mod the other reply to this up. Whoever modded it down is retarded.

    3. Re:pkgsrc by Homology · · Score: 4, Interesting
      In OpenBSD current there is (alot of) work to enhance the portsystem with a portupdate functionality as well, and hopefully this will be completed before release of OpenBSD 3.7. Looking forward to that functionality.

      As for DragonFly, it's my impression that they want to write their own, but for the moment they piggyback on FreeBSD ports system. I think that DragonFly rejected the other ports systems as inadequate for their needs (in an interview with Dillon).

  4. New logo... by ArbitraryConstant · · Score: 3, Insightful

    The new logo is so neutral and devoid of meaning, so "politically correct" that it says nothing at all about the project. It's not even distinctive enough to be recognized out of context.

    If I see a blowfish, I know it's OpenBSD. If I see Tux, I know it's Linux. But if I saw that damned flag without the word "NetBSD" nearby, there's no way I'd associate it with the project.

    This is why mascots should not be chosen by committee.

    --
    I rarely criticize things I don't care about.
    1. Re:New logo... by Brandybuck · · Score: 4, Insightful

      Tux and Puffy are *mascots* and not *logos*. The new logo is just that, a logo. Logos are not mascots and mascots are not logos. Just because Linux and OpenBSD do not have logos does not mean NetBSD should not have one either.

      --
      Don't blame me, I didn't vote for either of them!
    2. Re:New logo... by MrBoombasticfantasti · · Score: 3, Insightful
      Strictly speaking the NetBSD flag isn't a logo, but an emblem. A proper logo is readable and commonly consists of a brandname in a specific and usually artistic typeface.

      While Tux (as an emblem and/or mascot) is recognized because of gross overexposure in any and all media this is not true of Puffy. Not only does the picture change with every new release (check out the t-shirt page http://www.openbsd.org/tshirts.html) but it isn't quite clear what it stands for if you do not already know.

      I, for one, think the NetBSD flag is quite good. The design is crisp, has upbeat colors and anyway, it's a bloody step forward from that fugly Iwo Jima picture.

      --
      !ERR: Signature not found.