Slashdot Mirror


Why is BSD Not As Popular As Linux?

hill writes "An article over on Economic Times explains why BSD is as not as popular as Linux. Both use an open-source model, but Linux demands the user community to disclose modifications on its source code, while BSD allows its users to make proprietary changes. The current size of the BSD community is estimated at 2 million, with Linux being around 10 million. This is definately worth the read for anyone interested in comparing the two operating systems. " I'm sure we have a few opinions on the subject.

305 of 690 comments (clear)

  1. maybe... by abram_fettig · · Score: 1

    ...because penguins are cuter that daemons?

    1. Re:maybe... by Bruce+Perens · · Score: 1

      You weren't at Comdex.

    2. Re:maybe... by martin-k · · Score: 1
      >> Have you checked out TECHNOCRAT.NET?

      Yeah, great site! I especially love the graphics and the animation.

    3. Re:maybe... by bmetzler · · Score: 2
      Yeah, great site! I especially love the graphics and the animation.

      Waah!!! The links to the graphics are broken. I can't see it.... :)

      -Brent
  2. Linux Logo is cuter by kermyt · · Score: 1

    I think the reason for the awe inspiring sucess of Linux should be obvious. that darn penguin is much cuter than the little devil. that is the same reason imacs ar available in so many cute colors.

  3. The more the better by core · · Score: 5

    First, we should look at it this way: there are 12 million people that use a free unix-like operating system. Most if not all opensource applications run equally well on both. One (Linux) is an implementation from scratch, the other (Free/Net/OpenBSD) has royal blood as it is the direct descendant of 4.4BSD which itself descends from Unix. This should keep happy both the new army of coders that like to toy with new concepts, and the traditionalists for whom 30 year old code doesn't mean outdated, but proven and stable. Both points of view can be defended I think. We therefore have 12 million users and users-developers of free unixish applications, that's great and was absolutely unthinkable 10 years ago!

    As for the technical side, I keep having to look at both the linux and freebsd kernels as part of my work; they are good references. Both have very good parts. I have to say that usually, the solution adopted by FreeBSD is simpler and a lot more commented/documented (take the bogomips case for example; people are starting to wonder what will happen if the cpu speed changes at runtime, how to detect and recalculate it, etc; freebsd spins simply by looking at changes in the hardware clock counter. simpler :). Same for NIC drivers usually (hello, donald becker, do comment weird things :-). But the linux kernel is full of good and new ideas.

    So we need both if we want to keep the high standards we are used to have in the free unices now. That was my original point :) Long and happy life to all the linux and free/open/netbsd hackers, be it kernel or office applications writers :)

    1. Re:The more the better by Foogle · · Score: 1
      I could be mistaken, but I think you'll find a very serious absence of 30-year-old code in any of the three major BSDs.

      -----------

      "You can't shake the Devil's hand and say you're only kidding."

    2. Re:The more the better by Spamizbad · · Score: 1

      State Examples. Besides BSD init scripts.

    3. Re:The more the better by core · · Score: 1

      I could be mistaken, but I think you'll find a very serious absence of 30-year-old code in any of the three major BSDs.

      It's not meant to be taken literally. It can be 5 or 10 year old code. Some of the source files like C headers for network protocols (tcp/ip et al) were certainly created more than 20 years ago, IIRC for 4.2BSD.

      As I said old doesn't mean bad, just that there was no point in changing what wasn't broken. It doesn't mean any of the BSD code is out of date.

    4. Re:The more the better by Zurk · · Score: 1

      yep. the whole kernel is from scratch. be enlightened : http://khg.redhat.com - everything you need to know about linux kernels.

    5. Re:The more the better by Trailer+Trash · · Score: 1

      Linux is an OS kernel, and it is from scratch. Here's a hint, folks. man pages aren't part of the kernel, neither is anything is /usr/bin, or /bin/, or /sbin (see a pattern yet?).

      This is why Stallman notes that what we call "Linux" should be called "GNU/Linux", since an OS kernel is pretty much useless without the programs required to do something, minimally the C compiler.

    6. Re:The more the better by kijiki · · Score: 1

      look, I'll try to make this simple for you. Linux is a kernel. The SLIP, PPP, and qic02 (yay) code is BSD derived.

      Lines of code in 2.2.13 (wc -l `find . -iname "*.[chS]"`):
      ...
      1927155 total

      Lines of code in files containing ANY BSD code (wc -l `find . -name "*.[chS]" | xargs grep -il 'copyright.*regents'`):
      ...
      11011 total

      Sooo.... ~ 0.5% of Linux is BSD derived. Did you have any other stupid claims you wanted shot down?

      (Note: This is ignoring the fact that non-BSD code was undoubtedly added to the 6 .c and 2 .h files that contain BSD code to integrate them into linux.)

    7. Re:The more the better by kijiki · · Score: 1

      oops, got a bit more I forgot to attach to that post:

      number of lines in the openbsd kernel (wc -l `find /usr/src/sys -name "*.[chsS]"`):
      ...
      1874216 total (and this includes non-working ports)

      number of GNU lines (wc -l `find /usr/src/sys/gnu -name "*.[chsS]"`):
      ...
      12004 total

      So OpenBSD (the only BSD I have locally, sorry Free and NetBSDers) contains ~ 0.6% of that EVIL, tainted GNU code. Which, in case you're up too late, is 0.1% more lines than BSDed lines in Linux.

      In other words, not only are the "Linux is full of BSD code" people idiots, at least OpenBSD contains some of that evil FSF/GNU code.

      Note: I run OpenBSD and Linux. I love OpenBSD and think Theo et al are doing a great job. I will not, however, let such foolish statements as "Linux is full of BSD code" pass uncommented. These idiots reflect poorly on the entire free software community, GPLed or BSDed. Please refrain from resorting to lies when advocating your platform of choice, if you insist on advocacy. It undermines your credibility.

  4. Moderation this ARTICLE redundant by FascDot+Killed+My+Pr · · Score: 1

    This discussion is already being held right here
    ---

    --
    Linux MAPI Server!
    http://www.openone.com/software/MailOne/
    (Exchange Migration HOWTO coming soon)
    1. Re:Moderation this ARTICLE redundant by paul.dunne · · Score: 2

      Hah! Proof that complaining about Slashdot doesn't work: JonKatz will be right back after this short break...

  5. It seems fair enough by stimuli · · Score: 2
    Frankly I haven't crawled around in either Kernel to know which is superior, but I'm not about to accept any simplistic analysis that BSD is better than Linux, of visa-versa.

    What I am convinced of, however, is that the BSD's are each a solid piece of work, and each deserves as much attention as Linux has gained lately. It isn't that much work to write software that will run on the BSD's as well a Linux, and I think vendors should be encouraged to support them.

    In the end I'll probably keep using Linux, I'm comfortable with it, but I don't want that choice to be based on a lack vendor support for BSD -- we've all had enough of the "one supported OS" syndrome, let's not continue it.

  6. Interest and Effort by Foogle · · Score: 2
    Well other than the legal-issues that BSD had when they should have been becoming the prominent free OSes, there's the matter of interest, which is directly tied to effort.

    More people are interested in Linux simply because more people are interested in Linux. It's sort of like a rolling ball of snow; Linux is collecting more people as it goes. So are the BSDs but they are a little behind right now.

    -----------

    "You can't shake the Devil's hand and say you're only kidding."

    1. Re:Interest and Effort by Cramer · · Score: 1

      That's not really true. People like the openness of Linux... any idiot can mess about with the kernel, discuss messing about with the kernel, and submit patches and/or new stuff for the main kernel. FreeBSD is a rather closed environment. Of course, these are both good and bad things.

      Compared to Linux, BSD is alot harder to install and always has been. Can you install FreeBSD with only a floppy and a net connection?

    2. Re:Interest and Effort by davet · · Score: 1

      "Can you install FreeBSD with only a floppy and a net connection?"

      Yes, you can. As a matter of fact, I've installed FreeBSD this way on my laptop, which only supports USB peripherials and has a single PCMCIA slot, occupied by the network card. So FreeBSD booted off a USB floppy drive, something I haven't been able to do with any Linux distribution I've encountered.

    3. Re:Interest and Effort by Cramer · · Score: 1

      The boot loader uses the BIOS interface to the floppy. As long as you only need the boot floppy for the initial kernel and ramdisk (assuming the ramdisk is loaded by the boot loader), everything should work ok. Two of my machines have LS-120's so I've got the same problem -- once the kernel takes over, the "floppy" is gone (win98's the only thing that hasn't cared so far.)

      Not that I like Redhat, but have you tried this with RH6.1? (boot from floppy and install from a CD? I think that's the only one that won't ask for the other floppy.)

    4. Re:Interest and Effort by Lazaru5 · · Score: 1

      These are VERY irresponsible comments.

      If you don't know that you CAN do a net install with *BSD, then I would say you're not terribly experienced with their installation process at all and you're not really in a possition to say whether or not they're harder to install.

      As for FreeBSD being closed, that is also not from first hand experience, but from misinformation propogated on this and other forums.

      Want to mess with the kernel? It's in /usr/src/sys. Want to discuss it? `echo "subscribe freebsd-hackers" | mail majordomo@freebsd.org` or check out comp.unix.bsd.freebsd.misc. Want to submit patches/additions? `/usr/bin/send-pr` or use the web interface at http://www.FreeBSD.org/send-pr.html


      People will read your lies and believe them. Please be more cautious.

      --

      --
      My comments and opinions completely reflect those of anyone and anything I am remotely associated with.
    5. Re:Interest and Effort by Cramer · · Score: 1

      Redhat (assuming you have a few spare gigs of HD for all the source)...

      rpm --rebuild


      REBUILD AND RECOMPILE OPTIONS
      There are two other ways to invoke rpm:

      rpm --recompile +

      rpm --rebuild +

      When invoked this way, rpm installs the named source pack-
      age, and does a prep, compile and install. In addition,
      --rebuild builds a new binary package. When the build has
      completed, the build directory is removed (as in --clean)
      and the the sources and spec file for the package are
      removed.

    6. Re:Interest and Effort by Cramer · · Score: 1

      Actually, that "fucking RPM crap" just wraps up the original source tarball and all the bugs^Wchanges done by Redhat (etc.)

      The RPM crap is mostly a Redhat-ism. Other dists have started using it, but some don't. As I recall, slackware is all tarballs and yes, you can do a "make world"-ish rebuild everything.

      This begs the question, "why would you want to?" How often do you have the need to rebuild everything on your hard drive?

    7. Re:Interest and Effort by Cramer · · Score: 1

      All I can say is the first linux system I installed back in '91 was from a single floppy download. It ftp'ed everything it needed to install and went on it's merry way.

      If this is true, why isn't it documented somewhere obvious?

    8. Re:Interest and Effort by Cramer · · Score: 1

      Couldn't be please dispense with babytalk?
      no.

      Yes, it's insane. However, seeing as the netscape source code is 127M!... If one installs everything on the Redhat 6.1 x86 CD, you'd lose about 1.3GB. I've never installed the entire source code, but I'm venturing a guess that it'd be around 4x that size. The Linux kernel is an enormous snowball of code -- there's what, nine arch's in the tarball? Glibc... I'm not gonna go there. [I'll give it a go tonight if the AccelRAID 150 doesn't lock up again #$%@$]

      As for "just type make"... nothing is ever that simple. Someone/thing has to install the source code first. "rpm --rebuild" isn't that much different, but it is a redhat-ism. As it was explained to me a year ago, the FreeBSD "make world" will download the missing source code (via cvs.)

      But this still doesn't answer my previous question: Why would you want to rebuild your entire distribution?

  7. Follow the Money by mr · · Score: 4

    There is no billion dollar IPO backing the hype about BSD.

    The hype will come when:
    1) There is a billion dollar BSD IPO.
    2) When the BSD community starts explaining the biggest advantage of the BSD licence to Multinational corporations. That advantage is, you can choose to HIDE your own source code if you wish. (Get them to at least start supporting OpenSource. Once they find its not as bad as Microsoft says, they will keep coming back for more. Like drugs...the first hit, we'll give ya free.)
    3) Some cleaver BSDers (Hi Pat!) start whispering in Wall Streets ears "Feel that you mised out on the Linux IPO frenzy? Take heart, here is BSD...the next big IPO launchpad. It runs Linux binaries, its OpenSourced, AND the licencing difference over Linux doesn't cause the heads of the lawyers in your IP departments to spin about."

    When the first IPO of BSD is successful, then you will see the people who use Linux instead of the word OpenSource, refer to BSD as OpenSource...and Linux also. And, the more OpenSource is out there, the better for BSD, Linux, Apache, Sendmail, vi,
    NO CARRIER

    --
    If it was said on slashdot, it MUST be true!
    1. Re:Follow the Money by Anonymous Coward · · Score: 1
      That advantage is, you can choose to HIDE your own source code if you wish. (Get them to at least start supporting OpenSource. Once they find its not as bad as Microsoft says, they will keep coming back for more. Like drugs...the first hit, we'll give ya free.)

      This is a definition of "supporting" with which I was previously unfamiliar. After you've been subsidizing their proprietary products, how do you get them to free their software. You can't just stop; there will always be more unpaid employees out there eager to "help"...

    2. Re:Follow the Money by mr · · Score: 1

      Take some time to examine the history of Apple and Rhapsody.

      Note how Apple (one of the most closed companines in existance due to thier past with Apple ][ cloning) has submitted bug fixes to BSD. Note also how Apple had no intention of OpenSourcing the code now called Darwin, and yet here we are today....with even Apple SUPPORTING OpenSource.

      Also note, how the BSD code writer considers SUPPORT of the code as USE of the code.

      If you can't grok the above views of support, perhaps you need to think different?!?

      --
      If it was said on slashdot, it MUST be true!
    3. Re:Follow the Money by Thomas+Charron · · Score: 2

      Linux was successfull *LONG* before the market hype. I hope that's not what you're basing your argument on as to why Linux is more popular then BSD.

      --
      -- I'm the root of all that's evil, but you can call me cookie..
    4. Re:Follow the Money by JordanH · · Score: 2
      • The hype will come when:

        1) There is a billion dollar BSD IPO.

      Uhhmmmm... billion dollar IPOs are a result of hype, not the cause of it...

      Seems like you're getting the cart before the horse.


      -Jordan Henderson

    5. Re:Follow the Money by JordanH · · Score: 2
      • 3) Some cleaver BSDers (Hi Pat!)

      That Pat must be a pretty sharp fellow!


      -Jordan Henderson

    6. Re:Follow the Money by sklein · · Score: 1

      There is no billion dollar IPO backing the hype about BSD.

      Uhh, looks like the hype backs the IPO. I know the hype certainly came first. It was there when I started using Linux well before the first IPO. You may not have known about it, but it was there.

      cheers,
      sklein

    7. Re:Follow the Money by MasterMnd · · Score: 1

      I think you've got that kind of backwards.. There will be a billion dollar BSD IPO AFTER the hype takes off.. the only reason linux companies are doing so well is because linux is getting popular, not the other way around...

    8. Re:Follow the Money by mr · · Score: 1

      Popular is when my parents and grandparents ask "What is Linux?"

      That happened AFTER the billion dollar IPO. Not before. I don't have it backwards.

      Things like a billion+ help your popularity. Being popular because you have a billion+ isn't the best reason to be popular, but its still a reason for popularity.

      --
      If it was said on slashdot, it MUST be true!
    9. Re:Follow the Money by JordanH · · Score: 1
      • Popular is when my parents and grandparents ask "What is Linux?"

      Well, this says a lot about your parents and grandparents, but not much about the populace at large. I guess all those investors that made the billion+ $ IPOs were completely in the dark about Linux.

      What a crazy stock market. People are pushing prices up to 10 and 20 times initial offer and they've never heard of what it is the company is doing.

      A certain level of "popularity" is necessary before investors are attracted to something. Sure, there's a feeding frenzy effect caused by this, which makes it even more popular, but you have to have a certain mindshare to make it possible.


      -Jordan Henderson

    10. Re:Follow the Money by mr · · Score: 1

      The investment style is called momentum investing. This style has NOTHING to do with what the company actually does. What you try to do is jump on the same bandwagon as everyone else.

      It comes from the concept of technical analysis. You don't care what the company does, only how it has performed.

      As for the parents/grandparents crack, the majority of the population doesn't have computers. (Unlike the readers of /.) So the majority don't GIVE A DAMN about this site, Linux or OpenSource.
      And for most brokers, OpenSource is as remote to them as biotechnology, sub-micron lithography, or FPGA's. The people who are analysts care, but your average broker doesn't. The people who read the analyst don't grok the technology, just what the analyst says.

      Again, the MAJORITY of investors read what some analyst says. Look at what you have read about OpenSource or Linux or BSD in the 'mainstream' and ask yourself: Do these 'experts' understand?

      From the Fool
      message board: VA Linux
      date: 12/09/1999 author: gliptak
      I heard this IPO was cancelled, as the underwriters did not anticipate enough interest
      [VA Linux IPO wasn't canceled]

      message board: VA Linux
      date: 12/10/1999 author: JeanDavid
      In the Linux market, the biggest two databases are probably MySQL and Oracle.
      [And PostgreSQL was voted #1 database, with MySQL as #2. Lack of facts (again)]

      That is 2 pages in.

      I'd post some of the tech analysts from the broker, but:

      1) I don't have them at hand
      2) Posting facts on /. Is rather useless....especially if it conflicts with Linux-based religious zelotry.


      --
      If it was said on slashdot, it MUST be true!
    11. Re:Follow the Money by JordanH · · Score: 1
      • Oh, you can't refute the posts with FACTS so lets use an ad-homnem attack.

      It's not exactly a post that can be refuted by facts. The poster has one definition of "popular" that doesn't yield to argument.

      I think something is popular when it attracts a lot of investor interest and thus the Billion $ IPOs.

      The poster feels it's not popular until somebody's relatives are asking about it.

      It's a semantic argument with no authority to decide it.

      As for Ad Hominems it was the poster - mr - who bitterly complained about the Slashdot posters as being religious zealots who don't listen to facts.


      -Jordan Henderson

    12. Re:Follow the Money by Thomas+Charron · · Score: 2

      And, by the same token, CP/M was a win long before BSD was ever dreamt of.. ;-P

      I was merely stating that Linux is currently more popular then BSD, and this popularity is NOT based on marketing hype..

      --
      -- I'm the root of all that's evil, but you can call me cookie..
    13. Re:Follow the Money by Thomas+Charron · · Score: 1

      Please expand on this. How is the popularity of Linux based on ignorance??

      --
      -- I'm the root of all that's evil, but you can call me cookie..
  8. Mostly cause BSD is harder to say than Linux by WillAffleck · · Score: 1

    I think it also has something to with the name. Maybe not for the serious amongst us, but I remember some of the reactions against unpopular languages were driven by how hard it was to say the name, in the past. Even if we can't agree on how to pronounce Linux, it still is easy to say. BSD, on the other hand, is very staccatto and doesn't roll trippingly off the tongue on the way to Piccadilly.

    --
    Will in Seattle
    1. Re:Mostly cause BSD is harder to say than Linux by heh2k · · Score: 1

      say "beast-dy", not "bee-es-dee"

    2. Re:Mostly cause BSD is harder to say than Linux by WillAffleck · · Score: 2

      A nice theory, but people don't. Linux is normally pronounced by the great unwashed with two syllables, although Europeans tend to pronounce it differently than Americans. BSD, three syllables. Just like the Net is one syllable (three in French, but at least it's shorter than most words).

      Spiff it up, give it a new name, a plush toy that won't poke kid's eyes out, and you've got marketing acceptance. Stick to the computerese and it loses points.

      Sigh.

      People frequently mistake my descriptions of reality for my personal opinion as to How Things Should Be - this is what I'm saying, not What Should Be.

      --
      Will in Seattle
  9. better luck w/ bsd, for now. by pope+nihil · · Score: 1

    my brother couldn't get a shiny clean install of redhat 6.1 to work properly, so i suggested he load the latest from OpenBSD (2.6). it properly detected and configured all of the devices. now he's happy about it 'cuz he gets to finally ditch M$.

    unfortunately, there's nothing to prevent an Evil Empire (TM) from making proprietary changes to *BSD and selling, for instance, M$ BSD. the ability of proprietary companies to embrace and extinguish is what really scares me.

  10. Two factors by Bruce+Perens · · Score: 5
    I like the BSD system and might even do some commercial things with it. So please don't take this as anti-BSD propoganda.

    1. Time. BSD was held back by the ATT lawsuit and Linux already had so much mindshare when that was over.

    2. The BSD license doesn't enforce the quid-pro-quo. This is a real sticking point for me personally. When I put a lot of work into something, I like to be a partner in a free software development, not someone's unpaid employee dupe. But I feel like a dupe when somebody takes that work private, makes proprietary modifications to my work and doesn't return their modifications to me or the other free software authors who gave him our work.

    Unfortunately, history shows that without a license requirement the return of code doesn't happen. Most of the workstation Unix systems are BSD-derived (although these days there is more System V in there) and all of their X servers are derived from software under a very similar license to the BSD. Try to get the source code for those systems. Sun only released its modifications to the BSD system recently, 10 years late, and then under a license that would not allow their reincorporation into the BSD system as free software! Most other workstation manufacturers didn't bother to release source at all.

    So, I am more likely to put work into a GPL project. It is possible to take the BSD system and GPL it. The new BSD license and the GPL are compatible, and you can GPL all new work that you do, and in general establish a GPL source thread. But that would annoy a lot of the long-time BSD folks.

    Thanks

    Bruce

    1. Re:Two factors by nickm · · Score: 2

      The real reason is that BSD is an acronym, while Linux is a bit of a play-on-words.
      People find acronyms inscrutible. Imagine if RMS had not named it POSIX, and the original "IEEEIX" name was chosen.
      --
      I noticed

      --

      --
      I noticed

      It's getting about time to leave everywhere

    2. Re:Two factors by bvmcg · · Score: 2
      Sun only released its modifications to the BSD system recently, 10 years late, and then under a license that would not allow their reincorporation into the BSD system as free software! Most other workstation manufacturers didn't bother to release source at all.

      This is disgusting to read. It was nearly ten years ago that Scott McNealy, president/CEO of Sun Microsystems, spent a full half hour radio broadcast of the Commonwealth Club meeting beating on the government. The reason? He was insisting that it was ludicrous and short-sighted to spend money on closed systems. He further insisted that it shouldn't even be allowed, pushing a move such as the one the government of Brazil may enact.

    3. Re:Two factors by Bruce+Perens · · Score: 1
      I just don't buy that. I think the users are following developer mind-share, and Linux still has more of that, and the developers simply don't care if it has a marketable name or not.

      By the way, I started running 4BSD in the early 80's, so I'm no stranger to it. I got to NYIT computer graphics lab in 1981, we had one of the first VAXes to get out of DEC (it's the one in Soul of a New Machine) and ran Unix 32V (ATT VAX Unix, I think with no virtual memory) until we got 4BSD. We also had Version 6 Unix on PDP-11 systems. The lab had a V6 paint system application called Images that they never ported to V7. I finally ported 2.8 BSD to the V6 binary API to support that application.

      Bruce

    4. Re:Two factors by cjs · · Score: 2

      You can expect to get flamed if you ask one of the current BSDs to switch to the GPL; you won't get flamed if you simply fork off your own and GPL it (or, rather, GPL the bits that don't have a clause 3 in the licence; UCB is only one of hundreds of contributors to the kernel code).

      As for `resent[ing] the fairness [you] insist on,' well, yes, because a) it's certainly not fair to anyone who wants to incorporate ten lines of GPL'd code into ten thousand of his own, b) I don't believe it's fair to anyone to tell him what he can do with the code he writes, which is what the GPL does, and c) the FUD that Linux folks love to spread about how all non-GPL'd software is being taken proprietary and disappearing forever from public view is getting a bit old.

      cjs

      --
      The world's most portable OS: http://www.netbsd.org.
    5. Re:Two factors by evilpenguin · · Score: 3

      Open systems and Open source are not the same thing. McNealy has always advocated Open systems (meaning systems based on open standards), but he never went so far as to say that companies should give away their source code or the right to modify it and give it away modified.

      McNealy was ahead of the curve on networking and open standards, but he is very much behind the curve on Open source. He was truly commited to "open" he would not have withdrawn Java from the standards process. He still wants control. He hasn't picked up that last piece of the puzzle...

      Don't be disgusted. McNealy does not embrace Open source.

      To me, there's a heirarchy of technology worlds I want to work in:

      1) Open source -- the software is free, programmers are not.

      2) Open systems -- the standards are free, the software is not, and programmers are the drudges of the business world.

      3) Proprietary systems -- there are only de facto standards, software is expensive, and programmers are serfs of the dominant technology company. This was IBM in the past. This is Microsoft today.

      McNealy had the vision to aim at level 2. In the early 80's, this was radical indeed. He has not figured out the advantages of level 1. He's partway there, but he has missed the last step -- that the code belongs to the world, not to the originator. That assurance, that the code is yours, that the benefit you get for giving away your mods is the absolute assurance that anyone else who improves it must share his/her mods with you is the payment you receive for giving away your mods. It works. McNealy doesn't see this yet. He thinks programmers will give their mods to him, with no assurance that Sun's further improvements will go back to those programmers. The Sun version is a one way street.

      No, I do not weep for Scott McNealy.

    6. Re:Two factors by Bruce+Perens · · Score: 2
      Right. Remember that Open Systems != Open Source. People still get them confused. Open Systems means the API is documented and someone else can program to the system or application side of that API. It says nothing about the actual software being free or open, generally it's proprietary.

      One influential person I know still thinks that Open Source is a subset of the field of Open Systems, and we are constantly in argument about this because I think that Open Source means so much more, and he thinks I am not seeing the forest for the trees.

      Thanks

      Bruce

    7. Re:Two factors by Anonymous Coward · · Score: 1
      you won't get flamed if you simply fork off your own and GPL it

      Check an archive of gnu.misc.discuss; I'll dig up a reference if I have time. Some BSD authors go ballistic if you do this. I guess if you're publishing but not under the BSDL they'd just rather not know about it.

      a) it's certainly not fair to anyone who wants to incorporate ten lines of GPL'd code into ten thousand of his own,

      Sure it is. The only reason he has my code is that I get his in return, otherwise why would I publish it?

      c) the FUD that Linux folks love to spread about how all non-GPL'd software is being taken proprietary and disappearing forever from public view is getting a bit old.

      Are you arguing this doesn't really happen, or just that we shouldn't object to good work being abused to subsidize more proprietary crap we have to cope with?

    8. Re:Two factors by Bruce+Perens · · Score: 2
      Well, I'm assuming they will eventually release it under the SCSL. Fold that back into your BSD work. Ugh.

      Thanks

      Bruce

    9. Re:Two factors by Andy · · Score: 1

      Both true. BSD is great software but it failed to attract a fanatical developer base like lignux because of the aristocratic development model they employ. Lignux inspires orders of magnitude more contributers. This certainly has its negative side -- lignux does not have a reputation for being a scupulously clean design.

    10. Re:Two factors by _Sprocket_ · · Score: 1

      Heh. No flame bait to be found here either. :P

    11. Re:Two factors by Guy+Harris · · Score: 2
      [c] its true - quit whining

      What is "true"? The claim that "all non-GPL'd software is being taken proprietary and disappearing forever from public view", as per the statement of the person to whom you're responding:

      the FUD that Linux folks love to spread about how all non-GPL'd software is being taken proprietary and disappearing forever from public view is getting a bit old.

      or the claim that said noise is, in fact, getting a bit old?

      If you're asserting that the first claim is "true", then this is a use of "true" to which I was previously unacquainted; the use of "true" with which I'm familiar has connotations such as "in accordance with reality". It is NOT true that "all non-GPL'd software is being taken proprietary and disappearing forever from public view" (unless this is a use of "all" with which I was previously unacquainted, e.g. "all" meaning "some"); the code to FreeBSD, OpenBSD, NetBSD, and X11 are not "proprietary", and are still in public view. Proprietary derivatives of said code have been made, but that doesn't mean the code from which they're derived has been taken public; the attempt of The Open Group to impose restrictions on the redistribution of X11R6.4 source was, fortunately, beaten back - yes, there is the risk that this might happen with other software, and, yes, the GPL would make that more difficult, although note that XFree86's response was to say "we're not upgrading to X11R6.4", as the existing X source releases were still free. Even were one of the BSD groups to decide to impose those sorts of restrictions on the distribution of their OSes - something I consider unlikely, given that, unlike The Open Group, which was composed largely of commercial organizations, they're just collections of developers working on free OSes - earlier releases would continue to be available.

    12. Re:Two factors by Syberghost · · Score: 2

      Right. Remember that Open Systems != Open Source. People still get them confused.

      No shit; I've spent half the day responding to those people over in another story.

      Dare to say that the PC architecture is prevalent because of it's "Openness", and you'll get flamed for not knowing your history.

      Dare to suggest, in fact, that IBM makes money off the PC world, and you'll get flamed.

      Careful, Bruce, there are piranhas in the pool. :-)

      (Thankfully, with a little moderation they'll go from piranha to pariah. Just set your threshold to 2 and you can swim freely.)

      So, I have a question; why has no one released a "mainstream" GPL'ed BSD? Is it just because everybody inclined to do so is working on Linux instead?

    13. Re:Two factors by Guy+Harris · · Score: 2
      Are you arguing this doesn't really happen

      No, he's arguing that it is not the case that it always happens and that all non-GPL'd software "is being taken proprietary and disappearing forever from public view". It is, in fact, not the case - {Free,Net,Open}BSD are still in public view, and there is no sign that they are being taken proprietary, and there's plenty of other non-GPLed software that's non-proprietary and publicly available (heck, even if The Open Group hadn't abandoned their restrictions on the distribution of X11R6.4 source, previous releases wouldn't have "disappeared forever from public view").

      Yes, there is perhaps a greater risk of non-GPLed software "being taken proprietary and disappearing from public view" - although it may just be future versions that disappear from public view, allowing a fork to preserve the public version - but the mere existence of a risk doesn't amount to a certainty that the risked outcome will happen.

    14. Re:Two factors by Anonymous Coward · · Score: 1

      The BSDL allows derived works and does not require them to be distributed under the same license. Work under recent versions of BSDL (without the advertising clause) can and has been derived from and distributed under the GPL. Many BSD proponents get very upset about it, though IMHO they were fools not to realize their license allowed this.

    15. Re:Two factors by Daniel · · Score: 2

      I think it was a joke, Bruce :-)

      Daniel

      --
      Hurry up and jump on the individualist bandwagon!
    16. Re:Two factors by mr · · Score: 1

      As opposed to taking GPLed code and folding it back into your BSD work.

      Ugh.

      Thanks

      M.R.

      --
      If it was said on slashdot, it MUST be true!
    17. Re:Two factors by Bruce+Perens · · Score: 2

      Oops. Open mouth, insert foot :-)

    18. Re:Two factors by Bruce+Perens · · Score: 2

      No.

    19. Re:Two factors by Bruce+Perens · · Score: 1
      What good is a disclosed-source system that you can't modify? It's good for one thing: you can audit it. However, I'm not sure this works because I don't see why anyone would be interested in auditing such a system. You could pay someone to do it, I guess. I like it more when my heart's in it.

      If the API is encumbered, it's not an Open System even if it is published. You still can't program to it.

      I reject the notion that View Source in a web browser is Open anything. Sure, you can see it and learn the general principles, but you can't reuse the software at all.

      Thanks

      Bruce

    20. Re:Two factors by Eivind+Eklund · · Score: 1
      Unfortunately, history shows that without a license requirement the return of code doesn't happen.

      This is not true. The return of code does happen - just not always. However, we do get a lot of returned code, and we get a lot of returned code from places that wouldn't have used our codebase if it had been under the GPL.

      Eivind.

      --
      Doubting the existence of evolution is like doubting the existence of China: It just shows that you're uninformed.
    21. Re:Two factors by Cramer · · Score: 1

      Ain't that the damned truth... the Linux solution to just about everything is "stick it in /proc." procfs has become nothing more than a run-down gheto full of pimps and drug dealers.

      Seeing the ass-backwards shit being done via procfs makes me want to wipe the hard drive and install Win2000. (RC2 even)

    22. Re:Two factors by Anonymous Coward · · Score: 1

      Why not? It gets us a few steps closer to Plan 9 and Hurd. Since a file is Unix' quantum of both namespace and I/O, we should be asking why anything in the system can't be manipulated using our thorough collection of file-oriented tools.

    23. Re:Two factors by Gleef · · Score: 2

      Syberghost asks:

      So, I have a question; why has no one released a "mainstream" GPL'ed BSD? Is it just because everybody inclined to do so is working on Linux instead?

      Two reasons, first, until very very recently, the BSD license was not compatible with the GPL. The advertising clause of the BSD license prevented such a thing from happening. Secondly, some of the people most loyal to the BSD way of doing things have very anti-GPL feelings. Typically, such people are more concerned with their code being widely used (in Free or non-Free systems) than encouraging Free software, and the GPL gets in the way of that.

      We probably will see a GPLed BSD at some point, but there's no pressing need I see for someone to jump on the opportunity. The flaming that such a project would likely receive makes it even less worth it. In general, a developer picks a license because it matches how they want the software to be used; changing the license, even while legal, would be bad form without a very good reason.

      ----

      --

      ----
      Open mind, insert foot.
    24. Re:Two factors by _peter · · Score: 1


      > why has no one released a "mainstream" GPL'ed BSD


      Because the people who appreciate *BSD and know it well enough to maintain it tend to be the developers -- and they have bad associations with GPL'd code. Associations like the spaghetti mess that is gnu-tar, the overladen info/emacs help system, or not being able to exchange freely with the Linux kernel like they can amongst themselves.

    25. Re:Two factors by Gleef · · Score: 2

      Bruce Perens wrote:

      I reject the notion that View Source in a web browser is Open anything.

      Well, on most systems it's an open window :-)

      ----

      --

      ----
      Open mind, insert foot.
    26. Re:Two factors by Bruce+Perens · · Score: 1
      Well, if you folded GPL work back in it would still be free software. What's more, it would stay free software thereafter. I don't find that so bad.

      Bruce

    27. Re:Two factors by Lx · · Score: 1

      a) it's certainly not fair to anyone who wants to incorporate ten lines of GPL'd code into ten thousand of his own,

      Sure it is. The only reason he has my code is that I get his in return, otherwise why would I publish it?


      Because you are writing FREE software. The idea is not to have other people improve your code, although that is a side effect, but to give software into the public domain that you feel should belong there. To do it for other reasons is, IMO, selfish.

      -lx


    28. Re:Two factors by notsosilentbob · · Score: 1

      Actually, I think there is some merit to this. I just called out to my wife (who is NOT a geek in any way) and asked:

      Have you heard of Linux? Answer: "of course!"
      Have you heard of BSD? Answer: "Huh?"
      Have you heard of Posix? Answer: "Hmm.. that sounds familiar"
      Have you heard of RMS? Answer: "no"
      Have you heard of Richard Stallman? Answer: "I think so"

      Never underestimate the power of a catchy word: Apple, Yahoo, Linux, Emacs, iMac, Redhat.

    29. Re:Two factors by mr · · Score: 1

      As you said Ugh.

      People who've chosen a new-style BSD licence (happy RMS?) over all the other licence models have no desire to take GPLed code and infect the BSD code.

      So GPLed code is as useless as SCSL code. For neither option allow the FREEDOM TO DO WHAT YOU WANT WITH THE CODE. For the BSD camp, its about the rights of humans to make code use choices, and not about the rights of code to 'be free'.

      Again, as you said Ugh.

      --
      If it was said on slashdot, it MUST be true!
    30. Re:Two factors by dublin · · Score: 2

      Bruce,

      Two things:

      First, it's more than a little unfair to lump the present FreeBSD license in with the historic commercial BSD license. Due to the AT&T concerns and other issues, they are really completely different animals.

      As you no doubt know, Sun and the other workstation OEMs were under the old commercial BSD license, which does not require or even encourage reincorporation of code from the licensees. It's my understanding that even so, many (but not all) Sun improvements made it back into BSD up through the SunOS 3 & 4 days - which ended a geological epoch ago in Internet time.

      (You're right about there being more Sys V code than BSD in most modern commercial Unixes - although I'm personally more comfortable with Berkeley Unix practices, when the father of BSD (Bill Joy, for the newbies) decided that the SVR3-based Solaris was the only way to provide for future needs, that sent a message!)

      Sun went further than they had to in giving back any changes at all - as you corectly point out, almost no one else has given anything! I'm not sure what you're beef with either Sun or BSD is here other than, "the world isn't like it'd be if *I* were king!"

      Second, although I have not taken the time to seriously try FreeBSD (I should, I know), it's probably quite premature to either declare Linux' victory or the failure of the BSD license model. In fact, it's quite possible that BSD could have the last laugh - Both Linux and FreeBSD user bases are comparatively small, and big numbers will likly come from big promoters. (Of your two factors, I think time is the big one.)

      It's no secret that many commercial developers are more comfortable with the BSD license - if that ultimately translates into more commercial support for the BSDs rather than the Linuxes, then we could see a real shift in "popularity". Remember the communities are sparse enough that there's only about a 4 or 5:1 edge for Linux now, and most of the big guys are still straddling the fence. (e.g.: IBM both supporting Red Hat and buying BSD-based Whistle.)

      Some people will always abuse the system, and there's no good way to stop it. (I think most of us suspect GPL'ed code has been "privatized" a time or two!) License purity is not a cure for human greed.

      And no, I don't think "poisoning" the BSD waterhole with GPL would do either camp (or open/free software in general) any good at all. In reality, I think the town is more than big enough for both Linux and FreeBSD, and it appears there are things both camps could learn from one another.

      --
      "The future's good and the present is nothing to sneeze at." - Roblimo's last ./ post
    31. Re:Two factors by Eivind+Eklund · · Score: 1
      IMHO there's nothing moral about aiding and abetting organizations who have ripped off their customers and all but eliminated progress in my profession. Where does "refuse to help others do what you don't want them to" fit into your worldview? I give them source, they give me nothing - how can that ever be fair?

      You are assuming that they don't give back any changes. From my experience, this is generally false. Companies have employees that are human, and many of the companies that base things on open source software employ open source advocates.

      Changes will, in most cases, come back. Just not all of them, and perhaps not at all if what is being done is creating a new Unix clone. But this isn't common; what is common is to use the code for various types of embedded systems.

      Eivind.

      --
      Doubting the existence of evolution is like doubting the existence of China: It just shows that you're uninformed.
    32. Re:Two factors by Guy+Harris · · Score: 2
      and they have bad associations with GPL'd code. Associations like the spaghetti mess that is gnu-tar, the overladen info/emacs help system

      Are either of those due to the GPL? It seems silly to reject a license merely because some code released under that license doesn't meet your standards, unless you have solid evidence that the license somehow caused the code not to meet your standards and will cause a lot of other code not to meet your standards....

    33. Re:Two factors by cnflctd · · Score: 1

      selfish

      RMS calls it "pragmatic idealism", noting that "The GNU GPL is not Mr. Nice Guy."

      Would you admit at least that this selfishness isn't inspired by greed? Idealism is not a vice, so leveraging the copyright laws for idealistic reasons shouldn't be either.

      --
      I'm cool like a fool in a swimming p-p-pfft-pool
    34. Re:Two factors by Bruce+Perens · · Score: 2
      Yes, I remember the commercial BSD license, but it's been gone for quite a while now, and it doesn't seem to have changed much. Of the two companies that did at least make an attempt to give back, both wrote their own licenses rather than use the BSD license for their modifications.

      And of course the argument is different for X, that's been under a BSD-like license for much longer.

      I wouldn't suggest the GPL as a means of "poisoning the BSD water-hole" - that's pejorative. I would suggest the GPL as a means of providing a path for people who prefer to have a license protecting the free-ness of their efforts.

      Thanks

      Bruce

    35. Re:Two factors by cnflctd · · Score: 1

      My God, you're right! He's Dr. Evil with hair! The fiend!

      But what about all the thousands of GPL developers? Don't they realize they do the bidding of Dr. Evil-With-Hair? The fools! Look! RMS is nibbling his pinky!

      (whew, I'm all out of sacrasm. can't...even...hold...down...the...shift key. oh, well, better eat some more doritos.)

      --
      I'm cool like a fool in a swimming p-p-pfft-pool
    36. Re:Two factors by Lx · · Score: 1

      I suppose that I would admit that the selfishness is not motivated by greed in the traditional sense. Its hard to say which license is the more idealistic, though.

      -lx

    37. Re:Two factors by dennisp · · Score: 2

      The fact still remains that the BSD community has reached an order of magnitude that brings sufficient returns.

      The fact that it is not imperative to return code is irrelevant. There are many corporate users who have returned portions of their code who would not have used the GPL in the first place because they can not pick and choose.

    38. Re:Two factors by Eivind+Eklund · · Score: 1
      I said: You are assuming that they don't give back any changes. From my experience, this is generally false.

      Anonymous coward said:Could you give some precise references so we can add this to the demythification list, please?

      To give just a few examples:

      This is just a short list off the top of my head. There are a lot of other cases.

      Eivind.

      --
      Doubting the existence of evolution is like doubting the existence of China: It just shows that you're uninformed.
    39. Re:Two factors by _peter · · Score: 1

      What I was trying to get across without becoming flamebait was: the GPL is strongly connected to the FSF and their gnu utilities. The BSD people tend to dislike the creeping featurism and code bloat in GNU utils.

      Second, people who write code under BSD licenses do so because they believe that writing useful code is a higher goal than worrying about tit-for-tat. Yes, companies can rip their code off. But this happens much more often in the small case than the large.

      For example, I have a friend whose job for several months was adapting OpenBSD's ftp server for his company's specific requirements. In the process he found several obscure bugs in the ftp code. Those bugs have been submitted to Open's developers. Things like that happen often enough that sticking to the GPL looks unwise and petty.

    40. Re:Two factors by Guy+Harris · · Score: 2
      the GPL is strongly connected to the FSF and their gnu utilities.

      Yes, the GPL is strongly connected to the FSF, given that it was originally, I think, the idea of the FSF's founder.

      And, yes, the GNU utilities are, not surprisingly, licenced under the GPL.

      However, what I was trying to get across is that this does not, in and of itself, demonstrate that the GPL is connected to "the creeping featurism and code bloat in GNU utils"; somebody could write, say, a GPLed cat that lacked such creeping featurism and code bloat as the -v flag (-v being, by the way, Berkeley creeping featurism, not GNU creeping featurism...)

    41. Re:Two factors by cjs · · Score: 2

      `Fools' is perhaps a bit strong a word here, but I'm not surprised that some BSD advocates didn't realise some of the implications of the licence. Certainly some GPL advocates have shown from time to time that they don't realise the implications of the GPL, as well.

      But a lot of us have chosen the BSD licence (or something even more free--personally, I put my code into the public domain) specifically because we want you to be able to take it and GPL it if you like.

      BSD folks say to GPL folks, `Take our code and do what you like with it. If it helps you, great!' GPL folks say to BSD folks, `you can't use our code unless you GPL all of your code.' Now what does this say about the spirit of sharing on each side?

      cjs

      --
      The world's most portable OS: http://www.netbsd.org.
    42. Re:Two factors by Arandir · · Score: 2

      "Idealism is not a vice"

      But idealism put in practice often is. Because all idealism is, is wondering what the world would be like if you/I were king.

      --
      A Government Is a Body of People, Usually Notably Ungoverned
    43. Re:Two factors by Arandir · · Score: 2

      "IMHO there's nothing moral about aiding and abetting organizations who have ripped off their customers and all but eliminated progress in my profession."

      You are correct. The only progress in software has come solely from the GNU camp.

      --
      A Government Is a Body of People, Usually Notably Ungoverned
  11. V/S by razvedchik · · Score: 2

    Yes, but we all have to agree that both camps are adequately staffed with a bunch of radicals who will give you one hundred reasons why their brand is superior.

    When, for instance, they both run EMACS, VI, Apache, and loads of other GNU software.

    I think that if you don't like the look of the "alternative alternative operating system", A)Your information is out of date B)Wait 6 months and see if it has what you want C)What, you're using a MAC!!!

    --
    I do what the voices on my console tell me to do.
    1. Re:V/S by paul.dunne · · Score: 2

      Much as I hate to nick-pick... vi isn't GNU, nor is Apache.

    2. Re:V/S by razvedchik · · Score: 1

      Contex-derived error. You can take the phrase two ways. One is that the before mentioned software is GNU, and so are the tons of other software. The other is that they run these programs, and also the tons of GNU software.

      My bad.

      how about "...and tons of GNU software too."

      I used to be able to write in English fairly well. Then I learned Russian.

      --
      I do what the voices on my console tell me to do.
  12. Lets not start a flame war over this by rbunner · · Score: 1

    FreeBSD and the other BSD's are not as popular as Linux because they don't have as many users. They also have fewer distributions. The BSD's have also been more server sided then desktop untill recently. Certainly the BSD's have become more popular due to the succes of Linux as Linux has brought a great many people to look at Unix-like OS's. Which is better. I don't think there is an answer to that. Both work well. I use FreeBSD. It fits me well so I have no reason to look at Linux. I'm sure the same is true for many Linux user's.

  13. bsd didn't capture new users' interest by poopie · · Score: 5
    Life's not fair. I personally believe that linux has been so successful because:

    it invited in more new users than BSD
    it has a smart, savvy figurehead/spokesperson in the form of Linus, where BSD doesn't really have a single spokesperson for the media to contact, quote or interview.
    it has been marketed as something new, as opposed to yet another fragmented version of unix. (how many forms have a unix checkbox and a linux checkbox?)
    the linux community is more helpful to newbies, where the BSD community is more guru focused - RTFM!
    timing - linux timing was right for a unix renaissance
    random chance
    number of developers involved in linux kernel development and testing created a snowball effect with number of end users.
    confusion over the difference between FreeBSD, NetBSD, and OpenBSD. Maybe it would server BSD better (marketing-wise) to have a single name for their OS, and varying distributions
    the mass quantity of resources that are mostly unix-generic that have linux in their name -- like the LDP and many unix apps that have linux in their name
    1. Re:bsd didn't capture new users' interest by Gurlia · · Score: 1
      number of developers involved in linux kernel development and testing created a snowball effect with number of end users.

      But this begs the question. Why didn't the BSD developers snowball the same way?

      the mass quantity of resources that are mostly unix-generic that have linux in their name -- like the LDP and many unix apps that have linux in their name

      Objection, Your Honour. If this is the case, the question would be, why didn't the coders adopt BSD as part of the name, instead of Linux? Perhaps there is something deeper here.

      Just my $0.02 worth...

      --
      mikre he sophia he tou Mikrosophou.
    2. Re:bsd didn't capture new users' interest by homebru · · Score: 1

      Simple enough.

      BSD wouldn't run on my 486; Linux would. And that 486 still runs 1.2.8. (Slackware.)

    3. Re:bsd didn't capture new users' interest by Rilke · · Score: 5
      To add to this:
      • Linux has a cool name and a cool story. Folks (especially in the US) just eat up the whole Linus story.
      • a major goal in the early days of Linux was "let's write a driver for everything". BSD never really pushed that goal, and today Linux runs on a whole lot more popular hardware than BSD does.
      • Open development: Linus accepted patches from just about anyone. Kernel improvements on BSD always went "let's discuss it, and then one of the core developers will implement it". Linux discussions were always "send a patch in, and then we'll talk about it".
      • The lawsuit, of course. Linux owes much of its early success to the CD-ROM, which was just getting popular. At the time of yggdrasil and early slackware, I don't remember seeing any complete easy-to-install BSD CD-ROMs (did walnut creek have one maybe?)
      • Linus himself. He's directed the whole movement incredibly well, staying out of arguments when needed, and stepping in when necessary.
    4. Re:bsd didn't capture new users' interest by jedinite · · Score: 3

      the linux community is more helpful to newbies, where the BSD community is more guru focused - RTFM!

      This is a common concern I hear from the pro-Linux community. Admitably, the BSD guru's willing to help are lesser in number than those on the Linux side (and thus perhaps the underlying message of the article), but they're still out there, and are still willing to help the newbies.

      For example, check the following mailing lists for great support for those new to BSD:

      Free-BSD-newbies@FreeBSD.org*

      FreeBSD-questions@FreeBSD.org*

      -newbies is a discussion group for people new to FreeBSD, it's not intended for technical questions. Likewise, -questions is for technical questions, and not for discussions by new people. You WILL see a lot of "RTFM" on that list, and deservedly so...

      Also, of course, check out the support page at FreeBSD.org for more help.

      *=note: SlashDot is inapropriately parsing the extended info in the mailto's. You should be able to get the gist of it if you click on the mailto links. It should be addressed to majordomo@FreeBSD.org, and have the text subscribe FreeBSD-newbies or subscribe FreeBSD-questions

      ---------
      Question: How do I leverage the power of the internet?

      --

      ---------
      There is no try at jedinite.com
    5. Re:bsd didn't capture new users' interest by ChristTrekker · · Score: 1
      • confusion over the difference between FreeBSD, NetBSD, and OpenBSD. Maybe it would server BSD better (marketing-wise) to have a single name for their OS, and varying distribution

      OK, maybe I'm off my rocker here, but aren't Free/Net/Open basically equivalent to a distribution? How is it different to say "I run NetBSD" than "I run Red Hat Linux"? If anything, I think Free/Net/Open is alot less confusing than SuSE/Red Hat/Yellow Dog/Caldera/Slackware/Debian/etc. The BSDs are borrowing from each other all the time, so it remains relatively unified. One tweaks this and another tweaks that, no different than the Linux distros.

    6. Re:bsd didn't capture new users' interest by technos · · Score: 1

      Microchannel PS/2? That's the only non-flawed 486 that RH 5.x (and the rest of the 2.0.xx ilk) wouldn't run on. The 2.1.1xx and newer kernels run nicely. Both the current SuSe and RH distros install easily and even like the brain-damaged MCA SCSI adapters they usually shipped with.

      Just remember, there is a special MCA boot image for installation, and SuSe doesn't lock during the SCSI probe, it just takes seemingly forever to reset the SCSI bus.

      --
      .sig: Now legally binding!
    7. Re:bsd didn't capture new users' interest by Jerome+Jahnke · · Score: 2

      I think there are two reasons it didn't snowball. The first was, BSD was aleady well done, a lot of really good work had already gone into by the time it developers got to it. Linux was still a bit raw, which led to people poking around in it.

      Linux played catchup with BSD for quite a while. They clearly run neck and neck now. But lots of people like one camp over the other. I think both the BSD and Linux camps have lots of good developers working them both, and it will be intersting to see hat will happen in the next two or three years, neither is going away, but will industry embrace the GPL? It does seem unlikely to me.

      Personally since I learned about BSD OS's when I was in school I like them better than Linux ones. But I guess if I had to choose today which one I was going to install on a machine I could pretty much pick and choose. Lots of schools now teach Linux instead of BSD, in the OS classes. Some of them still teach Minix (if you want to read something entertaining you should try to find the thread of Torvalds and Tannenbaum discussing the merits of a monolithic vs a micro kernel.)

      I think overall the major difference in BSD vs Linux is Torvalds. One intelligent, well spoken, until recently, accessable individual has made all the difference in the world. Even now he remains a powerful voice in support of it, and he plays well in the papers. He is less important now than he was earlier, but don't discount his influence, there were a LOT of good alternative OS's out at about the same time.

      Jer,

    8. Re:bsd didn't capture new users' interest by _peter · · Score: 1
      • confusion over the difference between FreeBSD, NetBSD, and OpenBSD. Maybe it would server BSD better (marketing-wise) to have a single name for their OS, and varying distributions?

      Two problems:
      1. BSD types don't have take-over-the-world aspirations, they just want to write useful code. Thus, anything justified as better for marketing tends to be scorned.
      2. The three *BSDs are not just different distributions, there are fundamental technical differences among them. To the extent that they're interoperable at all, it's from emulation & conforming to a standard API.
    9. Re:bsd didn't capture new users' interest by homebru · · Score: 1

      Nope. Not microchannel, ISA. Good, clean, standard hardware.

      The problem wasn't with the bus, but with the drives I was using. I had one Seagate and one Maxtor. And the BSD "known problems" file (I forget the exact filename) said that that was the one configuration that had been found to not work. It didn't for me either, so I moved over to Linux.

      The 486 box remains at 1.2.8 (Slackware) because:

      1) it works (modem, print, file server)
      2) it only has 8mb of ram
      3) I'm lazy
      4) I have a p-II (300) that runs Linux 2.0.36 (RedHat).

    10. Re:bsd didn't capture new users' interest by The+Welcome+Rain · · Score: 1
      -newbies is a discussion group for people new to FreeBSD, it's not intended for technical questions. Likewise, -questions is for technical questions, and not for discussions by new people. You WILL see a lot of "RTFM" on that list, and deservedly so...

      So where do newbies go when they have technical questions?

      It does happen, you know.

      --

      --
      Some keywords for the NSA in the Lord of the Rings universe: One Ring bind find Sauron quest Nazgul freedom
    11. Re:bsd didn't capture new users' interest by Punto · · Score: 1
      I think there is another important thing: most new users don't know the difference between linux and bsd.

      When I first wanted to install linux, I went to some unix irc channel, and then to a linux irc channel, and I asked "where can I download a small linux to install on a 100MB hd, or run from a floppy disk?" (I didn't want to go and buy the CDs). And someone said: "you can go to freebsd.org and install freebsd through FTP".

      So, at first I though that FreeBSD was another linux distribution, like "red hat". At that time, all I knew was "linux is a free version of unix; unix is a OS that doesn't crash ever 5 minutes". Then I found out that there is actually a guy named "Linus", and that he wrote the kernel, and that there is a GNU part, etc.

      So, I think that a lot of people that are new to this think that bsd and linux are the same thing, and not the opposite, because they hear about "linux" and then run into bsd (because linux has more attention from the media and all).

      --

      --

      --
      Stay tuned for some shock and awe coming right up after this messages!

    12. Re:bsd didn't capture new users' interest by jojo80 · · Score: 1

      I wonder, if you wanted to start a flame war... ;) the linux community is more helpful to newbies, where the BSD community is more guru focused - RTFM!
      I really don't think so. At least in German Linux-Newsgroups there are lots of people who only answer 'RTFM man foobar(1)'. I rarely got good and helpful answers when I needed them.
      When I had a problem with FreeBSD and ISDN I did get very helpful answers, no one referred to man pages or told me to RTFM. To me, it appears as if the *BSD community is more helpful. timing - linux timing was right for a unix renaissance
      hmm....but the BSDs were already there. Why didn't people use *BSD? That would make more sense to me - don't take the trailing edge stuff, but the proven technology if you need a flavour of unix. just my 0.02 Euro...

    13. Re:bsd didn't capture new users' interest by Raven667 · · Score: 1

      The BSDs are no more compatable with one annother than any other Unix OS, or Linux. They are as fundementally different as Linux is to Solaris or HP-UX or SCO.

      While it is true that changes can get distributed between the different OSs it is not too much different than the code exchange between Linux and *BSD. Certainly not the same as the difference between RedHat and Caldera or Debian or SuSE, they can easily run each others binaries, use the same libraries, etc. The only main difference between distros is the default configuration and file locations.

      --
      -- Remember: Wherever you go, there you are!
    14. Re:bsd didn't capture new users' interest by E-Dragon · · Score: 1
      To rebuke some of these comments:

      1. FreeBSD developers develop drivers for the things they use. The OS itself supports a very large number of devices. If you want a specific device added, all you have to do is find a developer willing to add it, send them your hardware, and get them technical docs from the manufacturer. Of course, if they have the device themselves, maybe that's all the encouragement they need.
      2. FreeBSD will take patches from anyone. The problem is, most people don't know how to send them in - you can use the send-pr(1) interface at http://www.FreeBSD.org/send-pr.html. Of course, whether or not it gets accepted into the main source tree is what the discussion is for. The big misconception that I highly disagree with here is the fact that anyone can help out patching the system source. It's up to them to take the initiative to send mail the the appropriate mailing list, or to use send-pr(1).
      3. Walnut Creek has had FreeBSD CD's sent out since 1993 or 1994, ever since FreeBSD 1.0. Whether it was as "easy to install" back then as it is now (and has been for several years), I don't know.
      4. We have our own "representative" - Jordan K. Hubbard. He's just as energetic, helpful, and as much of a driving force for FreeBSD as Linus has been for Linux. And the FreeBSD community has obviously appreciated his efforts - there were a large number asking for his autograph at the closing ceremonies for the FreeBSDCon '99. And the other BSD's have their own representatives, most notably Theo de Raadt for OpenBSD and Alistair Crooks for NetBSD.

      Please don't try to spread untrue rumors for things you don't know anything about. If you had actually tried to give patches to the FreeBSD project and were rejected in the appropriate form, I'd be interested. But this is just a rumor spread around by people who don't know what they're talking about.

      In particular, I am irritated about the "closed discussion" and "elitist bastard" theory regarding BSD developers. I used to be a nobody in the FreeBSD scene, but after I started porting a large number of programs/libraries, I discovered how simple it is to contribute to this great OS, as well as how friendly MANY of the FreeBSD developers can be should you take it upon yourself to contribute.

      What I think is the best part is that with the send-pr(1) interface, you really don't need to have a fix already for a bug you've found. Somebody will eventually take up bugs/ideas that have been recorded in the GNATS database. They will not be thrown away without a valid response.

      As you can see, all it takes to contribute is an understanding of the differences between the organization for Linux and the organization for FreeBSD (and the other *BSDs as well).

      --Will
      --
      GCS/E/S @d- s+:+>+:- a--->+++ C++ UB++++ P+ L- E--- W+++ !N !o ?K w--- ?O M+ V-- PS+ PE++ Y+ PGP+>+++ t++ 5 X+
  14. The Oreilly Connection by Erore · · Score: 2

    The answer is so obvious is isn't a wonder that we are missing it: Linux is more popular than BSD because Oreilly has published more books that pertain to Linux.

    I mean, we all know that the only way we ever learn anything is by reading an Oreilly book.

  15. Source model? License model? User model! by Anonymous Coward · · Score: 5
    Perhaps one of the biggest reasons is that the Linux community is very inclusive, while the BSD community is highly insular. Visiting the FreeBSD web site and reviewing their mailing list archives, or visiting #freebsd and spending ten minutes watching the conversations is enough to prove the point.

    This applies somewhat to users and to an extreme with developers. As a user, a question revealing that you don't know UNIX, not just *BSD, is enough to have you shouted out the door. As a developer, unless you're a 20 year BSD veteran, suggest an idea or ask where you can begin to help and you should be prepared to be stomped on. Hard and repeatedly. Largely by many of the project principals.

    Review some of Matt Dillon's contributions to FreeBSD in the mailing lists. He's repeatedly helped to pull large portions of FreeBSD up to and even past their Linux equivalents. Then consider the rationale behind the community's treatment of him.

    A similar type of treatment resulted in the split of NetBSD and OpenBSD. Again, reviewing their mailing list archives shows that this kind of childish animosity and cliquish cult behavior abounds.

    To the contrary, it takes all of five minutes to find something to do for Linux and to find a mentor who will help you find your way to the in crowd the first few times you've got a core-level contribution to make. They give you the benefit of the doubt as a new contributor, reviewing and considering your contribution, not your credentials or your ability/willingness to pose as a BSD veteran long enough to be heard.

    Frankly, it's surprising that this group exists outside of acedemia at all.

    1. Re:Source model? License model? User model! by bvmcg · · Score: 1
      Assuming that the goal is to further the OS, the BSD crowd doesn't get it. Social Engineering is a foreign language to them. "Just do it. Someone might thank you later, now piss the fsck off and don't bother us until you've rewritten the SCSI subsystem."

      Sorry guys. That doesn't usually work.

      Your average developer wants to feel included and appreciated from the start. Some program for the sheer thrill. But the ones who don't at least secretly want a pat on the back are rare.

      Most want to be part of a club of peers with a common goal at the onset. It's not hard to send them packing early on. BSD isn't going to grow to Linux proportions without change.

      I suggest "How to Win Friends and Influence People" by Dale Carnegie and "Cultivating Successful Software Systems Development Projects: A Practitioners View" from Scott Donaldson.

    2. Re:Source model? License model? User model! by sterwill · · Score: 2

      I think you've touched on a very important point. BSD is a cult; the development is done by a closed group of people who keep running inside-jokes, reject anyone who knows less than they do, and envy those who know more. The code isn't closed, the group is. It's a popularity contest at its absolute worst. The attitude is "do something for us or go away." The BSD license is perfect for these people. No social conscience--"just give us the code, and leave quickly so we can do very important things with it."

      Fortunately, the people who get the most work done are least interested in raising a blue ribbon ego, or "op" status on the IRC channel, or guru of the mailing list. Unfortunately, these people rarely get the recognition they deserve, but are still recipients of any derision towards the group.

      If the high school mentality ended at the so-called "development" level, problems would be confined to the results of that group, but it doesn't. Users do occasionally come into contact with "developers," and when they're told to bugger off unless they've got a patch, that's when the BSD bit in the user's brain flips to 0.

      --

    3. Re:Source model? License model? User model! by Eivind+Eklund · · Score: 5
      This applies somewhat to users and to an extreme with developers. As a user, a question revealing that you don't know UNIX, not just *BSD, is enough to have you shouted out the door.

      Can you back this up with references to actual incidents, as opposed to rumours? It do not match my impression at all, with the exception of #freebsd on efnet, which is an has always been a cesspool (from what I hear, #unix and #linux are very similar.)

      As a developer, unless you're a 20 year BSD veteran, suggest an idea or ask where you can begin to help and you should be prepared to be stomped on. Hard and repeatedly. Largely by many of the project principals.

      This is not true. It match the rumours I hear from the the Linux community, but they do not match the reality I've experienced.

      I entered the FreeBSD community without having much Unix experience; I'd run Linux for a few months (on a machine somebody else set up for me), and had had a login on a couple of other machines (SGIs and Suns). I was welcomed as a mailing list participant without having done any hacking on Unix itself, and as a short time Unix user. I got commit privileges after having been active on the lists for a couple of months, continously feeling them as friendly and welcoming of suggestions.

      I am now regarded as one of the 'project principals' (to use your term); I have never seen anybody being flamed for asking where to help. If I ever see a developer flame somebody for that, that developer will need to defend his commit privileges. I do not consider that kind of behaviour acceptable, and neither does (as far as I can tell) the community as a whole.

      When it comes to ideas, I agree that there can sometimes come a backlash. This is usually in the form of 'Show me the patches' when somebody is suggesting someting that is a lot of work, but we do have people in the community that will pounce rather hard on proposals that are bad, and where the person proposing it could have found that out by spending a small amount of time.

      Review some of Matt Dillon's contributions to FreeBSD in the mailing lists. He's repeatedly helped to pull large portions of FreeBSD up to and even past their Linux equivalents.

      LOL! Matt has contributed a lot, sure, but he's not "pulled things beyond their Linux equivalents" - the things he has been working on has always been further ahead in FreeBSD than in Linux. They are some of our strongest pieces.

      Then consider the rationale behind the community's treatment of him.

      The treatment has mainly been to not accept that he should, on his own authority, refuse to accept advice from the rest of the community, and that he would not keep direct write access to the source tree (commit privileges) unless he learned to work with the community.

      Would you want to have somebody that was contiually at war with Linus write to the Linux source tree, in opposition to what Linus said was OK? One that also fought with the rest of the Linux users? I suspect not - and the FreeBSD core team felt they could not accept that situation, either.

      Note: I cooperate with Matt on FreeBSD development, and consider him a brilliant programmer. I also think that he should have commit privileges (which he has now). However, I don't think he has been mistreated - he has been behaving in a way that brought him repeatedly into conflicts with people, and that had to be handled.

      Eivind.

      --
      Doubting the existence of evolution is like doubting the existence of China: It just shows that you're uninformed.
    4. Re:Source model? License model? User model! by dcs · · Score: 1
      There I go... no moderation on this story just to answer to this.


      In two words: not true.


      A "closed group" of people? Of two hundred people with DIRECT access to the repository? Hell, that's so not true that you can see the very proof in the message to which this one is a reply. It mentions the treatment that Matthew Dillon received. Yes, and, guess what, he is a committer too.


      There is nothing "closed" about FreeBSD. It gets new committers all the time, often people whose involvement with FreeBSD is quite recent.


      Do you think all these people from all these different countries have always known each other? That they all even get along with each other all the time? The very existence of some incompatibilities between some of these developers is a proof that the group is by no means closed.


      But, ok, let me back this with facts. Me. I once submitted a keyboard layout and a patch to the ide driver long, but never did anything to actually catch any attention. Then, around mid december 1998, I got interested in the on-going work with the boot loader. I submitted some patches and within two months I was a committer.


      I certainly never got rejected by anyone who knew more than me, and I never saw any signs of envy from anyone knowing less than me.


      Sure, I had to submit patches. You can't become a developer if you don't develop, though. But FreeBSD WILL welcome anyone who is actually willing to do something. This might range from doing userland programming to kernel programming to third-party applications porting to documentation writing to bug fixing. And even if your contribution is not in enough volume to turn you into a committer, your contributions are still accepted (like my keyboard map once was).


      Don't trust me. Check for yourself. The list of committers, minus the core team, who are also committers, and the additional contributors. Feel free to count them. Pretty closed group, eh? :-)


      And that's not even the complete list...


      Now, let me ask you a question... did you intentionally misrepresented the facts, or you just failed to do any research and mindless repeated FUD you read elsewhere?

      --
      (8-DCS)
    5. Re:Source model? License model? User model! by Eidolon · · Score: 1

      I'm not sure what to make of it all. I am a very seasoned BSD user (since 4.2 running on a VAX) who dabbled in Linux for a while before realizing that beloved BSD runs on microcomputers these days.

      I'm still far from knowing all the answers... BSD has changed a lot since 4.2 and running it on microcomputers is in many ways more challenging than running it on a VAX. ;-) I've probably been around BSD longer than a good many of the #freebsd or #netbsd regulars.

      I've found that asking for help in #linux or #freebsd is rarely helpful. The reasons for this seem to be:

      1. Everyone assumes you're a newbie if they've never seen you before. Instant prejudice.

      2. Most participants don't know any useful answers to (what should be) simple questions.

      3. Some things don't work well on Linux because they came from BSD. Some things don't work well on BSD because they came from Linux. This is a much bigger problem than people customarily admit. The two operating systems are different enough to create real problems, despite binary compatibility. KDE, for example, is extremely Linux-centric and some of its features simply will not work on BSD even if you use the Linux compatibility API.

      The parent post reads as if someone has had a very brief and bitter experience with BSD. That's sad. If that's how things are, at least know that it's not how they used to be. I think it is more than possible to have the same sort of experiences in the Linux world, and I think that there is some truth to the notion that most of the people active on Linux and BSD newsgroups and IRC channels simply don't have a clue to answer technical questions. It takes a great deal of perserverance to find useful information in these forums.

    6. Re:Source model? License model? User model! by Alex+Zepeda · · Score: 1

      Bah. I happen to think that KDE is rather Linux-centric, however, I've tried to work around quite a bit of this. In a way I resent that, because in actuality, all of the base parts of KDE 1.x work quite nicely with FreeBSD. The things that break tend to be apps that other people write (and I don't care about, and apparently none of the other FreeBSDers out there do either). However with KDE 2.x, I'm running into quite a bit of trouble with some oddly undefined symbols. However, all in all, KDE isn't by nature as Linux centric as a lot of people think it is. Damnit Jim, help make it non linux centric.

      --
      The revolution will be mocked
    7. Re:Source model? License model? User model! by dennisp · · Score: 2

      I think it was friday that I and a couple of others (including JKH) helped you with your IPFilter problem.

      If I remember correctly, you said you had very little experience with FreeBSD. In other words, you have no idea what you are talking about and are using blind and misappropriated speculation.

      BSD is not a cult. You are just full of shit.

    8. Re:Source model? License model? User model! by dennisp · · Score: 2

      Please name some features that KDE has that do not work on BSD. I use KDE on my primary desktop and have not run into any problems whatsoever. I had to change maybe 4 lines in a Makefile to get Kdevelop working and all of base kde works perfectly.

      The one and only thing I did notice that was not working was the computer info page which is based on the linux proc setup which is not similar at all to the BSD equivalent.

    9. Re:Source model? License model? User model! by Eidolon · · Score: 1

      These are the difficulties I've run up against in using KDE 1.1.1 with FreeBSD 3.3-RELEASE:

      kdm has some subtle configuration issues, and its error reporting is cryptic beyond the call of duty. I still don't have kdm working, and I've put a lot of time into it. The BSD FAQ makes it sound trivial to do (which it isn't) and the KDE FAQ glosses over it totally. It appears that no one on the KDE mailing lists or in #freebsd or #kde over multiple IRC networks has noticed that this problem exists.

      Floppy device support for users other than root. BSD mount and /etc/fstab are different from Linux mount and /etc/fstab; the BSD fstab can't accept the "user" mount option, which KDE depends on to provide mount privileges to regular users. I tried to get around this with a sysctl -w vfs.usermount = 1 and chmod 777 /dev/fd0, but still can't mount floppies from KDE. Naturally, if I go to the shell and run mount by hand, BSD mounts the floppy. This is fine for me, but I've been configuring a FreeBSD system from a non-technical friend. I'd have just gone with Linux, but FreeBSD feels a bit more responsive on her old 486 box; even this slight advantage is important enough for running Communicator that I'm reluctant to switch to another OS.

      Yes, I too had noticed the info module not working, and it was clearly a /proc matter. Not a big deal, mostly.

      Thanks for reading.

    10. Re:Source model? License model? User model! by dennisp · · Score: 2

      Interesting,

      If i have time tommorow or thursday, I may look into this problem and submit a patch for the port or just give a heads up to the maintainer..

  16. A peek at history by Anonymous Coward · · Score: 2

    I suspect the real reasons for GNU/Linux's popularity over the BSDs are historical rather than technical. The BSDs were bogged down in legal battles at a critical time, a time when GNU/Linux systems were less mature but starting to take off. If not for that, 90% of the GNU/Linux geeks would probably be BSD geeks today.

  17. Sorry... by Anonynous+Coward · · Score: 1
    But, "Openness" only becomes a factor with a vast miniority of total Linux or BSD users.

    Linux is more popular than *BSD for the same reason Windows is more popular than Linux...Marketing. There's no Linux, Inc. but the grassroots marketing for Linux, and the fact that so many companies are offering easyish to use installation CDs you can buy at CompUSA is far superior to the marketing and end-user distribution available for any of the BSD variants.

    1. Re:Sorry... by Lazaru5 · · Score: 1

      The FreeBSD PowerPak is now also available at CompUSA.

      --

      --
      My comments and opinions completely reflect those of anyone and anything I am remotely associated with.
  18. It's yet another example of pump-priming by NateTG · · Score: 2

    BSD has been around for a long time in the academic world, but it hasn't had the massive user-coder base that Linux developed fairily quickly (This is the true genious of Linus). So it has been maintained AFAIK by a small group of people. BSD isn't as userfriendly as Linux, because that small group of pelple is more interested in the development of BSD than in helping newbies.
    Some BSD distros are really tough to install -- things like making your own boot disks from scratch for certain systems etc specifically because they want to discourage lusers from bugging them about it.
    So in general BSD is smaller because it is smaller -- there is not as big a user/developer community as there is for Linux, hence less development and exposure...
    As the OSS model starts to take more and more market share, BSD will develop a a strong competitor for Linux, especially in professionally administrated systems. This is a good thing -- competition provides for improvement. For example if this occurs we may see companies providing BSD service contracts, and improved security for linux.

  19. Another big reason: college undergrads? by belgin · · Score: 5
    Well, I really had never heard of BSD to any great degree until after I had finished my undergrad degree in computer science. Linux was a topic of discussion amongst undergrads in the first and second years of college.

    As self-fufilling prophecies go, this is another one. BSD continues to be less known, because it is less known. Over half of those same college undergrads I knew in computer science and engineering got hands on experience with Linux before they graduated, myself included.

    BSD continued to languish in the realms of unknown software.

    Many of the undergrads went out into the work force and are now doing jobs where they can at least provide knowledgable input about Linux. Many of them went to find jobs specifically where they could work on Linux systems. There was no similarly large pool of individuals who knew BSD amongst the dozens of fellow students I knew, including the systems operators (I was one) for our UNIX systems, or much in the faculty. Perhaps a few people seemed knowledgable about BSD, but they didn't talk about it much, because people knew more about and were already interested in Linux.

    For the most part, colleges provide the ground where our next generations of individuals in the computer industry learn UNIX-based OS's and determine what technologies they will bring to their initial workplaces. If BSD is as absent from most colleges as it was from mine, BSD won't catch on, because many of the people who would use it will not know about it.

    B. Elgin

    --

    B. Elgin
    "Read at your own risk; feel free to ignore."
  20. Quick factual correction by sethg · · Score: 3
    A lesser known operating system developed in 1970 at the University of California, Berkeley, called the BSD (Berkeley Software Design) is, in fact, the oldest free operating system.
    According to "Twenty Years of Berkeley Unix", Berkeley didn't even have a copy of Unix until 1973.

    The first free version of BSD (Networking Release 2) was distributed in June 1991, but got tied up in lawsuits from 1992 to 1994. By the time that was cleared up, early versions of Linux were already available.
    --
    "But, Mulder, the new millennium doesn't begin until January 2001."

    --
    send all spam to theotherwhitemeat@ropine.com
  21. "Berkeley Software Design" by kevin805 · · Score: 1

    It is "Berkeley Software Distribution", right? I've also heard "Berkeley Standard Distribution", but that makes less sense than "Berkeley Software Design". Maybe "Berkeley Standard Design"?

    1. Re:"Berkeley Software Design" by Guy+Harris · · Score: 2

      The distributions of software from the University of California at Berkeley were called "Berkeley Software Distribution"(s).

      A company named Berkeley Software Design, Inc. sells a commercial OS - called "BSD/OS", not "BSDI" - based on the BSD 4.4-Lite source.

  22. BSD = BERKLEY?! by Ion+Berkley · · Score: 1

    Whilst there are many historical reasons that
    undoubtedly contribute to this including the
    fragmentation of effort of open/free BSD etc....
    and the original BSD licensing issues, I can't
    help wondering if there is a key role played by
    the association of BSD with a physical entity
    namely Berkley rather with a global comunity of
    "no fixed abode". Maybe people psychologicaly
    don't feel an equal part of this thing, but more
    like they are helping with someone elses project.

  23. BSD = Berkely Software Design? by slickwillie · · Score: 1

    When will these people ever get it right?

  24. sloppy reporting by Anonymous Coward · · Score: 1
    Not only is the author thoroughly ignorant of history (BSD started in 1977 and not from scratch, and so until recently it was only "free" if you already had a very expensive AT&T source license- netbs d.org has some good history), he doesn't even get name "Berekeley Software Distribution" right.

    I'll leave the comments about which kernel is better to the more knowledgable, but I have to wonder why you'd question some random suit about it just because his managers holds the Unix trademark this year.

  25. Article is Flame-Bait by Blue+Lang · · Score: 1

    I'm a little tired of the 'we'll start it out sounding neutral and informative and then switch to some unsubstantiated claims about BSD's superiority' articles posted here. This person claims that BSD's kernel is much more 'sophisticated' than linux's, in ways preferred by grad students and professors.. Sigh, and yerg.

    So, responders, do us all a favor, if you wanna prove how, why, and where BSD is better than linux, post code and illustrate the difference - then explain why each OS does it a certain way.

    My opinion: shut up and use whatever you feel like using. If popularity is important, go use windows.

    --
    Blue

    --
    i browse at -1 because they're funnier than you are.
    1. Re:Article is Flame-Bait by mr · · Score: 1

      Hrmmm.

      At The Bazaar, Mr. Raymond said over dinner that the BSD kernel was cleaner.

      And Mr. Perens expressed a similar view. If I'm lucky, that I have on tape, and need to get it off the camcorder.

      Want "proof" of a BSD kernel being better than Linux at task X, or Linux being better than BSD at task Y? Then help create a Debian GNU/BSD. Because that is the only way anyone will be happy with the benchmark.

      (And I'm itred of the 1st posts, the fornicate-esque, and the BSD is dead posts. But because its cold out I wear a hat and so no one sees my point)

      --
      If it was said on slashdot, it MUST be true!
  26. Three reasons and bonus ranting by bjb · · Score: 3
    I think Linux and *BSD are fairly equal on the features and abilities front (yes, you can nitpick this if you want), but there are a few things:
    1. Linux is under the GPL, and wasn't held back by any ATT garbage
    2. The 'Image' of Linux; created by a single man (media view for the most part) and the logo is cute (the Daemon is cool, but probably scares someone, even WITH the halo)
    3. Microsoft is scared of Linux, not BSD.

    Yes, I fully agree that *BSD has numerous merits and that this is something that could easially be flamebait. However, Linux is just a bit ahead of the game (most likely due to the ATT crap), and it has caught the media attention. Its one thing when something comes out of a university, but when "the young finnish student created his own operating system because he didn't like what was out there" grabs peoples' attention, it seems to be a more heartwarming story.

    Ok, now let's look at this part about the "heartwarming". Yes, we as techies like to look at things for their technical merit, not their popularity. As I said above, they are both quite good and nitpicking is justified, but almost pointless. Wall Street knows about BSD, but they just don't really care. There are no Red Hats or VA Linux companies for *BSD, and Microsoft doesn't acknowledge *BSD (from what I've seen; tell me otherwise, please). I remember a few months back reading in the Wall Street Journal an article on how "If you thought Linux was the underdog, BSD is underground". People have read about it. They don't care.

    I guess I could rant about this for a while, and I'm sure people will flame and argue with this. The point I'm getting to is that Linux just has the head start on the public eye, and it is simply the center of a lot of attention. *BSD may be better than Linux. Linux may be better than *BSD. However, they're both quite good and certainly much better than that software from Redmond. RedHat and VA have both brought Linux to the public attention. I fear, however, that if there is a 'Red Hat BSD', it will just confuse people; it could turn out to be a good thing, but it could also just bring us back to the 80s when there were 20 different platforms and little in the way of 'cross platform' standards.

    Rant, rant, rant. I better stop before I talk in circles

    --

    --
    Never hit your grandmother with a shovel, for it leaves a bad impression on her mind...
  27. Re:Oh really by slickwillie · · Score: 1

    In the not-so-distant past, O'Reilly published more generic Un*x books (e.g. Unix in a Nutshell), but as the popularity of Linux rose so did the number of Linux-specific books from O'Reilly.

  28. Linux=Easy; BSD=Difficult by NatePuri · · Score: 3

    Initially Linux is decipherable with IRC help, mailing lists and on-line docs. Whereas, BSD takes some previous understanding and the man pages on BSD assume Unix know-how. The LDP HOWTOs are written for the uninitiated and that is a major reason why Linux appeals to people more.

    This whole Unix rebirth is very new. So people new to Unix will choose Linux first. Once they realize there is something objectively more mature for advanced purposes, they may consider a switch.

    I started out learning Unix by trying out the various Linuxes. Now I've settled on OpenBSD b/c security a huge issue for my business. And my level of security must be high. That is not so for other people. While I'm a huge proponent of security and privacy I feel most people can be by with their Windows computers if they have a good firewall/ip-masquerading gateway installed that runs either Debian (most secure Linux), FreeBSD or OpenBSD. With the growth of the home LAN, such a configuration is a no-brainer and you can install it on some relic of a PC that you thought could only have been used as a door stop.

    If people want to try a more stable desktop system; I usually will configure a system with KDE and FreeBSD or Debian for them. In terms of application capability they are about the same so it boils down to the person's taste in licencing features.

    But for someone who wants to go it alone and install and learn as one goes, I recommend something easy to install like Corel Linux or Caldera Linux (no not Red Hat which I recommend for the corporate environment).

    If a company came along that made a BSD easy to install and use it would be a truly awesome product; that is what Darwin and MacOS X is all about and they are awesome but expensive. If you have the money for Apple's new OS, the advantages for using a BSD based system speak for themselves after you've used them for a while. Unix gurus don't need convincing. They either only run BSD because it's 'real' Unix or they only run Linux because the GPL is preferrable. The arguments about Linux having more applications and better hardware support are, of course, silly because if that is the basis for an argument then we'd all be using Windows instead.

    The bottom line for new users is documentation that's easy to access and meant for them and an install process that people perceive as easy (i.e., it has a GUI). Linux has it and BSD doesn't.

    1. Re:Linux=Easy; BSD=Difficult by InfiniteReality · · Score: 2

      I'm a FreeBSD user, so I can't comment on other BSDs. However, FreeBSD has an excellent documentation system in their Handbook. It is a great resource for new users and experts alike. Also, FreeBSD 4.0 is scheduled to include hooks in their installation program which allows for a GUI installation.

  29. Popularity be damned by Zigg · · Score: 2

    Shrug. I could really care less if it's more popular or not. It works wonderfully for me, and at the time that I switched from Linux, it worked much better. Popularity be damned.

    I've contributed a few ports to FreeBSD. I contribute in the little ways that I can because I believe in BSD and know that if no-one contributed at all, BSD would indeed die. (In the BSD-kernelled Debian threads, someone seemed to think that BSD was dying ``because of its license''. I would challenge that by asking them if ``not dying'' means ``growing to an unmanageable size''.) By the same token, if contributions to Linux stopped, Linux would die.

    I believe in BSD because it works, and because the source code is open (though some seem to think that anything non-GPL'd is not ``open'' -- we need not rehash those arguments here.) I can do with it what I want.

    The community spirit of BSD ensures -- without encumbrance of license -- that BSD will be around as long as there are still people working on it.

    1. Re:Popularity be damned by treat · · Score: 1
      I could really care less if it's more popular or not.

      It's comforting to know that you care so much. Most of us, however, couldn't care less.

      The idiom is "I could care less". Like many others, it does not mean the same thing when taken literally. It's one of a few that actually means the opposite when taken literally. But this doesn't make your criticism valid.

    2. Re:Popularity be damned by treat · · Score: 1
      The idiom is "I could care less".
      Nope. That's erroneous. The correct phrase is the negation of that one. People who can't say what they mean shouldn't be near a computer.

      Well I don't see how I could possibly disagree with your stunningly brilliant position. You told me I'm wrong, without any explanation or evidence.

      Face it, there are many sequences of words in English that mean something different than what you would expect from the definitions of each component word. It's messy and imprecise, but a great deal of effort is put into learning it, and that's how it works.

      If you don't like it, you should start making suggestions for how the language should be changed. Don't tell people that a phrase that has been in use for half a century is "wrong".

  30. Thanks by Anonymous Coward · · Score: 1

    You saved me a lot of typing. :)
    In other words I agree with this poster. Linux is designed to bring in people. BSD doesn't seem to me to be similary designed. It's all about the initial planning stages and mission goals. BSD's goals seemed to be just for a free distribution of UNIX for poor academic geeks or something. Linux was a free reimplementation of UNIX for everyone.

  31. fsckin lame by CrudPuppy · · Score: 1

    pointing to a default apache page... are you just plain stupid?

    --
    A year spent in artificial intelligence is enough to make one believe in God.
  32. Sophistication? by ajs · · Score: 3

    The article contends that Linux is not as sophisticated as BSD. While I agree that certain features of BSD might be more advanced (e.g. from a brief chat with one of the NetBSD folks, the UVM sounds cool), Linux is braving uncharted water in a number of previously shunned areas (I was stunned to find, for example, that I can choose to enable a kernel-based static http server in my Linux kernel as of 2.3.x). This willingness to break with UNIX tradition is what sets Linux apart, and frankly is the reason that many of us like it.

    I also like BSD (I was a huge fan of 4.2, back when Ultrix was 4.2 with the serial numbers filed off). BSD has a tradition of stability and innovation that is hard to match, and look forward to a world where BSD and Linux are equal participants in the operating system development community. But can we stop pretending that one OS is "better" than another, and focus on which OS is right for a given task/environment?

    1. Re:Sophistication? by Charlatan · · Score: 1

      ...Linux is braving uncharted water in a number of previously shunned areas (I was stunned to find, for example, that I can choose to enable a kernel-based static http server in my Linux kernel as of 2.3.x). This willingness to break with UNIX tradition is what sets Linux apart, and frankly is the reason that many of us like it. ...

      I think that this is really one of the reasons that people choose BSD over Linux. While Linux is busy developing a 'kernel-based static http server' the BSD developers are ensuring a perfect blend between new features (as demanded by the market) and stability.

      I think it all boils down to the user. BSD users have come to expect a ROCK SOLID operating system. A system that does exactly what's expected of it, exactly as advertised. Linux users seem more willing to accept half operational features because they're 'new and cool'.

    2. Re:Sophistication? by ajs · · Score: 2

      While Linux is busy developing a 'kernel-based static http server' the BSD developers are ensuring a perfect blend between new features (as demanded by the market) and stability.

      As I've said, I don't think there's much value in this sort of "my OS is better than your OS" discussion. Anything that I point out that Linux has been audacious enough to do alone is an easy target, but the bottom line is that BSD and Linux are both more stable, feature-rich and supported than any commercial OS that I've ever seen.

      Linux is taking a bold step with khttpd, and perhaps it will turn out to be a mistake, or perhaps it will be succesful, and the BSDs will adopt it in order to maintain a competitive Web server position. Either way, we're watching the power of open source, and when journalists cite bogus comparisons like "In terms of sophistication, the BSD operating system is better than Linux", I just have to hang my head and sigh.

  33. After Mac OS X is released... by musique · · Score: 1

    ...there may be more copies of BSD flavored Darwin/OS X out there than Linux.

    You can still make proprietary changes to Linux, you just can't distribute or sell the binary result, which is counter to what the article states. Apple open sourced OS X (though not GPLed) except it will keep its GUI to itself--since that's what makes the Mac the Mac. If the GUI were opened up, Apple would rot. Apple could not make money without complete control over at least some of its system.

    I think that Linux and BSD are suited for different tasks. It's good that we have them both.

  34. Inspite of Bechmarking Linux & FreeBSD..... ? by siva06 · · Score: 1

    This is one of the many discussions Comparing FreeBSD and Linux ...

    Well there have been many a comparison between these 2 and many good point coming out of them. In turn these two have been raised to such atechnical levels, to countermand their negatives in each reviews. This is possibly the only real success that Open Source or FSF have really met.

    The real success would be in terms of the commecrial value of these system to support further enhancements. But the real situation is that commercial UNIX's like SUN / HP have still not implemented many of the good features that either FreeBSD or Linux have yet they are still outstanding in sales. To top the list the NET has whole list of pathetic performance of Windows NT and talk to any Sys ADMIN for the rest, still It tops the DeskTop...

    Could the real reason be that the word FREE is being misrespresented as POOR QUALITY ....

    I cannot think of a better reason for wither Free BSD or Linux not achieving the Compatitive levels. Where do we start the real education ... ?

    I would like to help on this ..

    Any suggestions

  35. FreeBSD vs. Linux by Kwikymart · · Score: 2
    My trusty FreeBSD book has a section on this. Some of the points are that

    1)FreeBSD aims to be a stable production exnviroment while Linux is more "Bleeding Edge" development enviroment.



    2)FreeBSD is still relatively unknown , since its distrobution was restricted for a long time due to the AT&T lawsuits. Linux did not have any lawsuits to contend with. So for a long time it was only free UNIX-type system available



    3)As a result of lack of knowledge about FreeBSD not much commercial software is available for it. Linux has a growing amount of commercial software for it.



    4)As a result of a smaller user base, FreeBSD is less likely to have drivers for brand-new boards than linux.



    some of these points may not help this discussion at all but I sure hope some do



    --

    Buying a Dell computer is equivalent to dropping the soap in a prison shower.
    1. Re:FreeBSD vs. Linux by TMB · · Score: 1
      3)As a result of lack of knowledge about FreeBSD not much commercial software is available for it. Linux has a growing amount of commercial software for it.

      Since FreeBSD and Linux both use ELF binaries, any well-written application written for one should work on the other, shouldn't it? Mind you, I've seen some commercial software that isn't entirely happy outside the distribution it was written on, never mind on a different OS. :-b

      4)As a result of a smaller user base, FreeBSD is less likely to have drivers for brand-new boards than linux.

      Often true (and self feeding), but it's a two-way street. For example, USB support is much better on FreeBSD than on Linux at this point.

      [TMB]

    2. Re:FreeBSD vs. Linux by Guy+Harris · · Score: 2
      Since FreeBSD and Linux both use ELF binaries, any well-written application written for one should work on the other, shouldn't it?

      No, not necessarily. {FreeBSD,Linux,Solaris x86,Unixware,...} ELF binaries for the platform in question expect the shared library routines they call to have particular calling sequences, with data structures having the layout of the OS on that platform, with various #defines, etc. having particular values, and so on. The mere fact that those OSes all use ELF is insufficient to arrange that binaries for a given CPU will run on all of them.

      Now, there are Linux-ABI implementations for all of those OSes (Linux implements it by definition; FreeBSD has support for Linux binaries; lxrun runs on Solaris and, I think, Unixware - it may originally have been an SCO program), so some commercial Linux binaries may be able to run on all of them.

      Often true (and self feeding), but it's a two-way street. For example, USB support is much better on FreeBSD than on Linux at this point.

      I've heard that to be the case for USB, and plug-and-play ISA seems to work better on FreeBSD than on Linux right now as well.

      Both of those will, I think, change with the 2.4 Linux kernel - but there may, in the future, be other places where FreeBSD does better than Linux, just as there are places where Linux does better than FreeBSD, when it comes to supporting hardware.

      The relative state of OSes X and Y at time T doesn't necessarily indicate that the relative state will be the same at time T plus delta T; some of the Microsoft anti-Linux marketing literature may well make correct points now about stuff that NT does better than Linux, but that doesn't mean it'll always do better - and the same applies to stuff Linux does better. Of course, marketing literature is generally intended to persuade, rather than inform, so if somebody says "XXX does better than YYY at ZZZ", be careful that you don't necessarily implicitly infer from that statement that XXX will always be better than YYY at ZZZ....

  36. Some thoughts of my own by jd · · Score: 3
    1. The Jolitz' kept their mods secret between releases, and development went at snails pace. At the same time, Linux entered the arena with an open, rapid development model and a lot of people (myself included) defected to the Linux camp, after it became obvious Linux would overtake 386BSD and keep going.
    2. BSD's installation method has not changed since the days of 386BSD. It still autodetects, in much the same way, and has everything in TAR files. No great problem - I prefer tarballs to RPMs, as they're more generic, but they aren't as friendly on novices.
    3. BSD's hardware support, frankly, sucks. It's awful. It's improving, but it's a long way from being as hardware-friendly as Linux.
    4. BSD is harder to obtain. Linux can be found in bookshops, in the computer stores, and probably in your cornflakes, before long. FreeBSD, OpenBSD and NetBSD are lucky to get a mention in some of the online stores on the Internet.
    5. Linux has =LOTS= of distributions, which means there's =LOTS= of choice and LOTS of growth. It also means that any 6th-former can cobble together a distribution for some specialised purpose, put it on the net, and get a name for themselves, and possibly an IPO a few weeks later. For a system that prides itself on being commercial-friendly, BSD hasn't done that. There are only three surviving distributions (386BSD is dead) and no new distributions look like appearing out of the fog. No experimentation = stagnation.
    6. The volume of supplied software, with many distributions of Linux, barely crams onto 4 CD's. You could fit all the BSD distributions on one CD and still have room to spare.
      1. This is nothing "bad" about BSD, but rather why I think there's a huge gap between them. It's a gap that's easily filled, if I'm right, but it's still there, at the present.
    --
    It's a small world and it smells funny; I'd buy another if it wasn't for the money; Take back what I paid (SoM)
    1. Re:Some thoughts of my own by erik+umenhofer · · Score: 1

      >BSD's installation method has not changed since the days of 386BSD....as they're more generic, but they aren't as friendly on novices.

      When I used the install it was pretty wasy and it had a nice gui type sysinstall type setup.

      >BSD is harder to obtain

      Huh? Give me an internet connection and a floppy disk and you shall have BSD.

      >Linux has =LOTS= of distributions, which means there's =LOTS= of choice and LOTS of growth

      I see this as bad! I like to know all the work is in one place. I don't want to buy 10 different version of the same OS to find what i need. (speaking of buying...forget that..ftp install!)

      >The volume of supplied software

      Your gain is our gain, It's called linux_compat! BSD can run linux binaries (among other os's) sometimes better then linux can run them! So if you complain about BSD's software base...then really linux has the problem too!

    2. Re:Some thoughts of my own by jd · · Score: 2
      *G* Never let anyone say that Open Source doesn't encourage quick bug-fixing. A whole host of problems, and all of them get fixed within the span of a few minutes! This must be an all-time record! :)

      Seriously, the *BSD distro I'm most familiar with is OpenBSD, which might as well use the original Jolitz' installation method. If FreeBSD is better, I'll give that a go and try it out. Though maybe the BSD folk should get it more widely known that some dialects of BSD have good installers.

      As for FTP install, you can do that with Linux, and grab stuff from other distros (via Alien) at the same time. What does it matter where it came from? The real advantage of multiple distros, though, is that you can focus on certain stuff. If speed is the name of the game, Stampede is going to save you a -lot- of time! If you want a low-cost embedded router, go for The Router Project's distro. And so on. With Special Interest Groups, there's not such a big demand for "other" software, it's more a case of getting the SIG software running optimally for that group.

      --
      It's a small world and it smells funny; I'd buy another if it wasn't for the money; Take back what I paid (SoM)
    3. Re:Some thoughts of my own by _Sprocket_ · · Score: 2
      >BSD is harder to obtain

      Huh? Give me an internet connection and a floppy disk and you shall have BSD.

      As it was pointed out, the same can be said for Linux. But that misses the point.

      Joe newbie isn't going to set up their machine to download an OS for hours on end via their questionable MODEM connection. They want it quick and easy. A CD from a local store provides that. It also provides mindshare as they see "Linux" plastered on different shrinkwrap boxes sitting on the shelf.

      Having said that, it could be argued that this kind of user isn't BSD's target. That's probably a subject for another thread.

      The point is... you like FTP installs. I like FTP installs. But the person who's curiosity is piqued by alternative OS' is more likely to want the quick fix a credit card and a CD they pick up at the store can give them.

    4. Re:Some thoughts of my own by jd · · Score: 2
      Because the moment you exclude a mind, whether it be the mind of a techie or the mind of Joe Average, you lose:

      1. A potential source of inspiration. Even the most mindless of morons CAN come up with delightful and original ideas.
      2. A potential source of bug-reports. Nobody finds bugs faster than a clueless newbie, except maybe a clueless newbie fool.
      3. A potential source of bug-fixes. Every pair of eyes looking at the code is another chance at finding where the semi-colon should be. They don't need to be technicians, any more than you need to be a professional director, in order to spot where a continuity error is, in a film. It's not much different.
      4. A potential source of suggestions. Is the OS missing some feature that the techs have grown used to coding round? Is coding round the lack a good thing, or is it a waste? If nobody asks, then nobody answers.
      5. A potential source of demand. Development takes money and resources. But if all your users are also developers, you're not going to get any of that green paper circulating, to fuel the fire.
      Discrimination is an Unnecessary Evil, and should be the only thing ever burned at the stake. Nobody should be compelled to use a tech system, but if someone wants to, they should have the means to do so. If BSD is a "free" system, then it's free for all. NOWHERE in the licence does it say that BSD folk should believe in freedom for some.

      BSD, like Linux, can only survive when people truly know that it's Freedom For ALL, Regardless.

      --
      It's a small world and it smells funny; I'd buy another if it wasn't for the money; Take back what I paid (SoM)
    5. Re:Some thoughts of my own by RAruler · · Score: 1

      386BSD perhaps?

      --

      --
      Insert Witty Sig Here
    6. Re:Some thoughts of my own by _peter · · Score: 1


      >no new distributions look like appearing out of the fog. No experimentation = stagnation
      The second part doesn't follow from the first; No new distributions does not indicates no experimentation.


      >You could fit all the BSD distributions on one CD and still have room to spare.
      This is patently untrue; OpenBSD alone takes up 2 CDs and has for several releases.

    7. Re:Some thoughts of my own by _Sprocket_ · · Score: 2
      Damn. My Communist Party registration card must have fallen out of my Linux box. Must remember to find it and fill it in so I can continue to use Linux.

      If I were into the flame fest thing (as opposed to lame attempts at humor), I'd point out all this "red scare" stuff that comes from BSD fanatics (note the play on mascot color). Ahh well. Maybe we can herd all the Linux zealots and aim them at the BSD zealots and cancel them all out - or point the whole lot at Microsoft. :)

    8. Re:Some thoughts of my own by _Sprocket_ · · Score: 2
      Why does anyone want non-tech types using a tech system? This is Linux's mistake, and BSD's success.
      The ease of a CDRom install has nothing to do with technical merrit. One day in the near future (hopefully) we'll all have broadband connections to our homes. Then a network install will be somewhat trivial. Until then, we're stuck with a majority of people using MODEMs (lets not even get into the economic issues involved here).

      Doing a network install over a slow connection requires a good deal of dedication (both to investment of time and tying up other resources). Someone who is curious about your favorite alternative OS may not be inclined to make that investment just out of curiosity. Again, going down to the store and transfering the entire OS via a payment, sneakers, and a CD is much quicker and gets them to trying out the new environment quicker. That's good.

      It's great to see Linux enjoying this advantage. It'd be great to see BSD too.

  37. The thing to understand. by Amphigory · · Score: 5
    One thing RMS is right about is that the Linux environment is about a lot more than a kernel. It is about userspace utilities. It is about X. It is about GNOME and KDE. It's about Mozilla and Opera. It's about apache, zeus, and sendmail.

    And all of these things will run, mostly without modification, on BSD.

    Who cares which kernel is used! That's a small (but very important) part of the whole picture. The important thing is that we are rapidly developing more and more user-space stuff that will run on any modern UNIXy platform -- whether its Linux, FreeBSD, or the Hurd.

    Linux's success helps to insure BSD's long term viability. Don't forget it. From some stuff I've seen, I gather that the core *BSD teams are well aware of it.

    --
    -- Slashdot sucks.
    1. Re:The thing to understand. by bolthole · · Score: 1

      What this means, is that there is a large vacancy for a "New distribution of Linux", which would consist of X, GNOME, KDE, Mozilla, Opera, apache, zeus, sendmail, .....

      But running on FreeBSD :-)

      Anyone with too much time on their hands, a CD burner, and good BSD setup skills?

  38. expand your horizons by pope+nihil · · Score: 1

    i always figured that it would be better to be well versed in as many different operating systems as possible. that way, not only do you start to figure out which OS is best for the job, you can feel comfortable if your own company pulls a switcheroo on you.

  39. Re:Linux=Incoherent; BSD=Integrated by Anonymous Coward · · Score: 1
    convincing. They either only run BSD because it's 'real' Unix
    No, we run it because the BSD distros are significantly more robust than any Linux distro. This means a lot to us. We are accustomed to a different level of testing and integration perhaps that non-Unix people. We know what a solid, connected, intuitive system, not a disconnected, hodgepodge one that feels like a patchwork quilt.
  40. BSD snobishness by mondamay · · Score: 1

    Linux included things like the DOS filesystem that the BSD kernel hackers looked on as a wart on their beautiful OS. Linux and BSD had different philosophies at the beginning, where Linux aimed to make a *NIX for the users, and BSD was shooting for the best--from the purists view--kernel. Since then, I think that you could argue that BSD has moved towards the Linux camp, with a little movement by Linux towards the BSDers (like Linux not allowing GGI).

    --
    --Last Exit To Babylon
  41. BSD rhymes with LSD by UnknownSoldier · · Score: 1

    You say jib, I say gib.

    As long as both parties know what the other person means, then pronounciation isn't [too] important.

    Cheers

    1. Re:BSD rhymes with LSD by norkakn · · Score: 1

      hmm.... i'm just a fool and have been unable to make my quad box work (free, openBSD, Redhat6.1, winblows 95[i ike games ok?]) and i think you may have hit on the solution... hmm....... well a little acid never hurt anyone

  42. Re:FreeBSD vs. Linux stability. by Zurk · · Score: 1

    Im not going to bother answering all your points but as for 1)FreeBSD aims to be a stable production exnviroment - youre wrong. Several bad implementations can be found in the FreeBSD x86 assembly code that render it unstable under certain rare conditions. In fact, Linus *rejected* these changes for Linux outright (even though they would have meant speed improvements).
    See this URL : [ http://kt.linuxcare.com/kt19991220_47.html#1 ]for one such example..others can be found elsewhere.

  43. Interesting: its in an Indian newspaper by gupg · · Score: 1

    I find it interesting that main stream Indian newspapers are giving thought to such geek dilemas such as why BSD is less widely used than Linux. It seems that the true test and fight of linux/unix variants versus Windows/Microsoft is going to be in Asia; China and India mainly. These are the huge markets of tomorrow with some of the highest growth rate in computer usage. Now is the time to capture market share; since it is always easier to capture market share as the market is created rather than have to take it from someone else. Also, these countries want and need inexpensive solutions; perfect for Linux marketing.

  44. FreeBSD by tsikora · · Score: 1

    Damn straight! That penguin is stealing all our glory. (Just kiddin') Probably for the best. The slower(development) pace makes a far superior and stable platform. Everything about FreeBSD in my opinion is better from CVSup to sysinstall. The very concept of make buildworld/make installworld is lightyears ahead of the rest. Most importantly it demands knowledge of Unix. That alone may very well spell Linux's downfall. Linux is slowly changing but not necessarily for the better.

    --
    -- Ted tsikora@powerusersbbs.com
  45. Its the license,s****d! by Kenneth+Stephen · · Score: 2

    No offense, but didnt you read the article? The point was not that BSD is superior or inferior to Linux. It was that fewer people are contributing to it.

    Yes, applications written for Linux may run on BSD and vice-versa. But the catch really is the license. If NT were as stable as *BSD or Linux, do you think that the development community would switch over to NT? No way - and this is because of the license.

    Note that the user community might switch over - but that isnt the point. When we talk of contributions, its the development community that we are talking about.Now, if the BSD license was changed to make a closed source distribution impossible, then you would see contributions increasing tremendously.

    PS : The story to which we are commenting is a bit confused in that the writer is unable to distinguish between the development community and the user community. Linux achieved a bigger user community because of features provided by a bigger development community.

    --

    There is no such thing as luck. Luck is nothing but an absence of bad luck.

    1. Re:Its the license,s****d! by stimuli · · Score: 2
      I agree with you to some extent, but when I talked of support for Linux and BSD, I'm thinking more along the line of applications, which will be covered by what ever licence the vendor sees fit. There is no reason there should be a Word Perfect (not open source, as it is) for Linux, but not for BSD.

      While the issue of the licence is important for kernel development, I don't see how that matters for those who will write applications that, by my estimation, should run happily on both systems.

      For open source applications it often isn't a problem -- in most cases I should be able to compile on either system with minor modification. However, for applications that are either closed-source (and thus binary only), or those which are open source, but have complex library and other environmental issues (such as something like KDE or Gnat -- the GNU Ada compiler), I hope that the makers of such software will take the time to put out a BSD version. I just don't see any reason that they shouldn't.

    2. Re:Its the license,s****d! by Pierre · · Score: 1

      Most apps are on both platforms.

      After running Linux for a couple years I installed FreeBSD and it's ports collection. I'm running KDE and Blackbox right now. I haven't found anything yet that I run on Linux that I don't have on FreeBSD. In fact it's hard to tell the difference. My debian box never crashes and neither does my freebsd box. I think this is what will hurt the BSD in the number of users department. The bulk of the users are likely using the OS as a desktop/workstation. If there isn't much of a difference and there are 5 times the number of people using Linux which do you choose?

      I don't know why more people chose Linux. Maybe the license is why more people use it. I think GPL sounds more glamorous but has it ever been an issue? Even if somebody takes code and folds it in to their program, it doesn't take the code away. It's just more people using the code.

    3. Re:Its the license,s****d! by Guy+Harris · · Score: 2
      However, for applications that are either closed-source (and thus binary only), or those which are open source, but have complex library and other environmental issues (such as something like KDE or Gnat -- the GNU Ada compiler), I hope that the makers of such software will take the time to put out a BSD version. I just don't see any reason that they shouldn't.

      Because, for the commercial software, it's Another Platform To Support, and they have to build it for the platform, test it on the platform, take support calls for the platform, etc.?

      Some vendors do have FreeBSD ports - Applix and Perforce, for example. Linux binaries of commercial products may run on FreeBSD, as well - I seem to remember Jordan Hubbard suggesting to vendors that they port to Linux first.

      As for the open-source applications, well, check out the BSD ports collection - my desktop is KDE 1.1.2, from the FreeBSD ports collection....

  46. Third Factor, and Addendum by MattMann · · Score: 3
    Somebody who to me sounded knowledgeable wrote a month ago, somewhere on slashdot, a third reason:

    3. Linux supported IDE long before *BSD did, and these were the inexpensive drives that the masses had.

    To that, I would add, now that Linux is way ahead,

    4. Linux is way ahead in market share, and just like the internal combustion engine, the incandescent bulb, Microsoft OSes, and other less than optimal technologies, once a product is entrenched with sales networks, R&D networks, customer support networks, etc., it takes a vast improvement in the underlying technology to overturn the economic advantage of sticking with the status quo.

    Any open sourced kernel offered just that sort of advantage over windows (to developers) and with the internet paradigm shift to vastly increase the numbers of servers, open source (especially of unix) on the commodity platform offered a compelling enough functionality jump to create the new market/new standard. But since Linux won the initial sprint, expect it to continue its hegemony. The BSDs have a chance of gaining share by being very compatible and utilizing highly transferable skills, so all is not lost for them, but things are often the way they are for many small good reasons, not by random chance, nor for one reason.

    1. Re:Third Factor, and Addendum by Bruce+Perens · · Score: 2
      But BSD had networking then. Linux didn't. So you had a choice of IDE disks or networking. I guess most people had IDE disks and no network to connect to.

      Thanks

      Bruce

    2. Re:Third Factor, and Addendum by MattMann · · Score: 2
      most people had IDE disks and no network

      I suspect you called it exactly there, but it should be pointed out that even with the availability of IDE disk and a network, the answer would still be "disk".

    3. Re:Third Factor, and Addendum by StenD · · Score: 2

      But BSD had networking then. Linux didn't. So you had a choice of IDE disks or networking. I guess most people had IDE disks and no network to connect to.

      I'm not sure when "then" was, but Linux had TCP/IP by early 1993. Trying to remember why we chose to go with Linux over 386BSD, it's a bit hazy. It wouldn't have been the IDE issue, as the systems we were looking to use with an affordable alternative to SCO initially all had SCSI drives. It wasn't failure to know about 386BSD, as Dave Burgess was right down the hall, gently evangelizing. The only thing that I can think of was the uncertainty of the USL vs BSDI lawsuit. I suppose that by the time that was settled, we had already invested enough into Linux, and showed enough progress with it, that there wasn't any reason at that point to switch horses to one of the BSD branches.

    4. Re:Third Factor, and Addendum by Skapare · · Score: 1

      FreeBSD (as of 3.1 which was released march 1999 ... I have not tested 3.4 the most recent version) appears to have limitations in the area of IDE support. Certain ATAPI devices and/or configurations do nor work and/or are not recognized to exist. Earlier discussions from advocates and at least one developer suggested lack of support was intentional because the configuration was not standard (though from reading the standards this appears not to be the case). Recent thread on comp.unix.bsd.freebsd.misc now suggests that support for all IDE is intended and succeeds for others. Perhaps device specific details are problematic.

      In a sense, you could say that BSD has not, or had not in the past, stooped down to the level of the masses. OTOH, I did notice in trying to install FreeBSD 3.1, there was some GUI orientation to the install tools. I much preferred the way SLS (how many Linux old timers go back as far as the SLS distribution) installed.

      --
      now we need to go OSS in diesel cars
    5. Re:Third Factor, and Addendum by dennisp · · Score: 2

      5) they don't have the momemtum gained from the endless hype in positioning it as an 'MS killer'

      6) a less divergent path where supporting anything and everything isn't a top priority

      7) lower key users who are less likely to advocate their OS choice

  47. Re:Stupidity? by pigeon · · Score: 1

    Linux is not a house of cards. The hype surrounding linux and it's related companies are. I do noet expect that Linux will come down as a dekc of cards, but the hype might, since Linux itself is not a bad product. But... why a shitty unix like SCO for commercial unix? You're pro BSD... choose BSDi! And your expectations about the companies taking another direction are very unprobable. I think these companies like Linux, and they're less or more stuck to some GPL matters.

  48. and BSDers are nastier thane Linuxers by Anonymous Coward · · Score: 1

    Really. When I started casting about for a substitute to Win31 or DOS/Minuet, I tried to download a floppy image of BSD.

    The response when I tried to ftp it? "Go away, stupid WinBlows lamer." "Fuck off, gates." I finally got an image on floppy, it wouldn't boot. Last experience with it.

    By then, Barkakati's flame book arrived, everything worked first off. Been using Linux ever since. Even wrote some stuff under the GPL, but mostly using it as an NT replacement for printer and modem serving.

    Might look at BSD again, if php4/apache works under it, but most probably, I'll just get a modern video card and give BeOS a spin.

  49. *BSD, various distributions of Linux(TM), etc. by crimsun · · Score: 2

    I will attempt not to fall into the dreaded "*BSD vs. various distributions of Linux" flamebait here. Here's my story:

    I'm still primarily a NT user. Why? Better IDE, more game support and more robust (not to mention widespread) hardware support. However, many, many moons ago I began the Slackware trek. Its simplicity and stability (courtesy of Linus's kernel, of course) really impressed me. I installed a few servers out of curiosity and promptly forgot about them. Four or five months later I realized that they were still running strong (given the requisite `kill ` that one must force on some runaway thread). This was utterly positive; I was used to checking my computers daily to ensure they were still running. Additionally, I noticed that performance wasn't hampered as much as under NT when more users connected or accessed the mounts. Thus, Linux became the fileserver OS.

    A few short months later I installed my first copy of FreeBSD (2.7?), again, just out of curiosity. I setup ircd, nfsd, a few other daemons and went on vacation. When I returned, needless to say, ircd (known for its uncanny ability to split) was still running. Of course the other parts of the installation were doing just fine. So when I was called to do a security-apparent job, I tried OpenBSD. Perhaps I was entrigued by the entire "secure by default" mentality (or was it the line-by-line auditing? ;-). Needless to say, that box is still running Open (uptime is nearly 500 days!), and I'm rather impressed by its ability to simply reject repeated exploits and intrusions.

    Linux has never failed me, nor has *BSD. My limited experience does not qualify me to say that *BSD is any more able to handle mission-critical jobs than Linux, but I will say this: the degree of success that surrounds Walnut Creek is simply amazing. If a site that handles unimaginable daily traffic can withstand attacks and impatient ftp'ers, then I can trust its mission-critical status.

    I now use two primary machines: a FreeBSD 3.4 (just made world a few nights ago! ;-) machine for the "good stuff" and a NT4 machine for gaming.

  50. Some thoughts on Some thoughts of my own by raytracer · · Score: 1

    1. It is true that the original 386BSD was hampered somewhat by the Jolitz' attempt to control development. That was pretty much over by the time FreeBSD entered the scene though.

    2. Installation of FreeBSD is quite a bit slicker than all but the most recent versions of Linux. Various Linux distributors have obviously made this a high priority, so it is improving for them.

    3. Over the years, I've found FreeBSD's hardware support to lag Linux a bit, but I've had some problems with supposedly debugged support under Linux as well. I've found that FreeBSD supports virtually all the hardware I have, but your mileage may vary as your equipment does.

    4. Linux certainly is easier to obtain. I used burn CDs for anyone I knew who wanted to try FreeBSD. Some FreeBSD people I know thought this was a bad idea, that if you wanted FreeBSD you should order the CDs from Walnut Creek to support the project. While I certainly urge people to do that if they find FreeBSD useful, I think it was shortsighted to insist on that. If someone doesn't try FreeBSD, they aren't going to contribute monetarilly or with their programming effort to make it better. Therefore our goal should be to get as many people to try FreeBSD as possible.

    Recently ISOs of the FreeBSD distribution have begun to show up more widely, which makes it easier for people to try it. I think this is a good thing. OpenBSD has not yet adopted this mentality, which is in my opinion at least partially responsible for its rather limited popularity (it also has a relatively unkind installation process, which is another).



    5. Linux does have lots of distributions. I'm not sure that this is a good thing. Most are either of poor quality or simple rehashes of other distributions. The plethora of distributions means plethoras of problems for the most part, as different kernel, config and packaging options make knowledge of one distribution less useful.

    To be fair, BSD suffers from similar divergence amongst its three major distributions as well.

    6. FreeBSD ships on 4 CDs. They are pretty full. Very little software available for Linux is not available on FreeBSD.

    I don't think there is a huge gap. I think the various Linux vendors are a bit further down the road in creating distributions that even novice users can install and use. Given the vast amount of money raised in various Linux IPOs, I don't expect that FreeBSD will close the gap quickly.

    1. Re:Some thoughts on Some thoughts of my own by Trashman · · Score: 1

      Recently ISOs of the FreeBSD distribution have begun to show up more widely, which makes it easier for people to try it.

      And where exactly may I find these iso's? I poked around freebsd.org and couldn't find anything.

      --
      Do not read this .sig
  51. Common misconception by Bruce+Perens · · Score: 2
    You are making a common misconception. The GPL does not tell a copyright holder what to do with his own code. The copyright holder can always issue his own code under any license, place his own code into the public domain, etc. It is only other people than the copyright holder to whom the GPL applies. It only tells people what they may do with other people's code.

    Thanks

    Bruce

    1. Re:Common misconception by cjs · · Score: 2

      he GPL does not tell a copyright holder what to do with his own code.
      Well, obviously what I'm saying is that the GPL tells you what to do with your code should you try to combine it with any GPL'd code.

      This makes the GPL different from other free software licenses in that the GPL is a weapon: its purpose is to help Stallman in his fight to purge the world of all non-GNU software. (Yes, all, including other free software. Read his disucssion of the readline library and the LGPL if you don't believe me.)

      I don't mind the GNU license otherwise, but the stance against pluralism really disturbs me. And even if I accepted the argument some people make that Stallman's really only out to get proprietary software, his willingness for free software to be collateral damage in that war is just as bad.

      cjs

      --
      The world's most portable OS: http://www.netbsd.org.
    2. Re:Common misconception by Arandir · · Score: 2

      You misunderstood the comment. If I write an extension to gcc, and that extension is 100% my own code, I am still required to use the GPL. BSDL folks have little problem with those who wish to keep their own personal source code GPLd forever. But it's a very different thing to require distinct code be under the same license.

      Think of how pissed the GNU community would be if BSD had similar clauses. There would probably be an article at GNU describing such a thing as obnoxious.

      --
      A Government Is a Body of People, Usually Notably Ungoverned
  52. Why I use Linux instead of *BSD by SoftwareJanitor · · Score: 2

    Let me start off by saying that my first exposure to *nix was 4.2BSD on a VAX-11/780 back in 1985. I spent the remainder of the 1980's using 4.2, 4.3 and 4.3-Tahoe on various VAXen as well as SunOS on Sun 3's. While I also played with other UNIXes such as Ultrix, HP/UX, A/UX, Xenix, Venix and AT&T SVR2 and SVR3 in those days, BSD was my primary platform.
    In the early 1990's I spent a lot of time with various SVR3 derived commercial UNIXes including Motorola's SVR3 on 88000 machines and AIX on RT's and RS/6000's. While still *nix, I pined for a lot of things that were missing compared to BSD. By late 1992 I was back to SunOS 4.1.x on Sparc which was more to my liking.
    The main reason I chose Linux over *BSD is back in 1993 when *BSD and Linux were first coming to my attention and I was able to scrape together enough cast-off parts and $$$ to hack together a decent enough box (a 386DX-20) to run them, I couldn't get *BSD to run on the junk hardware I had. Linux, on the other hand worked. With the olvwm window manager I was astounded how well it made a clunky PC look and act like a SparcStation running SunOS.
    Nowdays I use Solaris on Sparc at work (and some at home, although my primary home platform is Linux and my home SparcStations are all old and slow models) and I could afford to run *BSD as well as Linux at home (I've got dozens of machines), and I do occasionally load one of the *BSDs onto a box to see how things are coming along. I really have nothing against *BSD. If Linux didn't exist, or if it ever somehow falls apart, I will certainly look at switching to one of the *BSDs.
    But I have to say that Linux for me has the comfort level now, after six years, I've spent more time with it than any other *nix family. Every time I have tried the *BSDs lately, I just haven't been able to find a compelling reason that would lead me to pick one of them over Linux. Linux still seems to have a better combination of hardware support, easier installation and wider software availability. Mind that the *BSDs aren't really that far behind, but without any real compelling advantage, it is just enough of a subtle turnoff to keep me complacent.

    Well, there it is, just one person's opinion. Take it for what it's worth and with a grain or three of salt.

  53. BSD vs. Linux by jormurgandr · · Score: 1

    Personally, I use Linux. That is mainly because I am interested in kernel programming, and I like the idea of getting the source code to every app on my system. However, I think BSD has a few good ideas. It's great that a company can come along and take an operating system, pay nothing for it, change it to make it (hopefully) work better and provide some new feature or service that was previously unavailable (Example (kinda), the OpenGL X-server that was recently released). This is great not only for the *nix world, but also for developers. I think I might be installing BSD soon just to give it a try.
    =======
    There was never a genius without a tincture of madness.

    1. Re:BSD vs. Linux by Guy+Harris · · Score: 2
      Personally, I use Linux. That is mainly because I am interested in kernel programming, and I like the idea of getting the source code to every app on my system.

      I also am a kernel programmer, and like getting the source code to all components of my system.

      The OS most often running on my home machine is FreeBSD. I have full source code to the kernel and to all components of my system.

      Liking the idea of getting the source code to every app on your system is not a reason to prefer a Linux distribution to {Free,Net,Open}BSD; it's a reason to prefer an open-source OS - such as a Linux distribution or {Free,Net,Open}BSD - to a closed-source OS.

      (Note also that having Linux is not only not necessary if you want source to every app on your system, it's not sufficient, either - you have to avoid installing third-party apps that aren't open-source, which are available for Linux and {Free,Net,Open}BSD as well as for closed-source OSes.)

  54. Re:FreeBSD isn't as hyped as Linux by tweek · · Score: 1

    Well since I asked this about YRO about a month ago and got an answer, I'll give you the answer I got. Someone mark this up so maybe someone will read it and not ask the question again? ;)

    The colors are indicators of a special section of slashdot. Notice the Sections menu along the left hand side of the screen?
    Try selecting a specific section and check the colors. My favorite is the Apache section. YRO is just plain fugly though.

    The red used here is a tie-in to the bsd colors

    --
    "Fighting the underpants gnomes since 1998!" "Bruce Schneier knows the state of schroedinger's cat"
  55. it's not the license by arielb · · Score: 1

    if it was simply because of the license then how come more people use apache (bsd license) than any other GPL server?

    --
    ---
  56. 1 million vs. 10 million by SRT · · Score: 1

    In my experience people tend to graduate from Linux to *BSD once they've gotten their feet wet. Has anyone else experienced this?

    I base this not only on my own past, but many others I've spoken with.

    "Waiting for that OpenBSD IPO!!"
    Scott

    1. Re:1 million vs. 10 million by Guy+Harris · · Score: 2
      In my experience people tend to graduate from Linux to *BSD once they've gotten their feet wet. Has anyone else experienced this?

      No, not particularly. I know a number of people who've been using various Linux distributions for quite a while - i.e., they haven't "graduated from Linux to *BSD" - and people who've been using BSD for a while, but haven't personally seen a significant amount of movement in either direction.

      I'd like to see a very broad survey before I drew any conclusions about people moving from Linux to *BSD. The evidence people have presented seems largely anecdotal....

    2. Re:1 million vs. 10 million by rapett0 · · Score: 1

      I have seen that happen more then once. Many of the UK sysadm have gone from other unisys to FreeBSD when the dust settled.

  57. Timeline by core · · Score: 2

    For the various posts that seem to be interested in the BSD release timeline, here is how it went:

    1977: 1BSD (based on UNIX time-sharing system sixth edition from Bell)
    1978: 2BSD (based on 1BSD)
    1979: 3BSD (based on 2BSD and 32V which itself was derived from unix seventh edition)
    mid-79: 4.0BSD (derived from 3BSD)
    1981: 4.1BSD (derived from 4.0BSD)
    1982: 4.1aBSD
    1983: 4.1cBSD (not based on System V)
    1984: 4.2BSD (not based on System V release 2); SunOS is based on it.
    1986: 4.3BSD
    1988: 4.3BSD-Tahoe
    1990: 4.3BSD-Reno
    1991: NET/2 (386BSD spun from it)
    mid-1992: NetBSD 0.8 spawns from NET/2
    1993: FreeBSD 1.0 spins from 386BSD as well
    mid-1993: 4.4BSD
    1994: 4.4BSD lite 1
    1995: FreeBSD 2.0, 4.4BSD Lite-2, BSDI 2.0 spin from 4.4BSD lite 1

    Note that I'm a linux person, so don't hold me accountable for those dates :) Rather trust the book "the design and implementation of the 4.4BSD operating system" by marshall kirk mckusick et al.

    Linux of course appeared in 1991.

  58. Re:Linux=Incoherent; BSD=Integrated by law · · Score: 1

    What the flying fuck does this have to do about Linux?
    If you think somthing is a "hodgepodge" it the distro's not "Linux"

    EG
    Debian is not a "hodgepodge" it is not "insecure"
    My two favorite BSDisms. Robust can be argued, maybe.

    If I install or configure any Unix based system poorly. It will be insecure. Linux, BSD, even NT.

    I don't critize BSD, but then again I don't use BSD ethier. If you use these kind of arguments, your doing BSD a DISERVICE!

    Badly reasoned argments make me disbelieve that person's cause.

    --
    "Think of it as evolution in action."
  59. Re:The Linux Community is(was) Nicer by tsikora · · Score: 1

    Aw come'on there's jerks everywhere it just so happens there are more in comp.os.linux.*.
    (See... it's easy to start a war). Seriously I heard many complaints from people about this. On the other hand many FreeBSD'ers are the archtypical Unix user with zero tolerance for newbies. Myself included on occasion. Most of this attitude stems from users who refuse to read the faqs, readmes, and docs. We learned it that way why can't you. Of course I'm not like any of them.(Ha!)

    --
    -- Ted tsikora@powerusersbbs.com
  60. Life _is_ fair by Kenneth+Stephen · · Score: 2

    You missed out the most important reason : the BSD licence.

    Think about it : the Linux developers are just as smart as the BSD developers. The BSD movement also had the advantage that they were a mature operating system at the time Linux was a blip on the horizon. So why didnt the BSD movement gain as many developers as Linux did? Simply because the license was unattractive to them.

    Some people also say that the centralized committee nature of BSD is a detractment. Bosh! Linux also has the same committee nature where a patch doesnt appear in a distribution unless it has been blessed by the core developers and / or Linus. The only difference is that this committee is not as formalized as the *BSD committees.

    --

    There is no such thing as luck. Luck is nothing but an absence of bad luck.

    1. Re:Life _is_ fair by Spamizbad · · Score: 1

      Well... here's how I look at it.

      GPL = Good for the developer
      BSD = Good for the 3rd party source

      Who writes MOST of the software? The developer.
      Who is going to fix the most bugs? The developer.
      Who will in the end, probably write most of the drivers? The developer.

      With linux expanding, and more commericial organizations being involved in it, some say the BSD license would be better then the GPL.... This may be true but Linux NEEDED the GPL to get where it was.

      The GPL wasn't the only element, the posts above states what else it has.

      Everybody knows the major linux people, what about BSD.... it's just "oh-whats-his-name".

      Yes, FreeBSD is more stable, but Linux is something new, something fresh, something with new ideas and innovations. People like new. It comes down to that. Linux offered a new stable alternative to windows, it was easy to rally around, and you felt proud as a user and and/or as a developer of it.

      Linux filled the gap between BSD and Microsoft. Not a traditional Unix (Linux isn't very unixy). This is exactly what needed to be done.

    2. Re:Life _is_ fair by Kenneth+Stephen · · Score: 1

      First of all, get your facts straight : gcc is not proprietary.

      Secondly, the *BSD's do have a choice. Nobody forced them to use GCC. They always have the option of writing a compiler with the BSD license. The fact that none of the compiler writers have done so speaks for the popularity of the BSD license.

      --

      There is no such thing as luck. Luck is nothing but an absence of bad luck.

    3. Re:Life _is_ fair by Guy+Harris · · Score: 2
      Yes, FreeBSD is more stable, but Linux is something new, something fresh, something with new ideas and innovations.

      Does anybody have any data from a careful study of both the open-source BSD kernels and of the Linux kernel, or of both the open-source BSD OSes and the open-source components of Linux distributions, to indicate that "new ideas and innovations" are present in Linux to an extent significantly greater than the extent to which they're present in the open-source BSDs?

      (Linux isn't very unixy)

      Could you please justify that assertion with facts? When I log onto a Linux system, it sure as hell looks as much like a "Unix system" to me as do FreeBSD or Solaris or HP-UX or Digital UNIX or....

    4. Re:Life _is_ fair by pwileyii · · Score: 1

      I think 'unixy' is meant to say that linux has all these spiffy graphical utilities to configure things where UNIX has configuration files that you edit and that's it. Yes, Linux also has these, but look at linuxconf, it is not what I would call very 'unixy.'

  61. Article Title is a Fallacy by Overt+Coward · · Score: 1
    The article pre-supposes that Linux is more "popular" than BSD. The real question should be for what group is it more popular -- the majority of both the Linux and BSD user communities are still programmers. For many reasons (as specified in other responses) Linux seems to be more popular among them.

    However, because of the ability for a company to make a proprietary fork of BSD code, I would wager that there are more copies of software out there that owes their origins to BSD than there are for the GPL.

    So, really, "popular" to whom? Developers or end users?

    --

  62. Re:Stupidity? by moogla · · Score: 1

    You are neglecting that fact that you don't _need_ RedHat, SUSE or Debian to provide you linux... users have the most control. If the companies were to go astray, the someone would do The Right Thing and resume distributing their untainted versions. Tbis is an important to watch out for,, Linux could become too commercialized at some point, and young computer nerds all over the world will retch simultaneously. But I think that some new group will step up to revive it to it's prior, geeky glory with some new logo and clever name.

    --
    Black holes are where the Matrix raised SIGFPE
  63. Hippies by Ross+C.+Brackett · · Score: 1

    If people were OSs, BSD would be an accountant. Efficient, not too fancy, to the point, and not opposed to a little blatant capitalism from time to time as long as it got things done. Linux (and a lot of other GNU stuff), on the other hand is a genius hippie. Long haired, occasionally bong-hitting, Lennon-listening cool guy who happens to be a math whiz and plays concert piano. He may not get the job done as well as the first guy, but he's a lot more fun to hang out with!

    Okay bad metaphor. My point is that I think the success of Linux is possibly due to the fact that the Linux community is a little bit funky. And I like that. And I think a lot of people like that. For instance, user support is like being lost and asking a hippie for directions. He won't try to sell you a map, or instead give you directions to a store where he's trying to sell you something. True, the directions might be a little odd, and he might smell a little funny, but it's okay, because as they said at Woodstock, we're all feeding each other.

    What mystifies me is how big business is suddenly interested in Linux. I feel as if they've been bamboozled, but in a good way, like actually getting a pig elected to President. If big business actually knew what was good for them, they would adopt BSD like gangbusters. Big companies like things like restrictive licensing, being mean, and other things the BSD license permits them. But amazingly they've adopted Linux, and now Linux is beginning, in a good way, to corrupt those companies from the inside.

    Well I say nee-haw. Advocacy has paid off, and I say we take the money and run. If Redhat and other companies want to spend millions on producing high-quality GPLed software, I say right on. Free software will never collapse. It will never be un-useful. As long as we're true in our hearts and we code like madmen, the GPL will protect us, and that's exciting. That's why people fall in Linux, and that's why I fell in love with Linux.

    [This groggy Monday morning rant was brought to you by Coffee, or rather the lack thereof.]

  64. Distributions... by Lazy+Jones · · Score: 1

    One of the reasons why *BSD is lagging behind in popularity is certainly the lack of a well-known commercial distribution with the advertising, support and non-proficient-user-friendliness. Red Hat FreeBSD or SuSE FreeBSD would make a difference...

    --
    "I love my job, but I hate talking to people like you" (Freddie Mercury)
  65. Early on... by Rob+Riggs · · Score: 1

    It seems that many of the posters here are relatively new to Linux. But, as someone who was in the market for a Unix-like OS in 1994, I can tell you that "the communities" were the most important factors in the decision of which OS to use. The Linux community was so utterly helpful that it was hard not to use it. A visit to #linux on EFNET would answer just about any question that anyone would have. And just watching the enthusiasm of the group was awe-inspiring.

    On the other hand, the BSD users were the entrenched, holier-than-thou, get-outta-my-face-you-stinkin-newbie "gurus" who needed to deride the less knowledgeable in order to feel adequate. It was not a fun experience to be on the receiving end of the *BSD crowd in those days. The BSD crowd today is far different -- a really bright and helpful bunch. But the early days of the movement really hurt. It will haunt the BSD community for a long time to come.

    The fact that Linux now has the largest market share and the strongest momentum is due to the outrageously helpful member of the community early on. This sense of community and willingness to help was inspired by the kernel developers themselves. Back when the daily volume on the linux-kernel list was under 30 messages a day (imagine!) it was quite common for the developers to very gently point the newbies in the right direction when they asked for help. ("This list is for kernel development... I'm sure if you ask on 'linux-foo' you're question will be answered.")

    I just want to thank the Linux community for being such a helpful bunch. The early developers and users have inspired a large number of people (myself included) to continue the tradition of evangelizing the OS and helping the newbies get on their feet.

    --
    the growth in cynicism and rebellion has not been without cause
  66. You smoking crack??? by fr0g · · Score: 1

    Commercial? Have you never see www.bsd.org?

    1. Re:You smoking crack??? by Lazy+Jones · · Score: 1

      Commercial as in "free software backed by a company such as Red Hat".

      --
      "I love my job, but I hate talking to people like you" (Freddie Mercury)
  67. Linux has one major advantage. by kavi_3 · · Score: 1

    Linux has one major advantage over BSD in that Linux modifications happen faster then BSD modifications. The reasons I see for this is a different mindset between people who work on Linux and people who work on BSD and the difference between the GPL and BSD licenses.

    In the Linux world, if a feature is needed, it is added pretty quickly and any problems that arise are fixed when they are found. People don't try to make the software perfect, they just try to make it do what they need it to do. Other people likely to take the isk of using the new feature, because with the source code, they can fix anything that causes a problem, then these fixes are given back to due to the GPL and all will benefit from them. Therefore .many features are more readlily adopted.

    In BSD, things happen slowley because the people working on it are more concerned with sercurity and stability. While this allows them to create some very reliable systems, it slows the development of the OS so that it is always lagginf behind in features. Also, if someone does make a good change or add an important feature, they could always keep it and not share it, so these features will be adopted slowly.

    The end result is that Linux, while more prone to problem when using the latest and greatest kernal/library/etc, it more quickely adopts features that user want and need.

    For the desktop, I think that the Linux model is better, and for servers the BSD model is better. But that can be overcome by using an older and more stable versioin of Linux (most people with production Linux servers so this.)

    --
    "Attention Citizens, 2+2 now equals 3.947547175. Please recalibrate your equipment now" --The Computer
    1. Re:Linux has one major advantage. by Guy+Harris · · Score: 2
      Other people likely to take the isk of using the new feature, because with the source code, they can fix anything that causes a problem

      ...which would also be true of {Free,Open,Net}BSD, as you have the source code.

      then these fixes are given back to due to the GPL and all will benefit from them

      ...which is also often true of {Free,Net,Open}BSD as well.

      In BSD, things happen slowley because the people working on it are more concerned with sercurity and stability.

      Umm, how quickly do things happen in, say, the 2.2[.x] Linux kernel tree, as opposed to the 2.3[.x] tree? You appear to get at least some choice of "bleeding-edge" vs. "stable" there...

      ...and you also do with FreeBSD (and possibly the other BSDs), by going with the "-current" tree if you want to be on the bleeding edge or going with a "-stable" release if you don't.

      Also, if someone does make a good change or add an important feature, they could always keep it and not share it, so these features will be adopted slowly.

      That has nothing to do with adopting features, it has to do with whether they're available for the open-source BSDs to adopt - and there appear to be people contributing stuff back to the BSDs, e.g. Whistle have contributed a number of things to FreeBSD.

      The end result is that Linux, while more prone to problem when using the latest and greatest kernal/library/etc, it more quickely adopts features that user want and need.

      Well, maybe. Perhaps the ISA PnP tools, or the ISA PnP kernel patch, for Linux can be made tow work as well as the ISA PnP support has worked for me on my box (it handles my PnP ISA sound card just fine - no, I do not want a PCI sound card, I'd rather leave my PCI slots available for cards such as networking and SCSI cards), but the PnP ISA patch didn't work very well on the 2.0[.x] kernel on my Debian partition (I could've debugged it, but didn't particularly have any interest in doing so, as it Just Worked on FreeBSD), and it wasn't clear whether I'd have to update some config file to use the ISA PnP tools (I could've dug into that, but didn't particularly have any interest in doing so, as it Just Worked on FreeBSD).

      I.e., I don't think it's as clear-cut as you describe - you can do bleeding-edge stuff with FreeBSD (and perhaps the other ones) if you want, and you can do trailing-edge stable stuff with Linux if you want. (Note: "trailing-edge" is not being used as a pejorative here; heck, I don't run "-current" on my home machine, as I'm primarily using it for development of stuff for the Ethereal network analyzer, and for surfing/reading mail/etc., so I'm reasonably happy to be somewhat on the trailing edge.)

  68. Can you judge an OS by it's cover? by PC_Circus · · Score: 1

    I have tried both FreeBSD and Linux in my quest for the operating system that fits me. I like both operating systems, though with Linux I am a bit pickier about the distro. (FreeBSD has 1). FreeBSD seems a bit harder to do a post install setup (I.E. kernel config) the Linux "make xconfig" puts me at ease a bit more than scrolling through "LINT" on FBSD.

    I think the part that hurts the BSD community the most is the amount of stores that sell the operating system. You can go online and download or purchase FBSD, but it does not seem to get the shelf space everywhere like Linux.

    You can walk into Wal-Mart now and purchase a jewel case distro of Red Hat, or go to the bookstore and pick up pretty much any "Unix" (*) book or search through the shelves full of Linux books. (Though I think most of the books are outdated, books selling with say Rhat5.2) FBSD just is not out there.

    The people who choose FBSD are those who want it, alot of people find themselves buying and installing Linux because they find a copy of Linux for $19.95 at the local store or are sick of M$.

    Linux just seems to be the buzzword nowadays and the attention it has recieved has been turned into more users. I hope that both BSD and Linux continue to grow in power and availability.

    Nothing can last forever, we will continue to evolve and create more, better, faster as time goes on.

    I will continue to advocate both FBSD and Linux and let the user decide which is better based upon their wants and needs. If approximately 10 million people use Linux and 2 million use BSD, that is still 12 million that don't use Micro$loth!

    *I often wonder who is masquerading Unix with a fresh copy of linux? apples and oranges.. apples and oranges.

    --
    'Speaking in terms of reliability, isn't it time for your Windows to crash?'
  69. Why Is Disclosing Improvements Bad? It isn't. by EXTomar · · Score: 1

    You make it sound like writing code for any GPL project is bad. Why shouldn't a writer give back any improvements made to a GPL project? After all, the others who have contributed the GPL code did a lot of work for you.

    Sitting on code that isn't submitted back only makes it useful to you. If you don't give back and share, the mainline code is going to advance and you're going to end up constantly patching or even better, some one else who isn't so selfish submits the same code fixes.

    There are plenty of situations where the GPL is not feasible. I just happen to believe that OS-level and mid-level utilities are perfectly suited for GPLing.

  70. Re:*BSD File System by NovaX · · Score: 2

    Generally BSD used UFS, but free varients are now incorperating SoftUpdates into the filesystem. I've been told that for the most part, UFS is slightly slower than ext2, but safer. The main reason is because ext2 doesn't sync as often, though both can be tweaked either for the speed or for the safety. Softupdates will do the same as a JFS for Linux, so both systems can have safe and speedy filesystems.

    I haven't seen to much of an explanation of softupdates, only on McKusick's page.

    --

    "Open Source?" - Press any key to continue
  71. We don't need another flamewar! by Daniel · · Score: 4

    If moderation extended to articles I'd mark this one down Score -1: Flamebait. Not necessarily because it's inflammatory in and of itself (although the last comment was practically asking the soapboxers to come out of the woodwork), but because we've all seen this ground hashed over again, again, and again: "BSD license sucks! Disinfect the GPV! BSD==Proprietary! GPL==Commie Facists! BSD users are elitist jerks! Linux users are clueless idiots! BSD is k00l! Linux is k00l!"
    I've browsed the first few comments and found that, unsurprisingly, they say nothing that hasn't already been repeated ad nauseum. I'd like to ask /. to try for a little more discretion in posting articles and to try to cut a little of the hype and bullbaiting. Not that the odds are in favor of this occuring..
    Luck,
    Daniel

    --
    Hurry up and jump on the individualist bandwagon!
    1. Re:We don't need another flamewar! by Geordon · · Score: 1

      I've browsed the first few comments and found that, unsurprisingly, they say nothing that hasn't already been repeated ad nauseum. I'd like to ask /. to try for a little more discretion in posting articles and to try to cut a little of the hype and bullbaiting. Not that the odds are in favor of this occuring..

      That's exactly why I read more than I post. One of these days, I'd like to be able to actually have some valid input, but until then, I just read and learn. (Two eyes, one keyboard...)

      --
      It is by caffiene alone I set my mind in motion. It is by the beans of java that thoughts acquire speed, hands acquire
  72. BSD should be right where it is. by Loualbano2 · · Score: 1

    I think one of the reasons is the "ease of use" factor. This is more of an concern for Linux distos than for xBSD distros. This is probably one of the reasons for the undergroundness of BSD. And frankly I hope it stays that way.

    I would really like things to stay the same as they are now, BSD positioning itself as a rock-stable, bad ass mother and let Linux go off and try to make everyone happy with the pretty install progs and such.

    2 cents from and ex managers of wrestlers

  73. Perhaps the "friendlyness" of the groups long ago. by jopasm · · Score: 1

    Long ago I was searching for a "free" Unix for
    my PC. At that time I was on Delphi (anybody
    remember them? :>) and had access to Usenet as
    well as ftp, etc. I'd heard about 2 different
    "projects" (well, one project and one family
    of project to be precise) - Linux and *BSD.
    I checked out the newsgroup(s) for each project.
    The *BSD seemed to be full of endless flame wars
    about which "version" was better, and any "newbie"
    questions were instantly pounced upon as an
    opportunity to berate the person in public about
    their ignorance. Not a very friendly situation.
    Then I checked out the linux groups - lots
    of people helping others, with an attitude of
    "hey, look at this cool new thing we've got,
    what can you do with it?". Guess which one I
    went with? Personally, I think that the openness
    of the linux guys & gals (and not just the license and/or legal troubles)
    is what really helped push linux in the early days
    over *BSD. No, it may not result in the cleanest
    tightest code ever, but it is a friendly
    attractive environment where would could/is
    progress at a rapid pace and most people involved
    could have fun.

    I'm currently running Linux (various distro's),
    FreeBSD, OpenBSD soon (gotta order that CD),
    and a couple of other things. FreeBSD seems to be
    a nice, tightly written OS. I am in the process of building a file/print server using
    FreeBSD. The documentation structure is not
    as "newbie friendly" as linux, but is fairly complete (hint: "Just get a good book on Unix"
    does not for newbie-friendly documentation make)
    No doubt there'll be some nice "flaming" replies
    to that comment. :>

    The *BSD groups have become *much* friendlier to
    newbies, and *BSD is starting to grow in popularity. Coincidence?

    As somebody else pointed out, both groups are
    (to some degree) working towards the same ends -
    free, powerful, useful software. This is not a
    cut-throat financial competition, there's room
    enough for several OS's/distributions. More and
    more software is being developed "across platform"
    (Linux/BSD/etc), and that's a step in the right
    direction. Cooperation not competition and all
    that. :>

    --

    ObTagLine: The more you run over the 'possum, the flatter it gets.

  74. Loud advocates make the difference. by Proteus · · Score: 1
    Why is Linux more "successful" than BSD?

    First of all, I don't know how true that is unless you define "successful" to be "widely used." Let's just assume that definition for the duration of this post...

    It's simple really: BSD users use(d) BSD because it serve{s|d} thier purpose. BSD is, like Linux, a free implementation of UNIX. The difference is, the BSD community never wanted to be any more than that -- so they succeeded extremely well at what they set out to do: reimplement UNIX under a (arguably) free license.

    On the other hand, the Linux community decided that "a better UNIX than UNIX" and "world domination" were the goals for Linux. This lead to the main advocates (ESR, Linus, AC and others) being much more vocal than BSD advocates. The Linux community _wanted_ universal acceptance, whereas the BSD community was simply concerned with making the best OS possible for their own ends.

    Not that either approach is worse (I use NetBSD for several web and intranet servers, and Linux on many desktops and app servers), but they have different results.
    -- Never underestimate the power of very stupid people in large groups

    --
    We may not imagine how our lives could be more frustrating and complex—but Congress can. – Cullen Hightower
  75. How is BSD > Linux? by Broccolist · · Score: 1

    I've heard a lot about the various BSDs being "technically superior" to Linux, but I've never actually heard any BSD advocate point out specific ways in which it is better. I've also heard it's more stable and more secure .. but a properly configured Linux box that isn't using wacky new kernel features can stay up for years, also.

    Legal issues put aside, why would I want to use BSD? Thanks,

    Broccolist

  76. support, support, SUPPORT! by tuffy · · Score: 2
    Linux support is all over the web. HOWTO sites are abundant. Precompiled software is abundant. Distributions are abundant. There's lots of places to get useful info about Linux, which equals support - and that's what people really want. Most software compiles on both, Linux binaries can run on BSD (on the proper hardware), but where's the support? There's some, certainly, but nowhere near as much as Linux has.

    Licensing is not the cause. Linux runs lots of software using BSD-type licenses (Apache has a similar license, IIRC), and that hasn't driven anyone away except for the die-hard zealots (who are in the minority). The real cause is a lack of support, and that needs to be addressed before BSD starts garnering popularity.

    Perhaps it can be addressed with commercial *BSD distributions, more *BSD web sites, or maybe just a new mindset in the community - perhaps the *BSD users don't want popularity. But the conditions won't change until the support arrives.

    --

    Ita erat quando hic adveni.

  77. BSD, Linux, and Debian by misleb · · Score: 1

    Something I just thought of that I think might sound interesting is that, as Debian Linux user I feel a bit left out of a lot of the Linux hype. Almost in the same way that BSD users are. And really, I like it that way. Debian is very strict. It has a somewhat closed develpment base and yet is completely GPL'd. Best of both worlds as far as I am concerned. I am not going to argue the benefits of GPL vs. BSDL. I will just say I feel more altruistic working under a GPL in general, and with Debian more specificly. I don't really care how popular the OS that I use is. I will use what I feel most comfortable with. Debian Linux is it.

    I hate managing BSD installations much in the same way as I hate Slackware Linux. So, for me, I would say that Debian has kept me from going to the BSD side. I think if I had the choice between Slackware and FreeBSD, I would go with FBSD on technical merit alone. But technical merit isn't enough when deciding between Debian and FreeBSD.

    As for the popularity of Linux over BSD? It is probably for the same reason that Debian hasn't gotten the mindshare that other distributions of Linux have. It is simply that most Linux distibutions cater to newbies. They are more inviting to novices. It is that simple. It has nothing to do with application or hardware support or penguins vs. daemons.. etc.

    The world is mostly full of idiots. If you cater to them, you are bound to get a larger marketshare. Bill Gates has proven this to be a winning strategy.

    So, anyone running RedHat or Slackware, ready to try FBSD, make sure you try Debian Linux too.

    -misleb

    --
    "THERE IS NO JUSTICE, THERE IS ONLY ME." -Death
    1. Re:BSD, Linux, and Debian by mr · · Score: 1

      >It would be better if Debian and Slackware would just go away and convert to BSD, so that Linux can remain free of that crap,

      If BSD is crap...why are you not working on removing all BSD-derived source code from Linux? How dare your GNU/Linux be contaminated with such BSD crap.

      (What? That would be work, and you don't believe in work...just mindless flames?)

      --
      If it was said on slashdot, it MUST be true!
    2. Re:BSD, Linux, and Debian by misleb · · Score: 1

      I don't know if you have ever actually maintained a Debian system, but it isn't like BSD. The packaging system alone makes a huge difference. Not to mention the sysvinit aspects. You must be refering to the installation process. And probably dselect more specificly.

      Now, as for the advocates, yes, we are a bit elitist but for good reason. We don't want a perfectly good system ruined by dumbed down UI's and lazy users. With a little work and a few brain cells anyone can join the club. Just run Slackware for a year.. find out how much it sucks when you have to reinstall to upgrade your system and come to the dark side. You need to be a lowly newbie for a while before you can be cool. Kinda like being a freshman in high school.

      And I don't WANT to embrace the Microsoft market! I want to perform a hostile takeover!


      misleb

      --
      "THERE IS NO JUSTICE, THERE IS ONLY ME." -Death
  78. Re:NT stability by jaclu · · Score: 1

    >If NT were as stable as *BSD or Linux, do you think that the development community would switch over to NT?


    I like and use linux, but can't agree with you on this.

    One of the main reasons why peolple make the move NT -> linux is stability.

    If that was available in NT - Why would any NT shop bother to do the switch?

    It sure costs them a lot of relearning to go to a new OS, not many would do it just on license issues. (At least that's what I think)

  79. Re:Big fallacy alert by shlong · · Score: 1

    If you would have read the entire article, you would have seen that Linus eventually reversed his position and agreed that the optimization (used in FreeBSD) was safe and correct. Man, I really want to turn on the flame switch when I read uneducated posts like yours. You make a perfect example of the reason that Linux is slowly gaining a black eye in the enterprise world.

    --
    Cat, the other, tastier white meat.
  80. Re:Big fallacy alert by Infidel+IV · · Score: 1
    So because it was suggested on the FreeBSD list (as it apparently was on the Linux lists) FreeBSD is more unstable?

    Did this optimization even go into the FreeBSD source tree? (It's not in my system anyway, just checked)

  81. Ugggggggggg by tweek · · Score: 1

    Linux this...
    BSD this....

    Why the fuck does it matter? Use what works best for you. Hell use an MS product if it works best for you.

    I have a question. Why in the hell does it matter which is more popular? They both kick ass in my opinion and I have one of each ehre at the office. I *personally* use linux as my desktop because I started with it before FreeBSD and feel much more comfortable with it. It wouldn't matter a rat's ass to me if I had to use a *BSD and couldn't use linux. You wanna know why? (I know you don't but I'm going to tell you anyway)...

    Because I have the source to all the applications I run. For those I don't, FreeBSD supports linux binaries.
    Why must obviously intelligent people getting into cock measuring contests about which one is better. Quite honestly "better" is all in the mind of the person at the helm of the computer itself.

    So let's all get a fucking grip and put our dicks back in our pants and get over it.


    --
    "Fighting the underpants gnomes since 1998!" "Bruce Schneier knows the state of schroedinger's cat"
    1. Re:Ugggggggggg by steffl · · Score: 1

      you care about popularity of OS you choose because the more popular (number of installations) it is the more hardware support it has. and you usually want hardware support (for good graphics card (that's more X issue than OS), sound cards, network card, usb devices, pnp cards, etc...). that's general situation, in some particular cases you indeed might not be interested in popularity...

      erik

      --
      ...all excited, don't know why...
  82. Why this colour scheme? Red for flamebait? by Anonymous Coward · · Score: 1

    I am getting angrier just looking at all this red!

  83. Re:Big fallacy alert by shlong · · Score: 1

    Yeah, it went in around early December. Only on -current though (which is where experimental stuff is supposed to go).

    --
    Cat, the other, tastier white meat.
  84. Re:NT stability by Kenneth+Stephen · · Score: 1

    If that was available in NT - Why would any NT shop bother to do the switch?

    But "shop" switching is a user-community switching - not developer switching - especially if we are talking about NT. My comment was about the reasons why the developer community showed a preference to Linux - thereby causing a user community expansion.

    --

    There is no such thing as luck. Luck is nothing but an absence of bad luck.

  85. Ultimately, what's it matter? by Greyfox · · Score: 2

    It really shouldn't matter which you use. All the interesting source is open, so doing a BSD-like dist of Linux (slakware?) or a Linux-like dist of BSD should be quite possible. I've found porting C code between two UNIX systems is relatively straight forward. At this point BSD seems to be able to run Linux binaries as well. So what does it really matter?

    --

    I'm trying to teach myself to set people on fire with my mind... Is it hot in here?

  86. Re:Stupidity? by the+eric+conspiracy · · Score: 1

    Check out netcraft and any HIGH volume site. None of them run Linux.

    There are many large, high volume sites that run Linux. Google, for example is a 2000 CPU based Linux site. Other examples include eToys, dejanews and RealNetworks.

    The idea that Linux cannot support a large website is misinformation, easily disproven by the facts of what is happening on the net today.

    Linux demands the user community to disclose modifications. That won't last. It can't.

    Have you no clue as to the provisions of the GPL? The day RedHat tries to hide moddifications is the day the Free Software Foundation sues them.

    This is in fact one of the STRENGTHS of Linux vs. BSD - the BSD license makes it easy for companies to take modifications private, while the GPL makes it impossible.

  87. #openbsd by fr0g · · Score: 1

    This channel has been very helpful to me many of a time. Sure they will not hold your hand but thats not what I want. I either want an answer or point me in the right direction.

  88. They don't say the GPL is the reason by Guy+Harris · · Score: 2
    An article over on Economic Times explains why BSD is as not as popular as Linux.

    At most, they quote somebody from Novell India as saying that "The reason why it is not as popular as Linux is the lack of commercial support".

    There's no place I can see where they attribute the difference in popularity to the license. I see a place where they make the factual statement that the BSDL and GPL are different, but I see nowhere anything in the article claiming that this is the reason for a difference in popularity - the sentence after the one about the license difference might, at most, be suggesting that, as a result of the license difference, "the BSD operating system" (although they don't say which particular flavor of BSD - one of the free ones, or BSD/OS) is inside some firewalls (however, there are plenty of "appliances" with Linux Inside, as well; some even have, I think, proprietary code in them, even if it's not in the kernel).

  89. Re:im glad... by bugg · · Score: 1

    "with such a lack of knoweldge"

    Apparently, judging by the lack of capitalization. Real gurus follow the syntax of the English language.

    --
    -bugg
  90. Re:*BSD File System by Guy+Harris · · Score: 2
    um, what file system does Solaris use? what does your vfstab say?

    ...ufs...logging, perhaps? (I.e., UFS with journaling enabled?) To quote the Solaris 7 "mount_ufs" man page (fetched from Sun's online documentation collection; unfortunately, the URLs look suspiciously like per-session URLs, so I'm loath to put them in the article, but go to "Solaris 7", then go to "Solaris 7 Reference Manual Collection", then go to "man Pages(1M): System Administration Commands", and it's under there):

    logging | nologging

    If logging is specified, then logging is enabled for the duration of the mounted file system. Logging is the process of storing transactions (changes that make up a complete UFS operation) in a log before the transactions are applied to the file system. Once a transaction is stored, the transaction can be applied to the file system later. This prevents file systems from becoming inconsistent, therefore eliminating the need to run fsck. And, because fsck can be bypassed, logging reduces the time required to reboot a system if it crashes, or after an unclean halt. The default behavior is nologging.

    I.e., perhaps he's using a journaling UFS.

  91. sublime by jbarnett · · Score: 1

    "In terms of sophistication, the BSD operating system is better than Linux. Its original kernel is highly advanced. It has always been popular with people doing their masters and doctorates in computer science research. The reason why it is not as popular as Linux is the lack of commercial support,"

    Does anyone else think the BSD community is subtly spreading FUD towards the Linux community. I use both Linux and FreeBSD and they both have their advantages and disadvatages, but I think the BSD community likes to display and bring up Linux disadvantages or the advantages BSD has over Linux whenever they can.

    They are both FREE and STABLE Unix systems for the lowend to highend hardware, but these hardcore BSD users need to stop thinking their OS is BETTER then Linux. In some ways, it is, in some it is not, we don't need both the Linux and BSD communities pited at each other. Both communities need to brag about what they do best and fix anything that is broken.

    Neither BSD or Linux will benfit from bashing and FUD-ing each other, they will benfit from advocating each other though.

    One (of the very many) benifits of Open source and Free software (as in speech) is a choice.

    You are free to choice. If you dislike something, you can either 1) change it, or 2) find a differnat OSS project that will fit your needs/wants. There is the opinion to FUD anything that you don't like, but this ONLY applies to closed source software.

    Everywhere I go:

    "see I am SSH-ed into this openBSD from my Linux workstation and th..."

    "Get rid of Linux, that is your problem, use FreeBSD as your workstation man, it is BETTER and doesn't crash as much"


    "Uh Linux has never crashed on me, and the problem is I had a surge on my Ethernet wired and it physically fired my ethernet card. My question was, can I fix a burnt PCI slot or do I have to replace the motherboard?"

    "uh, surge, a? Still FreeBSD is Better in alot of ways, for example, let me start back in 1972..."


    sigh... and this is a TRUE story, talking to some hardcore Free BSD user at college about a burnt PCI slot on my freind's motherboard. To this day he is still conviced that Linux physically burnt out some of my freind's hardware, even after the IT director admitted that there was some surges in the school network wiring... sigh

    I know this sounds REAL cheese, but "can't we just all get along?"

    --

    "`Ford, you're turning into a penguin. Stop it.'" -THHGTTG
    1. Re:sublime by jbarnett · · Score: 1

      Well, yes to Windows maybe. But I have never seen any Linux users talk bad of BSD, Solaris, IRIX or AIX. Every Linux users I meet as liked a differant Unix, open source or not, just for the fact it is something new. Something differant then the penguin is good for the soul once in awhile.

      --

      "`Ford, you're turning into a penguin. Stop it.'" -THHGTTG
  92. Re:No fricking group hugs by bvmcg · · Score: 1
    BSD isn't into the touchy-feely group hug thing that Linux babes are
    Precisely that attitude is why it misses out on a lot of good things. You make it sound as though wanting to work as part of an inclusive group is a bad thing.

    For my part, I work for a game company which has created products for Microsoft, Lego, Williams, Interplay and a few other notable players. Earlier this year I was soliciting people to create text content on updating FreeBSD's packaging to give it more shelf appeal and soliciting information and space to create a well-structured PR team.

    My staff created a tasty looking box on their own time without asking for a dime (save the artist making a 3D daemon who was putting in a LOT of hours) as I was cheerleading, working with them and "giving group hugs" as the poster put it. They were working to be part of something and enjoying the appreciation from the onset.

    While this was going on, I was met with a lot of fighting and resistance to most any kind of input, so I just told my team to "drop it. I don't want to work with these people." I care more and work better with positive group attitude. My people too. And it's hard for me to keep it exciting for my people here when people there are busy posturing and pissing on me.

    I still think FreeBSD is one of the best things that's happened to the PC, and it's my undisputed OS of choice - I'm even using it for Linux targetted programming at work. But working on it simply hasn't got the social returns that make it worth my free time, so I'll stick to being a non-contributing user.

  93. GPL vs BSD License by Scientist · · Score: 1

    The GNU Generical Public License is obviously much better then the BSD License. The reason for this is GPL forces the creator of a software package to release the feature back into the community while the BSD License lets those features be used for properitary purposes, therefore allowing those features to be hidden from the community.

    1. Re:GPL vs BSD License by Scientist · · Score: 1

      This comment could have been worded better and should have been free of spelling errors.

      Sorry.

  94. Re:The Linux Community is(was) Nicer by drwiii · · Score: 1
    The *BSD community routinely treats people who go on their channels looking for help, like they're a piece of crap
    Not unlike that jeff guy on #slashdot on irc.slashnet.org

    jeff may yawn alot, but I haven't seen him treat anyone like crap. Most people use IRC as a leisure tool, and if their daily job involves heavy computer use or even providing support, I doubt they'd want to do that on their off-hours as well.

  95. Re:Tehcnical Superiority != hype != popularity by Guy+Harris · · Score: 2
    That's why people choose the stability of BSD for their embedded projects (see the Whistle InterJet, NFR's Sniffer, Secure Computing's products, etc.) as well as high end ones (Network Appliance, et al.)

    Well, first of all, Network Appliance doesn't run BSD on their boxes (I joined the software engineering group at NetApp when there were about 7 or 8 people in the group, and I'm still there, so I know what I'm talking about here) - we use the BSD networking stack, and various BSD commands, but it took a fair bit of work with a chainsaw to fit them into our environment (which is a kernel-mode-only, single-address-space OS that would probably not be completely unfamiliar in its innards to a BSD developer, but which is very much not a BSD kernel).

    Second of all, there are also embedded boxes that use Linux, e.g. Cobalt's boxes, and, I'm sure, plenty of others.

    As for whether Linux is "flakey and not meant for real world use", there are Web sites using it, there are places (including, err, umm, Network Appliance, Inc.) where people use it on their desktops and on their compute servers (most of our compute servers are running Solaris or Digital UNIX, but there is one Linux PC, and there will probably be more over time), and so on. People seem to manage to use it in "the real world" even if it's "not meant for real world use".

  96. one little prob. by CrAlt · · Score: 1
    "The day RedHat tries to hide moddifications is the day the Free Software Foundation sues them." And fails...This is also the same day that the GPL becomes worthless. This is the US of A. It dosnt matter who is right-It matters who has the most $$$. Look at etoys..look at OJ..and im sure you could find a 1000 more cases.


    The only real thing keeping Redhat strait is that they dont have 100% of the Linux pie. That is why I hope that SuSe,Slackware,Debian, Bob's big ass Linux Disto, etc... keep up the good work and keep making Redhat do some work.


    People need to remember that Redhat's share holders didnt sign on to better the linux comunity, they signed on to make some cash. And if fucking over linux makes their stock go up 200% then they would do it with out a 2nd thought.

    --
    I have to return some videotapes...
    1. Re:one little prob. by the+eric+conspiracy · · Score: 2

      This is the US of A. It dosnt matter who is right-It matters who has the most $$$.

      A very cynical view not born out by fact. Examples:

      STAC vs. Microsoft - Microsoft loses.
      Apple Records vs. Apple Computer - Apple Computer Loses.
      Dow Corning vs. various private parties. Dow Corning now bankrupt.
      Phillip-Morris vs. various private parties - Phillip Morris loses.
      Johns-Manville vs. various private parties - Johns Manville bankrupt.
      McDonald's vs. old lady who spills coffee - McDonalds loses.
      Exxon Corp (Oil Spill) vs. various parties - Exxon loses.
      Hooker Chem vs. Love Canal residents - Hooker Chem no longer exists.
      GAF vs. Woburn MA residents. - GAF loses.
      man who invents intermittant wipers vs. Ford. Ford loses.

      A number of these cases are quite questionable as to whether the large company did anything really wrong.

      While money allows you to buy a lot of nice fancy lawyers, jurys have a heavy bias against large corporations. If you go into a lawsuit against somebody like the Free Software Foundation you are in trouble right from the beginning.

  97. Re:color is spelt COLOR not COLOUR... by atdot · · Score: 1

    Name three countries whose official language is English and which use "color". Heck, name two. There are oodles more that use "colour".
    Of course, "colour" is a perverse Gallic invasion, with no place in Latin. So even though you're in the minority countrywise, you can have philological correctness on your side.


    for that matter, name one country.

    be carefull not to show too much ignorance

    @.

  98. Only one fact. by cmc · · Score: 1

    I can accept your article as one of mostly opinion. Except the "code stealing" bit. We [FreeBSD] have very little if anything at all that can be considered "Linux code." We have the GPL math emulator, GNU binutils... but then again, things like that are GNU code, not Linux code.

    So where do you get the idea that BSD programmers steal Linux code?

  99. BSD wouldn't be as popular without Linux by Camelot · · Score: 1
    I am sure this will draw a few flames my way from *BSD advocates, but I consider BSD popular (a few million users ? Yes, that is popular to me) because of Linux, not despite Linux. Given that, I don't see *BSD folks have anything to complain about - except the fact that they're not leading the pack.

    *BSD lacks several factors that made Linux the big success that it is today. Linus, the license that can be corrupted (theoretically, at least), fragmentation.. The FreeBSD IPO (?) I heard would not have happened if there hadn't been Linux IPOs first; people are only riding the wave; *BSD is coming in the wake of Linux and getting more publicity, not less.

    Then there is the competition aspect.. *BSD is better because of Linux, and vice versa. Of course you might argue that *BSD would have more developers if it weren't for Linux, but that can't be proved.

    I have great respect for *BSD - but Linux deserves respect, too. It does not deserve to bashed simply because it's more popular.

    As a phenomenon, Linux is unique. *BSD would not have made it.

    1. Re:BSD wouldn't be as popular without Linux by crimsun · · Score: 1

      Heh heh, I believe you have it reversed.

      *BSD has been quietly serving the Internet community at large for much longer than any distribution of Linux has been visible. Walnut Creek ftp, the distributing hub of several Linux distributions, has been dishing out gigs for years, and ISPs have used *BSD since... the inception of ISPs. Chat networks have preferred *BSD servers for their stability and security.

      This isn't to downplay Linux, just to say that the ftp from which you downloaded a Linux distribution was probably running *BSD.

      How then is it possible to say that *BSD wouldn't be as popular without Linux? =P

    2. Re:BSD wouldn't be as popular without Linux by Camelot · · Score: 1
      It is true that I might not have given *BSD as much recognition as it would have deserved, and, yeah, of course Linux owes a lot to *BSD and Mother Unix in general - but that is not the issue.

      Some *BSD people feel that *BSD would be right where Linux is now, had Linux never existed, and this is what I disagree with (for reasons that I outlined in my previous post). *BSD (and other unices) have been silently running the world - and that is what they would still be doing, had Linux never existed. Microsoft would be free to reign in the desktop world, eating away the UNIX dominance in the server realm.

      As you can see, this has absolutely nothing to do with what *BSD had done before Linux entered the scene, and everything to do with what *BSD might have done if Linux hadn't done that. This is, of course, pure speculation.. but you should ask yourself: Would a BSD distribution be having billion-dollar IPOs ? I think not.

  100. Personal reason for not liking it: command options by Clonezone · · Score: 1
    My Dad did/does work for Bell Labs. I grew up using SysV, so, I got used to the SysV versions of the standard commands. I feel more comfortable with "ps -ef" than "ps -aux".

    --

    --

    He's seeing monsters. He's losing his mind and he feels it going.

  101. Re:color is spelt COLOR not COLOUR... by atdot · · Score: 1

    OK, good point. Name one country whose official language is English and uses "colour"

    hehehehe

    there may be one out there, but I cannot think of it.

    @.

  102. Blame AT&T by David+Muir+Sharnoff · · Score: 1

    Linux simply got a head start while the BSD camp was distracted by the AT&T lawsuit.

    *BSD is growing just as fast as Linux. It's just a couple of years behind.

    I don't know what the long-term picture looks like. Either operating system could falter. Mostly growth of Linux is good for *BSD and vice versa.

    1. Re:Blame AT&T by David+Muir+Sharnoff · · Score: 1

      Sorry, perhaps I should have been more clear. I was talking solely of market share and mind share.

      As for as technology goes, I think FreeBSD solves my problems the best. That said, I did my competative analysis nearly five years ago. I've been very happy with FreeBSD ever since and thus I have not done a detailed comparision since.

      Nothing I've heard from other people in the interm has made me think I would get a different answer now. I run an ISP (Idiom) and my analysis reflects my requirements. Here's how I think things stack up now...

      FreeBSD: focus on performance and stability (exactly what I want!). Note that stability requires security.

      Linux: focus on features, too many players and too much energy to be really stable. Lots of fun and what I would reccomend for most new unix users.

      NetBSD: focus on doing things right. Glad someone is, but I'll use something else until they finish :-)

      OpenBSD: focus on security and integration of encryption. Mostly follows NetBSD development.


  103. Re:color is spelt COLOR not COLOUR... by Daevcollie · · Score: 1

    Canada does and I think the U.K. does too.

  104. Re:color is spelt COLOR not COLOUR... by paul.dunne · · Score: 1

    How about ENGLAND?! sheessh...

  105. Re:what are you talking about? by Guy+Harris · · Score: 2
    After a fresh install of FreeBSD 3.4 I could mount my dos and ntfs partitions right away.

    I think he's trying to imply that they may have adopted it now, but rejected it originally.

    The CVS tree seems to imply that it may have been in FreeBSD at least as far back as 2.0, however; the comment from the initial checkin, with a date of Mon Sep 19 15:41:43 1994 UTC, says "Obtained from: NetBSD", so NetBSD may have had it even longer.

  106. Hmmm. Should I give FreeBSD a Try??? by BweeDwee · · Score: 1

    This article is oddly timely for me since my subconscience lately has been bubbling up little whispers to ditch Linux and move over to FreeBSD. Is this irrational on my part? I love Linux, don't I? Ok, Ok, I know AM worried about all the recent IPOs and Linux certification and I do have this irrational fear that the suits aren't far behind and when the suits get involved the inevitable ruination waits in the wings. But to ditch something that's provided so much intellectual pleasure? Plus there's a whole new cast of characters in FreeBSD land - who are they? Are they friendly? Are they open to newbies asking a bunch of dumb questions?

    Aaahhhh! Maybe "those guys in the basement" as Steven King calls them aren't done figuring it out yet. I guess I'll wait a little longer.

  107. Re:Linux=Newbies; BSD=Robust by Null_Packet · · Score: 1

    Linux is a great starting point for many, many new people in the Unix world. With that said, almost every single person I know that uses *BSD is someone who came from linux, not from another OS. OpenBSD for example comes locked-down out of the box. The ports tree in BSD lets you install anything after that. A good comparison is between a Redhat 6.1 install and an OpenBSD 2.6 install. Redhat's GUI frustrated me to no end, and there was no way to break out of it that I could see. Redhat does not have readily-identifiable links to it's docs from their main page- Open and FreeBSD do. Open and Free also use man pages- a central reference for any command in BSD. The 2.6 install was a little different, but I did not epxect it to be the same- so I printed out the install.i386 html doc- I never had to ask a fellow user a question when I installed Open 2.6. Let's Recap:

    Linux Pros:
    Easy install (for even the lamers)
    Lots of Software
    Lots of Documentation
    Linux Cons:
    >Not everyone wants or needs a GUI install.
    >Messy dependencies, especially with RPM's
    >HOWTO's written by my baby brother- seemily never profread

    BSD Pros:
    >Centralized Documentation
    >Ports Tree (ports.tar.gz rocks!) for *easy* installs of anything for BSD
    >Lean,mean installs- FTP installs from one floppy was never easier!

    BSD Cons:
    >New users don't like to read, especially docs
    >Linux users are used to gurus massaging them through everything- this is not the case with Open or Free
    >Gnome hasn't been ported to BSD (hooray!) due to problems with security and Gnome. (not sure if this is a con)

    Null_Packet


  108. Being at the right place at the right time by SerpentMage · · Score: 1

    I think the question of why Linux is more popular than BSD should not be over-emphasized. You could argue this point over that point.

    But it really is being at the right place at the right time. Linus is a popular person who has a good personality. People LIKE HIM...

    It is like asking why Microsoft is more popular than Apple or UNIX. Microsoft was at the right place at the right time.

    --

    "You can't make a race horse of a pig"
    "No," said Samuel, "but you can make very fast pig"
  109. I was there by Mr.+Protocol · · Score: 2

    No one seems to have mentioned that this article is shot full of errors. The first one's in the first paragraph: BSD stands for Berkeley Software Distribution. The company BSDI changed the D to Design, for their company name only.

    Bill Joy didn't write free UNIX. He wrote a lot of code, but Sam Leffler, Kirk McKusick, Keith Bostic et al. are not exactly slouches either. Not to mention the whole effort was overseen on a continuing basis by a design board of academics chosen by DARPA. You like the socket interface? Thank DARPA's board. They pounded Bill Joy really hard (probably for the first time in his career) until he "got it" that most of the brilliant things CSRG came up with originally had been tried and rejected by them severally at their own institutions. The Berkeley socket mechanism was the result of several go-rounds of this sort of thing.

    Here's another. "When Berkeley stopped funding the project..." Hoo-hah. Berkeley never funded the project. DARPA did. They did it because they got tired of paying all of their research institutions in parallel just to support their computing environments: they wanted a stable base of Internet code that would be used by everybody, and they figured they'd pay for it just until commercial versions became viable. When the Internet took off the funding stopped. CSRG hung on for a year or two looking for other funding, didn't find any, and folded. There was a tag end of work there, by the way: 30,000 lines of OSI networking code (think X.25 & Co.) was inserted. I think it's probably gone by now, but it left its mark in the data structures, at least.

    Then there's that amazing quotation: "In terms of sophistication, the BSD operating system is better than Linux. What flame-bait. This was definitely true in earlier days, but these days it's probably a push, for most applications. I believe that BSD may be better for truly huge server installations, but in comparison with the total installed base, this isn't a very high percentage.

    Looking back, I think the history of Linux and BSD can be compared with current theories of the early universe. Very small things result in huge differences later on. Frankly, I don't think the preponderance of Linux over BSD has squat to do with licenses. The BSD system was designed in an encumbered environment, with everyone under license. It took two years in court to get out from under the AT&T license, which was the exact opposite of free software ("You can exchange software freely! ...so long as the other guy has this license too."). Those two years were all it took to give Linux the edge. Linux was at that time clearly less stable than BSD, which had had fifteen years to get the kinks out. But Linux was freely available and BSD wasn't. That made all the difference. I daresay that in those days the only contribution of the GPL (and it was a minimal contribution) was negative. Several largish institutions (including, as I recall, Purdue University) wouldn't let GPL software onto their campuses because their lawyers got wind of the GPL, read it, said, "We have no idea what this would really mean in court. Don't you dare go there." And, let's face it, while you can't have a software revolution without thousands of individuals pushing things at a grass-roots level, that isn't enough. Big institutions have to pick it up and support it, too, or the revolution doesn't happen. The GPL has, arguably, been of assistance in preventing some large corporations from forking private versions of Linux, but it has been of no assistance in convincing large institutions to adopt the software in the first place. Quite the reverse.

    I grew up in a BSD world. (Truth in advertising: I was on that DARPA board.) I recommend FreeBSD for really large server applications. For smaller outfits, and for desktops, I recommend Linux enthusiastically. Not for the GPL, on which I'm neutral (now THAT makes me a rarity, I think!), but for the ease of acquisition, the base of available software, and the size of the support community. (My understanding is that ease of installation for many of the Linux distributions has a ways to go yet, at least compared to FreeBSD.)

    Those actively involved in development know that GPL or not, Linux and the BSD movement trade software back and forth all the time, freely, openly, and in an atmosphere of mutual support. The bigots for one side or the other are, in the main, out of the loop. I hope it stays that way.

    1. Re:I was there by davet · · Score: 1

      Well said, Sir!

      GPL or BSDL, developers worthy of the title will continue to exchange ideas, if not source code. There is at least one case where two projects with similar goals but different licenses (GPL and BSDish) do work together. Instead of beating up on each other, they work together and both projects are richer for it.

      Lets just keep the rabid advocates on either side occupied beating up on each other, not getting in the way of those of us who want to get something done.

  110. Re:FreeBSD vs. Linux stability. by Dj · · Score: 1

    Um, is this in the FreeBSD code though? All the message mentions is that it was discussed on the FreeBSD mailing list. By that token Linux must be unstable as it was discussed on the Linux kernel lists.

    Or is this just Linux Nu-FUD(TM).

    --
    "You know you want me baby!" - Crow T Robot
  111. Re:The Linux Community is(was) Nicer by treat · · Score: 1
    The *BSD community routinely treats people who go on their channels looking for help, like they're a piece of crap

    I frequent an IRC channel that used to get a lot of people joining and asking questions (we had to set a channel key because of this). They would not usually be treated with kindness, though there were plenty of exceptions to that. They'd frequently get at least a pointer to the answer to their question, even if it was in the kick message. I've seen identical behavior on other channels, e.g. #linux.

    Here's why. First, they're not help channels. The people that are there are not trying to volunteer their time to answer anyone's questions. That's not usually fun.

    The clueless newbies answering questions is constant. Multiple times per hour, perhaps. How do constant stupid questions make you react?

    Nobody in the channel knows these people, they come out of nowhere asking for help. They ask questions that are answered in the documentation, or that a search engine could have easily found the answer to. They ask confusing or vague questions. They ask questions that show they don't have basic fundamental knowledge that nobody wants to explain to them. And these people treat the people they're asking like total crap. They want us to believe that our time is worth so little that it's better that we answer their question out of kindness, rather than them going out on their own and learning it.

    When not treated with perfect kindness, people who ask questions sometimes become incredibly angry. They make threats, try DoS attacks, etc. It gets very annoying.

    And to top it all off, not only do the clueless help-me-please babies *act* like the people in every channel they come to have a responsibility to help them, but there's people like you who almost come out and say it.

    If the people in the channel had to deal with stupid questions all day, the people begging for help on IRC make a fabulous target for the response that we've been longing to give to someone all day. This should be obvious pretty quickly, therefore if you continue to run around on IRC thinking that every channel #x is "help for newbies on x", you're hassling people that you know are in a bad mood, and that you know don't have to take any crap from you at all.

  112. The problem is definitely the BSD license... by mjuarez · · Score: 1

    Yes, Linux was the right Unix in the right place at the right time, and it took away BSD's chance to rule the world. However, a lot of people I know who work or tinker around in Linux, myself included, would have already tried out BSD if it weren't so adamant about two things: First, you can do whatever you want with the source code, including making it closed-source and selling it off, and second, that requirement to mention the University of California at Berkeley to everything you do and later redistribute. First off, one likes to give credit where credit is due, and I'd say that 99% of GPL software gives credit to the original authors somewhere in the source code, even though they are not forced to. However, forcing people to put it in is not liked by the developers, and so, they favor Linux, besides that fact that, by now, Linux is plenty more popular.

    And second, it's a lot more "cool" belonging to a community where all involved cooperate and share their code, instead of hiding it and trying to sell it to you later. It's more of a sense of belonging to a truly free community, one that can't be tarnished by people taking all that software and selling it repackaged as closed-source.

    I think that, mostly, describes my feelings on the subject. Just my $0.02...

    1. Re:The problem is definitely the BSD license... by Graymalkin · · Score: 2

      That is just bullshit, who decides not to use BSD because they have to add a comment about the original authors.

      --
      I'm a loner Dottie, a Rebel.
  113. NetBSD, Linux, and Chronology by niemidc · · Score: 1

    On chronology: I recall NetBSD being available by early 1993; in fact I used it prior to using Linux. Minix and 386BSD were the real pioneers in this genre and date back long before the lawsuit with AT&T was resolved. Minix wasn't quite open source and was very limited; while 386BSD degenerated into a series of patches upon patches, and after a while full releases came out late to never. A lot of its users simply gave up and switched to NetBSD or Linux.

    By late 1993 Linux was way ahead of NetBSD in user base (perhaps 100,000 at that time). This is mostly because NetBSD was not aimed at general technical home users with PCs like Linux was, it was aimed at UNIX people. As a result:

    1) Linux was much earlier at taking advantage of PC hardware, without necessarily trying to make it look like real UNIX workstations. It arguably still does a better job of this, even compared to FreeBSD. This isn't necessarily an advantage if you are already familiar with UNIX workstations, but if you know PCs it is less confusing.

    2) Linux wasn't really UNIX. Linux developers haven't been afraid to add features or implementations that are different from standard UNIX design as long as the standard UNIX semantics continue to work. This may sound like a disadvantage, but it enabled Linux to gain a lot of users, and some truly brilliant developers, from the DOS/Windows world. By several estimates over half of Linux users had never used any kind of UNIX before. These DOS/Windows people added features and documentation that made future DOS/Windows people more comfortable, and it became self-perpetuating.

    3) Linux (in SLS, and in late 1993 Slackware) was much earlier in having distributions that could be installed fairly easily on typical cheap PC hardware. True, they were horrid by today's standards, but the NetBSD installation of the time was far, far harder. This locked in a fair number of users back in the 1993-1994 timeframe, before FreeBSD provided a BSD installation that was more or less as easy as those for Linux. Presumably NetBSD is much easier now; but back then hardly anyone who didn't already know UNIX quite well could have installed it. This is not intended as a criticism -- NetBSD simply did not aspire to be a mass-market OS at the time, and as a result, it wasn't.

    True, Linux networking wasn't really stable at all back in 1993, but for home use that didn't matter much yet -- in fact PPP was not even widely available at ISPs until about a year later, and by then Linux had workable support for it.

  114. Re:Only 10 million Linux users by MinusOne · · Score: 1

    > Linux ranks so far behind MacOS and Windows in installed base it's laughable. They are about even with OS/2...maybe...

    Perhaps you could bother to provide some evidence for this opinion? I have no clue how many Linux users there actually are, but I could pick numbers out of the air just as easily as you or anyone else. Until I find some solid number backed by reasonable research, I'll keep my mouth shut. I *believe* the number must be more than 10 million, but I can't back it up any more than any else can their guess.

  115. Re:High Volume Web Sites by the+eric+conspiracy · · Score: 1

    Really man, four sites. Is that all you could come up with. A couple no name sites. No mp3.com or Yahoo, or Netcraft.com for that matter..

    Really. All I needed was one to prove my point. The man said NO high volume Linux web sites. Do you think I am going to sit here and do a flippin' web survey and list all of them? I have at least part of a life. As far as being no name, I think you look pretty foolish claiming Netcraft is a bigger name than any of the ones I listed.

    Novell, NT, SCO and many other Operating systems can as well.

    So what? I never said they couldn't.

    just look at the Caldera vs MS suit...

    Yeah, just look at it. The judge recently threw out all of Microsoft's efforts to prevent a trial. Last I heard the jury convenes in early February.

  116. Re:that's great when the manuals work! by Master+of+Kode+Fu · · Score: 1

    R'ing the F'ing M's is not always enough when the manuals are often quickly thrown together, incomplete and poorly-written. In any revolution, either political or software,everyone wants to be a general and no one wants latrine duty. Guess which category doc writing falls under.

  117. Re:Personal reason for not liking it: command opti by TeChYMaN · · Score: 1

    FreeBSD does not complain about the hyphen. Linux, being the pain it is, does.

  118. Re:Linux=Newbies; BSD=Robust by reg · · Score: 1

    GNOME not ported?

    cd /usr/ports/x11/gnome && make install clean; some day...

    -Jeremy

  119. Re:FreeBSD vs. Linux stability. by Guy+Harris · · Score: 3
    See this URL : [ http://kt.linuxcare.com/kt19991220_47. html#1 ]for one such example..

    Oh, you mean the discussion that includes

    Erich Boleyn, an Architect in an IA32 development group at Intel, also replied to Linus, pointing out a possible misconception in his proposed exploit...

    ...

    There was a long clarification discussion, resulting in a complete turnaround by Linus

    i.e., that Linux later accepted the change:

    "Everybody has convinced me that yes, the Intel ordering rules _are_ strong enough that all of this really is legal, and that's what I wanted.

    ...

    Thanks, guys, we'll be that much faster due to this.."

    As for "others can be found elsewhere", please give references - perhaps they're also not bad implementations.

  120. um...how about the GPL? by pope+nihil · · Score: 1

    proprietary software for linux yes, but proprietary changes to the linux kernel would be illegal. unlike *BSD.

  121. GNOME on BSD by Lazaru5 · · Score: 1


    Hmm...yes..I supposed technically there's not GNOME "port" and that's because "./configure && make install" works just fine.

    To ease this though, GNOME *IS* in the Ports Collection (Note 'Port' the noun != 'port' the verb) so a `cd /usr/ports/x11/gnome && make install` will fetch and build GNOME with all the necessary dependancies.

    Please post responsibly. Don't spread misinformation.

    --

    --
    My comments and opinions completely reflect those of anyone and anything I am remotely associated with.
  122. Re:color is spelt COLOR not COLOUR... by higuita · · Score: 1

    ooohhh no.... another one i'm sick of this english speaking people that dont want to understand that other speak/write diferent from then... try to learn 2 other languages (not english related ) and you will be more open mind about this you are not the center of the world, you now!! grow up

    --
    Higuita
  123. Divided we stand. by cnflctd · · Score: 1

    Maybe Linux is more widespread because Linus isn't responsible for the whole OS? He just puts up a new kernel every few weeks, and lets others handle the packaging. But the BSDs do it all. And because, say, FreeBSD is presented as a single production, would-be distro-makers lack motivation to brew their own versions, ala RHAT, Corel, Mandrake, etc. Kind of like Apple's originally closed architecture, and IBMs quickie off-the-shelf, but ultimately more popular PC.

    Maybe that's why I like Debian. Every little .deb is maintained by dedicated volunteer(s), while RHAT is responsible for the whole ball of wax, just like FreeBSD is. Maybe the Linux motto should be "let's divide ourselves, and conquor."

    (Boy, this is written badly. instead of giving up, I think I'll post anonymously.)

    --
    I'm cool like a fool in a swimming p-p-pfft-pool
  124. Re:The Linux Community is(was) Nicer by treat · · Score: 1
    And in their zeal they attack even people who come in and who have read all the manuals and who have detailed descriptions of the errors they're encountering.

    Yes, because it's still not a help channel, and because these people still have no obligation to help you, no matter how good your question is. Those people don't want to help you, and you should let them be.

    1) The linux community has fraudulently swindled its way into an award for technical support.

    I can see your point, I suppose. Absolutely every single time I have asked a question in the comp.os.linux.* newsgroups, I have received no help. It's probably because I only ask for help there as a last resort, so they're always fairly difficult problems. A few people will try to help, but they'll suggest things that are completely wrong, or I've already said did not work. I always go through great effort to make sure my questions are clear, concise, and include all pertinent information.

    But I have just read those groups also, and helped people in them, and people asking simple questions, or difficult questions that other people have already had to solve, do get very good help. If you ask something that's a little unusual, all the people that are intelligent enough to answer quickly aren't wasting their time with you. And all the people that could solve it with some effort aren't going to bother unless it's an interesting problem.

    The support you can get for Linux on comp.os.linux.* and mailing lists blows away any commercial Unix support I've dealt with. Consider that a scathing indictment of commercial OS support.

  125. 2,000,000 users is some kind of failure? by SurfsUp · · Score: 2

    2,000,000 is an awfully big number of users. In no sense does it represent any kind of failure.

    Frankly I'm stunned by the swift rise of FreeBSD - I thought nothing would ever touch the success of the Linux movement. Being a relatively new Linux convert I'm willing to admit that I suffered from a kind of parochialism with respect to FreeBSD - when I heard news of it I kind of wanted not to hear it because, hey, I've already found the answer and it's Linux, right?

    I think I'm probably not alone in that: many of you probably have the same feelings (you know who you are:) Recently though my attitude towards the BSDs has changed from a kind of jealousy to admiration and respect. A lot of that has been due to the sympathetic and interesting coverage on Slashdot. A larger part of it is the obvious truth that there's a lot to respect technically in the BSD's - look at the security audits just for one thing. I now see the BSD's as another tool in the toolbox - it's what I'll do when I need a slimmer, tighter box that doesn't necessarily have to get all dressed up to kill.

    Now, I don't seriously believe that the BSD's will ever pass Linux in popularity, for reasons that are set out nicely in your article and are beaten to death elsewhere in this thread. But neither do I believe that there is room in this world for only one open OS, especially when they are interoperable. The BSD's will help us achieve world domination. They are but one more division in the open source army.

    --
    Life's a bitch but somebody's gotta do it.
  126. Yea, verrily by autechre · · Score: 1

    I've been using ext3 (journaling ext2, still considered quite experimental) for a month now with no problems. I've been using Mozilla for even longer than that, so I guess I'm just that sort of guy :)

    In my eyes, BSD seems like the "safe" OS for servers, though this can also translate into it being the "boring" OS for people like me; I take backups and I want the new features now...if the developer says they work for him, OK. Everything always seems to work for me...perhaps it's the "Magic Ass" theory at work...


    --
    WMBC freeform/independent online radio.
  127. Re:what are you talking about? by harlows_monkeys · · Score: 1
    Furthermore, even after FreeBSD got DOS filesystem support, it was only primary partitions. Extended partitions took quite a bit longer to come in.

    From the start, Linux did a better job of fitting in with whatever OS might already be on your PC, and did a better job of fitting in with existing hardware.

    There's no real polite way to put this, so I'll just be blunt: a few years ago, the FreeBSD were a lot more snotty than the Linux people when it came to cheap hardware. If you were the kind of person who thought that spending $350 for a SCSI CD-ROM was silly when an IDE CD-ROM was only $100 because you only use the thing for installations, then FreeBSD was not the system for you.

    The FreeBSD people have gotten a lot better in the last few years, and I believe they now try to support cheap commodity hardware well.

  128. Re:Not in my experience by Magnanimous+Cowturd · · Score: 1

    I tried it - once. After much effort to get it to work on my hardware I was rewarded with an interesting but wholly unintuitive GUI.
    Apps? mini-apps? ANYTHING I could start up that was going to let me know I was in for an experience of a lifetime? Nope. Just a broken Internet browser.
    I had to switch operating systems to hunt around for anything I might download that would show off this wonderous system. Everything remotely interesting had a price tag on it.
    I'm sorry, but even Windows comes with a couple of gizmos to click on.
    Thanks, but no thanks, I'll stick with GNU/Linux.

    --
    The Supreme Art of War Is To Make the Enemy Look Foolish --- Li Atwater
  129. Why this infighting? by Red+Pointy+Tail · · Score: 1

    When you are threatened, it makes sense to close ranks with your allies and set up the fort.

    So why this infighting? Windows NT caught up in the enterprise share because IBM, HP, Sun, BSD are too busy trying to compete with each other (or selling their propietary hardware) to bother with improvement or innovation. Starting Linux/BSD camps wouldn't to help.

    Don't flame me, but I believe Win2000 represents a genuine threat to acceptability of Unix. Just because WinNT is crap now does not mean it will always be crap in the future - never underestimate M$ ability to improve and most especially to market and brainwash MIS managers. Also Win2000 got quite an impressive bit on the new features (rather if it really works still is yet to be seen).

    Personally, I would just like to see our most talented guys putting their effort to Linux all the way and, sorry to say, screw BSD :)

  130. Tell em George by datazone · · Score: 1

    Its all penis envy if you ask me.
    Its like that question you hear people ask: "do you think you are better than me?"
    if you say "yes" they feel offended, if you say "no" you acknowledge that you are as good or worse than the person. So, you damned if you do, and damned if you don't.

    Like the man said, "use what works best for YOU"

    --
    Its spelt "L-I-N-U-X", but pronunced as "Free Beer"
  131. Re:FreeBSD vs. Linux stability. by Guy+Harris · · Score: 2
    Aren't you forgetting an important part? The part at the end where the source code is shown, that Linus didn't actually make the change, just made a comment saying that it would be nice if he could.

    That part showed up after that issue of KT came out; I don't know whether it showed up after I checked it earlier today or not (I'd assumed that issues of KT are invariant after publication, and I saw that issue before the note was added).

    Some stuff in the FreeBSD archive indicates that they may have decided that the unlock optimization couldn't be done that way, either, although I'd have to plow through a ton of -current code and, perhaps, CVS logs to see exactly what they did do - see this message, for example, and this message.

    (And, the hypothesis in, as I remember, one of the linux-kernel messages nonwithstanding, the FreeBSD folk do have P6 machines - some of Matt's timing experiments were, as I remember, done on a Pentium III.)

    The comment in the code also suggests that it might be useful to have a way of building a kernel without the lock, if it truly can be removed on all but the early PPro's to which the comment refers.

  132. Way to avoid the issue. by Wakko+Warner · · Score: 1
    What about the mailinglist then? Since the core FreeBSD developers frequently post to the list, I'd say it's a pretty good barometer of the camp as a whole.

    I don't personally like what I've seen of it, either.

    - A.P.
    --


    "One World, one Web, one Program" - Microsoft promotional ad

    --
    "Remember when the U.S. had a drug problem, and then we declared a War On Drugs, and now you can't buy drugs anymore?"
  133. There will probably never be one by scabpicker · · Score: 1

    When an os is based on bsd, due to the license, the person releasing the os is allowed to call that program their own. Well, if I were going to try to make my buisiness have a billion dollar ipo, I would call my os something else, not BSD. This would make it seem that I had something that others did not have, and make my business have a percieved edge against the competition. I may be completely incorrect, but I believe I have heard that Solaris and BSD are related in the past somewhere this way (maybe through Bill Joy). Sun is not a billion dollar ipo company, but I wouldn't sniff at their value.

    --
    _this is not a signature_
  134. When you're out of sticking points... by Wakko+Warner · · Score: 1
    ...point out spelling, punctuation, or capitalization errors. Isn't that one of the Usenet rules?

    - A.P.
    --


    "One World, one Web, one Program" - Microsoft promotional ad

    --
    "Remember when the U.S. had a drug problem, and then we declared a War On Drugs, and now you can't buy drugs anymore?"
  135. Request for Slashdot Poll by mvw · · Score: 2
    Who really believes that the success of Linux is due to the GPL? I am not. There is no reason to believe that his kernel project would have grown much different, if he used a BSD/XFree86 style license.

    I would really like to see such a Slashdot poll

    I bought BSD/Linux because

    1. it is cool
    2. my friends got it
    3. it runs stable
    4. it runs stable and comes with source
    5. it runs stable and comes with source under GPL
    6. it runs stable and comes with source under BSD license
    7. Hemos uses it

    My personal guess is that only those who actually program might rank the type of open source license so high that it influenced their decision. And these are a minority, I believe, maybe ranking in the ten thousands but not in the millions.

    1. Re:Request for Slashdot Poll by slim · · Score: 2

      I'd say the GPL has made a lot of difference to the way Linux is treated in the commercial world.

      The world is littered with non-free forks of free BSDs -- if hte original had been GPL'd, we'd all have got to share those changes.

      For example -- I remember a BSD based Internet gateway for novell networks. That will be a kernel hack, but the BSD world did not get to see the source.

      A couple of recent Linux examples are the Tivo kernel changes and the port to IBM System 390. It's unlikely that either of those sets of code would have been released as source if the GPL didn't force it.

      That said, we're seeing a lot of Apache code gifted from commerce (although there's a lot of proprietary stuff I'd also like to see freed). I'd say that Linux has proved to many large companies that freeing the source is not necessarily an act of selflessness. Now they've been forced to try it, they can go on to free source even when the licence says they don't have to.
      --

  136. Re:Disclosed Source by Tony-A · · Score: 1

    You _can_ find out what it does, rather than trying to guess from poorly written specs.
    Not as good as BSD/GPL licensed source, but _much_ better than nothing.

  137. Re:Not in my experience by Magnanimous+Cowturd · · Score: 1

    Power and elegance? Where? BeOS gave me no indication it had anything to offer. My point was show it to me! I haven't time to waste on an operating system that forces me to beat "power and elegance" out of it.

    --
    The Supreme Art of War Is To Make the Enemy Look Foolish --- Li Atwater
  138. HE! Moderators! by Eon78 · · Score: 1

    Why isn't this whole damn flamebait tree set to -1? OR -99999 for that matter?

  139. Re:Linux=Newbies; BSD=Robust by gaj · · Score: 1

    > Linux is a great starting point for many, many new people in the Unix

    Agreed.

    > world. With that said, almost every single person I know that uses
    > *BSD is someone who came from linux, not from another OS. OpenBSD for
    > example comes locked-down out of the box. The ports tree in BSD lets

    Which is a *good* thing. Closest thing to this I've used in the Linux
    world is a bone stock Slackware, tho many feel Debian is also reasonable.
    RedHat, tho a very nice distro, need not apply here!

    > you install anything after that. A good comparison is between a Redhat
    > 6.1 install and an OpenBSD 2.6 install. Redhat's GUI frustrated me to
    > no end, and there was no way to break out of it that I could see.

    Um...you mean other than reading the clearly described choices on the
    install boot screen and choosing the non-GUI install?

    > Redhat does not have readily-identifiable links to it's docs from
    > their main page- Open and FreeBSD do. Open and Free also use man

    Um...other than the section titled "Linux Documentation" with links to
    LDP, Redhat manuals, etc.? Did you ever even *go* to their site?

    > pages- a central reference for any command in BSD. The 2.6 install was

    Um...last I checked (just now) so does Linux. Have you every actually run
    Linux? We also have the LDP and a well defined place to put app specific
    docs (/usr/doc). Works for me.

    > a little different, but I did not epxect it to be the same- so I printed
    > out the install.i386 html doc- I never had to ask a fellow user a
    > question when I installed Open 2.6. Let's Recap:

    > Linux Pros:
    > Easy install (for even the lamers)

    What is the point of the parenthetical there?

    > Lots of Software
    > Lots of Documentation
    > Linux Cons:
    > >Not everyone wants or needs a GUI install.

    Which is why many (most?) of us don't use 'em. Get your facts straight.

    > >Messy dependencies, especially with RPM's

    Or usefull ones, depending upon your perspective. For a home or small
    office user deps can be a godsend. I personally run Slack for the most
    part, and compile much of my own software, so it's pretty much a no
    issue for me. This point can be seen as either pro or con...thus there
    are choices ether way...the only choice that gets *really* messy is "both".

    > >HOWTO's written by my baby brother- seemily never profread

    Pot. Kettle. Black. Is any of this ringing a bell?

    > BSD Pros:
    > >Centralized Documentation

    Um... so man pages and /usr/doc doesn't count?

    > >Ports Tree (ports.tar.gz rocks!) for *easy* installs of anything for BSD

    This does work well. But most Linux distros have pretty damn easy package
    install tools as well. (RPM, apt, installpkg/upgradepkg)

    > >Lean,mean installs- FTP installs from one floppy was never easier!

    Um...deb comes damn close, and Slack can as well. Hell, even the much
    maligned Redhat can do a two floppy FTP install.

    So what. CD install is usually easier & faster.


    > BSD Cons:
    > >New users don't like to read, especially docs

    Looks like that is a con for a certain BSD user trying Linux anyway.
    Sheesh. *Most* people are stupid. It's a fact of life. This is a problem
    for anything more complicated than dialing a phone. Sucks to be them.

    Since this is the case, why not profit from making a no-brainer install
    for those to lame to even read the screen messages? Doesn't hurt those of
    us who don't need it.

    > >Linux users are used to gurus massaging them through everything- this is
    > not the case with Open or Free

    Well...some BSDers are happy to give help when asked, and some Linuxers
    are to lame or scared to admit they don't know it all to help. Works both
    ways. However, painting "Linux user" with such a broad brush is stupid.
    There are many more newbies running Linux than BSD. Comes with the 10+ times
    larger user base...even with the same percentage of newbies Linux would have
    around 10x more of 'em. "I canna' change the laws of physics, capn'" Er...
    make that arithmatic.


    > >Gnome hasn't been ported to BSD (hooray!) due to problems with
    > security and Gnome. (not sure if this is a con)

    Wa? What stops you from compiling it for BSD? Do your research, man. At least
    have enough facts straight to *appear* to know what you are talking about.

    --
    If your map and the terrain differ,
    trust the terrain.

  140. Re:Linux=Newbies; BSD=Robust by gaj · · Score: 1

    Wasn't being disingenuous. I don't see what the problem with seeking appropriate docs in a standard place is.

    man works on Linux for basic stuff and much less than basic stuff. I'd love to see better man page coverage than there is...I'll readily admit that Linux man page support is less than it should be.

    Your attempts to "define" what a standard centralized location is is silly. For Linux, /usr/doc is the location for LDP and non-man page docs. Would I like the non-LDP stuff in man pages instead? Of course. And most of it is.

    As for the "not" examples...I'll grant netscape. I don't use it for docs. In the rare occasion that the docs I need are in HTML I use lynx. But I digress.

    I fail to see how seeking out and reading the READMEs is a bad thing. I also fail to see how find | less is any less standard than man. man is just a fancy-schmancy locate | groff | less anyway. A *nice* fancy-schmancy locate | groff | less, mind you.

    As for emacs, bleah. I, and more importantly my hands, prefer vi. Emacs is also not part of the standard install of some Linux distros. What does that have to do with centralised docs?


    --
    If your map and the terrain differ,
    trust the terrain.

  141. BSD? by Millennium · · Score: 2

    As I see it, there are a few reasons...

    1) PR. Not that BSD has bad PR. It just doesn't get as much of it as Linux does. Most people have at least heard of Linux, but you don't hear about BSD in the media very often. You can't use what you don't know exists.

    2) The license. Say what you will, but the non-quid-pro-quo has a lot of disadvantages, not the least of which is that it discourages development by independent authors. Look at it this way: a commercial company can do whatever it wants with BSD-licensed software, make it proprietary, and make a ton of money off the stuff (witness Solaris). Corporations have nothing to fear from BSD, the way they do GPL. An independent author could theoretically do this, but it's not practical; one person simply doesn't have the marketing power of a corporation and thus isn't going to be able to profit. Therefore, the independent author has no real choice but to keep his code free and Open-Source. This tips the balance of power, and means that independent authors usually end up working, in effect, as unpaid coders for the companies that leech off of BSD's work.

    3) Fragmentation. The fragmentation of BSD really isn't that bad. But it is there; you have three major versions (FreeBSD, NetBSD, and OpenBSD) and a few others (Darwin could, in a way, be considered one, though it's hardly a major variant at this point in time). Is this a Bad Thing? No. It's not good, but it's not bad. But it does scare most bosses. It scares them enough so that it doesn't take much extra FUD to sway their decisions (unless the bosses know what they're talking about, in which case it takes considerably more effort).

    Is BSD a bad system? Hardly; I don't have very much experience with BSD but I like what I've seen so far (though I think I'll stick with Linux all the same). But it does have a few issues. Linux does too; don't get me wrong, no OS is perfect, and they both have some way to go. It just happens that, for now, Linux is farther ahead. That might change, or it might not. Either way, it keeps things from being dull.

  142. I prefer Linux to ???BSD for historical reasons by dltaylor · · Score: 1

    Way back in the old days, I developed an antipathy to BSD because Berkeley insisted on charging
    license fees; I felt that we (in California, at least) had funded the development of the
    kernel and utilities and should be allowed free copies (media cost only), whether for personal
    or business use.

    Now that there are free versions, I may make use of BSD, but, until I find something that Linux
    won't do for me, I see no reason to add another OS to the mix (mostly Linux, one Amiga) that I run
    at home. For my professional use, Linux has broader embedded processor support. What is
    sad is that Linux' popularity has slightly opened the door for corporate use, but those %$*$#
    that "approve" technical decisions now have two names that they can remember (M$ and Linux);
    getting another name into that mindspace is hard.

  143. Cool! by _Sprocket_ · · Score: 2
    I saw freebsd at compusa the other day...
    Cool!

    While I really enjoy using Linux and have no inclination to "jump" to BSD myself... I'm also of the opinion that BSD deserves some attention. Great to see it hit the shelves too.

  144. In short, you're proud of lying. by Brett+Glass · · Score: 1
    Incidently, BSD advocates, it was Brent Glass

    The name's Brett Glass, thank you very much.

    that helped me along to this conclusion. Because of him, I used my influence at a major manufacturing company (considering requiring all mission critical systems be open source) to convince them that the *BSDs were NOT open source - and they bought the argument.

    In short, you admit outright that you told a destructive lie to your employer or client. I hope you're proud of yourself. No, on second thought, it's quite obvious that you are not, since you've posted as "Anonymous Coward."

    It's obvious that you yourself believed that you would have had a more difficult time selling your employer on Linux vs. BSD if you'd been ethical enough to be truthful.

    --Brett Glass

  145. Moderate this fucker down. by tarp · · Score: 1
    Excuse me, but Bruce Perens is far from stupid. In fact, I'd fathom to guess that he's a genius.

    And the technocrat.net thing is his signature, you nitwit.

    --
    WorldServe Consulting

  146. Threads, baby. by GeekWSpots · · Score: 1

    I would use it, but it lacks thread support - namely proper threaded SMP support. The other thing is that pesky non-automatic kernel config problem. I guess I'm a Solaris loser, but proper modules with hardware detection is a lot more fun than recompiling the kernel in production.

    To be more to the point, I'd use OpenBSD for more than just firewalls. I love OpenBSD.

    --
    Kyle Hodgson Systems Geek
  147. Re:Shut the fuck up, moron. by Arandir · · Score: 2

    Ah, yes. GNU advocacy at it's finest. Makes me so proud to use Linux. After all, there was no such thing as Free Software until the concept mythically sprouted from the forehead of Richard Stallman. Since then we have been freed from the bondage of, of, of... non-GNU software.

    After all, the GPL demands that all those who use gcc must worship Richard Stallman.

    --
    A Government Is a Body of People, Usually Notably Ungoverned
  148. Re:Poppycock by Arandir · · Score: 2

    "The unwritten rule of the BSDL seems to be "you can make a proprietary version, but not a GPL'd version""

    The reason for this is that the GPL extends to third parties, the "viral" clauses in other words. No other license that I am aware of, proprietary or otherwise, does this (except for those few derived from the GPL). BSDL developers have no desire whatsoever to impose anything on third parties.

    However, there is nothing preventing you from copylefting your mods to BSD code. Just don't expect it to get rolled back into the source tree. If GNU will refuse, or even sue, those who would return modifications under BSDL, why should BSDL behave any differently?

    "They seem to resent the fairness we insist on."

    Enforced fairness is not fair. It is impossible to commit a moral act if you have no choice. If you choose to use a fairness enforcing license, that is your choice, but by making on airs of moral superiority by doing so is utter hypocrisy. That's like calling taxation charity.

    "Perhaps they're trolling for work from naive coders.."

    Okay, now I'm completely offended! My actions are my own, and it's none of your damn business what they are. It's interesting how Stallmanistas rant on and on about freedom, but once someone makes a free and conscious choice, they call us dupes and knaves. You guys don't know the first thing about freedom.

    --
    A Government Is a Body of People, Usually Notably Ungoverned
  149. Re:Not in my experience by screeching+weasel · · Score: 1

    Is this comment refering to the BeOS still?!?
    "a wholly unintuitive GUI"... what are you, a retarded four year old? what could possibly be unintuitive about Be's GUI? It's as simple and effective as could be. "Broken internet browser"?
    You must have been using an OLD OLD version or something.
    I urge you to give it another try. It really does rock.