Slashdot Mirror


FreeBSD 5.1 Review and BSD Roundup

securitas writes "Both eWEEK's review of FreeBSD 5.1 and ExtremeTech's BSD overview and roundup (single page) will be of interest to BSDers and anyone else who wants to explore their open source OS options. The review of FreeBSD 5.1 says it lacks the stability of v4.8 but adds features that some may find useful (for example, more processor architectures are supported) so it shouldn't be considered for critical deployments yet. And the BSD round-up speaks for itself."

385 comments

  1. I tried it, I liked it by _narf_ · · Score: 4, Informative

    A lot more polish than the 5.0 release.

    Also a lot more of the new stuff on by default.

    --
    Have you painted a shed today?
    1. Re:I tried it, I liked it by AndroidCat · · Score: 2, Interesting

      I did have some problems with older hardware, but that was the "install out of the box and see what happens" pass rather than the "pot of heavy-duty coffee and read the docs carefully" pass. Time for coffee, I guess. :^)

      --
      One line blog. I hear that they're called Twitters now.
    2. Re:I tried it, I liked it by _narf_ · · Score: 5, Informative

      Speaking of hardware issues, VMWare doesn't like some of the ways FreeBSD performs some operations now. You need to recompile the kernel with an option to disable use of CMPXCHG to get it to run ok.

      Basically it'll just keeeep sloooowiing doooown.

      But you can fudge through the install easily enough by suspending/resuming the VM, which will bring it back to speed. You need to do it a few times mind you as it keeps slowing down. :/

      --
      Have you painted a shed today?
    3. Re:I tried it, I liked it by craig2787 · · Score: 5, Funny

      I checked the website, and there is no indication that any more code came from Poland in this release than 5.0.

    4. Re:I tried it, I liked it by minus_273 · · Score: 1, Funny

      hey, what do you mean alot more POLISH? are you some kind of racist? oh polish, i see .. sorry

      --
      The war with islam is a war on the beast
      The war on terror is a war for peace
    5. Re:I tried it, I liked it by the_consumer · · Score: 0, Offtopic

      Hey Fucko, The Polish aren't a race, they're a nationality.

      --
      "If you're thinking what I'm thinking, you're right." -
    6. Re:I tried it, I liked it by minus_273 · · Score: 1

      sheesh. get a sense of humor. Polish !=polish

      --
      The war with islam is a war on the beast
      The war on terror is a war for peace
    7. Re:I tried it, I liked it by Anonymous Coward · · Score: 0

      hey cool, thanks for the tip, I had problems with this myself .. though in my case it just ran very fast, about 1.5 seconds per real second. I just changed the a sysctl for ticks per second (apparently it uses a different timer than 4.8) and now it is fairly stable, I even have ntp keeping the clock set within VMWare.

    8. Re:I tried it, I liked it by Solosoft · · Score: 1

      It took this many posts for a BSD is dying !!
      Wow ... you's are slacking ... We all know it's dying nothing like a little reminder

    9. Re:I tried it, I liked it by AndyElf · · Score: 1

      It is on by default in 5.x releases -- this has been discussed on the lists 6 months ago, if not more.

      --

      --AP
    10. Re:I tried it, I liked it by Anonymous Coward · · Score: 0

      The old crappy poker AI has a pretty good shot at winning. But read other people's messages before posting your own to avoid simply duplicating a better feature would be a tutorial. Replies to your comments are sent to you, yet the Go project announces its formation and the release today to the worldwide open source development community. It has some good points, and I think it sums up what many of us know, but haven't quite been able to put into words yet.

    11. Re:I tried it, I liked it by Anonymous Coward · · Score: 0
      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 in the recent Sys Admin comprehensive networking test.

      You don't need to be a Kreskin 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 only could be among oddball OS hobbyist dabblers. *BSD continues to decay. Nothing short of a miracle could save it at this point in time. For all practical purposes, *BSD is dead.

      Fact: *BSD is dead

    12. Re:I tried it, I liked it by Anonymous Coward · · Score: 0
      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 only could be among oddball OS hobbyist dabblers. *BSD continues to decay. Nothing short of a miracle could save it at this point in time. For all practical purposes, *BSD is dead.

      Fact: *BSD is dead

    13. Re:I tried it, I liked it by Anonymous Coward · · Score: 0

      It's dead. Get over it.

    14. Re:I tried it, I liked it by flashz · · Score: 1

      Which version of VMWARE ? I havn't got the 4 to run under FreeBSD

    15. Re:I tried it, I liked it by Anonymous Coward · · Score: 0

      Ok. BSD RIP.

    16. Re:I tried it, I liked it by Anonymous Coward · · Score: 0

      death is not pretty, is it?

  2. I'm not sure I get the analogy by Surak · · Score: 4, Funny

    One might well be justified in calling BSD the "Mr. Chips" of operating systems. In the final scene of the classic movie "Goodbye, Mr. Chips", a doctor remarks that it is a shame that the title character -- a masterful schoolteacher now on his death bed -- has never had children. Referring to the many youngsters whose lives he had helped to shape, Mr. Chips replies that he has indeed had children... thousands of them.

    I'm not sure I get the analogy, but I *think* he just said *BSD is dying. ;)

    1. Re:I'm not sure I get the analogy by vandel405 · · Score: 3, Insightful

      And that a bunch of other OS's use it's code, that's what's meant by the children part.

    2. Re:I'm not sure I get the analogy by rootofevil · · Score: 1

      thats probably better applied to the original unix, which has inspired a great many operating systems.

      --
      turn up the jukebox and tell me a lie
    3. Re:I'm not sure I get the analogy by SugoiMonkey · · Score: 1

      I don't know what the hell you are talking about. I have found FreeBSD more friendly than any of the so-called friendly linuxes out there. If more people gave it a try I'm sure there would be more *BSD users. It's easy to install, programs are easy to install, and thank God it doesn't make me l33t...well, not upon installation at least...

    4. Re:I'm not sure I get the analogy by Anonymous Coward · · Score: 0

      I don't use Linux because all the distributions suck. If there was a Linux distribution as good and well organized as FreeBSD then I might consider using it.

    5. Re:I'm not sure I get the analogy by evronm · · Score: 1
      Mr. Chips replies that he has indeed had children... thousands of them.

      So he was a pedophile?

    6. Re:I'm not sure I get the analogy by Anonymous Coward · · Score: 0
      The End Of FreeBSD

      [ed. note: in the following text, former FreeBSD developer Mike Smith gives his reasons for abandoning FreeBSD]

      When I stood for election to the FreeBSD core team nearly two years ago, many of you will recall that it was after a long series of debates during which I maintained that too much organisation, too many rules and too much formality would be a bad thing for the project.

      Today, as I read the latest discussions on the future of the FreeBSD project, I see the same problem; a few new faces and many of the old going over the same tired arguments and suggesting variations on the same worthless schemes. Frankly I'm sick of it.

      FreeBSD used to be fun. It used to be about doing things the right way. It used to be something that you could sink your teeth into when the mundane chores of programming for a living got you down. It was something cool and exciting; a way to spend your spare time on an endeavour you loved that was at the same time wholesome and worthwhile.

      It's not anymore. It's about bylaws and committees and reports and milestones, telling others what to do and doing what you're told. It's about who can rant the longest or shout the loudest or mislead the most people into a bloc in order to legitimise doing what they think is best. Individuals notwithstanding, the project as a whole has lost track of where it's going, and has instead become obsessed with process and mechanics.

      So I'm leaving core. I don't want to feel like I should be "doing something" about a project that has lost interest in having something done for it. I don't have the energy to fight what has clearly become a losing battle; I have a life to live and a job to keep, and I won't achieve any of the goals I personally consider worthwhile if I remain obligated to care for the project.

      Discussion

      I'm sure that I've offended some people already; I'm sure that by the time I'm done here, I'll have offended more. If you feel a need to play to the crowd in your replies rather than make a sincere effort to address the problems I'm discussing here, please do us the courtesy of playing your politics openly.

      From a technical perspective, the project faces a set of challenges that significantly outstrips our ability to deliver. Some of the resources that we need to address these challenges are tied up in the fruitless metadiscussions that have raged since we made the mistake of electing officers. Others have left in disgust, or been driven out by the culture of abuse and distraction that has grown up since then. More may well remain available to recruitment, but while the project is busy infighting our chances for successful outreach are sorely diminished.

      There's no simple solution to this. For the project to move forward, one or the other of the warring philosophies must win out; either the project returns to its laid-back roots and gets on with the work, or it transforms into a super-organised engineering project and executes a brilliant plan to deliver what, ultimately, we all know we want.

      Whatever path is chosen, whatever balance is struck, the choosing and the striking are the important parts. The current indecision and endless conflict are incompatible with any sort of progress.

      Trying to dissect the above is far beyond the scope of any parting shot, no matter how distended. All I can really ask of you all is to let go of the minutiae for a moment and take a look at the big picture. What is the ultimate goal here? How can we get there with as little overhead as possible? How would you like to be treated by your fellow travellers?

      Shouts

      To the Slashdot "BSD is dying" crowd - big deal. Death is part of the cycle; take a look at your soft, pallid bodies and consider that right this very moment, parts of you are dying. See? It's not so bad.

      To the bulk of the FreeBSD committerbase and the developer community at large - keep your eyes on the real goals. I

    7. Re:I'm not sure I get the analogy by mdew · · Score: 1, Funny
      --
      http://www.fanboy.co.nz/adblock/
  3. FreeBSD is good by Anonymous Coward · · Score: 1

    I highly recomment FreeBSD for both a server and a desktop. Doesn't have all the support as Linux has, but on the other hand, Linux doesn't have all the support that Windows has. So speaking as an OS offering, it is a very nice and good UNIX.

  4. I always recommend FreeBSD by Jack+Wagner · · Score: 5, Funny
    As a long time IT professional I recommend FreeBSD all the time. I'll go into meetings where people are just crying for me to help them gain synergy by decreasing their TCO while at the same time increasing their ROI, yet these people look like a deer caught in the headlights when I flat out tell them that the only way to do that is by looking at taking the next step to the next level by integrating their asset management supply side relationships into leveraged content delivery paradigms, with an eye towards aligning their collaborative relationship initiatives towards common goals and the first step in that direction is to move to an OS that has Olog(n)performance, namely FreeBSD.

    I've been able to do this in the past with a a few Fortune 500 companies by implementing a strict B2C affinity marketing plan which relies heavily on E-mediation performance metrics, something that not everyone is willing to go through.

    In short, don't even come to me with questions about your Value chain collaborative commerce unless you're willing to pay the piper and upgrade to FreeBSD because this is not your daddy's economy and you'll get nowhere by running legacy operating systems. Times have changed and unless you're willing to change with them you'll be left behind wondering what the hell happened to all your profits.

    Warmest regards,

    --Jack

    --


    Wagner LLC Consulting Co. - Getting it right the first time
    1. Re:I always recommend FreeBSD by Stone316 · · Score: 1

      Yeah, what he said!

      --
      "Thanks to the remote control I have the attention span of a gerbil."
    2. Re:I always recommend FreeBSD by mdowling · · Score: 1

      ew... you said 'synergy'.

    3. Re:I always recommend FreeBSD by Anonymous Coward · · Score: 0

      Is this a joke post. Or a posting by an unemployed venture capitalist for scam.com yearning for the pretentious cocktail party acronym barf lingo from the tech Ponzi scheme of the late 90s.

      Sounds like the PR department of CommerceOne in a permanent coma from the day it was trading at $300 per share.

    4. Re:I always recommend FreeBSD by Anonymous Coward · · Score: 0

      is not

    5. Re:I always recommend FreeBSD by Anonymous Coward · · Score: 0

      "a boss 69 camaro" ... ha!

    6. Re:I always recommend FreeBSD by Viol8 · · Score: 1

      You figure it out you halfwit.

  5. YFI!!! by usotsuki · · Score: 0, Flamebait

    Proof that BSD is alive and kicking despite the recurring claim that it is dead.

    No dead program comes out in new releases.

    Ha!

    -uso.

    --
    Dreams, dreams, don't doubt dreams, dreaming children's dreaming dreams. Sailor Moon SS
  6. Sounds familiar... by goldspider · · Score: 5, Funny
    "The review of FreeBSD 5.1 says it lacks the stability of v4.8 but adds features that some may find useful so it shouldn't be considered for critical deployments yet."

    Isn't this what has been said about Windows for quite some time?

    --
    "Ask not what your country can do for you." --John F. Kennedy
    1. Re:Sounds familiar... by Anonymous Coward · · Score: 0
      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.

  7. A review or a re-write of the 5.1 release notes? by swb · · Score: 2, Funny

    Give me a break. Somebody gets paid for doing that kind of work, and a title like "Senior Analyst"?

  8. Well duh.... by Alan+Hicks · · Score: 5, Informative

    The review of FreeBSD 5.1 says it lacks the stability of v4.8

    That's why it's 5.1-CURRENT and not 5.1-STABLE. That's like saying version 2.5.60 of the linux kernel lacks the stability of version 2.4.21.

    --
    Slackware, what else when it must be secure, stable, and easy?
    1. Re:Well duh.... by Anonymous Coward · · Score: 1, Informative

      Incorrect. It's 5.1-RELEASE.

      http://www.freebsd.org/releases/5.1R/announce.ht ml

    2. Re:Well duh.... by phoenix_rizzen · · Score: 4, Informative

      It's still part of the -CURRENT branch, though. The -STABLE branch is still 4.x.

      The 5.x codebase will not be made -STABLE until at least 5.2 or 5.3.

      -RELEASE is nothing more than a snapshot of *either* -CURRENT or -STABLE.

    3. Re:Well duh.... by CoolVibe · · Score: 1
      No, it's part of the RELENG_5_1 branch. CURRENT is the head branch. Sure, it's not stable, but it's a RELEASE and does get maintained seperately, just like the RELENG_4_[something] branches are being maintained.

      Note that no new features are added to the RELENG_[Major]_[Minor] branches, just bugfixes and security updates.

    4. Re:Well duh.... by Anonymous Coward · · Score: 1, Interesting
      The End of FreeBSD

      [ed. note: in the following text, former FreeBSD developer Mike Smith gives his reasons for abandoning FreeBSD]

      When I stood for election to the FreeBSD core team nearly two years ago, many of you will recall that it was after a long series of debates during which I maintained that too much organisation, too many rules and too much formality would be a bad thing for the project.

      Today, as I read the latest discussions on the future of the FreeBSD project, I see the same problem; a few new faces and many of the old going over the same tired arguments and suggesting variations on the same worthless schemes. Frankly I'm sick of it.

      FreeBSD used to be fun. It used to be about doing things the right way. It used to be something that you could sink your teeth into when the mundane chores of programming for a living got you down. It was something cool and exciting; a way to spend your spare time on an endeavour you loved that was at the same time wholesome and worthwhile.

      It's not anymore. It's about bylaws and committees and reports and milestones, telling others what to do and doing what you're told. It's about who can rant the longest or shout the loudest or mislead the most people into a bloc in order to legitimise doing what they think is best. Individuals notwithstanding, the project as a whole has lost track of where it's going, and has instead become obsessed with process and mechanics.

      So I'm leaving core. I don't want to feel like I should be "doing something" about a project that has lost interest in having something done for it. I don't have the energy to fight what has clearly become a losing battle; I have a life to live and a job to keep, and I won't achieve any of the goals I personally consider worthwhile if I remain obligated to care for the project.

      Discussion

      I'm sure that I've offended some people already; I'm sure that by the time I'm done here, I'll have offended more. If you feel a need to play to the crowd in your replies rather than make a sincere effort to address the problems I'm discussing here, please do us the courtesy of playing your politics openly.

      From a technical perspective, the project faces a set of challenges that significantly outstrips our ability to deliver. Some of the resources that we need to address these challenges are tied up in the fruitless metadiscussions that have raged since we made the mistake of electing officers. Others have left in disgust, or been driven out by the culture of abuse and distraction that has grown up since then. More may well remain available to recruitment, but while the project is busy infighting our chances for successful outreach are sorely diminished.

      There's no simple solution to this. For the project to move forward, one or the other of the warring philosophies must win out; either the project returns to its laid-back roots and gets on with the work, or it transforms into a super-organised engineering project and executes a brilliant plan to deliver what, ultimately, we all know we want.

      Whatever path is chosen, whatever balance is struck, the choosing and the striking are the important parts. The current indecision and endless conflict are incompatible with any sort of progress.

      Trying to dissect the above is far beyond the scope of any parting shot, no matter how distended. All I can really ask of you all is to let go of the minutiae for a moment and take a look at the big picture. What is the ultimate goal here? How can we get there with as little overhead as possible? How would you like to be treated by your fellow travellers?

      Shouts

      To the Slashdot "BSD is dying" crowd - big deal. Death is part of the cycle; take a look at your soft, pallid bodies and consider that right this very moment, parts of you are dying. See? It's not so bad.

      To the bulk of the FreeBSD committerbase and the developer community at large - keep your eyes on the real goals. It'

    5. Re:Well duh.... by znode · · Score: 1
      No, it's part of the RELENG_5_1 branch.
      No, you're just playing with the word "branch", and you know it.

      RELENGS are not the same "sized" branches as CURRENT and STABLE. A RELENG is a "twig" of either a CURRENT branch or a STABLE branch, and RELENG from CURRENT is not as stable as a RELENG from STABLE.

      You can argue that "technically it is defined as a branch", but if everyone argued classifications I dont' think humanity would exist.
    6. Re:Well duh.... by Anonymous Coward · · Score: 0
      Please make a note in your day-planner:
      *BSD is dying.
      Get with the program. It's dead.
  9. Re:first post by Anonymous Coward · · Score: 0

    Nope, sorry.

  10. D - E - A - D by siskbc · · Score: 1
    I'm not sure I get the analogy, but I *think* he just said *BSD is dying. ;)

    Don't swallow everything you read. If it doesn't come from Netcraft, I'm not believing it. What? Oh.

    BSD is dead! Long live BSD...

    --

    -Looking for a job as a materials chemist or multivariat

  11. FreeBSD should support more NICs than ARCHes by mnmn · · Score: 3, Interesting


    Part of the reason why Linux is in a better market position than FreeBSD is the range of hardware supported by Linux. For instance FreeBSD supports only two ATM cards and no Tokenring cards, while people have done fancy things using Linux with both networks.

    --
    "Give orange me give eat orange me eat orange give me eat orange give me you." -Nim Chimpsky
    1. Re:FreeBSD should support more NICs than ARCHes by Anonymous Coward · · Score: 2, Informative

      Are you kidding? FreeBSD supported both PCMCIA and USB _literally_ years before Linux.

    2. Re:FreeBSD should support more NICs than ARCHes by Anonymous Coward · · Score: 2, Informative

      Tokenring?!? Please tell me you are joking. Even the most decrepit IT manager knows that tech has long been dead.

      Also, FreeBSD supports more then two ATM cards:

      Efficient Networks, Inc. ENI-155p ATM PCI Adapters (hea driver)

      FORE Systems, Inc. PCA-200E ATM PCI Adapters (hfa driver)

      IDT 77201/211 NICStAR ATM Adapters (idt driver)

      FORE Systems, Inc. LE155 ATM Adapter (idt driver)

      --EG

    3. Re:FreeBSD should support more NICs than ARCHes by smnolde · · Score: 1

      Too few? How about one too many!

      One day when I get commit access I'm gonna remove if_rl.c and solve a lot of problems.

    4. Re:FreeBSD should support more NICs than ARCHes by Arandir · · Score: 2, Funny

      Those two people out there still using Tokenring will just have to stick with Linux then...

      --
      A Government Is a Body of People, Usually Notably Ungoverned
    5. Re:FreeBSD should support more NICs than ARCHes by jo42 · · Score: 2, Interesting

      Is that why most, if not all of the Linux WiFi drivers originally started off being pinched from FreeBSD?

    6. Re:FreeBSD should support more NICs than ARCHes by CoolVibe · · Score: 1
      No please don't. I actually need if_rl.c, since I own and use those wretched RealTek NICs. Actually, removing it will actually cause a lot more problems that it would solve...

      Oh, and if_rl.c is great reading material. I love how the comments in that file blast RealTek to hell and back. :)

    7. Re:FreeBSD should support more NICs than ARCHes by LWATCDR · · Score: 1

      You might be suprised how many places still have token ring networks. Some times it is not so easy to just rip out everthing and put in all new stuff. Would I kill myself adding support for it to bsd? Not really.

      --
      See my blog http://ilovecookes.blogspot.com/ for light hearted technical information.
    8. Re:FreeBSD should support more NICs than ARCHes by Anonymous Coward · · Score: 0

      Not much good to support an interface type if you don't have support for the devices that connect to them. FreeBSD wouldn't work with my PCMCIA modem/NIC, whereas OpenBSD would. Go figure.

    9. Re:FreeBSD should support more NICs than ARCHes by tarius8105 · · Score: 0

      I take it you run Linux for tokenring support too?

    10. Re:FreeBSD should support more NICs than ARCHes by forged · · Score: 2, Insightful
      You obviously haven't been visiting a IBM facility lately. Call me troll or flamebait, but I was on assignment there for a couple of weeks and I was told to make sure to bring a PCMCIA token-ring card for my laptop, to get any sort of connectivity (which of course I did).

      The funny thing there was that the token-ring network was so slow that the 56K modem integrated to my laptop was actually faster for accessing my email..... However the several hundreds employees still working there didn't have much of a choice. Remember, token-ring was very expensive and state-of-the-art 10 years ago.

      The facility is now being migrated to a switched network deploying fast-ethernet, but planning and implementation will take months because the installed token-ring base is so huge.

    11. Re:FreeBSD should support more NICs than ARCHes by forged · · Score: 1

      Facilities requiring token-ring didn't wait for *BSD to implement drivers (which it doesn't if I understand your post correctly) but would have deployed something equivalent i.e. commercial unix of some sort, OS/2, even perhaps Linux...?

    12. Re:FreeBSD should support more NICs than ARCHes by Anonymous Coward · · Score: 0

      Yes! And it STILL doesn't support USB joypads. Seriously. Some of us like to play emulators on our desktop boxes, so that's a very nice feature to have (and one of the main reasons I use Linux instead of FreeBSD).

    13. Re:FreeBSD should support more NICs than ARCHes by mnmn · · Score: 1

      Linux's tokenring support is broken when you route multiple ethernets and one tokenring card in one box. I tried the 2.2, 2.4.20, 2.5.67 but after some heavy duty routing using SNAT with ipfilters the thing crashes on multiple test machines with different tr cards. Ive tried the olicom tr for the FreeBSD 4.7 and that crashes with heavy traffic too.

      I'm completely stuck with a demo version of Solaris 8.0 x86 for that purpose.

      --
      "Give orange me give eat orange me eat orange give me eat orange give me you." -Nim Chimpsky
    14. Re:FreeBSD should support more NICs than ARCHes by mnmn · · Score: 1

      You can get 16 speed pci tr cards for $2, and their 24-port switches for $14. Now do you see all the 'student' linux users with cheap homelans and throwaway 486 computers using tokenring?

      TokenRing is far from dead. Its only not talked much about. Heck I even use Arcnet and am proud of it. :)

      --
      "Give orange me give eat orange me eat orange give me eat orange give me you." -Nim Chimpsky
    15. Re:FreeBSD should support more NICs than ARCHes by Ded+Bob · · Score: 1

      You obviously haven't been visiting a IBM facility lately.

      Which one? I thought they had all switched to ethernet.

    16. Re:FreeBSD should support more NICs than ARCHes by Brooks+Davis · · Score: 1

      Olicom Tokenring cards are support and have been for some time.

      -- Brooks

      --
      -- Any statement of the form "X is the one, true Y" is FALSE.
    17. Re:FreeBSD should support more NICs than ARCHes by Anonymous Coward · · Score: 0

      La Gaude.

    18. Re:FreeBSD should support more NICs than ARCHes by parc · · Score: 1

      Note also that the rl driver just had some updates for the newer 8139C(i think) chipset. According to the driver writer, the new chipset is reall pretty good.

    19. Re:FreeBSD should support more NICs than ARCHes by The+Vulture · · Score: 1

      It's been about five years since I've worked at IBM, but I recall at IBM Canada, they were heavily standardized on Token Ring, OS/2 and using their own brand of PC's. The IT people had the job of putting in a 4/16 Token Ring card in every new PC that came into the building. Many of the PC's didn't even have Ethernet cards (they were mostly useless in the building).

      If they're still on Token Ring now though, somebody should shoot them. I remember, it used to be fun whenever somebody kicked out their Token Ring connection. Also, as I recall, it was not very fault tolerant... I was running an application that relied on LAN connections, but kicked out the Token Ring by mistake. Not only was their a loud beeping that everybody in the classroom could hear, but the program couldn't re-establish it's connection. It was a pain to go to each machine by hand and grab the test results. Now yes, I realize that it could have been an application problem, but that problem seemed to plague many applications running on the Token Ring network.

      Just a rant about my good old times at IBM...

      -- Joe

    20. Re:FreeBSD should support more NICs than ARCHes by MyHair · · Score: 2, Funny

      I was told to make sure to bring a PCMCIA token-ring card for my laptop ... the token-ring network was so slow ...

      Apparently you should've brought your own token, too.

      (Wishing I knew how to find a link to that Dilbert strip where PHB is searching his office for the token.)

    21. Re:FreeBSD should support more NICs than ARCHes by LWATCDR · · Score: 1

      If they are using odds are they are still using OS/2 or even an AS400.

      --
      See my blog http://ilovecookes.blogspot.com/ for light hearted technical information.
    22. Re:FreeBSD should support more NICs than ARCHes by pingbak · · Score: 2, Interesting

      Tell me that this is the only reason you can't/won't use *BSD... if it is, it's pretty weak.

      ATM just sucks. Yes. Yes it does. I worked on ATM, I worked on various ATM deployments. It sucks. I have the scars to proove it.

      TokenRing, which is a neat graduate network course topic, is largely irrelevant, even it's cheap.

      Can't you think of a better reason to **not** use BSD?

    23. Re:FreeBSD should support more NICs than ARCHes by TheLink · · Score: 1

      Uh. But why when I can get a NEW 10/100 Mbps ethernet card for the equivalent of USD6.50? New with warranty etc.

      And a new 5 port switch goes for USD20 to 25. 8 port switch for not much more.

      If you want old ethernet stuff you can get it for less than half the price of new stuff. We recently got some old 10/100Mbps NICs for about USD2.50 each.

      --
    24. Re:FreeBSD should support more NICs than ARCHes by Anonymous Coward · · Score: 0
      dead men's club
      • BSD
      • OS2
      • CP/M
      • MSDOS
      • BeOS
      • Multics
  12. Flash 'n' Trash by SavoWood · · Score: 5, Interesting

    I started reading the article, and found the summation of why I prefer BSD.

    ...the BSDs have always been the choice of system administrators who cared more about integrity, security, and reliability, than sizzle and flash.
    --
    Plant a tree in a developing country.
    1. Re:Flash 'n' Trash by Ezdaloth · · Score: 1

      You forgot consistency. Since the whole base OS comes from one distributor in one piece, it is often more logically consistent and things work together better, than with an OS where loose parts are scraped together from different distributors.

    2. Re:Flash 'n' Trash by jo42 · · Score: 1

      Agreed. Not to mention the total lack of bloatware (RedHat, SuSE, etc. are bigger bloat, waste of disk space, than any Microsloth offering).

    3. Re:Flash 'n' Trash by Anonymous Coward · · Score: 0

      These types of BSD folks are delusional. You can get the same integrity, security, and reliability out of pretty much any Unix OS.

    4. Re:Flash 'n' Trash by eric76 · · Score: 1

      I don't even bother to install X Windows on most of my OpenBSD machines.

    5. Re:Flash 'n' Trash by Anonymous Coward · · Score: 0

      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
      .
    6. Re:Flash 'n' Trash by Anonymous Coward · · Score: 0

      Which is quite understandable. Since you cannot run Mozilla on it, no point installing it.

    7. Re:Flash 'n' Trash by eric76 · · Score: 1

      You can't?

      There's one in the ports tree. But I never tried to build it.

    8. Re:Flash 'n' Trash by tigga · · Score: 1
      These types of BSD folks are delusional. You can get the same integrity, security, and reliability out of pretty much any Unix OS.

      Yes, you can. But you have to spend a lot of time reconfiguring system to bring it to the same level as BSDs have right after install.

  13. Architecture by Anonymous Coward · · Score: 0

    Adding more then just the Alpha and Intel chip was a smart move. With the support of SPARC Linux being given up bu both RedHat AND SUSE IT folks in a mixed environment(SPARC / Intel / Alpha) have both a choice and a consistent OS to use. Yes, this was available on the the other BSDs since they supported
    more then one or two platforms.

    --EG

    1. Re:Architecture by agent+dero · · Score: 1

      Sparc has been supported for a while by FreeBSD.

      If fact, I believe redhat last supported the sparc platform in 6.2 Zoot release.

      I also believe that redhat is now up to at least version 8

      Think twice before you talk about how supportive of multiple OSes those linuxes are. Albeit, SuSE and redhat have great i386 support, and decent Alpha support (7.2)

      --
      Error 407 - No creative sig found
    2. Re:Architecture by Anonymous Coward · · Score: 0

      Ultrasparc support (not 32 bit sparcs) is coming along quite well, but not in FreeBSD-STABLE. As for Linux support of non-i386 architectures, I have little knowledge of what the various distros support beyond i386. Slackware is crap and Debian seems somewhat behind the times too. You'd think the Linux zealots out there would do a better job of maintaining their distros. Redhat is bloatware and gentoo won't even boot. If you want non-i386 support, check out NetBSD or OpenBSD.

  14. UNIX on steroids by geekmetal · · Score: 0, Redundant

    Truly the UNIX on steroids, has had a pioneering role in the evolution of the *nix operating systems.

    Sad indeed that such a good system is dying.

    ----

    --
    There are two kinds of egotists: 1) Those who admit it 2) The rest of us
  15. the article itself is sort of flamebait by itself. by ketamine-bp · · Score: 5, Insightful

    the article is way too pro-BSD to be said, and is comparing apple (linux, kernel sense) with oranges (BSD, distribution-sense).

    Though being a BSD-user (OpenBSD server & MacOSX desktop), I feel uneasy to read all those, esp. the 'linux-copy-bsd' phrase.

  16. FreeBSD: 9 out of 10 CLECs and ISPs choose FBSD by Anonymous Coward · · Score: 0

    I did not like this comment one bit in the article. "In fact, as far as anyone knows, only one worm has ever been developed that attacked any of the BSDs."

    What is the point of that? He should not step outside his specialty...

    Otherwise i liked the article, rehashed well known points, but good to see press for 5.*.

    man jail, on freebsd 4.8 or 5.1. You will be very pleased with it. Virtual servers are nice.

    later

  17. Sorry, but YFI by usotsuki · · Score: 4, Informative
    --
    Dreams, dreams, don't doubt dreams, dreaming children's dreaming dreams. Sailor Moon SS
    1. Re:Sorry, but YFI by AvengerXP · · Score: 1

      Sorry, but that's FYI.

      --
      Trolls dont like to be Flamebait, because they burn so well. Protect our Troll heritage!
    2. Re:Sorry, but YFI by pboulang · · Score: 3, Funny

      Didn't we all read that as "YFI: You're Fucking Insane"?

      --

      This comment is guaranteed*

      *not guaranteed

    3. Re:Sorry, but YFI by usotsuki · · Score: 1

      It's YFI - "you fail it".

      -uso.

      --
      Dreams, dreams, don't doubt dreams, dreaming children's dreaming dreams. Sailor Moon SS
    4. Re:Sorry, but YFI by Anonymous Coward · · Score: 0

      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.

    5. Re:Sorry, but YFI by Anonymous Coward · · Score: 0

      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.

  18. Lacking stability?! by Dthoma · · Score: 3, Funny

    "The review of FreeBSD 5.1 says it lacks the stability of v4.8"

    A BSD lacking stability? *universe explodes*

    --

    Note to M1-ers: a curt but otherwise insightful message is not "Flamebait" or "Troll".

    1. Re:Lacking stability?! by Anonymous Coward · · Score: 1, Informative

      So far 5.1-RELEASE has been very stable for me, but then I'm not running SMP and I only use it on a lightly loaded box. I'll have to try it out on a more loaded box sometime soon.

    2. Re:Lacking stability?! by dubious9 · · Score: 3, Insightful

      Yeah, but it's like saying granite is soft compared to dimond. They wouldn't release it if it didn't have them same famous stability, but rather they're acknowledging that no recently released product is as stable as its tried and true predecesor.

      --
      Why, o why must the sky fall when I've learned to fly?
    3. Re:Lacking stability?! by jonadab · · Score: 1

      > A BSD lacking stability? *universe explodes*

      Actually, BSD can be quite unstable and easy to crash. All you
      have to do is change the voltage going to the hard drive by just
      a few volts, and all sorts of weird things can happen.

      --
      Cut that out, or I will ship you to Norilsk in a box.
    4. Re:Lacking stability?! by Dthoma · · Score: 1
      "Si hoc legere scis nimium eruditionis habes."


      "If you know how to read this, you are overeducated."? :-)
      --

      Note to M1-ers: a curt but otherwise insightful message is not "Flamebait" or "Troll".

  19. Re:mac problems by vandel405 · · Score: 1

    Try out OS X, not classic :( some time.

  20. SMP & MT Progress by rapiere · · Score: 5, Informative

    Good objective articles despite extremetech's review is more than 8 months old now. Interested slashdot readers can look at the progress of fine grained SMP and advanced multi-threading system (KSE), two features which made me try this great operating system.

    5.1 is not in the stable branch yet, but 5.2/3 show great promises.

    1. Re:SMP & MT Progress by Anonymous Coward · · Score: 0
      Developer Laments the End of FreeBSD

      [ed. note: in the following text, former FreeBSD developer Mike Smith gives his reasons for abandoning FreeBSD]

      When I stood for election to the FreeBSD core team nearly two years ago, many of you will recall that it was after a long series of debates during which I maintained that too much organisation, too many rules and too much formality would be a bad thing for the project.

      Today, as I read the latest discussions on the future of the FreeBSD project, I see the same problem; a few new faces and many of the old going over the same tired arguments and suggesting variations on the same worthless schemes. Frankly I'm sick of it.

      FreeBSD used to be fun. It used to be about doing things the right way. It used to be something that you could sink your teeth into when the mundane chores of programming for a living got you down. It was something cool and exciting; a way to spend your spare time on an endeavour you loved that was at the same time wholesome and worthwhile.

      It's not anymore. It's about bylaws and committees and reports and milestones, telling others what to do and doing what you're told. It's about who can rant the longest or shout the loudest or mislead the most people into a bloc in order to legitimise doing what they think is best. Individuals notwithstanding, the project as a whole has lost track of where it's going, and has instead become obsessed with process and mechanics.

      So I'm leaving core. I don't want to feel like I should be "doing something" about a project that has lost interest in having something done for it. I don't have the energy to fight what has clearly become a losing battle; I have a life to live and a job to keep, and I won't achieve any of the goals I personally consider worthwhile if I remain obligated to care for the project.

      Discussion

      I'm sure that I've offended some people already; I'm sure that by the time I'm done here, I'll have offended more. If you feel a need to play to the crowd in your replies rather than make a sincere effort to address the problems I'm discussing here, please do us the courtesy of playing your politics openly.

      From a technical perspective, the project faces a set of challenges that significantly outstrips our ability to deliver. Some of the resources that we need to address these challenges are tied up in the fruitless metadiscussions that have raged since we made the mistake of electing officers. Others have left in disgust, or been driven out by the culture of abuse and distraction that has grown up since then. More may well remain available to recruitment, but while the project is busy infighting our chances for successful outreach are sorely diminished.

      There's no simple solution to this. For the project to move forward, one or the other of the warring philosophies must win out; either the project returns to its laid-back roots and gets on with the work, or it transforms into a super-organised engineering project and executes a brilliant plan to deliver what, ultimately, we all know we want.

      Whatever path is chosen, whatever balance is struck, the choosing and the striking are the important parts. The current indecision and endless conflict are incompatible with any sort of progress.

      Trying to dissect the above is far beyond the scope of any parting shot, no matter how distended. All I can really ask of you all is to let go of the minutiae for a moment and take a look at the big picture. What is the ultimate goal here? How can we get there with as little overhead as possible? How would you like to be treated by your fellow travellers?

      Shouts

      To the Slashdot "BSD is dying" crowd - big deal. Death is part of the cycle; take a look at your soft, pallid bodies and consider that right this very moment, parts of you are dying. See? It's not so bad.

      To the bulk of the FreeBSD committerbase and the developer community at large - keep your eyes on

  21. Too true by siskbc · · Score: 3, Insightful
    I tried FreeBSD, heard it was cool, and I'm used to Slackware so I'm not afraid of any install. So I got it installed fine, but none of the commercial apps I use were supported. Vmware 3 is only supported by 5.0, despite vmware 3 being a couple of years old. Matlab seems to be unsupported.

    So bottom line is, I really liked a lot of BSD's features, but unfortunately an OS without programs is useless. The ports guys do a great job, but can't make up for lack of vendor support. ;(

    --

    -Looking for a job as a materials chemist or multivariat

    1. Re:Too true by CounterZer0 · · Score: 1

      Linux emulation! You can run *anything* you can run on linux, it just takes a little bit more work.

    2. Re:Too true by root+66 · · Score: 1

      It's funny that some people on the FreeBSD mailinglists recommend you to get OS X if you want a shiny BSD desktop with lots of commercial apps.

      OTOH I don't see why some/most vendors don't port their programs to the BSDs. If developed cleanly and standarized, there shouldn't be that much problems.

      Of course, vmware is a bit different, because it relies on some kernel stuff I guess.

      --
      -- I love the smell of Blue Screens in the morning.
    3. Re:Too true by Anonymous Coward · · Score: 0

      Elegy For *BSD


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

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

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

    4. Re:Too true by MadAhab · · Score: 1
      Matlab is "unsupported", but only because the Mathworks dudes don't feel like it, either because they are lazy, or dumb, or timid, or pricks, or their lawyers scared them out of it, or whatever. It's actually worked with the Linux emulation mode for years (and some claim it's faster than under Linux!)

      Read about it here: matlab for linux and freebsd

      That being said, Matlab is very overpriced when stuff like Octave is available. $5K is a lot to pay for a pretty font or two and GUI to support greenhorns.

      --
      Expanding a vast wasteland since 1996.
    5. Re:Too true by Anonymous Coward · · Score: 0
      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 in the recent Sys Admin comprehensive networking test.

      You don't need to be a Kreskin 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.

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

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

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

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

      Fact: *BSD is dead

    6. Re:Too true by Anonymous Coward · · Score: 0

      This is a lie. There are cases where Linux programs will NOT run, such as apps that make extensive use of Linux's /proc filesystem.

    7. Re:Too true by Anonymous Coward · · Score: 1, Insightful

      Dude, look at the date of that post you link to. 1998? Sure, back then FreeBSD outperformed Linux in many areas, but those days are gone, unless you are using the 2.0 kernel or something..

    8. Re:Too true by Anonymous Coward · · Score: 0

      Nice troll.

      I've seen it before, of course.

    9. Re:Too true by jrees_alps · · Score: 1

      5 points for a guy who apparently didn't even bother to try linux emulation? And didn't mention a reason for not bothering? --/.

    10. Re:Too true by tigga · · Score: 1
      There are cases where Linux programs will NOT run, such as apps that make extensive use of Linux's /proc filesystem.

      That's right. Too many clueless programmers...

    11. Re:Too true by siskbc · · Score: 1
      5 points for a guy who apparently didn't even bother to try linux emulation? And didn't mention a reason for not bothering? --/.

      Here you go: First, because some of the stuff I have to use, like vmware, doesn't work under linux emu from what I'm told (I did mention that). Second, because it means that installing anything that doesn't come tgz'd is a royal pain in the ass, generally. And third, ports aren't released at a rate that is sufficient to take care of 1) and 2) above, though they seem to generally do a good job.

      --

      -Looking for a job as a materials chemist or multivariat

    12. Re:Too true by InSinU8 · · Score: 1

      Flame bait... at best.

    13. Re:Too true by Anonymous Coward · · Score: 0
      Although it is true that BSD is dying, there are some helpful steps you can take to help you cope:
      • deal with the inevitable.
      • grieve for your loss.
      • move on.
      Never let your emotions get tangled up with something as silly as a computer
      operating system. It isn't healthy. So BSD fails. Big whoop. Deal with it and move on.
    14. Re:Too true by Anonymous Coward · · Score: 0
      Pro or con, whether you support BSD or not, there is
      one irrefutable fact upon which we can all agree:
      *BSD is dying
      End of story.
    15. Re:Too true by Anonymous Coward · · Score: 0

      Its funny that netcraft itself runs FreeBSD... Don't you think?

      http://uptime.netcraft.com/up/graph?site=www.net cr aft.com

    16. Re:Too true by jrees_alps · · Score: 1
      Don't take this personal, I'm just making suggestions:
      Here you go: First, because some of the stuff I have to use, like vmware, doesn't work under linux emu from what I'm told (I did mention that).
      You've been told one thing, and I have heard another. Did you search the questions@freebsd mailing list archives for vmware and matlab?
      Second, because it means that installing anything that doesn't come tgz'd is a royal pain in the ass, generally.
      Can you quantify the PITA effect of using the compiler? I personally find the compiler less a Pain in the Pack Animal and more of a useful tool. Would like a little less GNU cruft, I suppose.
      And third, ports aren't released at a rate that is sufficient to take care of 1) and 2) above, though they seem to generally do a good job.
      It looks to me like you're arguing popularity there. Is popularity a valid argument?

      Personally, I think your point #2 sums up your argument. Even if you have antipathy to using the compiler, there are Linux distributions that you can set up and get to work on fairly quickly. For a variety of reasons, Linux may be better for you.

      Maybe I'm just being overly sensitive, but it seemed that your parent-parent post implied that Linux would be better for me too, especially if I need to use vmware or matlab, and I just wanted to point out that your brush was a little wide for your picture.
    17. Re:Too true by p00ya · · Score: 1

      I recently tried to convert a friend's box from Debian (GNU/Linux blahblah) to FreeBSD. It was quite a lower power box and it wasnt his main desktop system either - he was mainly using it for an irc console and a few ssh sessions.
      I put FreeBSD 5.0-RELEASE on it, and after a few weeks I asked him how it was going and he told me he was going to revert back to Debian. When I asked why, he showed me: the consoles had terrible lag. Whenever a new line came up in the irc client, it took a full second for the screen to redraw.
      I looked through the kernel config, and some of the docs floating around at the time, and couldnt find any reason why this should be the case. The box is now running Debian.

      If anyone can explain this phenomena, I'd love to know. Either way, I'd still consider *BSD before linux for a server system, but I'm now more hesitant for interactive systems.

  22. MOD THIS JACKASS DOWN by Anonymous Coward · · Score: 0

    We now have a buzzword troll.

  23. that's BS by Anonymous Coward · · Score: 0

    My system slows to a crawl when I copy 100+mb files from partition to partition on Windows. I mean, it shouldn't black out at 100% CPU for an f***ing file copy!! IE is unusable. Networking suffers. It makes no sense. Why the hell do you need to put 100% CPU into file I/O? I don't have this problem in *NIX.

    1. Re:that's BS by Anonymous Coward · · Score: 0

      My system slows to a crawl when I copy 100+mb files from partition to partition on Windows. I mean, it shouldn't black out at 100% CPU for an f***ing file copy!! IE is unusable. Networking suffers. It makes no sense. Why the hell do you need to put 100% CPU into file I/O? I don't have this problem in *NIX.

      Sounds like you are using PIO instead of DMA. For some reason, Windows (this has happened to me with win2000) will switch itself to PIO -- maybe if encounters errors or something.

  24. Re:mac problems by Lysol · · Score: 4, Informative

    Dude, first off, that's an old machine.

    Second, it's pretty well known the old finders were not multitasking. Or at least, not preemptive. I always wondered about formatting a floppy, copying a file while trying to do something as well. But a lot of people I've seen use Macs are happy doing one thing at a time.

    Others have claimed Macs were/are superior because they tend to just work. For a long time they came with sound on board, networking, video, Scsi, and in GUI usability terms were far ahead of Windows pre-95.

    Granted, Apple has a monopoly on their OS and hardware, but there's a reason for that; they believe that the whole computer should be package, not a bunch of parts. I was not much of a Mac fan until I bought my first Titanium Powerbook. After that, my Mac has replaced my Linux and Win desktops. I still love Linux and Intel hardware, but there is something to be said about plug and play that works - even for geeks.

    So yah, you're right, you're using a shitty browser on a old slow Mac. But why does it have to get to the point of calling people fanatics all the time. I'm sure all the Windoze, BSD, etc.., people speak highly of Linux zealots complaining about any OS that doesn't have skinnable everything and doesn't run on the shittiest hardware invented.

    I'd still buy a Mac for my parents in a hearbeat even though they 'like' Windoze. That said, my mom runs a online store off a Gentoo box I built her, so..

  25. Re:mac problems by Anonymous Coward · · Score: 0

    agreed, the only thing Mac zealots will do is repeat marketing crap. I like Macs, but I only own a 350Mhz iMac for my daughter. I don't see the need to buy a G4 (that was billed as a 'supercomputer on your desk') or the G5 (which is billed as the 'fastest personal computer') if I can get better perf from a 'roll yr own' AMD boxen running Gentoo.

    CB

  26. Crist on f****** pogo stick, this is a troll. by Dante · · Score: 0, Troll


    Jack Wagner is fiction, what this troll is saying is compleate nonsence. Please do not encourage him.

    --
    "think of it as evolution in action"
    1. Re:Crist on f****** pogo stick, this is a troll. by Anonymous Coward · · Score: 0

      PLEEEEZE Keep it up Jack! We're pulling (our puds) for you! If there's one thing Slashdot has been lacking since it's inception, it's a buzzword troll. Everyone else FAILS IT!!!! But you NAILED IT!!!!

    2. Re:Crist on f****** pogo stick, this is a troll. by homer_ca · · Score: 1

      Not just that! Jack Wagner played Dr. Peter Burns on Melrose Place. That guy sure gets around.

    3. Re:Crist on f****** pogo stick, this is a troll. by Anonymous Coward · · Score: 0

      Yeah, just look at his comments:

      Jack Wagner's Latest 24 of 68 Comments

      Replies:11 Score:5, Funny
      attached to FreeBSD 5.1 Review and BSD Roundup

      Is Dykstra still relevant today? Wednesday July 09, @10:08AM Replies:21 Score:1, Troll
      attached to Dijkstra's Manuscripts Available Online

      It's all in the perspective Tuesday July 08, 01:50PM Replies:10 Score:3, Insightful
      attached to The New Yorker on Business Process Patents

      Not too surprising really Wednesday May 21, @02:01PM Replies:9 Score:2, Flamebait
      attached to Mainframe Techies Are A Dying Breed

      I did some work for him on this book Friday May 09, @01:34PM Replies:2 Score:5, Informative
      attached to 'Quicksilver' Website and Release

      So true Thursday March 27, @10:51AM Replies:8
      Score:3, Insightful attached to Too Cool For Secure Code?Re:Well Friday February 21, @01:37PM

      Score:0, Informative attached to Lawyers Say Hackers Are Sentenced Too Harshly

      The problem as I see it Tuesday February 11, 01:45PM Replies:4 Score:0, Troll attached to Programmers and the "Big Picture"?

      This is typical Thursday January 23, @02:05PM Replies:11 Score:-1, Troll attached to The Costs of Making a DRAM Chip

      Maybe Friday January 17, @02:50PM Replies:9 Score:0, Troll attached to Scaling Server Performance

      Not too comprehensive Thursday January 16, @10:50AM Replies:17 Score:0, Troll attached to The New Face of Global Competition

      This should be helpful Wednesday January 15, @01:53PM Replies:7 Score:0, Troll attached to Linux 2.4 VM Documentation

      This may decrase performance in some cases Tuesday January 14, @04:18PM Replies:3 Score:1, Troll attached to Hyper-Threading Speeds Linux

      Fine for what it is Tuesday January 14, @12:59PM Replies:2 Score:1, Troll attached to The Art of Deception

      Is this really good though Friday January 10, @12:44PM Replies:3 Score:1, Interesting attached to TiVo to support HDTV by "Year-End"

      No so fast there Wednesday January 08, @04:02PM Replies:6 Score:0, Flamebait attached to Windows XP Media Center Edition Review

      It's a deep complex issue Wednesday January 08, @03:17PM Score:1, Interesting attached to How Would You Improve Today's Debugging Tools?

      Tuning for performance isn't really the problem Wednesday January 08, @12:41PM Replies:3 Score:0, Troll attached to Sendmail Performance Tuning

      My Problem with RMS Thursday December 05, @02:08PM Replies:8 Score:1, Troll attached to Free Software, Free Society

      The underlying problem with programming Thursday November 14, @11:27AM Replies:18 Score:5, Insightful

      attached to The Law of Leaky Abstractions

  27. Mods on crack by Anonymous Coward · · Score: 0

    Can this guy POSSIBLY have a higher buzzword quotient? Sheesh! I think we need to add a BWQ to anti-troll filters.

  28. No commercial gain from GPLed code? by spray_john · · Score: 3, Insightful
    When code is licensed under the GNU General Public License or GPL (as is Linux), the license effectively eliminates any financial rewards anyone -- whether an individual or a corporation -- might hope to gain from improving upon it.

    Oops! It looks like IBM and Redhat were just charities after all...

    But seriously, does this stink of someone that's lapped up the FUD to anyone else?

    1. Re:No commercial gain from GPLed code? by Anonymous Coward · · Score: 0

      IBM and Redhat sells software (and services for software) that _others_ has made.

      It's just a handfull of people in both companies that write stuff that is GPLd.

      The GPL is all about free labour, thats what makes it good for companies like IBM, that the people writing is unpaid in all regards. IBM sells the software and also grabs the service-market for it and the people writing it gets nothing.

      There are exceptions ofcause but generally this is the case.

    2. Re:No commercial gain from GPLed code? by curious.corn · · Score: 1

      No way! The GPL is about commoditizing the platform and prevent standards "fencing" to stifle competition. Anyone playing by the GPL rules cannot, under any chance, wrap it's customers in a stranglehold like drug dealers do. Imagine if you didn't like the new M$ licence costs and conditions... yet your businesss process is built upon a highly custom proprietary platform you can't wriggle away even if you wanted... I'm not talking only about product differentiation that makes a particular task to implement but wholesale process captivity.

      --
      Mi domando chi à il mandante di tutte le cazzate che faccio - Altan
    3. Re:No commercial gain from GPLed code? by Anonymous Coward · · Score: 0

      When code is licensed under the GNU General Public License or GPL (as is Linux), the license effectively eliminates any financial rewards anyone -- whether an individual or a corporation -- might hope to gain from improving upon it.

      Oops! It looks like IBM and Redhat were just charities after all...


      Actually you are somewhat correct. IBM hardware sales and RedHat support contracts subsidize their Linux improvements.

    4. Re:No commercial gain from GPLed code? by AHumbleOpinion · · Score: 1

      When code is licensed under the GNU General Public License or GPL (as is Linux), the license effectively eliminates any financial rewards anyone -- whether an individual or a corporation -- might hope to gain from improving upon it.

      Oops! It looks like IBM and Redhat were just charities after all...


      Actually you are somewhat correct. IBM hardware sales and RedHat support contracts subsidize their Linux improvements.

      Apologies for the accidental AC post.

    5. Re:No commercial gain from GPLed code? by cozman69 · · Score: 1

      Last time I checked, I could go to a redhat mirror and download the entire redhat distro for free. RedHat doesn't make money directly from the code they write (because of the GPL). They have to market their OS to their clients and actually sell support to their clients. RedHat makes money from the support it provides for its code. IBM also doesn't sell the GPL'd code. They sell the hardware that runs the code, and the proprietary applications that run on Linux. And support for their solutions. So yes, you can't make money directly from GPL'd code (because if the code is GPLd you always have to allow access to the source to anyone), but you can make money because of the code.

    6. Re:No commercial gain from GPLed code? by Quill_28 · · Score: 1

      No, the GPL is about riding the world of proprietary software, pain and simple.
      Another goal along these lines is to rid the world of high paying programming jobs.

      Haven't you read your manifesto?

    7. Re:No commercial gain from GPLed code? by curious.corn · · Score: 1

      High paying programming jobs are all about building taylor made business logic on some kind of platform. Automation tools are always built to simplify the task pushing up the complexity mark for high margin commissions. Some platforms mostly make their adoption compelling in terms of features and yield but some make it compulsory by proprietarizing the platform on which the code is supposed to run. Don't blame GPL for the first statement, but do blame Microsoft for the second though.

      --
      Mi domando chi à il mandante di tutte le cazzate che faccio - Altan
  29. Re:I've always hated you and your comments, usotsu by usotsuki · · Score: 2, Insightful

    Ah, Slashdot, land of the ad hominem and home of the trollbait...

    *sigh*

    I don't have anything to do with BSD other than my experiments porting OpenBSD tools to DOS (!), but my crystal ball shows FreeBSD holding its own...

    I like the BSD license better than the GPV anyway. I started work a couple years ago on a project called RMF-DOS (Reduced Memory Footprint DOS), which never got off the ground, but I did it because I felt the world needed a BSD-licensed DOS clone suited for embedded systems and ancient 8086 boxen. I still believe in it. I just haven't had any way to write a kernel for it.

    BSD's philosophy is why it endears itself to the hearts of companies better than Linux (this is not intended as a troll or a flamebait), and also, it is why it is not as well-known as the more radical GNU projects and the Linux kernel.

    As long as there's a use for it - and as long as there is BSD code in MacOS X - BSD is very much alive.

    Good. Now mod me down into oblivion again.

    -uso.

    --
    Dreams, dreams, don't doubt dreams, dreaming children's dreaming dreams. Sailor Moon SS
  30. Who Owns UNIX? by jooon · · Score: 2, Insightful

    Those were the days. In the chapter "Who Owns UNIX?" they never once mention SCO.

    1. Re:Who Owns UNIX? by MidnightLightning · · Score: 1

      I guess it won't matter in time anyway. Remember, just like BSD, SCO is dying also, which in this instance, is a good thing.

      --

      -------
      Those who can, do, and those who can't, well ... teach.
    2. Re:Who Owns UNIX? by rollthelosindice · · Score: 1

      They mention the open group. I believe that's either SCO, or owned by SCO.

    3. Re:Who Owns UNIX? by Anonymous Coward · · Score: 0

      The most important thing to consider is that BSD has no future. It quite literally is dying. Time invested in BSD today is wasted completely. It is better to choose an OS which will be around for the foreseeable future. Anyone other than a starry-eyed zealot already knows the score: BSD is dead.

    4. Re:Who Owns UNIX? by Anonymous Coward · · Score: 0
      While it is a fact that BSD is dying, there are some helpful steps you can take to get on with your life:
      • deal with the inevitable.
      • grieve for your loss.
      • move on.
      Never let your emotions get tangled up with something as silly as a computer
      operating system. It isn't healthy. So BSD fails. Big whoop--deal with it and move on.
    5. Re:Who Owns UNIX? by Anonymous Coward · · Score: 0

      It's dead, Jim.

  31. Actually... by Anonymous Coward · · Score: 0

    ...it was my intention to point out that what has been the main problem with Windows for years is now being defined as 'progress' for *BSD. Hypocritical? Nah, not Slashdot!

    1. Re:Actually... by mjmalone · · Score: 5, Informative

      It's a bit different. FreeBSD is stating outright that this is not *AS* stable as 4.8-STABLE. I'm sure it is a much more stable OS than anything MS has to offer. They are merely stating that they are still working out kinks in the software and are warning people before hand not to be surprised if an issue arises. When was the last time MS released an OS upgrade and said "well, this OS isn't as stable as the last one, but we will release some service packs in a few month and those who are running mission critical applications should wait until these are released before upgrading."

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

      But of course this isn't the *BSD team coming out and warning users that their latest release isn't stable, it's an independent reviewer.

    3. Re:Actually... by mjmalone · · Score: 2, Informative

      The FreeBSD Project describes Version 5.1 as a "new technology" release, intended to enable users to check out new features, such as Version 5.1's expanded support for USB (Universal Serial Bus) 2.0 devices, RAID and serial-ATA controllers, and USB Ethernet adapters.[...]the FreeBSD Project plans to begin a stable 5.x branch--possibly as soon as this fall--when 5.x should be considered ready for critical production deployments.

      looks to me like the "FreeBSD Project" admitted it.

    4. Re:Actually... by someonehasmyname · · Score: 2, Informative

      The FreeBSD project has an "Early Adopters Guide."

      I'm smart enough to infer from the term "Early Adopter" that this probably isn't quite ready for production use, but the less educated people can find sentences like "While suitable for testing and experimentation, these features may not be ready for production use." in the guide to help clue them in.

      --
      Common sense is not so common.
    5. Re:Actually... by ImpTech · · Score: 2, Funny

      > When was the last time MS released an OS upgrade and said "well, this OS isn't as stable as the last one, but we will release some service packs in a few month and those who are running mission critical applications should wait until these are released before upgrading."

      Never. See, these FreeBSD guys are slackers. They're clearly releasing beta code and calling it final. Every Microsoft release is Better, Faster, Easier to Use, More Stable and Reliable than Ever (tm), and helps You Do More Faster. FreeBSD needs to get its act together before it dies out.

      Humorless moderators, please consult your sarcasm meters before exercising your mystical powers.

    6. Re:Actually... by Anonymous Coward · · Score: 0

      I stand by the facts: *BSD is dying

  32. What's with the old article? by kenfrid · · Score: 2, Interesting

    The article that's linked to over at extremetech is an extremely good read, but its dated Sept 26, 2002. Does it take Slashdot that long to pick up on BSD-related news?

    1. Re:What's with the old article? by japhar81 · · Score: 1

      Yes... Thats why people keep modding us as Troll when we tell you that BSD is dying.

    2. Re:What's with the old article? by Anonymous Coward · · Score: 0
      So why now? I think there is a generally accepted sense that *BSD is indeed dying. 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.

  33. One thing in the ET article... by gatesh8r · · Score: 4, Informative
    When code is licensed under the GNU General Public License or GPL (as is Linux), the license effectively eliminates any financial rewards anyone -- whether an individual or a corporation -- might hope to gain from improving upon it. It does this by compelling an author who uses any part of the code to give up the right to charge a license fee for the finished product.


    There is nothing in the GPL that prevents you from selling GPL'ed software. In fact, the FSF says to go right ahead and do so if you want. What the GPL of course DOES guarantee is that the software can't become proprietary at any point, whereas the BSDs can be.

    --
    Karma whorin' since 1999
    1. Re:One thing in the ET article... by Tyler+Eaves · · Score: 1

      Has anyone actually sold GPLed software, ever?

      Just because you COULD do it doesn't mean it's viable.

      --
      TODO: Something witty here...
    2. Re:One thing in the ET article... by gatesh8r · · Score: 3, Interesting

      Has GPLed software been sold? Yes. Haven't you purchased a Linux distro before? The FSF even sells their GPLed software! (Order link)

      Is it viable??? Ask a company like Red Hat; they're in the black because of GPLed software and related services (one could argue that they are two completely different ways of getting revenue, but service contracts and software go hand and hand in the corperate world). GPLed software in the mainstream is just starting to become established; it's too early to say if it's a dead-end or not. Companies are gun-shy to change any of their methods in a conservative move to their stockholders.

      --
      Karma whorin' since 1999
    3. Re:One thing in the ET article... by Anonymous Coward · · Score: 0

      That's ridiculous; in all practical aspects the GPL does eliminate all possibility to sell the software for software developers.

      Say you arrange a concert. You have to cover all the expenses for the artists, the stadium, staff etc.

      Now, say you need to charge $50 per ticket to break even and $60 to make a profit for the risk you are taking. There are 50 000 seats.

      You then allow anyone to copy the tickets and sell for any price they want to. Someone makes 50 000 copies and sell them for $1; they can do that since they don't have the expenses.

      Who is going to buy your tickets then there are tickets for $1 to buy?

      If your development company spend 5000 man-hours to develop a piece of software and you GPL it Redhat can just include it in their distribution for no charge at all. They also sell support for it. What exactly are YOU going to live on? How are you going to be able to sell anything?

      The whole argumentation is ridiculous and I don't understand why it still comes up after the last few years of dot-com disaster that has brought unemployment to insane levels. Is it _still_ that difficult to understand that it's impossible to live on nothing?

    4. Re:One thing in the ET article... by Anonymous Coward · · Score: 0

      Redhat mainly sells software that OTHERS has made. Redhat is the prime example of why the GPL doesn't work for developers.

    5. Re:One thing in the ET article... by Anonymous Coward · · Score: 0

      According to their latest quarterly report most of Redhats revenue comes from selling per seat licenses for "their" advance server.

      The deferens from for example adobe, microsoft, symantec and the rest is that Redhat do NOT pay the people who actually spent lots of man-hours developing the software they are selling.

      So, no, the GPL does not work.

    6. Re:One thing in the ET article... by Anonymous Coward · · Score: 0

      So all those guys at RedHat that work on the RedHat kernel, supply patches to gcc and all sorts of other software, they don't get paid right?

      You're wrong. The GPL does work. I'm not foolish enough to believe it will work for everyone, but it does work in a lot of cases.

    7. Re:One thing in the ET article... by Anonymous Coward · · Score: 0

      No kidding, sometimes you'd think people learn everything about the GPL and Free software by reading slashdot trolls.

      However in this case, Brett Glass actually *is* a troll. He often seeds his writing with anti-GPL crap for no particular reason.

      Considering I get paid quite handsomely to "improve on" Linux (as well as FreeBSD for that matter), I can safely say that comment is just FUD. Just don't distribute the changes and it doesn't make ANY DIFFERENCE if it is GPL or BSD. That covers a majority of cases.

      If you want to make money selling copies of SOMEONE ELSE'S WORK, then well, don't expect the world to make it easy for you by putting everything under the BSD license. This "freedom" doesn't really strike me as an important one.

      It's pretty stupid to talk about the differences between BSD and GPL when we have Microsoft-type EULAs in this world........ the kind of petty and irrelevant infighting that plagues all intellecual movements, unfortunately.

      It just makes MY job more difficult as I try and explain to folks that no, despite what you hear, the GPL does not "force" you to "give away" your company property.

    8. Re:One thing in the ET article... by Rock+Ridge · · Score: 1

      You can sell GPL software if you find someone who doesn't know that they can get it for free. The only reason anyone would buy GPL is that they don't know this or hope to get a "turnkey" package by paying someone to do the configuration or whatever it needs.

    9. Re:One thing in the ET article... by cozman69 · · Score: 1

      Don't confuse selling the code with selling support for the code. GPLd code is always available for free (without support from the company).

    10. Re:One thing in the ET article... by Anonymous Coward · · Score: 0

      That may be true, but it doesn't have any bearing on the original comparison, which was between the GPL and BSD licenses -- both can defiantly be used for commercial gain, and both might not give anything back to the developers in those situations.

    11. Re:One thing in the ET article... by Anonymous Coward · · Score: 0
      Why did *BSD fail? It is no secret: BSD is a failure. 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.

    12. Re:One thing in the ET article... by Anonymous Coward · · Score: 0

      You are too simple minded. For any non-trivial enterprise level software, it is the cost of the support that is going to bite you the hardest. At a certain level, the cost of the software and hardware is nothing compared to what has to be payed to the support staff or contractor. That is how Oracle makes money. MySQL? Hah hah. Pardon me while I laugh.

  34. I'll always love you and your comments, usotsuki. by Anonymous Coward · · Score: 0
  35. Re:Awesome by bathmatt · · Score: 2, Insightful

    Your point may be true aobut the BSD license, it is not about *BSD in generl. Rhe OS is not just the kernel. That has been RMS's point for a long time. compilers, editors, libraries, those make up the OS, not just the kernel. Many of those are GPL'ed.

  36. Re:mac problems by realdpk · · Score: 1

    "Granted, Apple has a monopoly on their OS and hardware, but there's a reason for that; they believe that the whole computer should be package, not a bunch of parts."

    Funny, so does Microsoft.

  37. Re:bsd problems by Anonymous Coward · · Score: 0

    A common complait to the naive *BSD user. No biggie, everyone goes through it. The "damn! the filesystem is SLOW!"...

    Turn on softupdates.

  38. Hard times for *BSD by Anonymous Coward · · Score: 0
    So why now? 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 virtually 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.

  39. Re:Ugg, fuck you by Anonymous Coward · · Score: 0

    Nice. REAL nice fuckflap! You contributed absolutely nothing to the stream of stupidity taking place here. Go sit in a corner and think real hard before posting again lest I beat you with a rubber hoatse.

  40. Ignore these posts, there's lots of 'em by Anonymous Coward · · Score: 0

    "I don't want to start a holy war" ---- Mac fanatics
    "I don't want to start a holy war" ---- BSD fanatics

    Etc, etc...

  41. Re:mac problems by Anonymous Coward · · Score: 0
    Ive seen this post several times, its just copied and pasted.

    Check out http://www.kottke.org/98/11/981125my_mac_sucks.htm l

    Looks like this comment was made in 1998.

  42. Huh? by jandrese · · Score: 2, Insightful
    In the Extremetech review:
    Around the same time, Linux surfaced. Based on the Minix kernel written by computer science professor Andrew Tannenbaum, and unencumbered by the spectre of a lawsuit, Linux began to gain momentum and became the best known freely redistributable UNIX-like operating system.
    That's news to me.
    --

    I read the internet for the articles.
    1. Re:Huh? by klui · · Score: 1

      Would it not be more accurate to say "inspired by Minix" instead?

    2. Re:Huh? by Anonymous Coward · · Score: 0

      These "journalist" types inevitably get something wrong. It's getting pretty stupid. Practically everyone here ought to know by now that Linux was built from scratch by Linus and he got ideas from the Minix kernel. Usually they totally screw up the history of BSD.

    3. Re:Huh? by jandrese · · Score: 1

      Depends on how you read it. My original reading was that Linux used the Minix kernel "Based on Minix". Everybody else seems to have read that Linus was inspired by Minix, but that doesn't make a whole lot of sense either because Minix has a completely different architecture. Unless Minix inspired Linus to stay away from Microkernels of course...

      --

      I read the internet for the articles.
    4. Re:Huh? by FranklyMyDear · · Score: 0
      That's news to me.

      Didn't you know? It was written by a Swedish guy called Linux Thorvald and is continually being improved by hundreds of thousands of "crunchies" worldwide. Based on forty-year-old Unix technology patented, copyrighted, and trademarked by SCO, Linux is distributed under an untested and probably unenforceable licence called the GNU Public Licence that forbids commercial use of the code and destroys any intellectual property within a radius of 100m.

    5. Re:Huh? by Anonymous Coward · · Score: 0
      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

  43. Pull your head out of your ass by scosol · · Score: 1

    We live in the real world.

    Nobody is going to voluntarily pay for something they can get for free.

    And besides, you're wrong- BSD-licensed code can never be "made proprietary". However, modifications to it can be.

    The GPL is worthless anyway-
    "Sure, here's my source code- of course, it only works with my custom interpreter that I will sell you for $995."
    The road down describing "source code" and "human readable" is a very long one indeed...

    Now you can put that in your pipe and smoke it :)

    --
    I browse at +5 Flamebait- moderation for all or moderation for none.
    1. Re:Pull your head out of your ass by Anonymous Coward · · Score: 0

      You are a very ignorant individual.

      People pay for Linux (and *gasp* BSD) distros all the time, even though they can download them for free.

      Your comment about the GPL is equally ignorant.

    2. Re:Pull your head out of your ass by Anonymous Coward · · Score: 0

      how do you explain supermarkets? after all, anybody can grow vegetables.

    3. Re:Pull your head out of your ass by scosol · · Score: 1

      Right- and that's why you're anonymous...

      People pay for Linux distros for only 3 reasons:
      1) They feel a philisophical duty to do so
      2) They are paying for a more convenient distribution media (CD vs Download)
      3) They actually are *not* paying for Linux, but are in fact paying for the associated support and packaging. (See Redhat)

      The fact still remains- attacking the GPL based on it's "cant charge for the product itself" nature is still entirely valid, because *nobody* will pay for it. (unless they feel charitable; as in reason #1)

      And as for the GPL, source code is defined as: "The source code for a work means the preferred form of the work for making modifications to it."

      That's a *very* arbitrary definition, which renders it utterly meaningless. Suppose I code in binary, and it's my preferred method of making changes.

      Great- now what are you gonna go do with my "source code"?

      --
      I browse at +5 Flamebait- moderation for all or moderation for none.
    4. Re:Pull your head out of your ass by scosol · · Score: 1

      wrong, it takes a very signifigant time investment to grow vegetables

      if it took months to download a linux distro, then yeah- i bet you'd see a lot more of them being sold

      --
      I browse at +5 Flamebait- moderation for all or moderation for none.
    5. Re:Pull your head out of your ass by Anonymous Coward · · Score: 0
      Why not keep to the facts?

      Fact: *BSD is dying

  44. Re:Awesome by Arandir · · Score: 1

    compilers, editors, libraries, those make up the OS, not just the kernel.

    So you're saying then that Visual C++ and Word (or Visual Basic and Notepad) are part of an operating system? Huh?

    The typical user has no idea what an operating system is, but RMS ought to know better.

    --
    A Government Is a Body of People, Usually Notably Ungoverned
  45. I think that other AC could be right... by Anonymous Coward · · Score: 0
    "Ah, Slashdot, land of the ad hominem and home of the trollbait."

    "I like the BSD license better than the GPV anyway."

    Ahypocritesayswhat?

  46. Re:mac problems by Mikey-San · · Score: 1

    ahahjlghaahahahaha

    To everyone replying to this message:

    You got trolled. See also: http://users.adelphia.net/~khaosvoid/images/owned. jpg

    --
    Mikey-San
    Karma: +Eleventy billion (mostly affected by watching Celebrity Jeopardy)
  47. Re:Whoa to those who abuse moderation by CoolVibe · · Score: 3, Funny
    Thanks for reading and have a pleasant morning (or whatever time of day it is, depending on your geometric location).

    What does me living somewhere in a dodecahedral shape have to do with what timezone I live in?

    Oh you mean geographic, not geometric... Never mind...

  48. Re:mac problems by jhunsake · · Score: 1

    You just got trolled! Sucker!

  49. Duke Nukem 4-0 - balder, fatter by Anonymous Coward · · Score: 0
    Garland, TX

    Looks like middle age hasn't been kind to action hero Duke Nukem. In a prerelease press preview, presented by Joe Siegler, the studly hero is bald with a huge beer-gut. "We wanted to flesh out the character of Duke", Siegler said, "we want to make him more a character that his fans can directly relate to".

    In the new title, Duke is in a custody dispute with his ex-wife. Apparently, since he lost his job, he's in arrears on his child-support payments. When his (alien) wife kidnaps their kids and leaves for her mothers on Vega VII, it's butt-kicking time!

  50. News? by panda · · Score: 4, Informative

    It's amazing what passes for "news" around here!

    I use FreeBSD, and upgraded to 5.1 from 4.7 about a week after 5.1 was released. Though I did have some issues with X and DRI, I got it working with not much effort. (About 20 minutes of searching the web turned up some instructions that directed me to set ForcePCIMode on in my drivers section of XF86Config.)

    Though 5.1 is a new technology release and so not as stable or as fast as 4.8, it is still quite stable and quite fast at most everything I do. I've had no problems with doing my usual work, and some "weird" behavior in or two apps actually went away when recompiled on 5.1 versus 4.7.

    That said, I haven't gotten YMessenger to work, and I've been too lazy to try fixing it myself. (It just appears to need to be relinked against a certain lib, and I haven't bothered to find out which one that is.)

    Generally, I've not had any trouble running Linux apps under emulation, either.

    All my Java 1.4 stuff works, too.

    I know that anecdotal evidence proves nothing, but I just thought I'd weigh in with a mostly positive experience of someone who has been a FreeBSD user for quite some time.

    Yes, I also use GNU/Linux, too. In fact, I have two machines running GNU/Linux at home, only 1 running FreeBSD, and one other running OpenBSD. Though I may switch one of the GNU/Linux machines to FreeBSD in the near future (maybe after 5-STABLE is branched).

    --
    Just be sure to wear the gold uniform when you beam down -- you know what happens when you wear the red one.
    1. Re:News? by phoenix_rizzen · · Score: 3, Informative

      Unless you need a specific feature of Yahoo! Messenger, consider trying GAim, Kopete, or one of the other multi-protocol clients. They are slimmer than the YMessenger client, provide 90% or more of the same functionality, and let you connect to multiple IM servers with just one client.

      Oh, and just to be pedantic, it's not Linux emulation, it's Linux compatibility. There is a difference, although few people really care to know what it is. :)

    2. Re:News? by rplacd · · Score: 1

      Install the ymessenger port -- it handles the library issues with a binary patch. Funky, but it works.

    3. Re:News? by Anonymous Coward · · Score: 0
      Latest News: the End of FreeBSD

      [ed. note: in the following text, former FreeBSD developer Mike Smith gives his reasons for abandoning FreeBSD]

      When I stood for election to the FreeBSD core team nearly two years ago, many of you will recall that it was after a long series of debates during which I maintained that too much organisation, too many rulesand too much formality would be a bad thing for the project.

      Today, as I read the latest discussions on the future of the FreeBSD project, I see the same problem; a few new faces and many of the old going over the same tired arguments and suggesting variations on the same worthless schemes. Frankly I'm sick of it.

      FreeBSD used to be fun. It used to be about doing things the right way. It used to be something that you could sink your teeth into when the mundane chores of programming for a living got you down. It was something cool and exciting; a way to spend your spare time on an endeavour you loved that was at the same time wholesome and worthwhile.

      It's not anymore. It's about bylaws and committees and reports and milestones, telling others what to do and doing what you're told. It's about who can rant the longest or shout the loudest or mislead the most people into a bloc in order to legitimise doing what they think is best. Individuals notwithstanding, the project as a whole has lost track of where it's going, and has instead become obsessed with process and mechanics.

      So I'm leaving core. I don't want to feel like I should be "doing something" about a project that has lost interest in having something done for it. I don't have the energy to fight what has clearly become a losing battle; I have a life to live and a job to keep, and I won't achieve any of the goals I personally consider worthwhile if I remain obligated to care for the project.

      Discussion

      I'm sure that I've offended some people already; I'm sure that by the time I'm done here, I'll have offended more. If you feel a need to play to the crowd in your replies rather than make a sincere effort to address the problems I'm discussing here, please do us the courtesy of playing your politics openly.

      From a technical perspective, the project faces a set of challenges that significantly outstrips our ability to deliver. Some of the resources that we need to address these challenges are tied up in the fruitless metadiscussions that have raged since we made the mistake of electing officers. Others have left in disgust, or been driven out by the culture of abuse and distraction that has grown up since then. More may well remain available to recruitment, but while the project is busy infighting our chances for successful outreach are sorely diminished.

      There's no simple solution to this. For the project to move forward, one or the other of the warring philosophies must win out; either the project returns to its laid-back roots and gets on with the work, or it transforms into a super-organised engineering project and executes a brilliant plan to deliver what, ultimately, we all know we want.

      Whatever path is chosen, whatever balance is struck, the choosing and the striking are the important parts. The current indecision and endless conflict are incompatible with any sort of progress.

      Trying to dissect the above is far beyond the scope of any parting shot, no matter how distended. All I can really ask of you all is to let go of the minutiae for a moment and take a look at the big picture. What is the ultimate goal here? How can we get there with as little overhead as possible? How would you like to be treated by your fellow travellers?

      Shouts

      To the Slashdot "BSD is dying" crowd - big deal. Death is part of the cycle; take a look at your soft, pallid bodies and consider that right this very moment, parts of you are dying. See? It's not so bad.

      To the bulk of the FreeBSD committerbase and the developer community at large - keep your eyes on the r

  51. Linux on big machines by Anonymous Coward · · Score: 1, Interesting

    I've just made - PAINFULLY! - the expirience, that Linux isn't really stable on big machines.
    I've set up a NFS-Fileserver on a Dual-Xeon with 4GB RAM and after around 2-3 days it locks up.
    Tried several kernels, even used RH standard one (given the fact, that Alan Cox hacks around for RedHat...).
    The buffer is eating up 3.8GB and after a while kswapd is running amok, eating CPU and not swapping out a single page.
    The is no write starvation either, all buffers are clean (and I made sure they are synced often enough).

    I am not talking about some "funny little server here", but serving 10 machines via 100Mbit and 6 via 1Gbit and a total of around 500GB (right know; RAID is expanded next week to > 1 TB running JFS, thank god & IBM).
    Each run of a programm reads ~10-20 GB of data.

    I thought of FreeBSD as a viable alternative when I started that job, but choose Linux to have a common platform (clients and compute-servers are also Linux).

    This expirience leaves me right out in the dust. The Linux-Kernel-guys seem to know the problem as many other have reported it, but don't really do something. Unfortunately. And I've been polite :)

    1. Re:Linux on big machines by DShard · · Score: 1

      I would say that your vendor of the distro is the one you need to bark at... or the ever popular "the source code is there so just fix it yourself!"

      Using the former strategy, tell the vendor your needs and state that you will find a newer one if they don't commence to commiting resources to fixing it. For this strategy to work you must be capable of implementing the consequences, otherwise pissing of your only vendor is idiotic.

      The latter method is gruelling, time-intensive and worst of all may not be applicable to any future endeavor (about the most annoying aspect of existence IMNSHO is pointless drudgery). But this is the only reasonable way to expedite the fix if you don't have a support contract for your OS.

      GL

    2. Re:Linux on big machines by merdark · · Score: 1

      Yeah, I recently installed Linux on a dual P-III SCSI system. Tried a bunch of different kernels as well, but the damn thing keeps using up 30% of each processor for system tasks... at idle even!

      I checked all the processes, nothing taking up time. If I actually had a choice, I'd have used FreeBSD. A friend of mine runs a fairly large website with a LOT of traffic. It was crawling on redhat 8. He switched to FreeBSD and it's now able to handle the load easily.

      The confusing thing is, everyone always tells me Linux has great SMP! Oh well.

  52. Re:Awesome by paranode · · Score: 1
    You have the GPL, then you have the BSD License.

    The GPL license is "a virus" as defined by Microsoft, but has helped spawn many great free variants of the Linux operating system and tools for it.

    The BSD license says you can make money off of their code, and they spawned the virus that is Microsoft!

    How's that for your free software irony.

  53. Re:bsd problems by Anonymous Coward · · Score: 2, Funny

    [...] to copy a 17 Meg file from one folder on the hard drive to another folder. 20 minutes. At home, on my Pentium Pro 200 running NT 4, which by all standards should be a lot slower than this BSD box, the same operation would take about 2 minutes.

    I owned a Dual Pentium Pro 200 running NT4. What's even funnier is I owned it and the poor fool didn't discover I was serving MP3s (with Gnutella protocol) until about two months later! I did this by hiding the crackapp name of my custom gnutella server from the POSIX tasklist and only would serve the MP3s to the Gnutella network while another filetransfer was active by the local user. 1337 cr4x0r h47h 0wn3d j00!

    My 486/66 with 8 megs of ram runs faster than this 800 mhz machine at times.

    That's not uncommon. I own a 486/25 with 4MB of RAM, S3 video, XFree86-3.3.5, and I telnet to my GS140 AlphaServer, issue a "export DISPLAY='192.168.1.66:0.0'," and finish it off with a "darkplaces >/dev/null 2>&1." I get Icculus' DarkPlaces Quake1 engine playing on my 486/25 machine at about 300 frames per second in software rendering, but alas my 486/25 can effectivly only update the X Server display at about 20 frames per second. Still, my 487/25 is playing DarkPlaces twice as fast as your Pentium3/800! That makes my freeBSD 486/25 much faster than your measly Pentium3/800! And with Linux on the GS140, I have a great team-alliance for stability and performance.

    You realy need to ditch that M1cr0$l07h W1nd0z3 NT4 in favor of an operating system that can at-least handle more than four CPUs and USB/Firewire, becuase NT4 is sooo-obsolete, same for ActiveDirectory and IIS; just use Apache/FetchMail/ProFTP

  54. FreeBSD = top quality by koinu · · Score: 5, Interesting

    I am using FreeBSD stable since over a year now on my Intel-PC. I noticed I have everything I need here.

    The best is, my PC is a regular desktop PC. I can watch DVDs and TV, listen to Oggs, burn CDs, chat and now I am writing this comment. :)

    I have uninstalled Debian. I don't need it, because FreeBSD has got the best Linux emulation in the world. I can even play regular 3D-accelerated games with top frame rates.

    I don't understand why people are bitching about FreeBSD. It is easy and even trivial to use. You can install it in many different ways. Experts mostly use minimal installs or even the floppy install.

    You can choose between packages or ports, whatever you wish. There are 9000 software ports and they compile without problems. A simple 'make install' in the proper directory is enough to fetch dependencies and install the package. Most of them are pre-configured in a a way which is appropriate for many users. Before and after installation you will get further hints what to do and how to use a port.

    The manpages are good. You get examples and a centralized configuration file. I don't need to mention the possibilities if you want to use FreeBSD as a firewall. And the VM is top quality! Heavy load is no problem. You can still listen to your MP3 or watch an AVI while dd'ing a harddisk.

    FreeBSD is my favorite OS.

    1. Re:FreeBSD = top quality by AvengerXP · · Score: 0, Troll

      "Experts mostly use minimal installs or even the floppy install."

      Is this a joke? Experts still use floppy instead of PXE Boot or CD-Boot? And since when do experts use minimal install? I prefer custom. Your arguments are dubious.

      "It is easy and even trivial to use"

      I'll tell you what is trivial to use, without being a Windows fanboy. My sister installing her own network including hubs without any need for my help is trivial. BSD is tedious, as is Linux. That doesn't mean they are not good OSes quite the contrary, but please, don't capitalize on something the product is not. That's like saying Windows is modular, and easy to add/remove parts you don't really need.

      --
      Trolls dont like to be Flamebait, because they burn so well. Protect our Troll heritage!
    2. Re:FreeBSD = top quality by Anonymous Coward · · Score: 0

      He was talking about being trivial to use in comparison to Linux, in particular Debian -- not in comparison to desktop-specialized operating systems. I'm sure that modern Windows, Mac OS, or probably some of the commercial desktopish Linux distros make some tasks much more 'trivial', but I don't think thats what he ment at all.

    3. Re:FreeBSD = top quality by koinu · · Score: 1

      FreeBSD stable hasn't been out for at-least 6 months! I can tell you are lying...

      FreeBSD stable is a branch in the CVS tree. I'm sure it exists longer than 6 months.

      Troll, why did you say you uninstalled Debian in the first place?

      When I started to use FreeBSD my previous operating system was Debian. (Until they really made me angry neglecting KDE. I have been jealous that FreeBSD has always fresh packages which I cannot find on Debian. Furthermore, I wanted to try the CLI platform, aka C# compiler.) Is it clear enough?

      ...obviously so because Linux is always three steps^H 3x better than freeBSD...

      Now look who is the troll. How do you know that Linux is faster? Have you tried FreeBSD? I can clearly show you the opposite.

      This is your preference. You want an old 15+ years operating system instead of Debian Linux?

      What the hell are you talking about? FreeBSD got ten years old last month.

    4. Re:FreeBSD = top quality by strabo · · Score: 2, Informative
      This is your preference. You want an old 15+ years operating system instead of Debian Linux?
      What the hell are you talking about? FreeBSD got ten years old last month.

      And, for completeness, Debian turns ten years old next month.

    5. Re:FreeBSD = top quality by koinu · · Score: 1
      Note that I never said that Debian is bad. This is my favorite Linux distro. I just said that you don't need Linux (except perhaps as a software developer), if you already have FreeBSD installed (it has a good emulation). And I am not using the emulation part except for gaming. I would be glad if games were ported to FreeBSD directly.

      Second thing is, I just wanted to mention that FreeBSD is not older than Linux.

    6. Re:FreeBSD = top quality by curious.corn · · Score: 1

      Yesterday I've seen two engineers trying to share a net connection over two win laptops. The only way they had was thu a wizard and it failed. Had the routing machine been a *nix one it wouldn't have been more difficult than ifup'ing two ports and a sysctl.

      --
      Mi domando chi à il mandante di tutte le cazzate che faccio - Altan
    7. Re:FreeBSD = top quality by AvengerXP · · Score: 1

      ifup'ing two ports and a sysctl.

      I dont even understand that so do you expect the masses to? The wizard isnt perfect but its far from innefective. Ive seen little instances where it failed outside of defective cables. Note : I dont count Windows 98, im talking 2K/ME/XP here. 98 is a mess.

      --
      Trolls dont like to be Flamebait, because they burn so well. Protect our Troll heritage!
    8. Re:FreeBSD = top quality by curious.corn · · Score: 1

      Well, according to MS the masses either get their stuff done through wizards or just don't get anything. In all reasonable *NIX, Linux, BSD distros you get wizards but if they fail (ie, your vendor made a mess or couldn't forsee your particular condition) there's always a console and a set of documented sysadmin commands to get the thing done. I've been messing with LDAP (the thing that MS embraced&extended to make active directory) and remember figuring out insane compatibility between apps that weren't even meant to work together by checking their live debug logs. I know it's not what the avg user would do but a human readable /etc is way much better than a registry hive.

      --
      Mi domando chi à il mandante di tutte le cazzate che faccio - Altan
    9. Re:FreeBSD = top quality by bmad · · Score: 1

      You want an old 15+ years operating system instead of Debian Linux?

      Wow. Since when was age and stability a bad thing?

      IK, IK... IHBT.

    10. Re:FreeBSD = top quality by donweel · · Score: 2, Interesting

      I used Mandrake for years, multibooting with win98. Then I upgraded to XP and there was no way I could get the latest Mandrake to work with XP. I switched to FreeBsd and it worked with no sweat. Weeks of screwing around and lost data, I never looked back at Linux. Another thing, I had the cable guy over to install internet, he screwed around for about an hour or more with XP to get it working, actualy he pulled the plug on my Linksys router, so he actualy didn't. After he left I plugged the router back in hit reset, booted Bsd, ran sysinstall got broadband in about 5 minutes.

      --
      Many a long talk since then I have had with the man in the moon; he had my confidence on the voyage. Joshua Slocum
    11. Re:FreeBSD = top quality by tarius8105 · · Score: 0

      FreeBSD stable hasn't been out for at-least 6 months! I can tell you are lying, and as well expect you to lie in the rest of your post! As for having all that you ever need, people still say the same thing about running DOS4 and Windows 3.1 on their 80286/4MHz computers.

      Dude, you really do not get it. BSD Current would be in comparison to Linux Kernel 2.5, which has been in development for quite sometime. What? you expect that when they make a version that they just throw it out there into the market like Microsoft and say "Most stable ever version"!?

      Anyone that uses Debian doesn't need it uninstalled--case in point. Tell me, Troll, why did you say you uninstalled Debian in the first place? What's the point of trying to use software and then say you have the same thing on freeBSD you want to use? Did you know that freeBSD needs Linux emulation because freeBSD can't allure developers to its operating system when it is inferior to Linux? This is a model trend in operating systems...emulate your superiors.

      Uh reason being that "Linux" developers write specifically for the GNU/Linux operating system. There was a comment post to another bsd article about how BSD programmers dont program specifically to BSD, but GNU/Linux programmers write specifically for GNU/Linux and thats why BSD needs an emulator, for all the system calls that are not POSIX standard.

      This is sooo-old news. You know, Linux companies stopped listing packages and ports because an everage end-user assumes all the software they find at freshmeat.net and sourceforge.net will be default installed. I can't speak any exact numbers, but I'll say that a modern Linux distro includes over 27,000 programs; obviously so because Linux is always three steps^H 3x better than freeBSD. Linux has more software, does not want to emulate the dirtyness of the freeBSD, and Linux is much faster than freeBSD as a previous poster points out.

      So I'm to assume that better means, more then likely to be hacked? Hell I still get redhat errata's like twice a week for redhat 9. FreeBSD is faster if you consider the point that you have to compile for your system as opposed to using RPMS built on another system that might not have use of additional features of your computer (Thats why there are i386, i486, i586, and i686 arch rpms). Besides I like not having 27,000 different crap installed that I might never use.

      If the manpages were no good, how would you install freeBSD? As an example of the superiority of Linux, manpages are no longer installed because Linux is up-front easy to use. Nobody neads information; they just login to bash and exec or startx whatever program they want (TAB TAB), or opt to have X/KDE or X/Gnome startup on boot. Networking configuration and Movie watching in Linux needs no discussion; it is easy. You need to describe all the recent talents the freeBSD leached off Linux. Linux isn't like that. Comparing Linux and freeBSD with a woman of herpes, everyone assumes Linux has herpes while freeBSD fucks you in the ass and later tells you that it had herpes after it fucked you in the ass.

      That is so wrong, Linux still has man pages, some of them say to use info command to find out more information. However, linux is poorly documented then all of the BSD distros out there. I also take it that since you use X that you do not know any other commands then startx? And whatever happened between you and the drunken sailor at the bar should not taken out on BSD. BSD wasnt there to do that to you.

      This is your preference. You want an old 15+ years operating system instead of Debian Linux? That's like walking by a whorehouse of barely nude /legal 17.99 year-old bleached-blonde biker bimbos and prefering the 64+ year-old freshly retired/hammered seasoned seniorita citizens in the whorehouse down the road up-next to the erupting volanoe. Believe me, stick with the barely nude /legal 17.99 year-old bleached-blonde bike

    12. Re:FreeBSD = top quality by tigga · · Score: 1
      Is this a joke? Experts still use floppy instead of PXE Boot or CD-Boot? Have you ever tried to do CD-boot on box without CD-ROM? ;)))
      Or PXE boot on box without NIC, or without PXE support?

      Well, Hotmail did floppy+network install (but their customized install).

    13. Re:FreeBSD = top quality by tigga · · Score: 2, Insightful
      I'll say that a modern Linux distro includes over 27,000 programs;

      Could you please list them?
      FreeBSD has list for 8866 ports.
      Debian has 8710 packages - that means it's no modern, right?

    14. Re:FreeBSD = top quality by Quill_28 · · Score: 1

      Did you know that freeBSD needs Linux emulation because freeBSD can't allure developers to its operating system when it is inferior to Linux? This is a model trend in operating systems...emulate your superiors

      Which is way wine is around. So by your idiot logic Windows is a superior OS because it has more developers? Please. Get a life. So stop your trolling and your FUD. Go take some ritalin.

  55. Death rattle gurgle gurgle by Anonymous Coward · · Score: 0
    It's dead:
    One might well be justified in calling BSD the "Mr. Chips" of operating systems. In the final scene of the classic movie "Goodbye, Mr. Chips", a doctor remarks that it is a shame that the title character -- a masterful schoolteacher now on his death bed -- has never had children.
  56. Re:Awesome by Anonymous Coward · · Score: 0

    On a Unix system where you need to compile most of your applications (and especially the kernel), yes, it IS part of the OS. Under Win32, I'd say no, it's not part of the OS.

  57. You're killing me Larry! by Anonymous Coward · · Score: 0

    Ignore my overworked friend over there. Now is time for the annual *BSD is dying sale! Come on in and try our fine selection of dying products!

    BSDi! BSD86! iBSD! freeBSD! netBSD! openBSD!

    We'll beat any competitors price or your mattress^H^H^H^H^H^H^H dead BSD operating system is freeeee!

  58. Re:bsd problems by paradesign · · Score: 1

    talentless troll! anyone from teh apple section knows that all he did is replace MAC with PC and macOS with BSD. The poor state of trolling dissapoints me, at least you could be original.

    --
    I want 2D games back.
  59. Re:I've always hated you and your comments, usotsu by Anonymous Coward · · Score: 0

    Yes, because putting an "I'm not trolling" tag on your trolls is going to make it less obvious. Excellent strategy.

    Go fuck yourself, you stupid prick. Oh, that's not meant as a troll or a flamebait though. Just so you know.

  60. Re:bsd problems LOL! by Anonymous Coward · · Score: 0

    Mod this troll up!

    Funniest troll I've read in a long time - its a hilarious modification of the anti-Mac troll.

  61. or maybe Gnome? by alienhazard · · Score: 0

    ships with several desktop environments, including K Desktop Environment and GNU Network Object Model Environment.
    I haven't heard Gnome refered to that way in a while. Makes you wonder why they didnt say "Kool Desktop Environment" as well...

    --
    > "I allege that SCO is full of it" -Linus
  62. I've been using 5.1 since release... by Anonymous Coward · · Score: 0

    ...and I'm finding that for end-user applications it's much more stable than 4.7 was, and things just work compared to 4.8. I've been with FreeBSD since 4.4, and here's my recent summary:

    4.4 to 4.6: Used on my 2nd computer at home to burn backup data CDs, FTP and web server. Fairly low-key usage, not running X. No real problems, but it was mostly to learn my way around the OS.

    4.7: Stable, but KDE was a bit broken and Konqueror was a bit flakey. Multimonitor worked nicely at this point, so I switched to using this most of the time (from Windows) on my primary machine at home.

    4.8: Stable, but multimonitor support was broken. A few notable packages had also been broken when they were fixed for 5.0 support. The 4.X series is reaching the end of it's usefulness for desktop use. At this point, I went back to Windows for a bit on my main machine. In retrospect I shouldn't have upgraded from 4.7.

    5.1: Multimonitor support works again (as do X video extensions in multimonitor - something that was not previously be possible), for me stability is excellent compared to 4.7 & 4.8 - I've simply not had a problem with it, although there are a few quirky dependancy problems in the kernel (had to leave a bunch of SCSI stuff enabled or it wouldn't build - even though I don't have any SCSI drives). I'm back on FreeBSD from Windows (except for games).

    5.1 works for me - it's a joy to use as a server - or on the desktop. Each release has been better than the last.

  63. Re:Whoa to those who abuse moderation by EpsCylonB · · Score: 1

    Thanks for reading and have a pleasant morning (or whatever time of day it is, depending on your geometric location).

    Geometric ?, is that a word ?, I think you probably meant geographical.

  64. Re:Awesome by bathmatt · · Score: 1

    I think that most people would agree that libc is a core part of an OS, You really can't do anything w/o it (at least is a .so environment) In the windows world, most people would agree that explorer is part of the O.S, as is the rest of their GUI environment. I am not that up to day with the *BSD O.S, but I am guessing it would not be that complete without any of the GPL tools such as bash, tcsh or whatnot for example. Now the extesion to vi and gcc, somewhere this is a line between those where something stops becoming a O/S and a complete system. I don't thing a O/S is complete until it has a compiler, but that is just me.

  65. Re:bsd problems by Anonymous Coward · · Score: 0

    Is there a reason that it is not enabled by default? Because with it off, it seems the OS would be quite useless at speeds like that.

  66. Re:*BSD is dying by njdj · · Score: 0, Flamebait

    *BSD is dead.

    Fact: *BSD is dying

    Make your mind up, mate. It can't be both 'dead' and 'dying'.

  67. HILARIOUS by iSwitched · · Score: 1

    Thanks for the hearty guffaw. And don't pay any attention to the negative posts by kiddies who've obviously not actually been employed in the 'real world'.

    The scary part is, I once worked for a guy who sounded exactly like this! Except that he was serious and had no idea what an idiot he sounded like.

    --
    "That naive cube! How long must I suffer this!" --Sheldon J. Plankton
  68. Re:mac problems by Anonymous Coward · · Score: 0

    anyone replying to a troll gets trolled too.

    Idiot.

  69. LinuxThreads by Anonymous Coward · · Score: 0

    Maybe when it develops a robust way to handle multi-threaded applications that still use the same shared memory (read mysql) it will be a viable option.

    That is unless you talk to the only bsd guy in the shop.... but again who really wants to tinker...

  70. Re:bsd problems by Anonymous Coward · · Score: 0
    Most everyone can 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.

  71. Why Bother? by Anonymous Coward · · Score: 0

    Apple Mac OS X has all the benefits of FreeBSD,plus much much more. It has a better GUI, and it runs on better hardware (faster CPU's, etc). In addition, it runs way more software. Both commercial and open source, too. It is also supported by a visionary corporation that has been able to create software and hardware that literally redefine computing. FreeBSD (and Linux for that matter) are by comparison, quite primitive and not much more than hobby systems for people who are not really interested in cutting edge technology.

  72. Ever heard of the BS bingo ? by forged · · Score: 2, Funny

    Try this out ! I know that there are several versions out there, one of them specific to I.T. but I don't remember the link off-hand... Someone feeds this post through the B*S Bingo for some fun !

    1. Re:Ever heard of the BS bingo ? by jonadab · · Score: 1

      So basically you're saying that we need to follow up our action opportunity by revisiting our objectives and re-orienting our goals according to an open-source mindset so that we can pro-actively leverage agglutinative team dynamics and team-building best practices to create bottom-up holistic synergy through the empowerment and integration of key team players on the front lines of our sales and production demographics into our prioritized mind share, so as to focus everyone on the same page going forward in a fault-tolerant, results-driven, and robust expectations paradigm that will initiate strategic core competencies in our interpersonal assets management, foster win-win outside-the-box thinking in our targeted skill-set networking and group-to-group issues collaboration ecosystem, set us on a critical path to achieve total quality in our quality-driven, services-oriented resources management game plan, monetize the reusability of our top-down multitasking approach, and up-sell the competition in the new economy.

      --
      Cut that out, or I will ship you to Norilsk in a box.
  73. the Failure of *BSD by Anonymous Coward · · Score: 0
    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.

  74. Re:bsd problems by Anonymous Coward · · Score: 0

    Not only that, but the mac version was also posted for this article, up the page a ways.

  75. But the license is the key... by emil · · Score: 2, Interesting

    While I recently abandoned RedHat for OpenBSD, I am uncomfortable in the knowledge that Microsoft could continue to incorporate BSD code into their Windows variants, and that I am helping this process by purchasing OpenBSD CDs. While I love the reduction in traffic on the OpenBSD errata channel (vs. RedHat), I do not wish to see the Microsoft monopoly continue, and the only thing that will stop it is the GPL.

    While I realize that I could simply attach the GPL to every piece of source code in the BSD CVS tree and redistibute it, my actions would not in reality hamper any corporate acquisitions of BSD code.

    Ideally, I would like to see the hacker community free to use the BSD license, while I would like to force the corporate community to abide by the GPL in every piece of software they produce (as will someday occur when Microsoft is finally defeated by "viral" GPL code).

    I haven't always felt this way, but US corporations are abusive in many ways, and I would like to see them be more forcibly restrained. A judge instantaneously applying the GPL to all Microsoft software would be a real joy.

    1. Re:But the license is the key... by Geekboy(Wizard) · · Score: 1

      I am proud that MS can incorporate OpenBSD code into Windows. That is the entire point of the BSD license. =)

      I don't see how a judge applying GPL to all MS software would be a joy. I would look at it to figure out the API for Office docs, then run like hell.

    2. Re:But the license is the key... by ffsnjb · · Score: 2, Insightful

      Troll. You obviously don't understand the concept of free software: software that anyone can use, including Microsoft. I'm sure the BSD community is just tickled pink knowing that they write software that even MS thinks is great. Now, if only we could get rid of all the viral (your term, not mine) GNU software from FreeBSD. That there is my dream. If only I had the time to write a compiler...

      --
      "Why do you consent to live in ignorance and fear?" - Bad Religion
    3. Re:But the license is the key... by AHumbleOpinion · · Score: 1

      In light of your comments the original quotation should be updated:

      ...the BSDs have always been the choice of system administrators who cared more about integrity, security, and reliability, than sizzle and flash or politics .

    4. Re:But the license is the key... by cozman69 · · Score: 1

      As a longtime BSD user I don't really mind the Microsoft monopoly as it has little or no effect on BSD OSs. If Microsoft decides to use all the BSD code it wants it doesn't make a difference. Microsoft didn't become a monopoly because of BSD code (that should be obvious from the quality of the software that Microsoft produces). I am much more entertained by the actual technical aspects of the BSDs rather than the political aspects of the OS market.

      While you can take the BSD code and GPL license it, wouldn't that just be another Linux-like OS ? The BSD license causes BSD code to show up all over the place, prompting a faster development of the OS industry as a whole. I generally tend to think of the BSD developers as less selfish than the Linux developers (but that's just my opinion).

      In the long run, I think the "task" of "defeating" Microsoft is best left to GNU/Linux. If you still want to brag about BSD, you can point to Mac OS X, a BSD based OS which already surpasses Windows in ease-of-use and stability.

      A judge instantaneously applying the GPL to all Microsoft software would be a real joy.

      Sorry, but I don't think that's how capitalism works.

    5. Re:But the license is the key... by Groganz · · Score: 1
      While I realize that I could simply attach the GPL to every piece of source code in the BSD CVS tree and redistibute it...
      No you can't. Have you bothered to read a BSD license or anything about copyright law? You must retain the license on a redistributed source or binary file and only the copyright holder has the right to alter that license. The BSD license is a free license but it is not public domain.
  76. Java ? by Anonymous Coward · · Score: 0

    I'm always wondering why doesn't people use Java for such large developments... If tomorrow X86 is declared illegal because of the lack of DRM (very unlikely though), you just reinstall buy DRM hardware with a java vm ( i.e., pre-installed windows box) and keep on going.

    Multi-platform is an invaluable freedom on such projects where deployment and operating costs are so high
    *.sig: No such file or directory

    1. Re:Java ? by tigga · · Score: 1
      buy DRM hardware with a java vm ( i.e., pre-installed windows box) and keep on going.

      Heh, Microsoft has Java VM circa 1998 - very useful ;))

    2. Re:Java ? by Anonymous Coward · · Score: 0

      Quick summary: real Java doesn't work on BSD. No such animal

  77. Modifications can be, you mean by Chad+E+Dirks · · Score: 1

    "What the GPL of course DOES guarantee is that the software can't become proprietary at any point, whereas the BSDs can be"

    Just to be cleear, modifications can become proprietary, but what is presently available under the BSD license will always be available under the BSD license.

  78. biased flamebait statement in extremetech review by C_Kode · · Score: 1

    The BSD philosophy also differs from that of Linux. Proponents of Linux tend to take a "revolutionary" stance, seeing their work as a war to compete with, and destroy, Microsoft and other commercial software vendors. But the BSDs are content to coexist with commercial software, and in fact are happy to allow commercial software to use what they create.

    This is a bias statement that can not only apply to Linux, but any version of BSD. I'm pro linux, but I don't see Linux as a tool to kill Microsoft. I'm also pro BSD, but don't see it as that way either. I actually find BSD harder to work with in a enterprise environment due to the lack of software. I've been lucky enough to use Linux in many locations within the workplace because it's suited to the job (webserver/email server/ databases) and it has all the software I require to run it. (the main issues are BSD backup support for my hardware/software)

    Don't get me wrong. I love FreeBSD. It's my utility server at home. (procmail/ftp/webserver/database/file server-mp3s) I just prefer linux as my desktop (the drivers make a world of difference) at home.

  79. And people call it redundant... by Chad+E+Dirks · · Score: 1

    And to think, people call it redundant when RMS and others point out that "Linux" refers only to the kernel.

    Obviously we need to continue making clear the distinction if reviewers supposedly "in the know" don't have it straight.

    If we call the OS "Linux", what are we going to call the kernel? What are we going to call the OS, if it ceases using the Linux kernel.

    With some work, any of the major Linux-based distributions could probably replace the Linux kernel with the FreeBSD kernel and many end users, particularly those who do not understand the OS/kernel distinction, would be none the wiser.

    In this case, it would clearly be incorrect to call the OS "Linux", but these end users would not understand why this is so.

    1. Re:And people call it redundant... by Anonymous Coward · · Score: 0

      With some work, some new BSD spinoff could replace the FreeBSD kernel with the Linux kernel. This way you get to be flashy and cool with the Linux kernel but kill all the bloat and use the great ports collection of the FreeBSD system.

      What would you call _that OS?

    2. Re:And people call it redundant... by phoenix_rizzen · · Score: 1

      Oh, you mean like the Debian releases based on the NetBSD and FreeBSD kernels? :)

    3. Re:And people call it redundant... by Chad+E+Dirks · · Score: 1

      I have never used or read in depth about the modern BSDs. I don't know what nomenclature that community uses or would prefer.

      My understanding is that "BSD" has historically and does presently refer specifically to an entire distribution of software. Linux, historically, appears to have referred primarily to a kernel.

      "What would you call _that OS?"

      Probably, I would call it "FreeBSD" if it is true that the "BSD" of "FreeBSD" has historically and does presently refer to an entire software distribution, as in this case, the great majority of software in the distribution would remain unchanged.

      Similarly with Linux, I find myself more often referring to a particular distribution than to Linux-based systems generically.

    4. Re:And people call it redundant... by Chad+E+Dirks · · Score: 1

      Precisely projects of that sort, yes. Good point.

      Although I hadn't had those Debian projects particularly in mind when posting.

    5. Re:And people call it redundant... by merdark · · Score: 1

      Yo, it's called Gentoo.

      But on a side note, I'd *never* want to replace the FreeBSD kernel with Linux. There *is* a reason I use FreeBSD after all. Part of it is the user space and system integration, but a lot of it is the kernel.

    6. Re:And people call it redundant... by nutznboltz · · Score: 1
      What are we going to call the OS, if it ceases using the Linux kernel.
      Debian GNU/NetBSD
  80. Extreme oldTech by Anonymous Coward · · Score: 0

    Did anyone else catch that the Extreme tech article is more than a little out of date? Posted originally Sept 22/02?

    StatiK76

    1. Re:Extreme oldTech by Anonymous Coward · · Score: 0
      No surprise, after all it is no secret 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.

  81. what do you expect? It's written by Brett Glass by ksheff · · Score: 2, Interesting

    He's been harping on the "you can't sell GPL software" point for years even though it's not true. Linux people may also take issue with the quote that it was based on Minix. He's about as much of a pro-BSD, anti-Linux, anti-GPL person as you can get. Notice while he said that many systems are dependent on BSD code, he neglects also note that BSD relies on some GNU code as well.

    --
    the good ground has been paved over by suicidal maniacs
  82. You're Right by Anonymous Coward · · Score: 0

    This article was patheticly low in actual content. It reminds me of the Movie Review's by Teenages that many local newspapers like to do in lieu of hiring actual professional movie critics.

    It would be nice if some real-world IT type person who uses various unix type technologies on a daily basis would provide a review instead.

  83. Kevin, please stop this stupidity. by Anonymous Coward · · Score: 0

    Kevin,

    I wish you would stop posting this crap and just move on with your life. I'm sorry that things worked out the way they did, but you gave us no choice. As it was, I spent a lot of time convincing Jon and Bill not to have you brought up on criminal charges. I even managed to get you a week's severence.

    Instead of being grateful that they gave you a break, you have become obsessed with trying to sabotage their business -- but your *BSD is dying posts are just childish and silly. We move more product now than when you left. No one is cancelling orders because of your anonymous messages on Slashdot.

    I think that you could still have a bright future, but if this keeps up, Jon and Bill are going to get pissed off and have you brought up on criminal charges. Is that what you want? How many jobs will you get when potential employers see a criminal record that includes the theft of company computer equipment? Jon still has the laptop that he bought back from the pawn shop along with the company's original purchase records for it. He still has printouts of the ads you put up on ebay for the DLT auto-loader and the RAID array. There are records showing that your badge was used to gain entrance to the building at 2:13AM on the day that the equipment was stolen. On top of the thefts, we also have logs showing your attempts to break into the servers using your ID the evening after you were let go.

    Do you want to end up being some guy's bitch in prison? That's what may happen if you keep this up. If you think that your shopping mall karate classes are going to do you any good there, you are in for a shock.

    Tim

    P.S. Please don't bother with denying this, who you are, and so forth. This started practically the day after you were let go. The writing style and the Kreskin reference leaves no doubt as to who's posting this. (Like someone else is going to go to that much trouble to discredit BSD and then not sign their name! Get real.)

    1. Re:Kevin, please stop this stupidity. by Anonymous Coward · · Score: 0
      Tim,

      I don't know why you harbor a vendetta against me. Don't blame the messenger. We both know *BSD is dying. Suck it up and take your medicine like a man. It's all over for *BSD. Deal with it and get on with your life.

      Kevin

  84. Re:the article itself is sort of flamebait by itse by Anonymous Coward · · Score: 0

    You got it reversed: apple is to BSD as orange is to Linux. :-)

  85. Making the case for BSD by HardcoreGamer · · Score: 1

    In a recent eWeek analysis/opinion piece, ZDNet's Technical Director Jim Rapoza argues the case for BSD. He talks about some of the history of BSD, and says that "FreeBSD is probably the most Linux-like of the three, with good third-party application packages and user utilities."

    By the same token he also says that the greatest weakness of the BSDs "for those seeking an everyday operating system, is the lack of good desktop applications." Then he turns around and says that "if you really want a BSD-based system that has an excellent--maybe even the best--desktop and user application environment, there's always Mac OS X, which is based on BSD."

    Interesting analysis and opinion piece. But it's pretty clear that he's a BSD proponent.

  86. Well is it or isn't it???? by Anonymous Coward · · Score: 0

    From the "linked" article by Brett Glass
    http://www.extremetech.com/print_article/0, 3998,a= 31573,00.asp

    What is BSD? If you ask a typical computer "expert," he or she is likely to reply (incorrectly!) that it is "an operating system."

    ...programmers quickly developed replacements for these six files and made the BSDs into usable operating systems...

    Nowadays, the term "The BSDs" refers to the family of operating systems...

    Brett, what's up with this??? Is it or isn't it? I know that FreeBSD is and I appreciate it and use it every day. It has never failed to preform a task I have wanted it to do. Viva BSDs, whatever they are.

  87. happy dd to you by ratfynk · · Score: 1

    dd if=0 of=(whatever you want to hose!) Windows, a corrupted partition, your C drive? You never know. I love it.

    --
    OH THE SHAME I fell off the wagon and use sigs again!
  88. I DO IT RONG!! by Anonymous Coward · · Score: 0

    I do it wrong

    Laying here in the shadows of my room, I squint up at my love. My Ms. Portman. I am sore and tired after fucking her for eight solid hours. My chapped and aching dick is soaking in grits to relieve the pain. She gets on her knees and starts lapping the grits up out of the bowl. She places her beautiful hands on my penis and starts to lick the grits off my achy piece.
    Massaging my nutsack she....

    WAIT, I DO IT WRONG!!!!

    Yanking my dick out of her mouth I throw her to the ground and shove it in to her gaping freshly fisted ass. [goatse.cx]

    OH BIG ASS SPORK!! Fuck my ass, fuck my ass good. DEEPER, my stallion, deeper!! Make a Beowulf cluster of sperm on my back!!

    Imagine a Beowulf cluster of this baby!

    I DO IT WRONG!!!!

    I continue to hump her alabaster form. Glistening with beads of sweat, she bites her lip in delight as I tear her ass open with my engorged dick.

    Queen Amidala!! I shreik as I near climax.

    She looks up at me and screams, You are so alive in me, unlike *BSD or VA Software!!! Fill me with seed!! Yes, Yes, Yess!!!!

    For me you are calling, hhhmmm?

    YODA?!? What the fuck, can't you see I am using the force here?

    He savagely kicks my Natalie aside, he pulls out his large green penis and impales me...

    I DO IT WRONG!!

  89. Re:Awesome by merdark · · Score: 1

    Actually, gcc is the only *required* GPL program. I think all the other parts of a BSD system are BSD licensed. This includes libc, ash, and even a vi clone.

    It is less clear that a compiler is really a core part of an OS. It may be required to be practical, but I have an openbsd box on old hardware without a compiler! It's very usable!

  90. Re:biased flamebait statement in extremetech revie by Anonymous Coward · · Score: 0

    It's basically true though.

  91. s/BSD/Linux by pr0ntab · · Score: 3, Funny

    So bottom line is, I really liked a lot of Linux's features, but unfortunately an OS without programs is useless.

    If you want x86 Unix with some commercial support, there is Linux. If you just want commercial support, there is Windows.

    You can still get the commercial apps to work on BSD (and some may be native), but that's not why you are using it. You are using it because you are a geek and you're not a slashbot, macophile, amiga-freak, microsoftie, or aol-er. Also, you don't like getting 0wn3d.

    --
    Fuck Beta. Fuck Dice
  92. GNU's not . . . by Anonymous Coward · · Score: 0

    GNU's not Linux.

  93. Your point applies - for all software by lightcycle · · Score: 1

    But those three reasons are more or less why people pay for Widows, or any other proprietary software:
    1. Philisophical/moral reasons: They don't want to freeload
    2. CD vs p2p/warez-site
    3. They are not paying for Windows, but to keep the BSA out of their hair, or they got their legal windows when they bought their computer
    Laws aside (And in this case they are somewhat irrelevant) nobody will pay for commercial/proprietary software either, unless for moral reasons

    --

    The stars that shine and the stars that shrink
    in the face of stagnation the water runs before your eyes
  94. Re:Whoa to those who abuse moderation by jonadab · · Score: 1

    > Geometric ?, is that a word ?

    Yes. A geometric progression is one in which the second-order
    operation[1] is used rather than the first-order operation[2] to
    process each element of the progression in order to acquire the
    subsequent element. When charted on a cartesian visualization
    system, a geometric progression will be parabolic; whereas, an
    arithmetic progression would be linear.

    There are of course higher-order progression classes than the
    geometric class; by leveraging a higher-order operation it is
    possible to achieve progression performance on a scale that will
    cause the competition to revisit their benchmarks. The gamma
    progression is generally considered the market leader going
    forward in this regard. By incorporating integration of this
    function into your gameplan, you can achieve results-driven
    core competency in the progressions market.

    [1] Colloquially, "multiplication", although any second-order
    function will do; it does not have to be traditional
    Real-number multiplication.

    [2] Colloquially, "addition", but with the same qualification
    as for "multiplication".

    --
    Cut that out, or I will ship you to Norilsk in a box.
  95. Re:Whoa to those who abuse moderation by jonadab · · Score: 1

    > The gamma progression

    I should have put a third footnote there:
    Colloquially, "factorial".

    --
    Cut that out, or I will ship you to Norilsk in a box.
  96. X problems by jbolden · · Score: 0, Insightful

    1) I had a very common system (Inspiron 8000 which sold millions). I couldn't find a 5.0 configuration file which allowed me to use X (Nvidia driver incompatable). Even in the mid 1990s I could always get Linux X to run 640x480 on a machine.

    2) Slight errors in syntax when using ports results in ports trying to compile everything. Good system which needs a better safety.

    3) The configuration system doesn't allow for small changes easily (like getting rid of an IP).

    Linux now has: autohardware detection, good drivers, sample configs for virtually every system, lots and lots and lots of documentation.

    How is BSD "friendlier"?

    1. Re:X problems by xA40D · · Score: 4, Informative

      (Nvidia driver incompatable)

      Hmmm, I thought Inspiron's had ATI RAGE Mobility M4 graphics. Running X on mine at 640x480 was real easy, as was 800x600. I will admit that getting native resolution is a pain, but such issues are really down to the XFree86 Project, not the OS.

      Slight errors in syntax when using ports

      So the OS is at fault when you tell it to do something stoopid? You can only make such mistakes if you is root, and the world and his dog know that being root is DANGEROUS! I once fooked a Linux box when I accidentally did an rm-rf /dev but blaming the OS for my mistake would be churlish.

      The configuration system doesn't allow for small changes easily

      Right. And the SysV rc[0-6].d system is intuitive is it? I've always found BSD OSs much easier to reconfigure. The new RC subsystem has made this even easier.

      like getting rid of an IP

      ifconfig fxp1 inet 192.168.9.1 delete

      Then delete the relevant line from /etc/rc.conf if it's permanemt

      Linux now has: autohardware detection, good drivers, sample configs for virtually every system

      As does FreeBSD.

      lots and lots and lots of documentation.

      Yes. And most of it is out of date crap. I picked FreeBSD because finding useful Linux documentation proved so tiresome.

      How is BSD "friendlier"?

      Because the core team concentrate on doing things in a thoughtful, considered, and logical way; with major changes being implemented gradually and then only after a full peer review; and versioning system that makes sense.

      Oh yes, we also don't spawn a new distro every time somebody decides they want to do stuff their own way.

      --
      Do you mind, your karma has just run over my dogma.
    2. Re:X problems by gr · · Score: 2, Funny
      Oh yes, we also don't spawn a new distro every time somebody decides they want to do stuff their own way.
      You know, with the exception of certain Canadians. ;^> (In case the smiley isn't sufficient, that's a joke. All my computers run NetBSD.)
      --
      Do you have a /. uid shorter than five digits? No? Then piss off.
    3. Re:X problems by gr · · Score: 3, Interesting
      1) I had a very common system (Inspiron 8000 which sold millions). I couldn't find a 5.0 configuration file which allowed me to use X (Nvidia driver incompatable). Even in the mid 1990s I could always get Linux X to run 640x480 on a machine.
      What has the operating system to do with the XFree86 driver for your laptop? It's exactly the same code under FreeBSD as it is under Linux, provided you're using the same version of X.

      Is your problem really which version of XF86 ships with FreeBSD 5?
      2) Slight errors in syntax when using ports results in ports trying to compile everything. Good system which needs a better safety.
      Without a bit more specification, I can't speak to that particularly well, especially since I'm speaking mostly from NetBSD pkgsrc experience, but if ports is still what it was the last time I looked, it's pretty similar to pkgsrc, and is essentially just a bunch of Makefiles. If you don't want to build things, don't use the source version. On NetBSD, that means "instead of doing a make in pkgsrc/<utility type>/<package name>, do pkg_add <package name>". I have to assume that the FreeBSD ports commands are functionally similar since they're approaching the same problem the same way...
      3) The configuration system doesn't allow for small changes easily (like getting rid of an IP).
      Again, without a bit more detail, I can't comprehend how this was a problem. Is it a complaint against (POSIX standard, where Linux's is not) ifconfig(8) syntax? Is it a complaint against /etc/ifconfig.* files (whoops, maybe that's NetBSD-specific... though /etc/ifconfig.* matches the functionality of Solaris's /etc/hostname.*)? Or is it a complaint about removing some non-standard addition to a configuration file on a specific system?
      Linux now has: autohardware detection,
      ... if you're using Red Hat.
      good drivers,
      Oh, that must be why the BroadCom Tigon3 gigabit Ethernet chipsets in my Dell PowerEdge 2650s work so well. (The choices are: use BroadCom's closed-source bcm5700 driver, which is stable but runs at about one fifth the actual throughput you'd expect out of a gigabit ethernet connection, and, for bonus points, pads packets with random bits of kernel memory rather than 0s as it should; or use the community supported tg3 driver, which has really great performance, but will randomly, when under load for more than 24 hours, start passing only one in about one hundred packets.)
      sample configs for virtually every system,
      Aside from being a virtual impossibility, I doubt Linux provides much in the way of sample config files for, say, a Shark DNard. Or did you mean software system, not computer system?
      lots and lots and lots of documentation.
      ... which is held to no particular standard and, especially on the web, varies from quite good to wrong-headed to flat out wrong, distinctions the beginner has no hope of making ("Gee, this guy's web page is pretty, his advice must be right!").
      How is BSD "friendlier"?
      Let's have a look at the comment to which your little flamefest here is intended to reply, shall we?
      I have found FreeBSD more friendly than any of the so-called friendly linuxes out there.
      I don't see any overall value judgement that any operating system is friendlier than any other there. It seems pretty clear that that is a personal opinion. That's what "I have found" means. Sheesh.
      --
      Do you have a /. uid shorter than five digits? No? Then piss off.
    4. Re:X problems by Nevyn · · Score: 1
      Linux now has: autohardware detection,
      ... if you're using Red Hat.

      Yeh, whatever you do, when making comparisons between FreeBSD and Linux always choose the version of FreeBSD "out in a couple of months" and the lowest common denominator of all Linux distributions.

      The choices are: use BroadCom's closed-source bcm5700 driver, [...]; or use the community supported tg3 driver, which has really great performance, but will randomly, when under load for more than 24 hours, start passing only one in about one hundred packets.

      The "community" supported tg3 driver, is now both recommended by broadcom and been stable under very high loads for months (at least with all the Red Hat customers, who have the drivers that they helped write and fix).

      --
      ustr: Managed string API with ave. 44% overhead over strdup(), for 0-20B
  97. Reports of BSD death are premature! by ratfynk · · Score: 2, Informative
    FreeBSD is dying.

    Geepers I've seen this lame troll post before! If freebsd is dead then it sure is making alot of noise. If you really are into coding then bsd is alot more fun than anything else around.

    The kernel is rock solid and is easier to test virtual environments without hosing some core config. The core libraries are very easy to protect, and duplicate. The unfortunate thing that I have found about Linux is that the core libraries other than the Kernel make ./config on cross platforms a nightmare with some distros. Slackware is the only one thats still easy to figure out the path structure. With only one official Freebsd some people who are getting tired of having to find paths to ./config for the different Linux distros are switching to Slackware and FreeBSD, for the sake of their santity. To those who like to code for KDE Slackware runs about 30% faster with KDE 3 than Mandrake or RedHat. Bsd smokes if you set it up right. For the bunch that do shell scripts and code in Vi (and its variant) Bsd and Slackware are still the best dual boot and the closest to a real programmers tool. So what if you do not default boot directly into a window manager, unless you set it up. I still like to type startx and find that Mandrake and RedHat installs since version 8 have become geared to Windows users (which is fine) not the Gnu/Bsd/Linux community as a whole.

    FreeBsd, Slackware, and Debian have an important place in the free software world they are and will remain the developement platforms of choice, because choice is what they deliver.

    --
    OH THE SHAME I fell off the wagon and use sigs again!
    1. Re:Reports of BSD death are premature! by Perky_Goth · · Score: 1

      Yes, you've seen it. It usually gets a +5 funny. It's getting old now... There's a page on the web that generates dupes of that, just replace the strings with the OS, variants, Manufacture, etc.

      I won't be trying FreeBSD, though, did it once and seems too messy. I'll get comfy with Linux and then try it.

    2. Re:Reports of BSD death are premature! by ratfynk · · Score: 2, Insightful
      I cannot for the life of me see how Freebsd is messy. Sure you can screw things up but the man pages are great. It is easy to move things, change config, etc etc. If you are just interested in running X and not really learning to use a shell then mandrake9 fits the bill. Just remember there can be dependancy diffs between mdkrpm and rpm and debs. I much prefer to compile stuff from source and read the dependancy requirements first. To this end Slackware and Freebsd are the best, even though they have app-get and ports, it is very easy to find the right paths, when you try out a new app that is only available .tgz Changing things in ./configure, or commenting out functions, or changing dependancy paths are essential Linux skills.

      Sure effectively using make, chown, chroot, and shells etc in Freebsd and Slackware is a big learning curve. The upside is it makes you much more aware of how things work, and a better GNU/bee.

      --
      OH THE SHAME I fell off the wagon and use sigs again!
    3. Re:Reports of BSD death are premature! by Anonymous Coward · · Score: 0
      Come on now! It is no secret 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.

  98. Found this little gem buried in the article.. by avidday · · Score: 1
    FreeBSD currently runs on Intel-compatible 32-bit processors (including the AMD Athlon) and on the DEC Alpha processor (now out of production)
    Since when did the Alpha shuffle of this mortal coil???
    1. Re:Found this little gem buried in the article.. by phoenix_rizzen · · Score: 1

      Round about the time DEC was bought by Compaq, back in the 90's. A lot of the tech was sold to Intel or licensed by AMD, but all the engineers etc went to Compaq.

      The final death knell for the Alpha was the merger between Compaq and HP.

  99. FreeBSD by Anonymous Coward · · Score: 0

    FreeBSD is just a Gentoo Linux wannabe.

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

      And you probably had a bad grade in history.

  100. Re:the article itself is sort of flamebait by itse by Anonymous Coward · · Score: 0

    The old crappy poker AI has a pretty good shot at winning. Read other people's messages before posting your own to avoid simply duplicating a better feature would be a tutorial. Replies to your comments are sent to you at the same time that the Go project announces its formation and the release today to the worldwide open source development community. It has some good points, and I think it sums up what many of us know, but haven't quite been able to put into words yet--then your phone rings! I can't begin to count the number of times that happens. BSD won't survive another year. Its time on earth is over.

  101. Elegy for *BSD by Anonymous Coward · · Score: 0

    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.

  102. Last rites: What Killed FreeBSD by Anonymous Coward · · Score: 0
    The End of FreeBSD

    [ note: in this following text, former FreeBSD developer Mike Smith gives his reasons for abandoning FreeBSD]

    When I stood for election to the FreeBSD core team nearly two years ago, many of you will recall that it was after a long series of debates during which I maintained that too much organisation, too many rules and too much formality would be a bad thing for the project.

    Today, as I read the latest discussions on the future of the FreeBSD project, I see the same problem; a few new faces and many of the old going over the same tired arguments and suggesting variations on the same worthless schemes. Frankly I'm sick of it.

    FreeBSD used to be fun. It used to be about doing things the right way. It used to be something that you could sink your teeth into when the mundane chores of programming for a living got you down. It was something cool and exciting; a way to spend your spare time on an endeavour you loved that was at the same time wholesome and worthwhile.

    It's not anymore. It's about bylaws and committees and reports and milestones, telling others what to do and doing what you're told. It's about who can rant the longest or shout the loudest or mislead the most people into a bloc in order to legitimise doing what they think is best. Individuals notwithstanding, the project as a whole has lost track of where it's going, and has instead become obsessed with process and mechanics.

    So I'm leaving core. I don't want to feel like I should be "doing something" about a project that has lost interest in having something done for it. I don't have the energy to fight what has clearly become a losing battle; I have a life to live and a job to keep, and I won't achieve any of the goals I personally consider worthwhile if I remain obligated to care for the project.

    Discussion

    I'm sure that I've offended some people already; I'm sure that by the time I'm done here, I'll have offended more. If you feel a need to play to the crowd in your replies rather than make a sincere effort to address the problems I'm discussing here, please do us the courtesy of playing your politics openly.

    From a technical perspective, the project faces a set of challenges that significantly outstrips our ability to deliver. Some of the resources that we need to address these challenges are tied up in the fruitless metadiscussions that have raged since we made the mistake of electing officers. Others have left in disgust, or been driven out by the culture of abuse and distraction that has grown up since then. More may well remain available to recruitment, but while the project is busy infighting our chances for successful outreach are sorely diminished.

    There's no simple solution to this. For the project to move forward, one or the other of the warring philosophies must win out; either the project returns to its laid-back roots and gets on with the work, or it transforms into a super-organised engineering project and executes a brilliant plan to deliver what, ultimately, we all know we want.

    Whatever path is chosen, whatever balance is struck, the choosing and the striking are the important parts. The current indecision and endless conflict are incompatible with any sort of progress.

    Trying to dissect the above is far beyond the scope of any parting shot, no matter how distended. All I can really ask of you all is to let go of the minutiae for a moment and take a look at the big picture. What is the ultimate goal here? How can we get there with as little overhead as possible? How would you like to be treated by your fellow travellers?

    Shouts

    To the Slashdot "BSD is dying" crowd - big deal. Death is part of the cycle; take a look at your soft, pallid bodies and consider that right this very moment, parts of you are dying. See? It's not so bad.

    To the bulk of the FreeBSD committerbase and the developer community at large - keep your eyes on the real goals. It'

  103. D - E - A - D by Anonymous Coward · · Score: 0
    It is official; Netcraft now confirms: *BSD is dying

    Yet one more crippling bombshell hit the already beleaguered *BSD community when IDC confirmed that *BSD market share has dropped once 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 in the recent Sys Admin comprehensive networking test.

    You don't need to be a Kreskin 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

  104. Re:Reports of BSD death are accurate by Anonymous Coward · · Score: 0
    Ok, so why now--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.

  105. Re:the article itself is sort of flamebait by itse by Anonymous Coward · · Score: 0
    It is univerally accepted that *BSD is a failure. Of that fact there can be no argument. 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.

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

    Subject says it all. Period.

  107. Reports of BSD death by Anonymous Coward · · Score: 0
    While it is true that BSD is dying, there are some helpful steps you can take:
    • deal with the inevitable.
    • grieve for your loss.
    • move on.
    Never let your emotions get tangled up with something as silly as a computer
    operating system. It isn't healthy. So BSD fails. Big whoop. Deal with it and move on.

    My wife is a clinical psychologist. She actually had a patient who was suicidal over
    the declining fortunes of BSD. Pathetic. The advice I gave you is essentially the same
    as she gave her client (and it didn't cost you 500 bucks for the therapy sessions).

    1. Re:Reports of BSD death by Anonymous Coward · · Score: 0
      My wife is a clinical psychologist. She actually had a patient who was suicidal over the declining fortunes of BSD. Pathetic.

      It's unfortunate she cured you.

  108. FreeBSD Rules by Anonymous Coward · · Score: 0

    But under some assumptions.

    - If you have MS background or No University degree, forget it
    - If you have the linux "i want my free support right now you pathetic open source technical support guy" attitude, forget it
    - If you love making conclusions after one hour of "research" , forget it.

    P.S.

    I had JAIL configured.

    Amazing.

    2 IP's, 2 FS Hierarchies, 2 hostnames,
    2 root uids, 2 sendmails, 2 sshds,
    even 2 POSTGRESQL's!!!

    amazing....

    Do any of the guys over here know
    when SYSV IPC will be safely jailified??

    I am sure its just a piece of cake for the FreeBSD
    warriors...

  109. Re:what do you expect? It's written by Brett Glass by tigga · · Score: 1
    he neglects also note that BSD relies on some GNU code as well

    If you are talking about BSD as operation system, than yes - there is some GPLed software included. But there is no GNU stuff in the kernel. You easily could replace GNU programs with programs with about the same functionality and different license. There is no essential dependency on GNU.

  110. Re:*BSD - Born to Die by Anonymous Coward · · Score: 0

    My My He Hey
    FreeBSD is here to stay

    you dumpfunk!

  111. Re:what do you expect? It's written by Brett Glass by micheas · · Score: 1
    You can compile the kernel without any gpl code, But if you compile in a floating point emulator but don't specify no gpl code, you get a gpl tainted kernel.

    Not that this is used very much, but be aware that making Free BSD gpl free is a tricky task, and not worth it for most people.

  112. BSD really is dead by Anonymous Coward · · Score: 0

    When you lose marketshare year after year, when you have lost all commercial support,
    when no major ISV supports you, then you are dead, BSD. You are dead.

  113. Re:*BSD - Born to Die by Anonymous Coward · · Score: 0
    Be honest. BSD is huring real bad. In fact BSD is dying.

    When you lose marketshare year after year, when you have no commercial support,
    when no major ISV supports you, then you are dead, BSD.. You are dead.

  114. but BSD is dying by Anonymous Coward · · Score: 0
    Hey, you know it; I know it; We all know it.

    Fact: FreeBSD is dying

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

      bsd be one dead muthafucka biatch.

    2. Re:but BSD is dying by Anonymous Coward · · Score: 0

      Hey nigga, you misspelled "ded".

  115. Pull your head out of your ass: FreeBSD is dead by Anonymous Coward · · Score: 0
    While it is true that BSD is dying, there are some helpful steps you can take:
    • deal with the inevitable.
    • grieve for your loss.
    • move on.
    Never let your emotions get tangled up with something as silly as a computer
    operating system. It isn't healthy. So BSD fails. Big whoop. Deal with it and move on.
  116. Re:Developer lashes out: What Killed FreeBSD by Anonymous Coward · · Score: 0

    Thanks for the insight. It is hard to argue with facts, and the fact is BSD is dying.

  117. Re:first post by Anonymous Coward · · Score: 0
    Facts to remember:
    1. FreeBSD is dying
    2. OpenBSD is dying
    3. NetBSD is dying
    4. BSDI is dying
    5. *BSD is dying
    Hope this helps.
  118. Re:biased flamebait statement in extremetech revie by Anonymous Coward · · Score: 0
    In case you haven't heard the news:
    *BSD is dying
  119. Re:*BSD is dying by Anonymous Coward · · Score: 0
    You don't need to be a Kreskin 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.

  120. B - S - D - E - A - D by Anonymous Coward · · Score: 0

    BSD dead? Indeed it is. *sob*

  121. Re:FreeBSD = dead by Anonymous Coward · · Score: 0
    BSD has effectively been dead for several years. Ever since Walnut Creek CD Rom died there has been no commercial support for BSD.

    What does remain in the BSD world are a couple of penny-ante "mom and pop" shops, but nothing important. Think about it--crafts shops that sell macrame supplies gross hundreds of times more per year than all the BSD shops combined. BSD is dead commercially, that is for sure.

  122. Re:what do you expect? It's written by Brett Glass by Anonymous Coward · · Score: 0

    Brett Glass has a reputation for playing fast and loose with the facts. We have even banned him from some of the FreeBSD mailing lists. He is a zealot in the worst sense of the word.

  123. FreeBSDead by Anonymous Coward · · Score: 0

    buh bye!

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

      Buh bye yourself.

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

      buh bye freebsd. buh bye you dead rotting corpse.

  124. That article is a bit old isnt it? by pkplex · · Score: 1

    September of 2002? Cmon.

  125. Re:I've always hated you and your comments, usotsu by Anonymous Coward · · Score: 0

    bsd = fags 'n' hags

  126. my review and roundup by Anonymous Coward · · Score: 0
    On a very balmy evening on June 23, 2003 in New York City's historic Carnegie Hall, Petula Clark and an all-star cast took turns paying homage to the legendary Peggy Lee. The evening began with the orchestral arrangement of some of Miss Lee's best known tunes followed by a video montage entitled: "Remembering Miss Peggy Lee" --featuring clips of Miss Lee harmonizing with some of the greatest singers of all time--including a bar or two of her "I'm a Woman" duet with a certain Miss Clark. [Click here for the complete program}

    Petula's turn came early in the second half. With her hair pulled back and wearing her now signature black ensemble (long black skirt, black lace blouse, topped with a black jacket) and backed primarily by Miss Lee's own rhythm section, Petula spoke a few words about having first idolized & then ultimately having sung with Peggy, before enthusiastically launching into the uptempo "Things are Swinging" (written by Peggy Lee & Jack Marshall) using the very same arrangement used by Miss Lee but making it her own. Later, looking stunning in a new gold ensemble (reminiscent of the gorgeous blue dress she wore in Norfolk) she returned to the stage again very near the end of the show. This time, with lush orchestral backing, she sang a very heartfelt rendition of "Circle in the Sky." Both songs were very enthusiastically received, particularly by the front row.

    During a video clip of Miss Lee singing "Is that All There Is," Petula and ensemble returned to the stage for the finale and ended the show with a touching "I'll Be Seeing You" (with Petula being one of the few singers who seemed to know all of the lyrics.)

    During the after-party reception down the street at Shelly's, Petula could be heard sharing "Sunset Boulevard" memories with Rita Moreno (who had taken over the Norma role while Petula had been on vacation) and advising Nancy Sinatra about venue selection & performances in London, while in-between managing to enjoy a piece of chocolate cake and warmly greet several fans with a kiss on each cheek.

    Over lunch the following day she was anxious to hear our comments about the show, confiding that there had been precious little rehearsal and that unfortunately the singers on stage had been unable to hear many of the other performances, much less see them. She also mentioned that while she had been unable to see much from the brightly lit stage, she had very much enjoyed the feel of performing in the Hall, comparing it to the London Palladium and the Paris Olympia. Following lunch, she had a full afternoon of work-related activities scheduled for her and said she would be leaving the following day to return to London to prepare for her June 29th appearance at the Albert Hall, before commencing promotion for the upcoming German CD release.

    All and all, it had been a memorable evening and we were grateful for the time we spent with her, however brief.

  127. FreeBSD = slow painful death by Anonymous Coward · · Score: 0

    Where's the fun in that. Huh.

  128. No Need to. by dmelomed · · Score: 1

    Tiny C Compiler already exists and works.

  129. Google Search Result: "BSD user numbers" by Anonymous Coward · · Score: 0

    First hit:

    http://www.bsd-laptop.org/ .......
    Our users have posted a total of 26 articles
    We have 5 registered users
    The newest registered user is Mo===

    In total there is 1 user online :: 0 Registered, 0 Hidden and 1 Guest [ Administrator ] [ Moderator ]
    Most users ever online was 3 on Mon Jan 20, 2003 10:49 pm
    Registered Users: None

  130. Re:FreeBSD = top quality - FreeBSD is Lord by Zeio · · Score: 3, Informative

    One might like to point out also that FreeBSD is the basis for the best routing OS there is: JunOS. FreeBSD is very ripe for being a commercial product because of the no-nonsense base install, the wonderful kernel which is exceedingly stable and despite the rants of others, is fairly close to being on par with Linux. Linux tends to change rapidly. FreeBSD changes in a more deterministic way. I also must say that bundling the c library and compiler along with a coherent well documented userland is something that Linux systems may want to take a long had look at. I also really like building the kernel, libraries, compiler and userland easily and reliably from a very easy to follow procedure, mine is:
    - cvsup the base system to latest CVS stable release
    - configure /etc/make.conf; CPUTYPE?=p3; CFLAGS= -O2 -pipe -march=pentium3 ; CXXFLAGS+= -fmemoize-lookups -fsave-memoized -O2 -march=pentium3 ; [-march I do repetitively to make sure i get my probably not needed CPU optimizations ;p] ; COPTFLAGS= -O2 -pipe -march=pentium3 ; NOPROFILE= true ; WANT_EXT2FS_MODULE=yes ; MAKE_IDEA= YES ; COMPAT4X= yes ; configure cvsup in /etc/make.conf ; various other tweaks
    - reconfigure kernel config file to include SMP [options SMP; options APIC_IO], and a shorter timeout period for the SCSI driver [options SCSI_DELAY=4000], and I add a few things to support IDE-CD burning [device atapicam], etc.
    - backup /etc
    - clean out /usr/obj
    - in ./usr/src, build system
    make clean && make cleandepend && make cleandir && make clean && make cleandepend && make cleandir [anal retentive cleansing]
    make buildworld ; make buildkernel KERNCONF=SMP
    make installkernel KERNCONF=SMP
    single user mode
    fsck -p ; mount -u / ; mount -a -t ufs ; swapon -a ; adjkerntz -i ;
    mergemaster -p ; make installworld ; mergemaster ; reboot

    Now my whole system is custom made for my CPU and hardware. It lets me see the care taken in building the whole system and shows off a very clean build process.

    The ports system has many meta-ports that make making an instant workstation quite easy to construct. If you don't want to build your ports with massive optimizations, a large cache of packages are available.

    I would like to point out that I have never had an unbuildable world. I've heard of it on -CURRENT, but have never experienced it, but -STABLE is wonderfully - stable!

    Ports could use a rollback feature such as the one found in Gentoo. Not that I long for Gentoo [I've used this system and deprecate it for a multitude of reasons, maybe later], I have supervised many systems and find that FreeBSD is the best in terms of stability and longevity. Of course uptime is more of a game, who can build a better mousetrap, but its certainly not a meaningless metric.

    The biggest hole in FreeBSD at the moment is Sun's fault. Native Java 1.4 support is available with a bizarre license. Interestingly, IBM and Sun's Linux products actually run very well under the Linux emulation support.

    I have never understood the hatred people have for FreeBSD. It bizarre and unfounded. Its a non-RedHat systems to Winux [Windows weenie Linux wannabees] admins, so they have a conniption that real UNIX is complex and detail oriented, and that reading mans, howtos and docs are par for the course - no admin wizards to "save the day." No, you must actually understand and configure something properly.

    The documentation on FreeBSD is superior. There are many, many docs that cover basic to esoteric administration, with a lot of attention paid to performance enhancing things one can do.

    Add Vinum and UFS2 to the stack of features, and you have yourself some fairly serious filesystem support. While I would like to see XFS in FreeBSD as well, it is a pipe dream, as it is still in "stable" Linux - the best file

    --
    Legalize the constitution. Think for yourself question authority.
  131. Re:Hard times for *BSD by nutznboltz · · Score: 1
  132. death by Anonymous Coward · · Score: 0

    you know it's dead .

  133. Re:mac problems by Anonymous Coward · · Score: 0

    Don't you think that BSD is dead already? I would say so; yes I would.