Slashdot Mirror


FreeBSD security Advisories: FreeBSD-SA-03:09.sign

Dan writes "FreeBSD security team has released two new advisories. The first advisory entitled "Insufficient range checking of signal numbers" could allow a malicious local user to use this vulnerability as a local denial-of-service attack. The second advisory "Kernel memory disclosure via ibcs2" could allow a malicious user to call the iBCS2 version of statfs(2) with an arbitrarily large length parameter, causing the kernel to return a large portion of kernel memory containing sensitive information."

78 comments

  1. Here's the text in case it gets /.'ed by DrSkwid · · Score: 4, Informative

    nah, who am I kidding

    the signal thing is more than a D.O.S. though

    However, in FreeBSD 5.x, the assertion code is not present if the
    `INVARIANTS' kernel option is not used. In FreeBSD 5.0-RELEASE and
    5.1-RELEASE, `INVARIANTS' is not enabled by default. In this
    configuration, a malicious local user could use this vulnerability
    to modify kernel memory, potentially leading to complete system
    compromise. (FreeBSD 4.x is not vulnerable in this way.)

    --
    There are places where the networks are not touching,and there are places where they are-Boeing's Lori Gunter
    1. Re:Here's the text in case it gets /.'ed by Anonymous Coward · · Score: -1, Troll
      It is common knowledge that *BSD is dying, that ever hapless *BSD is mired in an irrecoverable and mortifying tangle of fatal trouble. It is perhaps anybody's guess as to which *BSD is the worst off of an admittedly suffering *BSD community. The numbers continue to decline for *BSD but FreeBSD may be hurting the most. Look at the numbers. The loss of user base for FreeBSD continues in a head spinning downward spiral.

      OpenBSD leader Theo states that there are 7000 users of OpenBSD. How many users of BSD are there? Let's see. The number of OpenBSD versus NetBSD posts on Usenet is roughly in ratio of 5 to 1. Therefore there are about 7000/5 = 1400 NetBSD users. BSD/OS posts on Usenet are about half of the volume of NetBSD posts. Therefore there are about 700 users of BSD/OS. A recent article put FreeBSD at about 80 percent of the *BSD market. Therefore there are (7000+1400+700)*4 = 36400 FreeBSD users. This is consistent with the number of FreeBSD Usenet posts.

      Due to the troubles of Walnut Creek, abysmal sales and so on, FreeBSD went out of business and was taken over by BSDI who sell another troubled OS. Now BSDI is also dead, its corpse turned over to yet another charnel house.

      All major marketing surveys show that *BSD has steadily declined in market share. *BSD is extremely sick and its long term survival prospects are very dim. If *BSD is to survive at all it will be among OS hobbyist dilettante dabblers. In truth, for all practical purposes *BSD is already dead. It is a dead man walking.

  2. sensitive information by patch-rustem · · Score: 5, Funny
    ... to return a large portion of kernel memory containing sensitive information.

    What, like the sys admins porn collection.

    --
    Karma: Bad due to google bombing - Robert Watkins woz 'ere.
    1. Re:sensitive information by Anonymous Coward · · Score: -1, Offtopic
      It is mostly common knowledge that *BSD is dying, that ever hapless *BSD is mired in an irrecoverable and mortifying tangle of fatal trouble. It is perhaps anybody's guess as to which *BSD is the worst off of an admittedly suffering *BSD community. The numbers continue to decline for *BSD but FreeBSD may be hurting the most. Look at the numbers. The loss of user base for FreeBSD continues in a head spinning downward spiral.

      OpenBSD leader Theo states that there are 7000 users of OpenBSD. How many users of BSD are there? Let's see. The number of OpenBSD versus NetBSD posts on Usenet is roughly in ratio of 5 to 1. Therefore there are about 7000/5 = 1400 NetBSD users. BSD/OS posts on Usenet are about half of the volume of NetBSD posts. Therefore there are about 700 users of BSD/OS. A recent article put FreeBSD at about 80 percent of the *BSD market. Therefore there are (7000+1400+700)*4 = 36400 FreeBSD users. This is consistent with the number of FreeBSD Usenet posts.

      Due to the troubles of Walnut Creek, abysmal sales and so on, FreeBSD went out of business and was taken over by BSDI who sell another troubled OS. Now BSDI is also dead, its corpse turned over to yet another charnel house.

      All major marketing surveys show that *BSD has steadily declined in market share. *BSD is extremely sick and its long term survival prospects are very dim. If *BSD is to survive at all it will be among hobbyist dilettante dabblers. In truth, for all practical purposes *BSD is already dead. It is a dead man walking.

  3. Bias in topic titles?? Never!! by Anonymous Coward · · Score: 5, Funny

    It's sort of interesting that this FreeBSD vulnerability is headlined with such a cryptic title. Now, if it were a vulnerability in Windows, it would probably have been titled 'New Windows Exploit crushes small furry animals mercilessly.'

  4. Windows Exploit ??News!? Never!! by Anonymous Coward · · Score: 0

    A new windows exploit would not get accepted as a news story.

  5. Re:Bias in topic titles?? Never!! by beefdart · · Score: 2, Informative

    Its not like someone could throw up an ActiveX enabled webpage, and root your box.

    The last few windows vulnerabilities have been a huge deal. Microsoft wouldnt bother to fix a hole this small unless someone made a worm for it.

  6. "Malicious Local User" by Farley+Mullet · · Score: 4, Insightful

    If someone malicious has access to your computer, bad things can happen. It's good to see that the FreeBSD team is tightening things up, but the bottom line is that if someone has an account on a system and they're determined, they'll find a way to do some damage.

    1. Re:"Malicious Local User" by Anonymous Coward · · Score: 1, Insightful

      Given all the big changes they've been making to the kernel, I'm not surprised that they're encountering un-dotted i's and uncrossed t's. That's one of the reasons that OpenBSD is the BSD with the fewest new features apart from those related directly to improving security. Theo is fond of saying that new features create new security holes. I wouldn't be too hard on the folks at FreeBSD though. It is -current they're concentrating on, after all.

  7. dont get it... by BigBadDude · · Score: -1, Flamebait

    I dont get it. Is this Slashdot, or is this Bugtraq??

    Besides, if we start writing about OS vulnerabilities here, it will fill the ./ with mostly windows-related stuff (specially on mondays) and we *ix-geeks dont want that, do we?

    1. Re:dont get it... by Anonymous Coward · · Score: -1, Troll

      "Help! I'm dying and can't get up . . ." -- BSD

  8. freebsd-security mailing list by dodell · · Score: 4, Insightful

    Subscribe to this list, and you had this story about 12 hours ago. You also downloaded and updated your src tree and fixed the bug in a matter of a few minutes. Why is it that a FreeBSD SA makes it to this site and Linux SAs don't?

    1. Re:freebsd-security mailing list by zenyu · · Score: 3, Insightful

      Subscribe to this list, and you had this story about 12 hours ago. You also downloaded and updated your src tree and fixed the bug in a matter of a few minutes. Why is it that a FreeBSD SA makes it to this site and Linux SAs don't?

      Prolly cuz the editor and poster were thinking of "only one remote security breach in the default configuration in seven years" OpenBSD. There are local user exploits found all the time in the Linux distros and in the BSDs, when remote vulnerabilities are found in any of them it usually does make it to /.

      But yeah, I usually read about and check my system based on security advisories before it ever makes it to slashdot.. prolly everyone else does as well which explains the 12 hour lag.

    2. Re:freebsd-security mailing list by kernelistic · · Score: 2, Informative

      It's interesting to note that you need to have shell access to do anything to the FreeBSD systems affected.

    3. Re:freebsd-security mailing list by Anonymous Coward · · Score: -1, Troll

      Elegy for *BSD


      I am a *BSD user
      and I try hard to be brave
      That is a tall order
      *BSD's foot is in the grave.

      I tap at my toy keyboard
      and whistle a happy tune
      but keeping happy's so hard,
      *BSD died so soon.

      Each day I wake and softly sob
      Nightfall finds me crying
      Not only am I a zit faced slob
      but *BSD is dying.

    4. Re:freebsd-security mailing list by Anonymous Coward · · Score: -1, Troll
      Fact: *BSD is dying

      It is common general knowledge that *BSD is dying, that ever hapless *BSD is mired in an irrecoverable and mortifying tangle of fatal trouble. It is perhaps anybody's guess as to which *BSD is the worst off of an admittedly suffering *BSD community. The numbers continue to decline for *BSD but FreeBSD may be hurting the most. Look at the numbers. The loss of user base for FreeBSD continues in a head spinning downward spiral.

      OpenBSD leader Theo states that there are 7000 users of OpenBSD. How many users of BSD are there? Let's see. The number of OpenBSD versus NetBSD posts on Usenet is roughly in ratio of 5 to 1. Therefore there are about 7000/5 = 1400 NetBSD users. BSD/OS posts on Usenet are about half of the volume of NetBSD posts. Therefore there are about 700 users of BSD/OS. A recent article put FreeBSD at about 80 percent of the *BSD market. Therefore there are (7000+1400+700)*4 = 36400 FreeBSD users. This is consistent with the number of FreeBSD Usenet posts.

      Due to the troubles of Walnut Creek, abysmal sales and so on, FreeBSD went out of business and was taken over by BSDI who sell another troubled OS. Now BSDI is also dead, its corpse turned over to yet another charnel house.

      All major marketing surveys show that *BSD has steadily declined in market share. *BSD is extremely sick and its long term survival prospects are very dim. If *BSD is to survive at all it will be among amateur hobbyist dilettante dabblers. In truth, for all practical purposes *BSD is already dead. It is a dead man walking.

      Fact: *BSD is dying

    5. Re:freebsd-security mailing list by Anonymous Coward · · Score: 3, Funny

      Why is it that a FreeBSD SA makes it to this site and Linux SAs don't?

      Because if they reported the Linux SAs, even the SCO stories would be lost the the tidal wave.

    6. Re:freebsd-security mailing list by Anonymous Coward · · Score: -1, Troll
      Fact: *BSD is dying

      It is general knowledge among the populace that *BSD is dying, that ever hapless *BSD is mired in an irrecoverable and mortifying tangle of fatal trouble. It is perhaps anybody's guess as to which *BSD is the worst off of an admittedly suffering *BSD community. The numbers continue to decline for *BSD but FreeBSD may be hurting the most. Look at the numbers. The loss of user base for FreeBSD continues in a head spinning downward spiral.

      OpenBSD leader Theo states that there are 7000 users of OpenBSD. How many users of BSD are there? Let's see. The number of OpenBSD versus NetBSD posts on Usenet is roughly in ratio of 5 to 1. Therefore there are about 7000/5 = 1400 NetBSD users. BSD/OS posts on Usenet are about half of the volume of NetBSD posts. Therefore there are about 700 users of BSD/OS. A recent article put FreeBSD at about 80 percent of the *BSD market. Therefore there are (7000+1400+700)*4 = 36400 FreeBSD users. This is consistent with the number of FreeBSD Usenet posts.

      Due to the troubles of Walnut Creek, abysmal sales and so on, FreeBSD went out of business and was taken over by BSDI who sell another troubled OS. Now BSDI is also dead, its corpse turned over to yet another charnel house.

      All major marketing surveys show that *BSD has steadily declined in market share. *BSD is extremely sick and its long term survival prospects are very dim. If *BSD is to survive at all it will be among OS hobbyist dilettante dabblers. In truth, for all practical purposes *BSD is already dead. It is a dead man walking.

      Fact: *BSD is dying

    7. Re:freebsd-security mailing list by ratfynk · · Score: 1

      As to why, is obvious, and the fact that with MS you do not, will eventually kill most Win servers! MS knows this and is the reason why they are implimenting Paladium, or fritz chip solutions. Make everything that runs on windows servers have traceable and revokeable security certificates. The mother of all shoot yourself in the foot security measures. The next few years are going to be very interesting for free software as alot of important people, especially the big ISPs start to get really pissed at Microsoft! That is if some branch of MS doesn't devour them all first.

      --
      OH THE SHAME I fell off the wagon and use sigs again!
    8. Re:freebsd-security mailing list by Stephen+Samuel · · Score: 1
      Why is it that a FreeBSD SA makes it to this site and Linux SAs don't?
      1. They're fighting to get one BSD story per day. This is today's story.
      2. Like any news -- it's the unusaual that gets the attention. BSD SA's are unusual.
      3. we wanted to get a rise out of you -- we succeeded.
      --
      Free Software: Like love, it grows best when given away.
    9. Re:freebsd-security mailing list by Anonymous Coward · · Score: 0

      And why is that interesting?

    10. Re:freebsd-security mailing list by Anonymous Coward · · Score: 0

      I haven't noticed any SAs for my C64 or AppleII, I guess that means they're the most secure (and therefore best) OS' around!

  9. Malloc(sizeof(ram.total) - sizeof(ram.used)); by mnmn · · Score: 2, Interesting

    I wouldnt worry about ibcs, always compile a kernel without it(and other binary compatibilities) for real usage. The statfs problem looks real and worrisome though. We've seen too many of similar problems where a user grabs large memory and reads the sensitive data.

    I wonder if a C-reading script could read all the source code and mark all the big mallocs/reallocs that users get access to.

    --
    "Give orange me give eat orange me eat orange give me eat orange give me you." -Nim Chimpsky
    1. Re:Malloc(sizeof(ram.total) - sizeof(ram.used)); by phoenix_rizzen · · Score: 2, Informative

      One thing to note about FreeBSD: just because it isn't compiled into the kernel doesn't mean you don't have access to it. Almost everything that is not directly compiled into the kernel is compiled as a module. If you fire up an app that requires ibcs2 support, then the kernel will load the ibcs2.ko kernel module. Any problems with the ibcs2 subsystem will then be in your kernel.

      IOW, you do need to worry about this, and you do need to patch your system.

    2. Re:Malloc(sizeof(ram.total) - sizeof(ram.used)); by mnmn · · Score: 1

      I custom-compile all kernels for the FreeBSD servers and remove everything I dont need, not even as 'option'. I also delete the old modules lying around. I like em lean.

      --
      "Give orange me give eat orange me eat orange give me eat orange give me you." -Nim Chimpsky
    3. Re:Malloc(sizeof(ram.total) - sizeof(ram.used)); by beefdart · · Score: 1

      >Almost everything that is not directly compiled into the kernel is compiled as a module.

      If you dont do your own, custom installs, yes...

    4. Re:Malloc(sizeof(ram.total) - sizeof(ram.used)); by phoenix_rizzen · · Score: 2, Interesting

      How does one disable the building of kernel modules? I've only ever seen the NO_MODULES_WITH_WORLD knob, but nothing to completely disable the building of modules.

    5. Re:Malloc(sizeof(ram.total) - sizeof(ram.used)); by Anonymous Coward · · Score: -1
      I don't want to start a holy war here, but what is the deal with you BSD fanatics? I've been sitting here at my freelance gig in front of a BSD box (a PIII 800 w/512 Megs of RAM) for about 20 minutes now while it attempts to copy a 17 Meg file from one folder on the hard drive to another folder. 20 minutes. At home, on my Pentium Pro 200 running NT 4, which by all standards should be a lot slower than this BSD box, the same operation would take about 2 minutes. If that.

      In addition, during this file transfer, Netscape will not work. And everything else has ground to a halt. Even Emacs Lite is straining to keep up as I type this.

      I won't bore you with the laundry list of other problems that I've encountered while working on various BSD machines, but suffice it to say there have been many, not the least of which is I've never seen a BSD box that has run faster than its Windows counterpart, despite the BSD machine's faster chip architecture. My 486/66 with 8 megs of ram runs faster than this 800 mhz machine at times. From a productivity standpoint, I don't get how people can claim that BSD is a "superior" machine.

      BSD addicts, flame me if you'd like, but I'd rather hear some intelligent reasons why anyone would choose to use a BSD over other faster, cheaper, and more stable systems.

    6. Re:Malloc(sizeof(ram.total) - sizeof(ram.used)); by kernelistic · · Score: 2, Informative

      Read the tunefs(8) and tuning(7) manpages.

      Here's a list of things that you might want to try out:

      - Rethink your slicing, see tuning(7) for more on this.
      - Enable softupdates on the data filesystems of choice.
      - Compile a custom kernel with only the drivers that you *really* need.
      - Tune the VFS sysctls. This item cannot be stressed enough. The values selected depend upon the role of the server.
      - Tune your IP stack. There's a number of sysctls that will quadruple your network throughput. Google has a number of guides which provide good insight.

      Remember: Copying a file from a directory to another is by no means a scientific test, as it depends upon the layout of the disk, sector size, disk cache, and a laundry list of other variables. The output of bonnie++ is what you should use to benchmark your IO subsystem.

    7. Re:Malloc(sizeof(ram.total) - sizeof(ram.used)); by Anonymous Coward · · Score: 0

      Don't reply to this, it's a well-known and much-used troll. At least wait for the trolls with some signs of intelligence to reply. :)

    8. Re:Malloc(sizeof(ram.total) - sizeof(ram.used)); by ffsnjb · · Score: 4, Informative

      uncomment the
      NO_MODULES= true # do not build modules with the kernel

      line in /etc/make.conf

      I don't build modules on my production machines, there is no need. This prevents that.

      --
      "Why do you consent to live in ignorance and fear?" - Bad Religion
    9. Re:Malloc(sizeof(ram.total) - sizeof(ram.used)); by phoenix_rizzen · · Score: 1

      Aha! Learn something new everyday. Thanks. (Don't know how I've missed that, considering how many times I've edited make.conf.)

  10. What We Can Learn From BSD by Anonymous Coward · · Score: -1, Redundant
    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.

    1. Re:What We Can Learn From BSD by beefdart · · Score: 1

      And people like that prove Darwin wrong...

      "I dont hate Linux, just the most of the stupid kiddies who use it"

    2. Re:What We Can Learn From BSD by bsd+troll · · Score: 0

      "I dont hate Linux, just the most of the stupid kiddies who use it"

      Keep up the good fight, work on the grammar.

  11. Binary patches... by cperciva · · Score: 3, Informative

    Binary patches aren't available for these advisories yet, but they will be soon (ETA 12 hours?)

    See my sig for details.

  12. *BSD is dying by Anonymous Coward · · Score: -1, Offtopic
    Fact: *BSD is dying

    It is common knowledge that *BSD is dying, that ever hapless *BSD is mired in an irrecoverable and mortifying tangle of fatal trouble. It is perhaps anybody's guess as to which *BSD is the worst off of an admittedly suffering *BSD community. The numbers continue to decline for *BSD but FreeBSD may be hurting the most. Look at the numbers. The loss of user base for FreeBSD continues in a head spinning downward spiral.

    OpenBSD leader Theo states that there are 7000 users of OpenBSD. How many users of BSD are there? Let's see. The number of OpenBSD versus NetBSD posts on Usenet is roughly in ratio of 5 to 1. Therefore there are about 7000/5 = 1400 NetBSD users. BSD/OS posts on Usenet are about half of the volume of NetBSD posts. Therefore there are about 700 users of BSD/OS. A recent article put FreeBSD at about 80 percent of the *BSD market. Therefore there are (7000+1400+700)*4 = 36400 FreeBSD users. This is consistent with the number of FreeBSD Usenet posts.

    Due to the troubles of Walnut Creek, abysmal sales and so on, FreeBSD went out of business and was taken over by BSDI who sell another troubled OS. Now BSDI is also dead, its corpse turned over to yet another charnel house.

    All major marketing surveys show that *BSD has steadily declined in market share. *BSD is extremely sick and its long term survival prospects are very dim. If *BSD is to survive at all it will be among OS hobbyist dilettante dabblers. In truth, for all practical purposes *BSD is already dead. It is a dead man walking.

    Fact: *BSD is dying

    1. Re:*BSD is dying by beefdart · · Score: 1

      And posts like that prove Darwin wrong...

      "I dont hate Linux, just the most of the stupid kiddies who use it"

    2. Re:*BSD is dying by Anonymous Coward · · Score: -1, Troll
      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.

  13. hot mail security flaw I knew it! by ratfynk · · Score: 2, Funny

    Hmmm so let me get this straight, security flaw 2 send lots of requests to the hot mail server and get lots of core info back. So thats why Hot Mail works the way it does and all we get is spam!

    --
    OH THE SHAME I fell off the wagon and use sigs again!
    1. Re:hot mail security flaw I knew it! by Anonymous Coward · · Score: -1, Troll

      Elegy For *BSD


      I am a *BSD user
      and I try hard to be brave
      That is a tall order
      *BSD's foot is in the grave.

      I tap at my toy keyboard
      and whistle a happy tune
      but keeping happy's so hard,
      *BSD died so soon.

      Each day I wake and softly sob
      Nightfall finds me crying
      Not only am I a zit faced slob
      but *BSD is dying.

  14. Elegy for *BSD by Anonymous Coward · · Score: -1, Troll

    Elegy For *BSD


    I am a *BSD user
    and I try hard to be brave
    That is a tall order
    *BSD's foot is in the grave.

    I tap at my toy keyboard
    and whistle a happy tune
    but keeping happy's so hard,
    *BSD died so soon.

    Each day I wake and softly sob
    Nightfall finds me crying
    Not only am I a zit faced slob
    but *BSD is dying.

  15. The *BSD wailing song.. by Anonymous Coward · · Score: -1, Troll

    What's left for me to see
    In my ship I sailed so far
    What can the answer be
    Don't know what the questions are.
    And after all I've done
    Still I cannot feel the sun
    Tell me save me
    In the end our lost souls must repent.
    I must know it is for certain
    Can it be the final curtain
    As long as the wind will blow
    I'll be searching high and low.
    Who knows what's really true
    They say the end is so near
    Why are we all so cruel
    We just fill ourselves with fear.
    And heaven and hell will turn
    All that we love shall burn
    Hear me trust me
    Inthe end our lost sould must repent.
    I must know it is for certain
    Can it be the final curtain
    As long as the wind will blow
    I'll be searching high and low
    Final curtain
    Final curtain

  16. The Failure of *BSD by Anonymous Coward · · Score: -1, Troll

    The Failure of *BSD

    Of course we can all agree that BSD is a failure, but why did BSD fail Once you get past the fact that BSD is fragmented between a myriad of incompatible kernels, there is the historical record of failure and of failed operating systems. BSD experienced moderate success about 15 years ago in academic circles. Since then it has been in steady decline. We all know BSD keeps losing market share but why Is it the problematic personalities of many of the key players Or is it larger than their troubled personalities
    The record is clear on one thing no operating system has ever come back from the grave. Efforts to resuscitate BSD are one step away from spiritualists wishing to communicate with the dead. As the situation grows more desperate for the adherents of this doomed OS, the sorrow takes hold. An unremitting gloom hangs like a death shroud over a once hopeful BSD community. The hope is gone; a mournful nostalgia has settled in. Now is the end time for BSD.

  17. What We Can Learn From BSD by Anonymous Coward · · Score: -1, Troll
    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 far 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.

  18. BSD problems by Anonymous Coward · · Score: -1, Troll
    I don't want to start a holy war here, but what is the deal with you BSD fanatics? I've been sitting here at my freelance gig in front of a BSD box (a PIII 800 w/512 Megs of RAM) for about 20 minutes now while it attempts to copy a 17 Meg file from one folder on the hard drive to another folder. 20 minutes. At home, on my Pentium Pro 200 running NT 4, which by all standards should be a lot slower than this BSD box, the same operation would take about 2 minutes. If that.

    In addition, during this file transfer, Netscape will not work. And everything else has ground to a halt. Even Emacs Lite is straining to keep up as I type this.

    I won't bore you with the laundry list of other problems that I've encountered while working on various BSD machines, but suffice it to say there have been many, not the least of which is I've never seen a BSD box that has run faster than its Windows counterpart, despite the BSD machine's faster chip architecture. My 486/66 with 8 megs of ram runs faster than this 800 mhz machine at times. From a productivity standpoint, I don't get how people can claim that BSD is a "superior" machine.

    BSD addicts, flame me if you'd like, but I'd rather hear some intelligent reasons why anyone would choose to use a BSD over other faster, cheaper, more stable systems.

    1. Re:BSD problems by beefdart · · Score: 1

      Well first off, no one in there right mind would listen to what you have to say: "Even Emacs Lite is straining to keep up as I type this."
      cause you use Emacs.

      If you have half a brain there is no faster x86 OS than FreeBSD.

      I am not an addict, I just use the best tool out there.

    2. Re:BSD problems by Anonymous Coward · · Score: 0

      Are you gay or something?

    3. Re:BSD problems by Phactorial · · Score: 1

      There wasn't. Now, there is. Please get a clue.

    4. Re:BSD problems by R.Caley · · Score: 1
      I don't want to start a holy war here

      Sure you don't.

      [20 minutes + on a PIII 800 to copy a 17MB file]

      Charitably, you have a machine which is seriously fucked up at the hardware level. Less charitably, you are making it up.

      For comparison, PIII 500, old scavenged (ie slow) disks, 11 seconds to copy a 130MB file between disks, 18 seconds within one disk.

      I have a policy of not tuning my systems, so this is about as slow as it is possible for FBSD to get, without underlying problems. I have no reason to think any of the other BSDs are significantly slower.

      If you really have the problem you claim, I can only think you are either getting huge numbers of recoverable hardware disk errors, or something has eaten all your memory and the system is thrashing wildly.

      --
      _O_
      .|<
      The named which can be named is not the true named
    5. Re:BSD problems by Anonymous Coward · · Score: 0

      [20 minutes + on a PIII 800 to copy a 17MB file]

      Charitably, you have a machine which is seriously fucked up at the hardware level. Less charitably, you are making it up.

      For comparison, PIII 500, old scavenged (ie slow) disks, 11 seconds to copy a 130MB file between disks, 18 seconds within one disk.

      The last time he posted this, I thought it was over the network... but thats still an obscenely slow time even over 10Mbit. I've copied 1GB files off of my old laptop to my old P/166 (its now a P2/350) NetBSD server over 10Mbit *thinnet* and it took less than an hour. Now, admittedly, that was with no other real network traffic, but still... 20 minutes for 17MB?? I'd have to agree, *serious* network problems. Either that or he's quoting the time to send it between machines on a 100Kbit serial cable.

    6. Re:BSD problems by adri · · Score: 1

      Yay, you've been owned by a troll!

    7. Re:BSD problems by Anonymous Coward · · Score: 0
      If you really have the problem you claim, I can only think you are either getting huge numbers of recoverable hardware disk errors, or something has eaten all your memory and the system is thrashing wildly.

      Heh, yeah.
      I had a 300MHz AMD K6-2 with a 4GB Samsung disk that this problem. Thousands of recoverable disk errors. But it still only took about 2mins to copy a 100MB file from one part of the disk to another. I couldn't believe it actually kept working - had debian linux on the box with reiserfs but kept getting corrupted and would refuse to boot. fsck'ing wouldn't help so I blew it away and put FBSD 4.7 on it. Worked for a while until the disk stopped working altogether (wouldn't spin up).

    8. Re:BSD problems by Anonymous Coward · · Score: 0

      Autotroll v0.1 ... just replace the various bits, and troll when ready.

      --------------

      I don't want to start a holy war here, but what is the deal with you <target system> fanatics? I've been sitting here at my freelance gig in front of a <target system> box (a <insanely fast high spec computer>) for about <very long time> now while it attempts to copy a <average size> file from one folder on the hard drive to another folder. <very long time>. At home, on my <old slow clunky computer>, which by all standards should be a lot slower than this <target system> box, the same operation would take about <very short time>. If that.

      In addition, during this file transfer, <random program> will not work. And everything else has ground to a halt. Even <very resource-light program which should work fine> is straining to keep up as I type this.

      I won't bore you with the laundry list of other problems that I've encountered while working on various <target system> machines, but suffice it to say there have been many, not the least of which is I've never seen a <target system> box that has run faster than its <troll's prefered system> counterpart, despite the <target system> machine's faster chip architecture. My <really really slow computer with crap specs> runs faster than this <insanely fast high spec computer> at times. From a productivity standpoint, I don't get how people can claim that <target system> is a "superior" machine.

      <target system> addicts, flame me if you'd like, but I'd rather hear some intelligent reasons why anyone would choose to use a <target system> over other faster, cheaper, more stable systems.

      --------------

  19. Re:Bias in topic titles?? Never!! by Anonymous Coward · · Score: -1, Offtopic
    Fact: *BSD is dying

    It is common knowledge that *BSD is dying, that ever hapless *BSD is mired in an irrecoverable and mortifying tangle of fatal trouble. It is perhaps anybody's guess as to which *BSD is the worst off of an admittedly suffering *BSD community. The numbers continue to decline for *BSD but FreeBSD may be hurting the most. Look at the numbers. The loss of user base for FreeBSD continues in a head spinning downward spiral.

    OpenBSD leader Theo states that there are 7000 users of OpenBSD. How many users of BSD are there? Let's see. The number of OpenBSD versus NetBSD posts on Usenet is roughly in ratio of 5 to 1. Therefore there are about 7000/5 = 1400 NetBSD users. BSD/OS posts on Usenet are about half of the volume of NetBSD posts. Therefore there are about 700 users of BSD/OS. A recent article put FreeBSD at about 80 percent of the *BSD market. Therefore there are (7000+1400+700)*4 = 36400 FreeBSD users. This is consistent with the number of FreeBSD Usenet posts.

    Due to the troubles of Walnut Creek, abysmal sales and so on, FreeBSD went out of business and was taken over by BSDI who sell another troubled OS. Now BSDI is also dead, its corpse turned over to yet another charnel house.

    All major marketing surveys show that *BSD has steadily declined in market share. *BSD is extremely sick and its long term survival prospects are very dim. If *BSD is to survive at all it will be among OS hobbyist dilettante dabblers. In truth, for all practical purposes *BSD is already dead. It is a dead man walking

  20. *BSD is dying by Anonymous Coward · · Score: -1, Troll
    Fact: *BSD is dying

    It is common knowledge that *BSD is dying, that ever hapless *BSD is mired in an irrecoverable and mortifying tangle of fatal trouble. It is perhaps anybody's guess as to which *BSD is the worst off of an admittedly suffering *BSD community. The numbers continue to decline for *BSD but FreeBSD may be hurting the most. Look at the numbers. The loss of user base for FreeBSD continues in a head spinning downward spiral.

    OpenBSD leader Theo states that there are 7000 users of OpenBSD. How many users of BSD are there? Let's see. The number of OpenBSD versus NetBSD posts on Usenet is roughly in ratio of 5 to 1. Therefore there are about 7000/5 = 1400 NetBSD users. BSD/OS posts on Usenet are about half of the volume of NetBSD posts. Therefore there are about 700 users of BSD/OS. A recent article put FreeBSD at about 80 percent of the *BSD market. Therefore there are (7000+1400+700)*4 = 36400 FreeBSD users. This is consistent with the number of FreeBSD Usenet posts.

    Due to the troubles of Walnut Creek, abysmal sales and so on, FreeBSD went out of business and was taken over by BSDI who sell another troubled OS. Now BSDI is also dead, its corpse turned over to yet another charnel house.

    All major marketing surveys show that *BSD has steadily declined in market share. *BSD is extremely sick and its long term survival prospects are very dim. If *BSD is to survive at all it will be among amateur dilettante dabblers. In truth, for all practical purposes *BSD is already dead. It is a dead man walking.

    Fact: *BSD is dying

  21. Re:Bias in topic titles?? Never!! by Anonymous Coward · · Score: -1, Troll

    Let me make this simple for you: *BSD is dying

  22. New virus is hitting hard by Anonymous Coward · · Score: -1, Offtopic
    All,

    Here a scoop to BSDers which is just now hitting us security pro's.
    <P> There is a first vulnerability that uses the MS Bug that MS addressed
    with MS 03-026 two weeks ago. <P> It is calling itself
    <a href="http://isc.sans.org/diary.html?date=2003-08- 11">MSBLAST.exe</a>
    and is spreading in the wild unbelievably fast.
    <P> A first advisory from McAffee has just been published --
    <a href="http://us.mcafee.com/virusInfo/defa...&virus _k=100547">virusInfo</a>
    Once it finds a vulnerable system, it will spawn a shell on port
    4444 and use it to download the actual worm via tftp. The exploit itself
    is very close to 'dcom.c' and so far appears to use
    the "universal Win2k" offset only. <P>
    In other words we need to make sure port 4444 is blocked inbound AND outbound.
    <P> Of course this is in addition to the MS03-026 patch being installed which
    Microsoft released two weeks ago (more info regarding the patch here --
    <a href="http://www.microsoft.com/technet/tr...n/MS03 -026.asp">
    MS03-026.asp</a>. <P> Another advisory was JUST posted by Symantec:
    <a href="http://www.symantec.com/avcenter/ve...aster. worm.html">worm</a>
    <P> Just thought everyone ought to know. <P> Thanks...

    1. Re:New virus is hitting hard by beefdart · · Score: 0, Offtopic

      I hate people...

  23. Linux is dying by cozman69 · · Score: 1, Funny

    Linux is dead. Long live BSD.

  24. Elegy for BSD by Anonymous Coward · · Score: -1, Flamebait

    Elegy For *BSD


    I am a *BSD user
    and I try hard to be brave
    That is a tall order,
    *BSD's foot is in the grave.

    I tap at my toy keyboard
    and whistle a happy tune
    but keeping happy's so hard,
    *BSD died so soon.

    Each day I wake and softly sob
    Nightfall finds me crying
    Not only am I a zit faced slob
    but *BSD is dying.

  25. A psychologist's guide for saddened *BSD users 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.
  26. BSD from the hood, my niggas (props to GNAA) by Anonymous Coward · · Score: -1, Troll


    BSD you grow in the ghetto, living second rate
    And your eyes will sing a song of deep hate.
    The places you play and where you stay
    Looks like one great big alley way.
    You'll admire all the numberbook takers,
    Thugs, BSD pimps and pushers, and the big money makers.

  27. this bitch is dead sucka by Anonymous Coward · · Score: -1, Flamebait

    see subject line

  28. *BSD IS DYING by Anonymous Coward · · Score: -1, Troll
    It is now official - Netcraft has confirmed: *BSD is dying

    Yet another crippling bombshell hit the beleaguered *BSD community when recently IDC confirmed that *BSD accounts for less than a fraction of 1 percent of all servers. Coming on the heels of the latest Netcraft survey which plainly states that *BSD has lost more market share, this news serves to reinforce what we've known all along. *BSD is collapsing in complete disarray, as fittingly exemplified by failing dead last [samag.com] in the recent Sys Admin comprehensive networking test.

    You don't need to be a Kreskin [amazingkreskin.com] to predict *BSD's future. The hand writing is on the wall: *BSD faces a bleak future. In fact there won't be any future at all for *BSD because *BSD is dying. Things are looking very bad for *BSD. As many of us are already aware, *BSD continues to lose market share. Red ink flows like a river of blood. FreeBSD is the most endangered of them all, having lost 9314763f its core developers. The sudden and unpleasant departures of long time FreeBSD developers Jordan Hubbard and Mike Smith only serve to underscore the point more clearly. There can no longer be any doubt: FreeBSD is dying.

    Let's keep to the facts and look at the numbers.

    OpenBSD leader Theo states that there are 7000 users of OpenBSD. How many users of NetBSD are there? Let's see. The number of OpenBSD versus NetBSD posts on Usenet is roughly in ratio of 5 to 1. Therefore there are about 7000/5 = 1400 NetBSD users. BSD/OS posts on Usenet are about half of the volume of NetBSD posts. Therefore there are about 700 users of BSD/OS. A recent article put FreeBSD at about 80 percent of the *BSD market. Therefore there are (7000+1400+700)*4 = 36400 FreeBSD users. This is consistent with the number of FreeBSD Usenet posts.

    Due to the troubles of Walnut Creek, abysmal sales and so on, FreeBSD went out of business and was taken over by BSDI who sell another troubled OS. Now BSDI is also dead, its corpse turned over to yet another charnel house.

    All major surveys show that *BSD has steadily declined in market share. *BSD is very sick and its long term survival prospects are very dim. If *BSD is to survive at all it will be among OS hobbyist dabblers. *BSD continues to decay. Nothing short of a miracle could save it at this point in time. For all practical purposes, *BSD is dead.

    Fact: *BSD is dead

    0

  29. *BSD IS DYING by Anonymous Coward · · Score: -1, Flamebait
    It is now official - Netcraft has confirmed: *BSD is dying

    Yet another crippling bombshell hit the beleaguered *BSD community when recently IDC confirmed that *BSD accounts for less than a fraction of 1 percent of all servers. Coming on the heels of the latest Netcraft survey which plainly states that *BSD has lost more market share, this news serves to reinforce what we've known all along. *BSD is collapsing in complete disarray, as fittingly exemplified by failing dead last [samag.com] in the recent Sys Admin comprehensive networking test.

    You don't need to be a Kreskin [amazingkreskin.com] to predict *BSD's future. The hand writing is on the wall: *BSD faces a bleak future. In fact there won't be any future at all for *BSD because *BSD is dying. Things are looking very bad for *BSD. As many of us are already aware, *BSD continues to lose market share. Red ink flows like a river of blood. FreeBSD is the most endangered of them all, having lost 9330373f its core developers. The sudden and unpleasant departures of long time FreeBSD developers Jordan Hubbard and Mike Smith only serve to underscore the point more clearly. There can no longer be any doubt: FreeBSD is dying.

    Let's keep to the facts and look at the numbers.

    OpenBSD leader Theo states that there are 7000 users of OpenBSD. How many users of NetBSD are there? Let's see. The number of OpenBSD versus NetBSD posts on Usenet is roughly in ratio of 5 to 1. Therefore there are about 7000/5 = 1400 NetBSD users. BSD/OS posts on Usenet are about half of the volume of NetBSD posts. Therefore there are about 700 users of BSD/OS. A recent article put FreeBSD at about 80 percent of the *BSD market. Therefore there are (7000+1400+700)*4 = 36400 FreeBSD users. This is consistent with the number of FreeBSD Usenet posts.

    Due to the troubles of Walnut Creek, abysmal sales and so on, FreeBSD went out of business and was taken over by BSDI who sell another troubled OS. Now BSDI is also dead, its corpse turned over to yet another charnel house.

    All major surveys show that *BSD has steadily declined in market share. *BSD is very sick and its long term survival prospects are very dim. If *BSD is to survive at all it will be among OS hobbyist dabblers. *BSD continues to decay. Nothing short of a miracle could save it at this point in time. For all practical purposes, *BSD is dead.

    Fact: *BSD is dead

    0

  30. *BSD IS DYING by Anonymous Coward · · Score: -1, Flamebait
    It is now official - Netcraft has confirmed: *BSD is dying

    Yet another crippling bombshell hit the beleaguered *BSD community when recently IDC confirmed that *BSD accounts for less than a fraction of 1 percent of all servers. Coming on the heels of the latest Netcraft survey which plainly states that *BSD has lost more market share, this news serves to reinforce what we've known all along. *BSD is collapsing in complete disarray, as fittingly exemplified by failing dead last [samag.com] in the recent Sys Admin comprehensive networking test.

    You don't need to be a Kreskin [amazingkreskin.com] to predict *BSD's future. The hand writing is on the wall: *BSD faces a bleak future. In fact there won't be any future at all for *BSD because *BSD is dying. Things are looking very bad for *BSD. As many of us are already aware, *BSD continues to lose market share. Red ink flows like a river of blood. FreeBSD is the most endangered of them all, having lost 9311601f its core developers. The sudden and unpleasant departures of long time FreeBSD developers Jordan Hubbard and Mike Smith only serve to underscore the point more clearly. There can no longer be any doubt: FreeBSD is dying.

    Let's keep to the facts and look at the numbers.

    OpenBSD leader Theo states that there are 7000 users of OpenBSD. How many users of NetBSD are there? Let's see. The number of OpenBSD versus NetBSD posts on Usenet is roughly in ratio of 5 to 1. Therefore there are about 7000/5 = 1400 NetBSD users. BSD/OS posts on Usenet are about half of the volume of NetBSD posts. Therefore there are about 700 users of BSD/OS. A recent article put FreeBSD at about 80 percent of the *BSD market. Therefore there are (7000+1400+700)*4 = 36400 FreeBSD users. This is consistent with the number of FreeBSD Usenet posts.

    Due to the troubles of Walnut Creek, abysmal sales and so on, FreeBSD went out of business and was taken over by BSDI who sell another troubled OS. Now BSDI is also dead, its corpse turned over to yet another charnel house.

    All major surveys show that *BSD has steadily declined in market share. *BSD is very sick and its long term survival prospects are very dim. If *BSD is to survive at all it will be among OS hobbyist dabblers. *BSD continues to decay. Nothing short of a miracle could save it at this point in time. For all practical purposes, *BSD is dead.

    Fact: *BSD is dead

    0

  31. *BSD IS DYING by Anonymous Coward · · Score: -1, Troll
    It is now official - Netcraft has confirmed: *BSD is dying

    Yet another crippling bombshell hit the beleaguered *BSD community when recently IDC confirmed that *BSD accounts for less than a fraction of 1 percent of all servers. Coming on the heels of the latest Netcraft survey which plainly states that *BSD has lost more market share, this news serves to reinforce what we've known all along. *BSD is collapsing in complete disarray, as fittingly exemplified by failing dead last [samag.com] in the recent Sys Admin comprehensive networking test.

    You don't need to be a Kreskin [amazingkreskin.com] to predict *BSD's future. The hand writing is on the wall: *BSD faces a bleak future. In fact there won't be any future at all for *BSD because *BSD is dying. Things are looking very bad for *BSD. As many of us are already aware, *BSD continues to lose market share. Red ink flows like a river of blood. FreeBSD is the most endangered of them all, having lost 9313641f its core developers. The sudden and unpleasant departures of long time FreeBSD developers Jordan Hubbard and Mike Smith only serve to underscore the point more clearly. There can no longer be any doubt: FreeBSD is dying.

    Let's keep to the facts and look at the numbers.

    OpenBSD leader Theo states that there are 7000 users of OpenBSD. How many users of NetBSD are there? Let's see. The number of OpenBSD versus NetBSD posts on Usenet is roughly in ratio of 5 to 1. Therefore there are about 7000/5 = 1400 NetBSD users. BSD/OS posts on Usenet are about half of the volume of NetBSD posts. Therefore there are about 700 users of BSD/OS. A recent article put FreeBSD at about 80 percent of the *BSD market. Therefore there are (7000+1400+700)*4 = 36400 FreeBSD users. This is consistent with the number of FreeBSD Usenet posts.

    Due to the troubles of Walnut Creek, abysmal sales and so on, FreeBSD went out of business and was taken over by BSDI who sell another troubled OS. Now BSDI is also dead, its corpse turned over to yet another charnel house.

    All major surveys show that *BSD has steadily declined in market share. *BSD is very sick and its long term survival prospects are very dim. If *BSD is to survive at all it will be among OS hobbyist dabblers. *BSD continues to decay. Nothing short of a miracle could save it at this point in time. For all practical purposes, *BSD is dead.

    Fact: *BSD is dead

    0

  32. *BSD IS DYING by Anonymous Coward · · Score: -1, Troll
    It is now official - Netcraft has confirmed: *BSD is dying

    Yet another crippling bombshell hit the beleaguered *BSD community when recently IDC confirmed that *BSD accounts for less than a fraction of 1 percent of all servers. Coming on the heels of the latest Netcraft survey which plainly states that *BSD has lost more market share, this news serves to reinforce what we've known all along. *BSD is collapsing in complete disarray, as fittingly exemplified by failing dead last [samag.com] in the recent Sys Admin comprehensive networking test.

    You don't need to be a Kreskin [amazingkreskin.com] to predict *BSD's future. The hand writing is on the wall: *BSD faces a bleak future. In fact there won't be any future at all for *BSD because *BSD is dying. Things are looking very bad for *BSD. As many of us are already aware, *BSD continues to lose market share. Red ink flows like a river of blood. FreeBSD is the most endangered of them all, having lost 9322414f its core developers. The sudden and unpleasant departures of long time FreeBSD developers Jordan Hubbard and Mike Smith only serve to underscore the point more clearly. There can no longer be any doubt: FreeBSD is dying.

    Let's keep to the facts and look at the numbers.

    OpenBSD leader Theo states that there are 7000 users of OpenBSD. How many users of NetBSD are there? Let's see. The number of OpenBSD versus NetBSD posts on Usenet is roughly in ratio of 5 to 1. Therefore there are about 7000/5 = 1400 NetBSD users. BSD/OS posts on Usenet are about half of the volume of NetBSD posts. Therefore there are about 700 users of BSD/OS. A recent article put FreeBSD at about 80 percent of the *BSD market. Therefore there are (7000+1400+700)*4 = 36400 FreeBSD users. This is consistent with the number of FreeBSD Usenet posts.

    Due to the troubles of Walnut Creek, abysmal sales and so on, FreeBSD went out of business and was taken over by BSDI who sell another troubled OS. Now BSDI is also dead, its corpse turned over to yet another charnel house.

    All major surveys show that *BSD has steadily declined in market share. *BSD is very sick and its long term survival prospects are very dim. If *BSD is to survive at all it will be among OS hobbyist dabblers. *BSD continues to decay. Nothing short of a miracle could save it at this point in time. For all practical purposes, *BSD is dead.

    Fact: *BSD is dead

    0

  33. *BSD IS DYING by Anonymous Coward · · Score: -1, Troll
    It is now official - Netcraft has confirmed: *BSD is dying

    Yet another crippling bombshell hit the beleaguered *BSD community when recently IDC confirmed that *BSD accounts for less than a fraction of 1 percent of all servers. Coming on the heels of the latest Netcraft survey which plainly states that *BSD has lost more market share, this news serves to reinforce what we've known all along. *BSD is collapsing in complete disarray, as fittingly exemplified by failing dead last [samag.com] in the recent Sys Admin comprehensive networking test.

    You don't need to be a Kreskin [amazingkreskin.com] to predict *BSD's future. The hand writing is on the wall: *BSD faces a bleak future. In fact there won't be any future at all for *BSD because *BSD is dying. Things are looking very bad for *BSD. As many of us are already aware, *BSD continues to lose market share. Red ink flows like a river of blood. FreeBSD is the most endangered of them all, having lost 9363720f its core developers. The sudden and unpleasant departures of long time FreeBSD developers Jordan Hubbard and Mike Smith only serve to underscore the point more clearly. There can no longer be any doubt: FreeBSD is dying.

    Let's keep to the facts and look at the numbers.

    OpenBSD leader Theo states that there are 7000 users of OpenBSD. How many users of NetBSD are there? Let's see. The number of OpenBSD versus NetBSD posts on Usenet is roughly in ratio of 5 to 1. Therefore there are about 7000/5 = 1400 NetBSD users. BSD/OS posts on Usenet are about half of the volume of NetBSD posts. Therefore there are about 700 users of BSD/OS. A recent article put FreeBSD at about 80 percent of the *BSD market. Therefore there are (7000+1400+700)*4 = 36400 FreeBSD users. This is consistent with the number of FreeBSD Usenet posts.

    Due to the troubles of Walnut Creek, abysmal sales and so on, FreeBSD went out of business and was taken over by BSDI who sell another troubled OS. Now BSDI is also dead, its corpse turned over to yet another charnel house.

    All major surveys show that *BSD has steadily declined in market share. *BSD is very sick and its long term survival prospects are very dim. If *BSD is to survive at all it will be among OS hobbyist dabblers. *BSD continues to decay. Nothing short of a miracle could save it at this point in time. For all practical purposes, *BSD is dead.

    Fact: *BSD is dead

    0

  34. *BSD IS DYING by Anonymous Coward · · Score: -1, Troll
    It is now official - Netcraft has confirmed: *BSD is dying

    Yet another crippling bombshell hit the beleaguered *BSD community when recently IDC confirmed that *BSD accounts for less than a fraction of 1 percent of all servers. Coming on the heels of the latest Netcraft survey which plainly states that *BSD has lost more market share, this news serves to reinforce what we've known all along. *BSD is collapsing in complete disarray, as fittingly exemplified by failing dead last [samag.com] in the recent Sys Admin comprehensive networking test.

    You don't need to be a Kreskin [amazingkreskin.com] to predict *BSD's future. The hand writing is on the wall: *BSD faces a bleak future. In fact there won't be any future at all for *BSD because *BSD is dying. Things are looking very bad for *BSD. As many of us are already aware, *BSD continues to lose market share. Red ink flows like a river of blood. FreeBSD is the most endangered of them all, having lost 9362434f its core developers. The sudden and unpleasant departures of long time FreeBSD developers Jordan Hubbard and Mike Smith only serve to underscore the point more clearly. There can no longer be any doubt: FreeBSD is dying.

    Let's keep to the facts and look at the numbers.

    OpenBSD leader Theo states that there are 7000 users of OpenBSD. How many users of NetBSD are there? Let's see. The number of OpenBSD versus NetBSD posts on Usenet is roughly in ratio of 5 to 1. Therefore there are about 7000/5 = 1400 NetBSD users. BSD/OS posts on Usenet are about half of the volume of NetBSD posts. Therefore there are about 700 users of BSD/OS. A recent article put FreeBSD at about 80 percent of the *BSD market. Therefore there are (7000+1400+700)*4 = 36400 FreeBSD users. This is consistent with the number of FreeBSD Usenet posts.

    Due to the troubles of Walnut Creek, abysmal sales and so on, FreeBSD went out of business and was taken over by BSDI who sell another troubled OS. Now BSDI is also dead, its corpse turned over to yet another charnel house.

    All major surveys show that *BSD has steadily declined in market share. *BSD is very sick and its long term survival prospects are very dim. If *BSD is to survive at all it will be among OS hobbyist dabblers. *BSD continues to decay. Nothing short of a miracle could save it at this point in time. For all practical purposes, *BSD is dead.

    Fact: *BSD is dead

    0

  35. *BSD we will miss you ... by Anonymous Coward · · Score: -1, Flamebait

    Would you know my name
    If I saw you in heaven?
    Would you feel the same
    If I saw you in heaven?
    I must be strong and carry on
    'cause I know I don't belong here in heaven...

    Would you hold my hand
    If I saw you in heaven?
    Would you help me stand
    If I saw you in heaven?
    I'll find my way through night and day
    'cause I know I just can't stay here in heaven...

    Time can bring you down, time can bend your knees
    Time can break your heart, have you begging please...begging please

    Beyond the door there's peace I'm sure
    And I know there'll be no more tears in heaven...

    Would you know my name
    If I saw you in heaven?
    Would you feel the same
    If I saw you in heaven?
    I must be strong and carry on
    'cause I know I don't belong here in heaven...

  36. The Failure of *BSD by Anonymous Coward · · Score: -1, Troll

    The Failure of *BSD

    Of course we can all agree that BSD is a failure, but why did BSD fail Once you get past the fact that BSD is fragmented between a myriad of incompatible kernels, there is the historical record of failure and of failed operating systems. BSD experienced moderate success about 15 years ago in academic circles. Since then it has been in steady decline. We all know BSD keeps losing market share but why Is it the problematic personalities of many of the key players Or is it larger than their troubled personalities
    The record is clear on one thing no operating system has ever come back from the grave. Efforts to resuscitate BSD are one step away from spiritualists wishing to communicate with the dead. As the situation grows more desperate for the adherents of this doomed OS, the sorrow takes hold. An unremitting gloom hangs like a death shroud over a once hopeful BSD community. The hope is gone; a mournful nostalgia has settled in. Now is the end time for BSD.

  37. Giving Credit where it is due. by Anonymous Coward · · Score: 0

    Silvio Cesare found this long ago, and the crack security team at FreeBSD *just* got around to doing an advisory. Here is the original finding
    http://www.ruxcon.org/post-con/slides/a2. tgz

  38. *BSD wont work? by Anonymous Coward · · Score: -1, Flamebait


    I don't want to start a holy war here, but what is the deal with you BSD fanatics? I've been sitting here at my freelance gig in front of a BSD box (a PIII 800 w/512 Megs of RAM) for about 20 minutes now while it attempts to copy a 17 Meg file from one folder on the hard drive to another folder. 20 minutes. At home, on my Pentium Pro 200 running NT 4, which by all standards should be a lot slower than this BSD box, the same operation would take about 2 minutes. If that.
    In addition, during this file transfer, Netscape will not work. And everything else has ground to a halt. Even Emacs Lite is straining to keep up as I type this.

    I won't bore you with the laundry list of other problems that I've encountered while working on various BSD machines, but suffice it to say there have been many, not the least of which is I've never seen a BSD box that has run faster than its Windows counterpart, despite the BSD machines faster chip architecture. My 486/66 with 8 megs of ram runs faster than this 800 mhz machine at times. From a productivity standpoint, I don't get how people can claim that BSD is a "superior" machine.

    BSD addicts, flame me if you'd like, but I'd rather hear some intelligent reasons why anyone would choose to use a BSD over other faster, cheaper, more stable systems.

    1. Re:*BSD wont work? by Anonymous Coward · · Score: 0

      I don't want to start a holy war here,

      Your claims have already been answered the last time you posted.

      Given you've reposted the same claim a 2nd time, you either can't understand English (or what passes for such on slashdot) or you ARE 'looking to start a holy war'.

    2. Re:*BSD wont work? by Anonymous Coward · · Score: -1, Troll

      Excuse me sir? When was the "last time" I posted?

      This is exactly why I cannot tolerate the BSD community. A bunch of pompous assholes who get their panties in a bunch when you point out obvious problems with BSD.

  39. He's dead Jim by Anonymous Coward · · Score: -1, Troll

    _d8b____________________d8b_______d8,
    _?88____________________88P______`8P
    __88b__________________d88
    __888888b__.d888b,_d888888________88b_.d888b,
    __88P_`?8b_?8b,___d8P'_?88________88P_?8b,
    _d88,__d88___`?8b_88b__,88b______d88____`?8b
    d88'`?88P'`?888P'_`?88P'`88b____d88'_`?888P'

    ______d8b________________________d8b
    ______88P________________________88P
    _____d88________________________d88
    _d888888___d8888b_d888b8b___d888888
    d8P'_?88__d8b_,dPd8P'_?88__d8P'_?88
    88b__,88b_88b____88b__,88b_88b__,88b
    `?88P'`88b`?888P'`?88P'`88b`?88P'`88b