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.

19 of 690 comments (clear)

  1. 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 :)

  2. 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!
  3. 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 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.

  4. 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 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.
    2. 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. 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 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.
  6. 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."
  7. 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
  8. 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...
  9. 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.

  10. 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?

  11. 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)
  12. 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.
  13. 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.

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