Catch up on stories from the past week (and beyond) at the Slashdot story archive

 


Forgot your password?
Close
typodupeerror
×
Operating Systems Software BSD

NetBSD Status Report for Oct- Dec '04 Published 27

Posted by timothy 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."
This discussion has been archived. No new comments can be posted.

NetBSD Status Report for Oct- Dec '04 Published More

NetBSD Status Report for Oct- Dec '04 Published

Comments Filter:
  • 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?

    • Re:New logo (Score:1, Funny)

      by Anonymous Coward
      it's just you, really :)
    • 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 [backfire.ca], 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.

  • NetBSD has OpenPAM now (Score:5, Informative)

    by TilJ ( 7607 ) on Wednesday January 12, 2005 @09:44AM (#11334688) Homepage
    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 [livejournal.com], but I haven't been able to dig much else up.

    • Re:NetBSD has OpenPAM now (Score:4, Interesting)

      by Homology ( 639438 ) on Wednesday January 12, 2005 @02:05PM (#11338373)
      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.

  • pkgsrc (Score:3, Interesting)

    by archen ( 447353 ) on Wednesday January 12, 2005 @10:45AM (#11335461)
    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.

    • Re:pkgsrc (Score:3, Interesting)

      by Anonymous Coward
      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.

      • Re:pkgsrc (Score:5, Interesting)

        by Homology ( 639438 ) on Wednesday January 12, 2005 @02:11PM (#11338450)
        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).

    • Re:pkgsrc (Score:4, Informative)

      by compass46 ( 259596 ) on Wednesday January 12, 2005 @12:04PM (#11336613)
      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.

  • New logo... (Score:3, Insightful)

    by ArbitraryConstant ( 763964 ) on Wednesday January 12, 2005 @12:30PM (#11337012) Homepage
    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.

    • Re:New logo... (Score:5, Insightful)

      by Brandybuck ( 704397 ) on Wednesday January 12, 2005 @02:38PM (#11338819) Homepage Journal
      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.
      • 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 [openbsd.org]) but it isn't quite clear what it stands for if you do not already know.

        I, for one, thi

Slashdot Top Deals

Order and simplification are the first steps toward mastery of a subject -- the actual enemy is the unknown. -- Thomas Mann

Close