Slashdot Mirror


IRC Forum with Matthew Dillon of DragonFly BSD

weebl writes "Thursday October 9th at 6:00PM PDT (9PM EDT/1AM GMT) SlashNET's #forum channel will be hosting a Q&A session with Matthew Dillon of the DragonFly BSD Project. This is your opportunity to ask about DragonFly BSD, BSD in general, or any other questions you might have for him. DragonFly BSD was first announced this past July." If you can't make it to the forum, SlashNET will have a bot running earlier in the day for question submissions, and logs available afterward.

223 comments

  1. Owned by SCO by Anonymous Coward · · Score: -1, Flamebait

    Its the truth and you know it. Hope you've got $699 sitting around.

    1. Re:Owned by SCO by Anonymous Coward · · Score: 0, Offtopic

      SCO isnt a very nice company. I would classify their attempts to extract funds from the Linux community as "crappy"....also, I believe them to have alterior motives

    2. Re:Owned by SCO by Anonymous Coward · · Score: -1, Troll

      "ulterior"







      fucker

    3. Re:Owned by SCO by Anonymous Coward · · Score: 0

      "posterior"

      ass

    4. Re:Owned by SCO by Anonymous Coward · · Score: 0

      That was a sweet putdown on so many levels. Still laughing...

    5. Re:Owned by SCO by Anonymous Coward · · Score: -1, Offtopic

      Anterior











      You Cruciate Ligament

    6. Re:Owned by SCO by Anonymous Coward · · Score: 0

      You are confused. You want the Linux 'blogs. This is the BSD section.

      BSD reached a settlement over IP improperly released to the public at large.

    7. Re:Owned by SCO by Anonymous Coward · · Score: 0

      Oh come on, this one is actually funny

    8. Re:Owned by SCO by m.dillon · · Score: 2, Interesting
      Which, very soon now, will hopefully bite SCO in the ass. It's hard to justify significant damages (or any damages at all) for a measily 200 lines of potentially 'stolen' code (SysV->Linux) when all 200 lines have either already been put in the public domain or are obsolete versions of things which ALREADY have equivalent or better functionality in the BSD codepath (the key being that the BSD codepath is completely protected from SCO's foolishness due to the USL lawsuit that AT&T lost).

      I've seen companies go down this road before. In many respects it is a holdover from the pre-internet days (or the pre-widely-dissemenated-internet days), where companies could obfuscate facts and possibly succeed in their absurdities simply due to a lack of collaboration and coordination by their opponents. But in the age of the internet, the truth becomes viral and companies like SCO and VeriSign have a much harder time playing the system.

      This isn't to say that the Media has clued in yet. Up until recently SCO got only glowing reports from investment media sources and research, primarily because most media and research sources simply parrot official press releases from the company and the open-source community has no 'official' source. But even the total idiots writing the glowing press articles are finally clueing into SCO's criminality. Not enough of them, yet, but the tide is turning.

      -Matt

  2. Change the name/logo! by michaelhood · · Score: -1, Offtopic

    Please? I'm fp. Does that count for anything?

  3. Rarr! by Anonymous Coward · · Score: -1, Troll

    Eye yam da TR0LL!!!111!!1!!!

    b0vv b4 m33333111!!!!1!

  4. On *BSD's Tombstone: by Anonymous Coward · · Score: -1, Troll

    "Do not stand at my hard disk and forever weep.
    I am not there; I do not sleep.
    I am a thousand winds that blow.
    I am the diamond glints on snow.
    I am the sunlight on ripened grain.
    I am the gentle autumn's rain.
    When you reboot in the morning's hush
    I am the swift uplifting rush
    Of quiet birds in circled flight.
    I am the soft stars that shine at night.
    Do not stand at my hard disk and forever cry.
    I am not there. "

    1. Re:On *BSD's Tombstone: by AvengerXP · · Score: 0, Offtopic

      Might be a troll but you have to admit it's pretty nice.

      --
      Trolls dont like to be Flamebait, because they burn so well. Protect our Troll heritage!
    2. Re:On *BSD's Tombstone: by Anonymous Coward · · Score: -1, Troll

      "Ford," he said suddenly, "look, if that Question is printed in my brain wave patterns but I'm not consciously aware of it it must be somewhere in my unconscious."
      "Yes, I suppose so," said Ford. "Well," said Arthur, "there might be a way of bringing that unconscious pattern forward."
      "Oh yes?" he asked. "Yes, by introducing some random element that can be shaped by that pattern."
      "Like how?" Arthur answered: "Like by pulling Scrabble letters out of a bag blindfolded."
      Ford leapt to his feet. "Brilliant!" he said. He tugged his towel out of his satchel and with a few deft knots transformed it into a bag.
      "Totally mad," he said, "utter nonsense. But we'll do it because it's brilliant nonsense. Come on, come on."
      The sun passed respectfully behind a cloud. A few small sad raindrops fell.
      They piled together all the remaining letters and dropped them into the bag. They shook them up.
      "Right," said Ford, "close your eyes. Pull them out. Come on come on, come on."
      Arthur closed his eyes and plunged his hand into the towelful of stones. He jiggled them about, pulled out four and handed them to Ford. Ford laid them along the ground in the order he got them.
      "F," said Ford, "A, C, T ... Fact!" He blinked. "I think it's working!" he said. Arthur pushed three more at him.
      "B, S, D ... Bee-Ess-Dee. Oh perhaps it isn't working," said Ford.
      "Here's the next three."
      "I, S, D ... Bsdisd? ... It's not making sense I'm afraid." Arthur pulled another two from the bag. Ford put them in place.
      "Y, I, Bsdisdy? Hmmm..." wondered Ford, "is it working?"
      "More here." Arthur was throwing them out feverishly as fast as he could go.
      "I, N," said Ford, "G." He paused. "Come on, where's the next one?"
      "Er, that's the lot," said Arthur, "that's all there were."
      He sat back, nonplussed. He rooted around again in the knotted up towel but there were no more letters.
      "You mean that's it?" said Ford.
      "That's it."
      "Fact. B.S.D.I.S.D.Y.I.N.G."
      "Fact: BSD Is Dying...?"
      "That's it. That's all there is."

  5. In other news, YEAH RED SOX!!!! by frenetic3 · · Score: -1, Offtopic

    Bring on the yankees baby!!!

    -fren

    --
    "Where are we going, and why am I in this handbasket?"
    1. Re:In other news, YEAH RED SOX!!!! by Anonymous Coward · · Score: -1, Offtopic

      Prepare to be swept by the Yankees.

    2. Re:In other news, YEAH RED SOX!!!! by Anonymous Coward · · Score: 0

      First the Giants (my team) choke, now the A's choke, and tomorrow a sex offender will be elected governor. It's a great time to be a Californian!

    3. Re:In other news, YEAH RED SOX!!!! by Anonymous Coward · · Score: -1, Offtopic

      LOL, did you see Clinton walking around trying to tell ALL about how BAD it was to mistreat women?.......now THAT fucker has no shame

    4. Re:In other news, YEAH RED SOX!!!! by Anonymous Coward · · Score: -1, Offtopic


      Yankees SUCK!!! Yankees SUCK!!! Yankees SUCK!!! Yankees SUCK!!!
      </chant>

    5. Re:In other news, YEAH RED SOX!!!! by Anonymous Coward · · Score: -1, Offtopic

      Who said anything about Clinton? If you brought him up as a comparison to your boy Arnie then that's not very flattering, is it? Get over the guy already, the rest of us have.

    6. Re:In other news, YEAH RED SOX!!!! by Anonymous Coward · · Score: -1, Offtopic

      Daaaaaarrrrrryyyyyyllllll, Daaaaaarrrrrryyyyyyllllll, ...

      Best. Chant. Ever.

  6. Shame.... by NightSpots · · Score: 5, Interesting

    His contributions to FreeBSD will be missed.

    I'm sure I represent a large portion of the community who greatly appreciated his work on the VM subsystem (he even pointed the Linux folks in the right direction on more than one occassion), and am disappointed to see him leaving the project.

    I understand that not everyone gets along, that goals differ between members; it's just a shame to see it happen.

    1. Re:Shame.... by Anonymous Coward · · Score: 0

      (he even pointed the Linux folks in the right direction on more than one occassion)

      So THAT's where the copyrighted SCO code came from eh? Well good riddance, I say.

    2. Re:Shame.... by NightSpots · · Score: 1, Insightful

      (Joking aside....)

      Everyone knows that the BSD codebase is infinitely more clean than the Linux codebase.

      Remember, the last few times there have been license issues with FreeBSD, it was people (*ahem* linux *ahem*) stealing FROM them.

    3. Re:Shame.... by Anonymous Coward · · Score: -1, Offtopic

      BSD is dying, and the Sox are going to the ALCS!!!

    4. Re:Shame.... by Anonymous Coward · · Score: 0

      Well, if he keeps doing great stuff like 'There's Something About Mary,' his movie career will regain its previously monumental status and eclipse all of his contributions to BSD. ;)

    5. Re:Shame.... by Anonymous Coward · · Score: 0

      What issues with the FreeBSD codebase?

      Its hard to steal under the BSD license..

    6. Re:Shame.... by Anonymous Coward · · Score: 1, Insightful

      He didn't use the right words. He meant that Linux kernel developers use code from BSD and don't have the decency to give credits -still perfectly within the BSD lincese. Of course this is not something new to Linux. IMHO, i'm not sure if Linux is more BSDish or SCOish -time will tell.

    7. Re:Shame.... by Anonymous Coward · · Score: 0

      Nope. Steal is the right word.

    8. Re:Shame.... by Anonymous Coward · · Score: 0

      > Its hard to steal under the BSD license

      No, it's easy. Just take UNIX source code and stick Berkeley copyrights on it. See BSD UNIX 4.4 and FreeBSD 1.x.

    9. Re:Shame.... by shepd · · Score: 1

      >Nope. Steal is the right word.

      Nope, it ain't.

      I think you'll find law in most other countries similarly clear on this issue.

      --
      If you could be told what you can see or read, then it follows that you could be told what to say or think - BoC
    10. Re:Shame.... by Anonymous Coward · · Score: 0

      ahh that BSD license sure is "free" huh?!

    11. Re:Shame.... by CoolVibe · · Score: 4, Insightful
      Why the hell is everyone thinking that Matt left? This fork isn't an 'angry' fork. DFBSD is just another BSD based off of FreeBSD 4 that is exploring some new ideas that Matt has. It's evolution. If DragonFly beats the pants off of 5.x in the future, I'm sure lots of DragonFly code will be appearing in the "official" FreeBSD tree.

      Matt already wrote a SHITLOAD of code for DragonFly. He already overhauled the threading in the kernel, and put in a totally new slab allocator. Right now he's overhauling the namecache system.

      Also, the DragonFly gang are doing chores nobody in the official FreeBSD camp cares enough about, like removal of __P(), removal of the 'register' keyword and ANSIfication of old K&R code. Of course we'll be seeing those efforts back in the other BSDs.

      These changes that Matt and his merry gang of hackers are making are changes that would never be accepted by the FreeBSD deities with a commit bit,because they're intrusive. Hence the reason Matt forked off DragonFly.

      He never left FreeBSD, dammit. Get over it.

    12. Re:Shame.... by UU7 · · Score: -1, Offtopic

      you're retarded.

    13. Re:Shame.... by Anonymous Coward · · Score: 0

      Matt's VM is what inspired Rik Van Riel to write the Linux VM, and the Linux VM is *HEAVILY* based on these ideas/concepts. He spoke at length to Dillon for months.

      Dillon's still part of the FreeBSD community.

      He just sees a different direction that is interesting, that he wants to pursue. I actually find his DFBSD fascinating - it's a "more AmigaOS-like" OS. And, IMHO, AmigaOS rocked for the time.

      But, Dillon's still part of FreeBSD. He's still contributing. Not as much, but hey, you can only keep so much up for so long... :)

    14. Re:Shame.... by m.dillon · · Score: 4, Informative
      The more I look back upon it the more I think forking off DragonFly was the right thing to do. The timing could not be better, in fact. A year ago would have been too early (because we would have had to backport a whole lot more from 5.x, whereas in the last year the FreeBSD folks have backported a considerable amount of work from 5.x to 4.x), A year from now would be too late (4.x would have been 'dead' for too long a period of time). Now is the right time.

      I still contribute to FreeBSD. If I see a bug or a security issue in DragonFly that also exists in FreeBSD they get a head's up, and some of the patch sets we've comitted to DragonFly have been organized in as legible a way as possible to promote a possible port from DragonFly to FreeBSD for those FreeBSD folks interested in the work. But my main focus these days is DragonFly.

      The biggest loss to FreeBSD from my departure is that they have one less person tracking down bugs in the kernel. To be sure, I had done less and less of that over the last year as FreeBSD-5 continued to diverge from what I believed could be supported, but before anyone chimes in with a silly 'Matt hasn't done anything' comment I will note that I spent several days reviewing and commenting on Jeff's scheduler and slab allocator work, which benefited greatly from the comments, plus brainstorming sessions with Julian on KSEs, with Alan and Tor on VM issues, and so forth. I had attempted to put FreeBSD-5 on a better track several times, but the ideas were rejected in piecemeal. I don't think there are any big-picture/multi-disciplinary folk left in the project, which is a problem. Basically the FreeBSD-5 team seems to suffer from a sort of myopia. It is possible to defend a piece of work taken in isolation, such as priority stealing for mutexes or kernel preemption, but when you look at the big picture there are simply too many such pieces, each complex in its own way, in the FreeBSD-5 kernel. The result is a huge mess that only a few programmers can actually navigate through without introducing new bugs, and that is a real problem insofar as progress in FreeBSD-5 goes. Too many developers are working only in their own little corner of their world and too few developers are doing general debugging and architectural work. And, most especially, too few developers are looking out for and supporting the end-users, something that has been a significant part of my work ethic ever since I wrote DICE. There are plenty of FreeBSD developers, their numbers certainly are not decreasing, but the class of developers is far less balanced now then it was in 1998. That is my opinion, anyway.

      Not having to deal with FreeBSD politics anymore as significant reduced my stress levels, and being able to work on innovative new designs rather then having to fix other people's bugs has improved my disposition dramatically :-).

      -Matt

    15. Re:Shame.... by NightSpots · · Score: 1

      He never left FreeBSD, dammit. Get over it.

      He was stripped of his commit bit. Effectively, that means his contributions are slow and filtered. He's not gone, but his role is diminished.

    16. Re:Shame.... by renoX · · Score: 1

      >removal of __P(), removal of the 'register' keyword and ANSIfication of old K&R code

      *removal of __P()?
      Could you explain what this is? I suppose that this is FreeBSD specific..

      *removal of the 'register' keyword
      If memory serves, the register keyword is only a hint to the compiler, so a global search and replace should be enough to remove the register keyword, no?

      *ANSIfication of old K&R code
      K&R, ouch my memory is fading, but I think that some preprocessor can do it automatically, no?

      Not that I'm not criticising: cleaning old code is good, but the two points I understood do not seem too difficult.

      The thing which looked interesting in DragonFly is the execution of system call within the user's context if it is possible (I've read that the AmigaOS could do this before).
      I'm wondering what is the main problem to do this for an OS?
      There must be some difficulties otherwise every OS would do it..

    17. Re:Shame.... by Anonymous Coward · · Score: 0

      *removal of __P()?
      Could you explain what this is? I suppose that this is FreeBSD specific..


      Google is your friend

      If memory serves, the register keyword is only a hint to the compiler, so a global search and replace should be enough to remove the register keyword, no?

      The problem probably isn't doing the work, but getting the changes accepted by the powers-that-don't-like-change.

    18. Re:Shame.... by renoX · · Score: 1

      I did a google search before posting, but without success, thanks for the link.

      >The problem probably isn't doing the work, but getting the changes accepted by the powers-that-don't-like-change.

      Well now that he has his own codebase, this shouldn't be too much a problem ;-)

    19. Re:Shame.... by sander · · Score: 1

      __P () is what lets the same code be compiled by both ansi and k&r c compilers - ansi compiler sees the prototype and k&r sees a version that keeps it civil too.

    20. Re:Shame.... by Anonymous Coward · · Score: 0

      removal of __P(), removal of the 'register' keyword and ANSIfication of old K&R code

      That's started in the 5.x branch quite a while ago. Since Matt broke off the 4.x branch instead, he had to redo all that.

    21. Re:Shame.... by Anonymous Coward · · Score: 0
      What I Know About BSD
      1. You can not play games on it.
      2. It cannot be used by my grandma.
      3. It lacks a GUI of any note.
      4. There is no support available for it.
      5. It is an assortment of fragmented OSes.
      6. It cannot be run on the x86 platform.
      7. You have to compile everything and know C.
      8. Support for the latest hardware is always poor.
      9. It is incompatiable with GNU/Linux.
      10. It is dying.
  7. DragonFly 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 DragonFly BSD fanatics? I've been sitting here at my freelance gig in front of a DragonFly 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 DragonFly 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 DragonFly BSD machines, but suffice it to say there have been many, not the least of which is I've never seen a DragonFly BSD box that has run faster than its Windows counterpart, despite the DragonFly 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 DragonFly BSD is a "superior" machine.

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

    1. Re:DragonFly BSD Problems by Anonymous Coward · · Score: 0

      Wow, insert "OS X" in every place where there is a DragonFly BSD in that message, and you have the same Mac OS X troll that's been posted on every Apple story for several months. I can't believe someone actually modded you 'Interesting.'.

    2. Re:DragonFly BSD Problems by Anonymous Coward · · Score: -1, Offtopic

      What kind of jacked up moderator marked this as "interesting"? This same stupid piece of shit gets posted in most stories about some new operating system, with just the name changed. Allegedly it was originally some Mac rant from ages ago.

      Needless to say, it does not fucking apply to dfly, so please get a clue before you moderate.

    3. Re:DragonFly BSD Problems by Anonymous Coward · · Score: 0

      >what is the deal with you DragonFly BSD fanatics?

      >I won't bore you with the laundry list of other problems that I've encountered while working on various DragonFly BSD machines

      This is a troll.

      If you are using DragonFlyBSD its because you are using bleeding edge diff's to the FreeBSD 4.8 source tree. DragonFly is a few months old, and likely unapolegetically broken in some places.
      I doubt that anyone is currently using it in production. 'DragonFlyBSD fanatic' is an amusing strawman.

      I am curious about this poster's long history of DragonFlyBSD woes. Dillon started the fork in July. There is no official install-CD as yet. It is curious that one so disaffected with BSD-ish systems would be slogging through CVS to build the boxes that have given him 3-4 months of woes.

      ignore this guy

    4. Re:DragonFly BSD Problems by Anonymous Coward · · Score: 0

      I did, for I am weasel.

    5. Re:DragonFly BSD Problems by Anonymous Coward · · Score: 0

      I.R. Weasel. Get your cartoons right.

    6. Re:DragonFly BSD Problems by MoronGames · · Score: 1

      I. R. Baboon! I Am Weasel! How about you get it right?

      --
      hey!
    7. Re:DragonFly BSD Problems by Anonymous Coward · · Score: -1

      I did, for I am weasel, not baboon.

    8. Re:DragonFly BSD Problems by Anonymous Coward · · Score: -1, Flamebait

      Thank you captain obvious.

    9. Re:DragonFly BSD Problems by Anonymous Coward · · Score: -1, Troll

      17 megs in 20 minutes?!? You're lucky, man! I'm sitting here with the latest Linux installation from RedHat and I've been waiting over 47 minutes for it to copy a 10 MB file. Not only that, but the display freezes while it copies the file so I can't do anything but wait and hope that blasted Linux kernel hasn't gone south like a greased Yoda doll up Linus Torvald's gay penguin asshole!

      Linux fanboys, flame me if you like, but I'd rather use a real operating system like BSD any day of the week.

    10. Re:DragonFly BSD Problems by Anonymous Coward · · Score: 0

      I WILL NEVERGETITRIGHT (on purpose) for I B Red Guy...

  8. Win2kPro by Anonymous Coward · · Score: -1, Troll

    Even though I run only Win2kPro can I still join the chat? I want to persuade ppl to switch from BSD to Win32.

  9. IRC Is Dead by Rick+the+Red · · Score: 3, Funny
    --
    If all this should have a reason, we would be the last to know.
  10. A dragonfly bit me the other day by Dancin_Santa · · Score: 2, Funny

    I was just doing some gardening and it bit me on the back of the hand.

    I don't want to use any operating system that reminds me of that traumatic experience.

    I liked Dillon in Footloose, though.

    1. Re:A dragonfly bit me the other day by Anonymous Coward · · Score: -1, Offtopic

      A dragonfly bit me the other day

      That's OK. He's dead by now.

    2. Re:A dragonfly bit me the other day by Brandybuck · · Score: 2, Funny

      Phhhhft! Linus got charged by an angry penguin, and had to run for his life, but he still works on Linux. I mean, having some rabid penguin chase you around a zoo is much more traumatic that getting bit by a dragonfly.

      --
      Don't blame me, I didn't vote for either of them!
    3. Re:A dragonfly bit me the other day by Anonymous Coward · · Score: -1

      You must have been tormenting it. Dragonflies don't bite unless provoked.

    4. Re:A dragonfly bit me the other day by Anonymous Coward · · Score: 0

      it bit me

      I know your post bugs me, so I can understand why a dragonfly would want to take a bite.

  11. LOL!! Troll got "interesting" by Anonymous Coward · · Score: -1, Troll

    3y3 4m b!ff!!11!!!!!!111!!

  12. IF I EVER... by Anonymous Coward · · Score: -1, Troll

    if i ever meet you i will kick your ass

  13. *BSD Wailing Song by Anonymous Coward · · Score: -1, Troll

    The *BSD Wailing Song

    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
    In the end our lost soul 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

  14. 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.

  15. 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 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.

  16. Be sure to ask him... by Anonymous Coward · · Score: 0, Funny

    about the future of *BSD and its imminent death.

    1. Re:Be sure to ask him... by Anonymous Coward · · Score: 0

      Hey, it's still $699 cheaper than Linux...

    2. Re:Be sure to ask him... by Anonymous Coward · · Score: 0

      Nope, fraid not. Same $699 license fee applies. At least Microsoft thinks so, since they're licensing BSD code from SCO right now.

  17. It is now official 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 93% of 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 dying

    1. Re:It is now official by endx7 · · Score: 4, Funny

      It is now official - Netcraft has confirmed: *BSD is dying

      I really shouldn't reply to this kind of comment, but doesn't that comment seem kinda weird if you consider the fact netcraft runs FreeBSD?

    2. Re:It is now official by Anonymous Coward · · Score: -1, Offtopic

      It is now official - Netcraft has confirmed: Netcraft is dying ...

  18. focus by endx7 · · Score: 3, Interesting

    This will be a good chance to find out what DragonFly BSD will be standing for.

    We all know the 3 main (free) BSDs have their focuses, namely:
    FreeBSD: ease-of-use and i386 platform (plus a few others)
    NetBSD: portability
    OpenBSD: security, plus some focus on ease-of-use
    and then there are a few other minors, and Mac OS X

    But the question is, what is DragonFly BSD's focus? What will it offer for us? How will it be useful?

    Perhaps we'll learn at this chat session.

    1. Re:focus by NightSpots · · Score: 4, Informative

      Since it's based on FreeBSD 4, it'll be "All of good things of FreeBSD 4 with a focus on performance."

      There's a LOT of work going into fine grained locking to allow faster SMP (which is a classic slowdown in FreeBSD 4) - light weight kernel threads, advanced caching, messaging APIs, and even plans for a package system that (if it works?) would completely change the way people think about installing third party software.

      There are a lot of big things planned. It may be slow to start, hopefully it'll take off... and we'll see some cross development with the other BSDs.

    2. Re:focus by Anonymous Coward · · Score: 0

      But the question is, what is DragonFly BSD's focus? What will it offer for us? How will it be useful?

      It will have more copied SCO code than the competition. It will also encourage homosexuality, pedophilia, and piracy of copyrighted music.

    3. Re:focus by Anonymous Coward · · Score: 1, Insightful
      Perhaps we'll learn at this chat session.

      Perhaps you can learn at this webpage, dipshit.

    4. Re:focus by Anonymous Coward · · Score: -1, Troll

      Make sure to ask what BSD stands for - is it Butt Sex Department or Boiz Sucking Dick?

    5. Re:focus by Anonymous Coward · · Score: -1, Troll
      Sure, we all know that *BSD is a failure, but why? 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 personas?

      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.

    6. Re:focus by Anonymous Coward · · Score: -1, Flamebait

      fuck you, asshole

    7. Re:focus by Anonymous Coward · · Score: -1, Flamebait

      No. Fuck you, asshole.

    8. Re:focus by Anonymous Coward · · Score: -1, Troll

      Somebody, anybody, fuck me please.

    9. Re:focus by Anonymous Coward · · Score: -1, Flamebait

      Go fuck yourself, asshat.

    10. Re:focus by thallgren · · Score: 5, Insightful

      >There's a LOT of work going into fine grained locking to allow faster SMP

      Unless I'm totally wrong, this is exacly the opposite from what DragonFlyBSD is about. Matt has never liked the way FreeBSD and Linux are designed, a kernel sprinkeled with locks.

      Instead, he's trying to do a kernel where kernel-side subsystems communicate via message-passing, not too far from how exec.library worked in AmigaOS.

      So Matt and his cowboys/cowgirls are actually removing locks. :-)

      Regards, Tommy

    11. Re:focus by Anonymous Coward · · Score: -1, Troll

      Oh great, so they're going to remove all reentrancy from the kernel? Excelent idea; that'll really improve performance!

      Its sarcasm, idiot.

    12. Re:focus by Leimy · · Score: 3, Informative

      As far as I know... and I have been following the list as well as reading the website... I see no plans to rely on fine-grained locking as an SMP enabling mechanism. There is an AmigaOS based messaging system that will allow people to run things like Filesystem drivers in userland should they choose to or they can keep it in ther kernel.

      But why are you reading /. comments to find out what this thing is? Go to the website and see for yourself.

    13. Re:focus by goon · · Score: 1

      OpenBsd could probably summed up more accurately as emphasising stability and security. Not so sure about ease of use.

      --
      peterrenshaw ~ Another Scrappy Startup
    14. Re:focus by Anonymous Coward · · Score: -1

      How does calling someone dipship qualify as Insightful?

    15. Re:focus by m.dillon · · Score: 3, Informative
      Some MP locking is unavoidable, but DragonFly will have much, much less of it then any other MP operating system that I know of. Having to use an MP lock is basically an admission that there will be cache contention between cpus... if not the lock itself, then the data that is being covered by the lock. If you have 4 cpus and all of them at one time or another are accessing a common data structure, then you are wasting 3/4 of your available aggregate L1 and L2 cache space storing that data structure plus you are wasting cycles obtaining the lock, wasting hardware cycles due to cache management operations, and wasting cpu.

      Now, of course, some data structures are more important then others. It doesn't make sense to try to avoid all locking... there are plenty of situations where you have to eat the duplication in the cache and plenty of situations where you have to eat cache mastership changes.

      But there are a ton of situations where the waste is not necessary. In DragonFly these situations translate to: The scheduler, the slab allocator, device driver interrupt management, and the networking stack, just to begin with.

      Lets take the networking stack as an example. In a fine-grained mutex model if a cpu is available it might be called upon to run pending work for the network stack... say processing packets for various TCP connections. In order to do the work the kernel will pull the next packet off the queue, figure out the protocol and port, obtain a fine-grained mutex on the PCB, and then do the work.

      In the DragonFly model the network interrupt will queue the packet and the queueing code will peek at the packet and direct it to a particular protocol thread. Any given connection will be directed to a single thread so, for example, if you have a 4-cpu system and you have told the kernel to create 4 TCP protocol stack threads (one on each cpu), then each new TCP connection will be assigned to a particular thread. Only that thread will process packets associated with that particular TCP connection, which means that no locks are required to process packets for that TCP connection and no L1/L2 cache duplication will occur between cpus because only one thread will ever touch it. If you have 1000 TCP connections, each of your four TCP protocol stack threads will be assigned approximately 250 of them.

      In DragonFly's case the trick then becomes to balance the assignments, but even here we get a leg-up because simply distributing the connections by ^^ mod the number of protocol threads will get you most of the way to that goal. When you add in the cache-locality you have just achieved (you have 4 times the available data cache by not sharing the PCBs across multiple cpus) the result is far higher performance then a fine-grained-but-perfectly-balanced model could ever give you.

      -Matt

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

    It is common knowledge that *BSD is dying. Nearly everyone is aware 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 erosion 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 very 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.

    Fact: *BSD is dying

    1. Re:*BSD is dying by Anonymous Coward · · Score: 0

      And your point is?

  20. Why Dragonfly? by Valar · · Score: 4, Interesting

    If I am a happy Linux or BSD (of some non-Dragonfly kind), then what would you say to entice me to switch? In other words, what do you think Dragonfly is particularly good at, that maybe is lacking elsewhere?

    1. Re:Why Dragonfly? by Valar · · Score: 1

      Sorry, I forgot to mention this: that was addressed to any DragonFly users in the crowd. The comment doesn't make much sense otherwise. Though I have been known to talk to myself...

    2. Re:Why Dragonfly? by Anonymous Coward · · Score: -1, Flamebait

      itz headed by a rebel who can't play nice with the other kids just like Theo de Ass

    3. Re:Why Dragonfly? by Anonymous Coward · · Score: -1, Troll
      haiku

      flask of ripe urine
      pressed to bsd lips
      bsd drink up

    4. Re:Why Dragonfly? by Anonymous Coward · · Score: -1, Offtopic

      Because not everyday an actor gets to write his own OS ;).

    5. Re:Why Dragonfly? by Anonymous Coward · · Score: 0

      Well, that make me want to switch! Sounds great!

    6. Re:Why Dragonfly? by Anonymous Coward · · Score: -1, Troll
      Don't waste your time. Outside of a few socially backward dweebs,
      no one, but no one, uses BSD.

      Yes it's dead. The BSD zealots need to wake up and smell the coffee.
      They also need to shower, brush their teeth, lose 100 lbs, and get a life.

    7. Re:Why Dragonfly? by be-fan · · Score: 3, Informative

      Dragonfly isn't a completed project at this point, or even one that made changes substantial enough to differentiate it from other systems. Dragonfly forked from FreeBSD because they have some very different ideas about where the kernel should be headed than the FreeBSD folks. Dragonfly will be based on a model of very lightweight threads that communicate via a messaging mechanism. They think they can get highly scalable designs without all the locking that the Linux and FreeBSD designs use. If it works, it could be a very large step forward for multi-CPU and clustured systems.

      --
      A deep unwavering belief is a sure sign you're missing something...
    8. Re:Why Dragonfly? by Anonymous Coward · · Score: -1, Troll

      Brian Eno drinks his own pee.

    9. Re:Why Dragonfly? by Anonymous Coward · · Score: -1

      Did you even bother reading the page ?

    10. Re:Why Dragonfly? by m.dillon · · Score: 4, Interesting
      DragonFly's first official release will be in a little less then a year. Half of that time is going to be spent rewriting the infrastructure, which is outlined on the site www.dragonflybsd.org We already have light weight threads and our slab allocator in place (which are a biggies) and the basic infrastructure for syscall messaging and DEV messaging in place. We are also steadily bringing in those elements from FreeBSD-5.x that make sense. At the moment my focus is on fixing inherited bugs and rewriting the namecache code. Other DragonFly developers are focused on syscall sepraration, networking, and userland bits. We are being very, very careful to preserve and improve upon the stability inherent in earlier 4.x releases. In fact, the namecache stage-3 work has been delayed over two weeks now while I have backed up and refocused on fixing a number of unrelated bugs.

      The biggest topic on our lists right now is the discussion on the infrastructure required to support a good binary and source-based package management system. FreeBSD's package management system currently suffers greatly from bitrot and upgrade-breakage (where upgrading one package breaks half a dozen others), amoung other problems. We are discussing the use of variant symlinks and VFS-based 'environments' for deploying and validating port dependancies in a manner that allows multiple versions of anything to coexist on the same system.

      Basically you can think of DragonFly as being all the things I've always wanted to do but couldn't due to politics in the FreeBSD camp. FreeBSD-5 has gone down a road that I believe will lead to a slow, cumbersome, and unmaintainable result. There are plenty of examples of this but the most aggregious is thread preemption in the kernel, preemptive thread movement between cpus (also while in the kernel), and a ridiculously complex API for various types of mutex operations. There are good things in FreeBSD-5, and we will snarf them as appropriate.

      The timing is appropriate. FreeBSD-4.x is nearing its end-of-life, and it is obvious that less care is being taken in preserving its vaunted stability then in the past. DragonFly will be the logical successor to FreeBSD-4.x statring in around a year, and I also fully expect to beat the shit out of FreeBSD-5 SMP-performance-wise by the time too.

      DragonFly's kernel model is basically to operate on cpus in isolation, with movement beween cpus strictly managed. For example, there is a separate light weight kernel scheduler on each cpu which handles all operations related to that cpu and requires the use of no mutexes. The slab allocator is also per-cpu and mutexless. If an operation needs to work on a data structure owned by another cpu an asynchronous IPI (message) is sent to that cpu rather then performing a locking/mutex operation. For example, if cpu #1 needs to free data owned by cpu #2's slab allocator, cpu #1 queues the work to cpu #2 (and in the case of a memory free, the work does not have to be done immediately). The term 'asynchronous' is important in this context, because it means that the IPI latency between cpus can be entirely absorbed and that sequences of messages (in more heavily loaded systems) can be processed in a tight loop. When we get into more complex entities such as the networking stack, the intention is to run the protocol stacks as threads (possibly multiple threads, one on each cpu or as needed by the situation) and assign protocol control blocks to particular threads on particular cpus. This eliminates nearly all locking and mutex operations related to any given protocol control block and guarentees cache locality of reference. If done properly the individual cpu caches on SMP systems will wind up with less duplication and far higher efficiencies then one gets using a fine-grained locking mutex model. In fact, DragonFly's model works equally well in both UP and SMP environments and we expect the SMP support will cause virtually no loss in performance on UP boxes.

      -Matt

    11. Re:Why Dragonfly? by Dick+Faze · · Score: 1

      So does all this mean that MP FreeBSD machines will be able to do all the funky science shit I see on two out of three pages of "Linux Journal"? 860 node BSD clusters in our future? That sure would help me out in the next Usenet pissing contest. Plus I could justify taking W2k off my 4 way xeon box. Matt should be elected to high public office.

    12. Re:Why Dragonfly? by aphor · · Score: 1

      The biggest benefit/drawback that I see is all the Slashdot trolling mirroring/mocking/echoing the "Imagine a Beowulf cluster of these" with "Imagine a Dragonfly cluster of these..." The change will be felt mostly when the pissing contest and flamewar between the trolls' biters resurrect the old Linux/BSD holy war.

      I predict this will happen when people figure out how to get the Dragonfly threading/messaging code into NetBSD.

      --
      --- Nothing clever here: move along now...
  21. BSD Ghetto 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.

  22. Don't make deals with the devil by Anonymous Coward · · Score: -1, Offtopic

    they might actually come true.

  23. Ahem by Anonymous Coward · · Score: -1, Troll
    It is official; Netcraft now confirms: *BSD is dying

    One more crippling bombshell hit the already beleaguered *BSD community when IDC confirmed that *BSD market share has dropped yet again, now down to less than a fraction of 1 percent of all servers. Coming on the heels of a recent 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 93% of 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 dilettante 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 dying

    1. Re:Ahem by magores · · Score: -1, Flamebait

      Okay.. I'm probably begging for Flamebait with this, but I'll ask anyway...

      Please provide links to PREVIOUSLY PUBLISHED articles, newsbriefs, etc (web-based or otherwise) that show:

      a) BSD is technologically inferior (speculations regarding present or future development allowed) to Linux

      or

      a) Linux is technologically inferior (speculations regarding present or future development allowed) to BSD

      --
      I do not ask for the purposes of trolling, or flaming, or somesuch...

      I'm not interested in GPL vs BSD except as it effects the above mentioned future development.

      (And, Yes. I did read the parent post re: developers leaving, etc.)

      I'm just curious about the technology aspect. (I've read enough comments and random opinion. I'd like some backup for the statement at this point.)

      Thanks.

    2. Re:Ahem by MoThugz · · Score: 1

      Non of them is totally inferior or superior to each other in the sense of the word. Just like 99% of things in life, it all depends.

    3. Re:Ahem by magores · · Score: 1

      Okay. Let me amend my above post by asking the "guaranteed-to-get-me-modded-as-flamebait" question...

      From a technological standpoint, why should the average person choose one or the other? ("Average" in this case, meaning someone debating with themself between linux/bsd/or even MS for next server.)

      I mean to ask this strictly from a strictly technology standpoint. I have heard the arguements re: bsd vs gpl, and it is an important issue as far as present and future development is concerned. But, I'm looking for a technology based-answer of which the license is a part, but not the focus, of the answer.

      I realize people could argue about this all day, and they "probably" have in the past.. This is why I asked for links to previously published arguements/stats/etc.

      I still haven't noticed it yet in this thread... Technologically, why is linux better/worse than bsd? Or, vice versa if you prefer.

      Is better hardware support the main thing linux has going for it?

    4. Re:Ahem by Anonymous Coward · · Score: -1, Troll

      Linux is better because BSD is dying.

    5. Re:Ahem by MoThugz · · Score: -1, Redundant

      I've used all three OS you've mentioned in your post... I too am license-neutral, I just couldn't give a damn how you choose to license it, I just want to use it as is...

      For the sake of the argument, I'm going to demonstrate what I think of the Security to Simplicity ratio of the 3 OSs.


      Windows Secure ========0= Simple
      Linux Secure =====0==== Simple
      BSD Secure =0======== Simple


      So there you have it... Let's say I have only a handful of MCSE monkeys to deploy and some bucks to spare, then I'd go with Windows, regardless of how I feel about the OS personally.

      If I have a bunch of Unix has-beens, then I might as well stick with what they know most, and that would be BSDs.

      If I had a bunch of RHCE monkeys, then of course I would be better off with Linux solutions.

      It's the same technology-wise. How do you measure technology? I mean if you're talking about architecture-specific optimizations then the open source solutions should be better than Windows because at least we can decide on that... and BTW, what processor is Windows XP optimized for anyway?

      And did you even google for your so-called articles of proof? If you did you can actually see that there's no concise answer, like I said it all depends... Only you can be the judge of what technology works for you... no matter how advanced it's pimped out to be. In fact, that is the best way in which to evaluate these OSs, because published findings can be biased in the direction of money, zealotry, or other agendas.

  24. *BSD Sux0rs by Anonymous Coward · · Score: -1, Troll
    In a startling turn of events today, a previously little-known fact came into the public eye: "*BSD Sux0rs". This came as a complete surprise to the BUWLA, or BSD Users With Large Assholes, as they previously thought that *BSD 0wned.

    "You see, even though I have never contributed code to any BSD project, I thought it was my duty to be a big asshole to others which don't use the OS I do, because it just 0wnz.", said one FreeBSD user. "Now that I know it sux0rs, though, I have to go find something else to be an asshole about."

    One notorious OpenBSD fanatic known as WideOpen, told reporters, "I have to kill myself. This isn't how it was supposed to happen. My BSD has always been the best, and shouting that opinion in other people's faces at every chance I got has been my only hobby. It was all I ever did. It was what got me out of bed in the morning. Now I have to die. I will jam my bedpost up my ass until I hit my brain. It is the only way to go: BSD style."

    In the volatile world of operating systems anything can happen. "At least we don't sux0r as much as Windows users", BigAzz, a relatively well-known NetBSD user said. "Screaming things in people's faces is my calling. Now I need to scream that BSD sux0rs. What a sad world. At least I won't kill myself like those uber-asshole OpenBSD guys. They are just way over the top. Or were, at least."

    Nobody knows for sure what the future holds for the state of operating systems, but with Netcraft confirming the sux0r status, *BSD users all over the world will have to stick something else up their asses from now on or risk looking even more gay than they used to.

  25. 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.


  26. BSD Rap by Anonymous Coward · · Score: -1, Troll

    yo bam
    bam
    puh
    puh uh
    puh uh huh uh
    the fatwork is back (puh uh, puh uh)
    and you know Don hates *****
    that nigga moved to Belgium
    where the guvment sells trash sacks
    puh hu hu ha ha uh puh uh puh uh ha ha ha

    1. Re:BSD Rap by Anonymous Coward · · Score: -1

      Come on! Get 'em up!

  27. YHBT YHL HAND by Anonymous Coward · · Score: -1, Troll
  28. What I know about BSD by Anonymous Coward · · Score: -1, Troll
    1. You can not play games on it.
    2. It cannot be used by my grandma.
    3. It lacks a GUI of any note.
    4. There is no support available for it.
    5. It is an assortment of fragmented OSes.
    6. It cannot be run on the x86 platform.
    7. You have to compile everything and know C.
    8. Support for the latest hardware is always poor.
    9. It is incompatiable with GNU/Linux.
    10. It is dying.
    1. Re:What I know about BSD by doobray · · Score: 0

      1 - yes you can. 2 - maybe not YOUR lame Grandma. 3 - Gnome? 4 - Nonsense, many consultants offer support. 5 - WTF? 6 - WTF?? don't be an idiot. 7 - Nonsense, it's as easy as Linux to install packages. 8 - More unsubstantiated nonsense. 9 - Also incorrect. 10 - I'm pretty sure this thread was spawned by a new distro of BSD.. Quit spewing Bullshite, do you kiss your mama with that mouth??

    2. Re:What I know about BSD by Anonymous Coward · · Score: -1, Offtopic

      HTML - it's not just for web pages anymore!

  29. BSD POETRY (hikau) by Anonymous Coward · · Score: -1, Troll

    flask of ripe urine
    pressed to bsd lips
    bsd drink up

  30. The real shame by the+man+with+the+pla · · Score: 3, Insightful

    Matt Dillon deserves absoluetely no pitty. His outrageous immaturity justified the revocation of his commit bit 1000 times over. Shame on you for painting him to be some kind of victim.

    --
    The linux hacker
    1. Re:The real shame by Anonymous Coward · · Score: 0
      roger that -- mod this shit up!

      dillon is another bsd megalomanic like Theo

    2. Re:The real shame by Anonymous Coward · · Score: -1

      He was good in Drugstore Cowboy, though.

    3. Re:The real shame by Anonymous Coward · · Score: -1, Offtopic

      Plleeaasee Leearrnn to spelll. Starttt witth your ussernamme.

    4. Re:The real shame by Anonymous Coward · · Score: -1

      How do you know he isn't a person associated with the Palistinian Liberation Army?

    5. Re:The real shame by Anonymous Coward · · Score: -1, Troll

      You like meat in your ass ?

    6. Re:The real shame by m.dillon · · Score: 2

      Gee I hope not *exactly* like Theo. But watch out who you lambast. Theo is responsible for or as managed some fairly major improvements in the open-source world, and we are far better off with that work.

    7. Re:The real shame by Anonymous Coward · · Score: 0

      FACK OFF! I'm with the Liberation Army of Palestine.

  31. Is this the guy that wrote dcron? by kingLatency · · Score: 1, Interesting

    Since this guy shares the name with that actor, I remembered the name. Is this the same Matt Dillon who is responsible for dcron on my Gentoo system?

    --
    "I've got to stop masturbating! It makes me too lazy! Stop it, Albert. Stop it." -- Albert Einstein
    1. Re:Is this the guy that wrote dcron? by Anonymous Coward · · Score: 0

      No. He's the one who cleaned up Dodge City.

    2. Re:Is this the guy that wrote dcron? by m.dillon · · Score: 3, Interesting
      Yah. I still get an occassional email regarding dcron. DCron was written because, at the time anyway, the VixieCron that Linux was using had a huge number of bugs in it. For example, just changing the time could cause VixieCron to suddenly execute hundreds of jobs all at once. This was a long time ago and I expect VixieCron has been fixed since then, but that was the original motivation for writing DCron. I just wanted something small, simple, and dependable, with per-user capabilities.

      It is gratifying to see that DCron is still being used regularly, but I am a bit miffed that nobody has gone and made any truely significant improvements to it. That is part of the nature of open-source, I guess.

      -Matt

    3. Re:Is this the guy that wrote dcron? by schon · · Score: 1

      It is gratifying to see that DCron is still being used regularly, but I am a bit miffed that nobody has gone and made any truely significant improvements to it.

      As a happy user of DCron, I can't honestly think there's anything significant to improve upon. It works, and works well. Thanks for a great piece of software!

  32. BSD is developed by idiots by Anonymous Coward · · Score: -1, Troll
    Both the Apple and the Sun OS offerings are worthless. In fact, Darwin is less than worthless.

    BSD is really bad, but it is supported and developed by idiots, and doesn't have enough protection of our Freedom, and is just absolutely unfriendly to users.

    It's going to the scrapheap of history, along with SCO.

    Ruben

    1. Re:BSD is developed by idiots by Anonymous Coward · · Score: 0
      BSD is really bad, but it is supported and developed by idiots, and doesn't have enough protection of our Freedom, and is just absolutely unfriendly to users.

      Do you mean the _OS_ is unfriendly or are you referring to the *BSD _community_?

      If the latter, I would say there is just as much, if not more "RTFM STFU j00 sux0r n00b!" in today's Linux "community" nowadays.

  33. Bob Hope joins the 'B' Team by Anonymous Coward · · Score: -1, Troll
    It is with a heavy heart that we must report that Bob "I'm still dead" Hope has gone on to join the "B" team. As you all may know, BSD has been part of the "B" team for quite some time.

    The Year of Our Lord 2003 has been a particularly bad year for the "B"s,

    • Bob Hope
    • Buddy Ebsen
    • Buddy Hackett
    • Barry White
    • BSD
    This honored list of dead is but a small token of adieu from the many fans of the deceased.
    These dead were truly some American Icons. They will be missed.
    1. Re:Bob Hope joins the 'B' Team by Anonymous Coward · · Score: -1, Offtopic

      The Year of Our Lord 2003 has been a particularly bad year for the "B"s,

      The real question here is, are the Linux-fanboy anti-BSD trolls going to remember to update the year after December 31st? Or will they just numbly cut and paste as they always have?

  34. *BSD for Windows XP? by Anonymous Coward · · Score: -1, Troll
    Is there a version of *BSD that works under WinXP? Please provide a BiTt0rReNt link to the installer. TIA!

    PS It's WinXP Professional, no service packs installed.

    1. Re:*BSD for Windows XP? by Anonymous Coward · · Score: 0

      I think that Windows XP has built-in security features that will disallow the installation of an OS such as BSD that is not "trusted". This is reasonable, after all BSD was responsible for the so-called "internet worm" and many other security holes.

      Anyway, XP takes the best parts of the obsolete Unix paradigm, and combines it with a truly best-of-breed user experience, while throwing out the rest. You don't need anything else.

    2. Re:*BSD for Windows XP? by Dancin_Santa · · Score: 1

      BSD is an operating system, so it actually can't run under WinXP. It gets to run all by itself.

      You could install it on another partition and actually dual boot BSD and Windows (dual booting is where you have two operating systems on the same machine, side by side). You can only run one operating system at a time, though.

      You can download the latest FreeBSD ISO (bootable CD image) from here

    3. Re:*BSD for Windows XP? by Anonymous Coward · · Score: 0

      BTW, be sure to install those service packs, they provide lots of exciting new features. You're really missing out otherwise.

    4. Re:*BSD for Windows XP? by Anonymous Coward · · Score: -1, Troll

      What's a partition?

    5. Re:*BSD for Windows XP? by Anonymous Coward · · Score: -1, Troll

      Is there a version of *BSD that works under WinXP? Please provide a BiTt0rReNt link to the installer. TIA!
      PS It's WinXP Professional, no service packs installed.


      No service packs, eh? Don't worry. I already have BSD running on your machine. You may have noticed the speed increase? It probably doesn't take 20 minutes to copy that 17MB file anymore now that BSD is running.

      You're welcome.

      Oh, and I hope you don't mind that I also took over your lame-ass Linux system. Bloody Linux distro was as insecure as a one-legged man with a greased Yoda doll shoved up his ass in a nude ass-kicking contest.

  35. Too many Matt Dillons! by PHPee · · Score: 4, Funny

    As soon as I saw Matt Dillon's name associated with BSD, I got really excited. I mean, who knew that the ol' gunslinger Marshal Matt Dillon became a programmer?

    Then, I realized I must have been thinking about the wrong Matt Dillon, but I still thought it was weird that the guy from There's Something About Mary became involved in a BSD project.

    Finally I remembered the other Matt Dillon who developed the DICE C compiler for the Amiga back in the good old days.

    1. Re:Too many Matt Dillons! by MobyTurbo · · Score: 2, Informative
      Finally I remembered the other Matt Dillon who developed the DICE C compiler for the Amiga back in the good old days.
      That Matt Dillon is the FreeBSD one, he did both the DICE compiler and the FreeBSD VM (and some other FreeBSD stuff.)
    2. Re:Too many Matt Dillons! by Anonymous Coward · · Score: 0

      He can hardly be credited with "doing" the FreeBSD VM (depending on your definition of "doing"). The VM system was originally picked up from CMU Mach (where it was written by Avie Tevanian and Michael Wayne Young) into BSD and improved in FreeBSD significantly by some of the older (in terms of involvement) FreeBSD developers (John S. Dyson, at least).

      Matt Dillon's involvement with FreeBSD was relatively recent (starting in '98 or so), and while he has contributed to the VM system significantly, crediting him for creating it isn't really justified.

    3. Re:Too many Matt Dillons! by m.dillon · · Score: 4, Informative
      You could credit me with being the primary mover for fixing the VM system going from 3.x to 4.x, and the buffer cache as well. I did some rewriting when it was called for, but most reorganized smaller sections of code in order to get rid of race conditions (bug fixing), clean up performance issues, and so forth. This created some friction because nobody else was willing to do the necessary work yet everyone still had an opinion on how the work should be done.

      I also completely rewrote the swap management code from the old list-of-holes format to a fixed radix tree with dynamic size hinting, fixed issues in VN and MFS, and generally put out a lot of fires all over the tree. Most of what I did in BSDland was fix bugs, because there were a lot of bugs that needed fixing and, again, there isn't much of a point having an advanced operating system if it crashes every so often.

      I probably spent far more time fixing bugs then anything else. My involvement with FreeBSD began during my BEST Internet days, in the 94 or 95 timeframe, with a commit bit coming in '98 I think, but my involvement with BSD began in 1985 at UC Berkeley, at about the same time I got involved with the Amiga.

    4. Re:Too many Matt Dillons! by Anonymous Coward · · Score: 0

      He also wrote the bible and fathered 2 of my children.

  36. Bones on BSD by Anonymous Coward · · Score: -1, Troll

    Bones : It's dead, Jim.

  37. YOU COUNT AS A FAILURE by Anonymous Coward · · Score: -1, Troll

    failure.

  38. The logs will be at slashnet.org by Motherfucking+Shit · · Score: 4, Informative

    For some reason, nobody ever bothers to mention where the logs of the Slashdot IRC forums get posted. After the IRC interview with CmdrTaco and Hemos a few months ago, it took me some digging to figure out where the log wound up.

    For those who can't make the chat, the log will eventually be at http://www.slashnet.org/forums/

    Editors: After the chat is over, any chance of having the log URL linked to the story text as an update?

    --
    "BSD: Free as in speech. Linux: Free as in beer. Windows 10: Free as in herpes." --Man On Pink Corner in #52607549.
  39. Lets make a bet... by Billly+Gates · · Score: 1, Interesting

    .. on how many hundreds of trolls from slashdot posting the ever so popular FreeBSD is dieing story and goatse.cx in ascii will head on over to the channel?

    Or better yet fooling the irc admins into thinking its a DDOS attack. :-)

    Wouldn't it be easier to use the handy slashdot moderation? I think CmdTaco would be willing to hand him 30 of the most highly rated questions.

  40. OT - GNU Tar question by Anonymous Coward · · Score: -1, Offtopic

    Is there a way to extract individual files from a tar archive without preserving the directory structure? I want something similar to unzip(1)'s command line modifier -j. This junks a file's archive path, and allows unzipping into the current directory.

    1. Re:OT - GNU Tar question by Anonymous Coward · · Score: 0

      Just open it up in winzip. I believe current versions of winzip support tar.gz archives.

    2. Re:OT - GNU Tar question by Anonymous Coward · · Score: 0

      Winzip's not exactly cross platform. What I need is individual extraction without regard to archive paths. .zip files are good at this, but I'm not certain how to do it with .tar files.

    3. Re:OT - GNU Tar question by Anonymous Coward · · Score: 0

      Winzip is too cross platform! It works on Windows 95, 98, ME, NT, XP, 2000, etc. What platform would you have in mind that it doesn't support?

    4. Re:OT - GNU Tar question by Anonymous Coward · · Score: 0

      I like WinZip the best. Your best bet would be to untar the archive and then repack it with WinZip. A little more trouble, but it make things easier in the long run.

    5. Re:OT - GNU Tar question by Anonymous Coward · · Score: 0

      Try Winzip. It should do it.

    6. Re:OT - GNU Tar question by Anonymous Coward · · Score: 0
      Nevermind, I concocted a hack that appears to do the job:
      tar xvf tar_file tar_element > temp; mv $(cat temp) ./
    7. Re:OT - GNU Tar question by Anonymous Coward · · Score: 0

      You should try Win Zip.

    8. Re:OT - GNU Tar question by Anonymous Coward · · Score: 0

      Too much typing. Get WinZip.

  41. What the fuck do you care? Really. by Anonymous Coward · · Score: -1, Offtopic

    I mean, who gives a fuck? These tools (Slashnet et al) are half-assed hack artists whose so-called contributions to modern computing are nothing more than fap-fodder for losers who can't find a way to make friends, create accomplishments, and so on.

    Fuck the chat logs. What's the matter with you? Go outside and get some fresh air. Ride a bike. Make a cake. Whatever... get away from your idiot box (and I don't mean the television).

    1. Re:What the fuck do you care? Really. by Anonymous Coward · · Score: -1

      Mr. Levin, step away from the computer.

  42. Holy shit this article is getting trolled to death by Anonymous Coward · · Score: -1, Offtopic

    As of 9:58pm PDT:

    -1 80 comments
    0 59 comments
    1 18 comments
    2 9 comments
    3 4 comments
    4 0 comments
    5 0 comments

    That's 77% of the comments modded at 0 or -1. And the 0's include such insightful comments as:

    *BSD for Windows XP?
    BSD is developed by idiots
    What I know about BSD (#10 is "It is dying")
    BSD Rap
    *BSD Sux0rs
    A copy of the cut-n-paste "bsd is dying" troll (the others are at -1)

    etc., etc., etc...

    This must be some kind of /. record. Does anyone have anything intelligent to say about BSD? Anyone? Anyone?

  43. Re:Holy shit this article is getting trolled to de by Anonymous Coward · · Score: -1, Offtopic

    Its not trolling, its just unfair moderation. Many of us are trying to post useful information for people considering BSD, so they can have some ubiased views to contrast with the pro-BSD propaganda. But the moderators don't appreicate that, since everyone has to be biased towards open-source.

  44. GUIs ARE FOR PUSSIES by Anonymous Coward · · Score: -1, Flamebait
  45. Linux Haiku by Anonymous Coward · · Score: -1, Troll

    • Linus Torvalds is
      perched on winter's maple tree,
      greased Yoda up ass.
    1. Re:Linux Haiku by Anonymous Coward · · Score: -1, Troll

      I, for one, welcome this as funny, not a troll.

  46. OMG KICK IT MOTHERFUCKER by Anonymous Coward · · Score: -1, Offtopic

    come on, come on

  47. Windows XP verus Dragon Fly BSD by Anonymous Coward · · Score: -1, Flamebait

    XP: Has the most advanced and easy to use GUI available.
    DFBSD: Has no GUI of note.

    XP: Supported by the world's largest and most trusted software company.
    DFBSD: Supported by a loser who got kicked off of the FreeBSD core team

    XP: Available for free preinstalled on computers from every major manufacturer.
    DFBSD: Available for free as an unstable source release that you have to compile yourself in C and then manually build your own base system.

    XP: Stable and reliable, and scalable from the desktop to the datacenter.
    DFBSD: Basically unusable due to major bugs. And it doesn't fix FreeBSD's SMP problems, so don't worry about running it on your server.

    XP: Everyone else uses it, so it has all the popular software.
    DFBSD: It runs...uh...vi...and...uhm...thats it actually...

    As you can see, Dragon Fly BSD is the clear choice!

    1. Re:Windows XP verus Dragon Fly BSD by Anonymous Coward · · Score: 0
      DFBSD: It runs...uh...vi...and...uhm...thats it actually...
      What more do you need? Well, add netcat to browse the internet. Study some of the RFCs for FTP, HTTP, and other net protocols and you're set.
  48. out of 123 comments... by Anonymous Coward · · Score: -1, Offtopic

    just over 20 have a score of 1 or higher...

    eesh.

  49. Thought for the day by Anonymous Coward · · Score: -1, Troll

    BSD is like the problem child dying of some rare incurable disease.

  50. I'LL RIP YOUR ASS CHEEKS APART by Anonymous Coward · · Score: -1, Troll

    THIS SCRATCH SHIT IS MAKING ME SHIT YOU BASTARD

    I GUARANTEE IT'S MAKING ME SHIT TOO

    NO SHIT YOU BASTARD FROM HELL

    YOU WANT TO FUCK A BABBOON GO RIGHT AHEAD IT'S NOT LIKE I'M GOING TO STOP YOU IT'S NOT LIKE I'M GOING TO JUMP YOUR STUPID BONES YOU COCKSUCKER

    GET REAL YOU FUCKING PISCES

    WHO WANTS TO COMPUTE SOME INTEGRALS

    Important Stuff:
    Please try to keep posts on topic.
    Try to reply to other people's comments instead of starting new threads.
    Read other people's messages before posting your own to avoid simply duplicating what has already been said.
    Use a clear subject that describes what your message is about.
    Offtopic, Inflammatory, Inappropriate, Illegal, or Offensive comments might be moderated. (You can read everything, even moderated posts, by adjusting your threshold on the User Preferences Page)
    If you want replies to your comments sent to you, consider logging in or creating an account.

    Problems regarding accounts or comment posting should be sent to CowboyNeal.Important Stuff:
    Please try to keep posts on topic.
    Try to reply to other people's comments instead of starting new threads.
    Read other people's messages before posting your own to avoid simply duplicating what has already been said.
    Use a clear subject that describes what your message is about.
    Offtopic, Inflammatory, Inappropriate, Illegal, or Offensive comments might be moderated. (You can read everything, even moderated posts, by adjusting your threshold on the User Preferences Page)
    If you want replies to your comments sent to you, consider logging in or creating an account.

    Problems regarding accounts or comment posting should be sent to CowboyNeal.Important Stuff:
    Please try to keep posts on topic.
    Try to reply to other people's comments instead of starting new threads.
    Read other people's messages before posting your own to avoid simply duplicating what has already been said.
    Use a clear subject that describes what your message is about.
    Offtopic, Inflammatory, Inappropriate, Illegal, or Offensive comments might be moderated. (You can read everything, even moderated posts, by adjusting your threshold on the User Preferences Page)
    If you want replies to your comments sent to you, consider logging in or creating an account.

    Problems regarding accounts or comment posting should be sent to CowboyNeal.Important Stuff:
    Please try to keep posts on topic.
    Try to reply to other people's comments instead of starting new threads.
    Read other people's messages before posting your own to avoid simply duplicating what has already been said.
    Use a clear subject that describes what your message is about.
    Offtopic, Inflammatory, Inappropriate, Illegal, or Offensive comments might be moderated. (You can read everything, even moderated posts, by adjusting your threshold on the User Preferences Page)
    If you want replies to your comments sent to you, consider logging in or creating an account.

    Problems regarding accounts or comment posting should be sent to CowboyNeal.

  51. fist pr0st! by skinney · · Score: -1, Offtopic

    uiu Topic (#forum): changed by ChanServ: Forum with Matthew Dillon of the DragonFly BSD Project is set for 6:00PM PDT on Thursday October 9th. (j0nkatz)

    -ChanServ(services@services.slashnet.org)- This channel has been registered with ChanServ.

    uiu mode/#forum [-o mod6] by ChanServ
    wh00p! fist prost!

  52. *BSD is dead?? by doobray · · Score: -1, Troll

    I TOLD you not to leave the hat on the bed!!

    1. Re:*BSD is dead?? by doobray · · Score: -1

      Troll??!! No way! just giving the much overdo Drugstore Cowboy reference.. I fully support and use BSD..

  53. you distractive bastards!! by Anonymous Coward · · Score: -1, Troll

    you'll ruin everything! don't you see!

  54. Re:Holy shit this article is getting trolled to de by Anonymous Coward · · Score: -1, Troll

    Well you know you can't argue with facts. FACT: BSD is dying.

  55. Re:Holy shit this article is getting trolled to de by Anonymous Coward · · Score: 0

    But what's your point? I don't see how BSD dying impacts upon what any of the BSDs can do right now... works fine.

    You're dying too, right? But you're still puttering along?

  56. And in other similar comparisment by Anonymous Coward · · Score: 0

    The Apple versus The Orange

    Apple: Comes in colors, Red, Green, Yellow.
    Orange: Only Yellow.

    Apple: Supports number of packaging formats such as pie, juice, caramel.
    Orange: Dramaticaly less number of packaging fomrats supported

    Apple: Rarely a perfect sphere
    Orange: Most of the time a perfect sphere, average orange can be represented with the following equation x^2+y^2+z^2=4

    Now, As you can see, Orange clearly is THE choice.

    1. Re:And in other similar comparisment by I+don't+want+to+spen · · Score: 1
      Yes, but Apple runs a better OS. And the Beatles recorded on the label, whereas the labels on ranges only say Jaffa ...

      Sorry, just taking the pith.

      --
      Don't go to a brothel if you want to buy broth
  57. Everytime you install BSD... by Anonymous Coward · · Score: -1, Troll

    ...God kills a kitten.

  58. BSD is evil by Anonymous Coward · · Score: -1, Troll

    BSD people worship daemons.

  59. Re:*BSD for Windows XP? Set up first! by ratfynk · · Score: 1, Funny
    First run a bsd boot floppy and use the set up command;

    dd if=dev/urandom of=dev/ad0

    this command will fix things up for you first.

    --
    OH THE SHAME I fell off the wagon and use sigs again!
  60. I for one..... by Anonymous Coward · · Score: -1

    I for one welcome our new BSD overlords...

  61. From his website - I'm a little frightened. by teamhasnoi · · Score: -1, Flamebait
    You're in a hurry, so you want PCs to respond faster. You do many things at once and wish your PCs could too. You want software that's more powerful, but also easier to use. You'd like more color. You're eager for your systems to communicate with other systems. You want improved reliability. And you want all this without obsoleting your investment in equipment, software and training.

    Well TOO BAD! STOP WHINING!

    Matthew Dillon brings you DragonFly BSD, the fastest and most gut-wrenchingly powerful operating system ever!

    EUNUCHS, PMS, Mac System X, AmigaDOS, Windoze XP2600, Linux, etc... don't even think about it! Give it up and GO HOME! We scoff! HA! All other operating systems cower and DELETE THEMSELVES due to their incredible relative lameness! Check it out!

    Real multitasking! Hundreds... even thousands of processes all running simultaneously in a non-stop BATTLE to the DEATH! The eventual winner burns itself into an EPROM and REIGNS FOREVER!!

    Over 500,000 levels of HIERARCHAL FILESYSTEM to be explored, complete with hundreds of SECRET INVISIBLE FILES!!

    An astounding 3-D GUI! Windows HURTLE open at BLINDING speeds to display cracked glass, piles of oozing gore, and UGLY HAGS who glare at users with the EVIL EYE! The GUI also features a mouse pointer shaped like a BLOODY KNIFE! The scroll bars are covered with MYSTICAL RUNES! Every file has TEN ICONS... but NINE of them are DEADLY TRAPS!!

    AUTOMATIC DISEASE SIMULATION! Every week, DragonFly BSD will create a new VIRUS to PLAGUE your valuable files! Each new virus is MORE POWERFUL than the last! Don't slack off... with DragonFly BSD, DOOM lurks around EVERY CORNER!

    Virtual reality? OLD NEWS! DragonFly BSD creates REAL reality with HIGH-SPEED SUBLIMINAL MESSAGES that ATTACK and DEVOUR the very MIND of the user!

    The world of DragonFly BSD will become your world too... AND YOU'LL LIKE IT!

  62. Simple Question by Anonymous Coward · · Score: -1, Offtopic

    Is there some special reason why *BSD submissions always get trolled? Look at how many comments are below 1 on a regular story, then check the *BSD stories. It seems to be especially obvious when it comes to DragonflyBSD. I don't understand what Matthew or anyone else has done to warrant this kind of reaction.
    You probably have to reply to this kind of question all the time on the *BSD part of /., but please explain. What the fsck is up?

    1. Re:Simple Question by Anonymous Coward · · Score: -1, Troll

      BSD is dying. Simple as that.

    2. Re:Simple Question by Anonymous Coward · · Score: -1, Offtopic

      So are you. Enjoy cancer.

    3. Re:Simple Question by Anonymous Coward · · Score: -1, Offtopic

      Not so simple an answer:

      3 Theories

      1) It is a couple of Linux fan-boys who think that for Linux to win, all others must loose.
      2) Mircosoft is somehow behind it.
      3) An ex-employee of BSDi is behind it.

      Whatever the reason, its been going on for 2+ years.

    4. Re:Simple Question by Anonymous Coward · · Score: 0

      Like I enjoyed your mother?

  63. How do you speak to the dead?? by Anonymous Coward · · Score: -1, Troll

    Well with *BSD .. they call it IRC.

  64. Linus Torvalds greased Yoda haiku by Anonymous Coward · · Score: -1

    • Linus Torvalds is
      perched on winter's maple tree,
      greased Yoda up ass.
  65. Haiku just for Linux by Anonymous Coward · · Score: -1
    • Linus Torvalds is
      perched on autumn's maple tree,
      greased Yoda up ass.
  66. Gay Linux Ass Association! by Anonymous Coward · · Score: -1
    Everyone shout the GLAA chant:

    • Linus Torvalds is
      perched on summer's maple tree,
      greased Yoda up ass.

  67. Gay Linux Asswiper's Assocation by Anonymous Coward · · Score: -1, Troll

    • Linus Torvalds is
      perched on the spring maple tree,
      greased Yoda up ass.

  68. GLAA members: grease up for Linux! by Anonymous Coward · · Score: -1, Troll

    Calling all GLAA members!
    • Are you gay?
    • Do you use Linux?
    • Are you a gay Linux user? (As if there's any other kind!)
    Every gay Linux user must attend the IRC chat, greased Yoda dolls in hand. Let's show those BSD folks how to properly grease our own assholes! This is meant as a peaceful protest by the Gay Linux Ass'n of America!

    Don't have a Yoda doll? Use the Linux penguin! That's even gayer than Yoda and greases up just fine. Why is "Tux" so fat? Because everyone "Tucks" their dick into its asshole and rams it full of cum. Linux fanboys all around the world line up with their greased dicks just waiting for a chance to drop their trousers and then tuck their tuckers into Tux.

  69. GLAA members: grease up for Linux! by Anonymous Coward · · Score: -1, Troll

    Calling all GLAA members!
    • Are you gay?
    • Do you use Linux?
    • Are you a gay Linux user? (As if there's any other kind!)
    Every gay Linux user must attend the IRC chat, greased Yoda dolls in hand. Let's show those BSD folks how to properly grease our own assholes! This is meant as a peaceful protest by the Gay Linux Ass'n of America!

    Don't have a Yoda doll? Use the Linux penguin! That's even gayer than Yoda and greases up just fine. Why is "Tux" so fat? Because everyone "Tucks" their dick into its asshole and rams it full of cum. Linux fanboys all around the world line up with their greased dicks just waiting for a chance to drop their trousers and then tuck their peckers into Tux.

  70. *BSD is growing! by Anonymous Coward · · Score: -1, Troll

    It is official; Netcraft now confirms: *BSD is growing

    One more crippling bombshell hit the already beleaguered Windows community when IDC confirmed that *BSD market share has risen yet again, now up to more than 30 percent of all servers. Coming on the heels of a recent Netcraft survey which plainly states that *BSD has gained more market share , this news serves to reinforce what we've known all along. *BSD is sending other OSes into complete disarray, as fittingly exemplified by topping the charts in the recent Sys Admin comprehensive networking test.

    You don't need to be a Daemon to predict *BSD's future. The hand writing is on the wall: *BSD faces a long and prosperous future. In fact there won't be any future at all for Linux because *BSD is growing. Things are looking very good for *BSD. As many of us are already aware, *BSD continues to gain market share. Red ink flows from RedHat like a river of blood.

    FreeBSD is the most loved of them all, having gained 93% more core developers. The sudden and pleasant release of the long developed 5.0 only serves to underscore the point more clearly. There can no longer be any doubt: FreeBSD is growing.

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

    OpenBSD leader Theo states that there are 70000 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 70000/5 = 14000 NetBSD users. BSD/OS posts on Usenet are about half of the volume of NetBSD posts. Therefore there are about 7000 users of BSD/OS. A recent article put FreeBSD at about 80 percent of the *BSD market. Therefore there are (70000+14000+7000)*4 = 364000 FreeBSD users. This is consistent with the number of FreeBSD Usenet posts.

    Due to the release of OSX, cool new technologies and so on, FreeBSD is expanding into more desktops than ever. FreeBSD has become more than the sum of its parts.

    All major surveys show that *BSD has steadily gained in market share. *BSD is very powerful and its long term survival prospects are very bright. If Windows is to survive at all it will be among OS dilettante dabblers. *BSD continues to improve. The progress achieved is nothing short of a miracle. For all practical purposes, *BSD is alive and kicking.

    Fact: *BSD will kick your ass

    1. Re:*BSD is growing! by Anonymous Coward · · Score: -1

      LOLz!!! Good one man!

  71. mascot abuse ... by Anonymous Coward · · Score: 0

    uff!
    what a super-pretty mascot!
    me really hopes they're not going to f#ck it up.
    would be a real shame.
    "firefly" sounds really innovative,
    but if this project fails they're going
    to take their mascot with them ... i hope the
    succed!

    1. Re:mascot abuse ... by Anonymous Coward · · Score: -1, Troll


      Don't have a Yoda doll? Use the Linux penguin! That's even gayer than Yoda and greases up just fine. Why is "Tux" so fat? Because everyone "Tucks" their dick into its asshole and rams it full of cum. Linux fanboys all around the world line up with their greased dicks just waiting for a chance to drop their trousers and then tuck their peckers into Tux.

  72. I'm with you ... 0%! by Anonymous Coward · · Score: 0

    Yeees, because he's thirsty, dammit!

  73. Please post a list of links to this 'unfair' mod? by Anonymous Coward · · Score: -1, Offtopic

    Go ahead. Please post links to all these 'unfair' moderations you claim is occuring in this story.

  74. First Question by BinBoy · · Score: -1, Troll

    a/s/l?

  75. GLAA members: grease up for Linux! by Anonymous Coward · · Score: -1, Troll

    Calling all GLAA members!
    • Are you gay?
    • Do you use Linux?
    • Are you a gay Linux user? (As if there's any other kind!)
    Every gay Linux user must attend the IRC chat, greased Yoda dolls in hand. Let's show those BSD folks how to properly grease our own assholes! This is meant as a peaceful protest by the Gay Linux Ass'in of America!

    Don't have a Yoda doll? Use the Linux penguin! That's even gayer than Yoda and greases up just fine. Why is "Tux" so fat? Because everyone "Tucks" their dick into its asshole and rams it full of cum. Linux fanboys all around the world line up with their greased dicks just waiting for a chance to drop their trousers and then tuck their peckers into Tux.
  76. Ladies and Gents, the rantings of GPL fans by Anonymous Coward · · Score: -1, Redundant

    Folks, remember that the parent rant comes from:

    Ruben I Safir ruben@mrbrklyn.com

    Brooklyn Linux Solutions

    DRM is THEFT - We are the STAKEHOLDERS http://fairuse.nylxs.com
    http://www.mrbrklyn.com - Consulting
    http://www.inns.net -- Happy Clients
    http://www.nylxs.com - Leadership Development in Free Software
    http://www2.mrbrklyn.com/resources - Unpublished Archive or stories and
    articles from around the net
    http://www2.mrbrklyn.com/downtown.html - See the New Downtown Brooklyn....

    1-718-382-0585

  77. Oh Linux! by Anonymous Coward · · Score: -1, Troll

    • Big greased Yoda doll,
      shoved ever so tightly in,
      Linux user screams.

  78. GLAA: Gay Linux Ass of America by Anonymous Coward · · Score: -1, Troll

    • Big greased Yoda doll,
      shoved ever so tightly in,
      Linux user's hole.

  79. Yoda loves Linux by Anonymous Coward · · Score: -1, Troll
    He went to the LUG in peace,
    to see all the nerds who were fleeced,
    "Linux sucks" he doth say,
    "in a terrible way",
    "But I'm glad that your assholes are greased!"
  80. Grease 'em up, Linux boys! by Anonymous Coward · · Score: -1, Troll


    Grease. Stuffed Yoda doll. Your asshole.

    Any questions?

  81. Linux Haiku by Anonymous Coward · · Score: -1, Troll

    • BSD Trollers
      wank with greased Linux fanboys.
      Yoda smells funny.

  82. Linux is dying! by Anonymous Coward · · Score: -1, Troll

    Tux lies prone on ground.
    Daemon stands overtop him.
    Grease pours from Tux-hole.

  83. My questions by Call+Me+Black+Cloud · · Score: -1, Offtopic
    1. While you received great reviews for Rumblefish, you followed that up with a role in The Flamingo Kid. Do you think TFK was the reason for a downturn in your career and will "Employee of the Month" revive it?
    2. Better to work with: Christina Applegate, Cameron Diaz, Neve Campbell, or Bronson Pinchot?
    Thanks, I'll take my answers off the air.
  84. Yep it is by Anonymous Coward · · Score: -1, Troll

    Keep your pedantic legalisms up your ass where you keep strangers' cocks.

    Morally it is stealing.

    Douchebag.

    1. Re:Yep it is by Anonymous Coward · · Score: -1, Offtopic

      LOL.

      You swear in public yet purport to know of morals?

      ROTFLMAO.

      Thank god you got -1 troll.

      Dumbshit.

    2. Re:Yep it is by Anonymous Coward · · Score: 0

      You swear in public yet purport to know of morals?

      Oh, so morals is all about the words you choose? Don't be an idiot.

  85. GOATSE LINK ABOVE by Anonymous Coward · · Score: -1, Troll

    Mod DOWN!!!!!!!!!!Lameness filter encountered. Post aborted!
    Reason: Please use fewer 'junk' characters.

    Re focusHow can you do 'New Math' problems with an 'Old Math' mind? -- Charles Schulz

    rss

  86. Re:Holy shit this article is getting trolled to de by Anonymous Coward · · Score: -1, Troll

    It's really simple, Linux sux so badly that they have to troll BSD. If they had a quality product in Linux then they would have actual factual arguments against BSD. Instead they act like big babies because Linux is used by big baby blockheads and Slashdot attracts those big baby blockhead Linux users and they troll BSD. Simple, no?

  87. I, for one, by Anonymous Coward · · Score: 0

    I, for one, welcome our new zombie BSD overlords

  88. CowboyNeal has a million mod points... by Anonymous Coward · · Score: -1, Troll

    Did you see what that overweight monster did to this article's comments? Jesus... he took a flamethrower called "Overrated" to this place. Nice work. Apply the same impetus to a diet!

  89. Future Architecture Idea by aphor · · Score: 1

    It seems to me that your SMP (Symmetric) kernel could just as easily (with a kernel module or something) become AMP (Asymmetric): creating one class of thread on a particular class of processor. What I mean is the loader would create an executable main memory thread/object tagged for a DSP or a x86 or an AMD64 or PPC processor, and the kernel would be able to execute these tagged objects on specific processors on expansion cards or a remote host or a FC WWPN target or such craziness..

    --
    --- Nothing clever here: move along now...
  90. FUCK by Anonymous Coward · · Score: 0

    YOU