8 ms·
Why doesn't *BSD have a greater market share? I just set up an openbsd firewall and loved it. Plus I have experience with zfs on FreeBSD-also loved it.
by ianai 10y ago
Why doesn't *BSD have a greater market share? I just set up an openbsd firewall and loved it. Plus I have experience with zfs on FreeBSD-also loved it.
- 2trill2spill 10y agoThe ATT lawsuit stopped BSD development for a year or so and many people moved to the Linux community during this time, because of the uncertainty caused be the lawsuit.
- ianai 10y agoComparatively, it's got the more permissive licensing, now.
- 2trill2spill 10y agoTrue, hence why so many products are built on top of FreeBSD. But for organizations not shipping Linux binaries the license doesn't change much. Also Linux is a pretty awesome operating system so it doesn't make much sense for lot's of organizations to switch to FreeBSD even if there are some advantages to using FreeBSD.
- dijit 10y agoAnecdatum; I'm moving our CentOS/RHEL Linux systems to FreeBSD over the coming two years. Databases/Fileservers/Firewalls/Webservers etc; So it's making a comeback, at least in my 11,000+ person org. :D
- ianai 10y agoI do feel like it has a comparative advantage in all of those spaces. ZFS, jails, and pf are all killer features for all of those spaces. The only possible draw back is it requires your IT staff know the technologies. What a company saves on licensing easily makes up for the staff wages though...maybe.
- 2trill2spill 10y agoGood to hear! FreeBSD is my favorite OS and I wish I could use it at work, but were a CentOS/RHEL and Windows shop. However the security team has a handful of FreeBSD servers going, so it is used.
- gribbly 10y ago>But for organizations not shipping Linux binaries the license doesn't change much. hmmm.. Android, Chromebook, Smart TV's, Routers, set-top boxes, NAS etc, these all ship Linux binaries, so I don't think it's a big issue. If you do kernel space modifications which you want to keep as a 'competitive advantage', then going with something like FreeBSD instead of Linux would make perfect sense, otherwise I don't see why the license would matter much.
- bluGill 10y agoIt is the pain of complying with the license. You have to ensure you have everything in place just in case someone asks for the source code. It isn't hard, but it is effort that nobody wants to do yet you have to. It isn't good enough to say "we use version 1.2.3 unmodified download that from the internet", you actually have to have a copy of version 1.2.3 ready to send out (apparently in case the internet deletes all versions of source code 1.2.3).
- junk_disposal 10y agoThat's the FreeBSD line, but I don't think it's so simple. The lawsuit ended in 1994. That was before RedHat, and one year into Debian. At that time, the majority of Unixen were proprietary, so if you wanted your programsto run, you couldn't assume GNUisms or Linuxisms.
- phicoh 10y agoI think the big difference in culture accounts for more than the lawsuit. FreeBSD moves very carefully. New features are introduced when they are quite mature. For major changes, the old way of working is maintained for quite some time. Early nineties that showed in hardware support. If you wanted to have a real system, you got yourself a SCSI card. There were some really crap IDE controllers out there and in the FreeBSD community nobody cared for them. So resources is one thing, but basically the FreeBSD community didn't want to spend time getting completely broken hardware sort of working. (For a long time, partitioning was also a twisted maze. The BSD partitioning scheme was somehow combined with the MBR in weird ways. No problem for a system dedicated to FreeBSD, tricky if you want to shared with Windows). The Linux community was way more trying to run on everything. In the same way, the Linux community is much more into shiny, new. Color ls, that would famously break scripts because it also output escape sequences if you send the output to a pipe. By and large a FreeBSD system looks less cool than a Linux. So FreeBSD attracts the users who know they want stability above everything else.
- junk_disposal 10y ago>The Linux community was way more trying to run on everything. In contrast to some opinions, I like this sometimes. For example, would the world come to an end if FreeBSD came with neovim? If the prompt out of the box showed pwd? I know that some things are controversial (ahem systemd), but when learning a new system, little things matter and make your system popular. (And, as a side rant, in contrast to some who like to use haskell on nixos (Which I actually like!) running on an obscure chipset, popularity is good. If someone asked me what Unix should he learn, I'd send him to Linux and not FreeBSD, since it's going to be much easier to find noob help online. Then, this noob will go on to become a sysadmin, he'll recommend Linux because he knows it and will be able to find others who do.)
- tete 10y agoI agree on that question, but it's also a bit strange to say, because if you think about where BSD code ends up it's a pretty big market. You have stuff where there is a big amount of FreeBSD code in it: MacOS, iOS, Playstation 3/4, Cisco Routers, Juniper Routers, Android (though way less, then in the rest) You have a couple of big names using FreeBSD in big amounts or for important parts of their infrastructure: Facebook (WhatsApp), Netflix, NetApp, VMWare, Trivago, DuckDuckGo, Flightaware, ... And you have big amounts of code in other projects. Stuff like OpenSSH and many libraries. I didn't include the usual suspects, such as non router hardware manufacturers (ARM, Intel, HP, Dell, ...) that use it a lot, but they also use other stuff. In other words: The market share I think grows if you use big companies. For smaller companies there is a rule of kind of sticking with the most used stuff. And that simply is Linux (among other things for that legal reason, already mentioned here).
- pjmlp 10y agoThe problem is that thanks to the way the license works, not all companies do upstream their changes.
- loeg 10y agoWhy is that a problem? (Or, put another way: the BSD community does not consider this to be a problem. Why do you?)
- pjmlp 10y agoI don't care as I even run Windows most of the time, but it is indeed a reason why BSD is behind GNU/Linux and the community does care. "The Trouble with FreeBSD" @ 43:20 https://www.youtube.com/watch?v=Ib7tFvw34DM https://www.youtube.com/watch?v=Ib7tFvw34DM
- johnsmith21006 10y agoLinux runs all of Android which is the most common OS today. But it also runs the biggest clouds in terms of infrastructure. Google and Amazon are completely built on Linux. Linux also runs 95% of the super computers in the world. As containers eat the world you will see more and more Linux, IMO. Used both since .96 Linux and for network BSD was far superior but you could feel which was going to win very early so switched once Linux was usable.
- loeg 10y agoFreeBSD developer here. A lot of Linux' success vs BSD is due to the USL lawsuit in the early 90s. I believe Linus has said he wouldn't have even made Linux in the first place if BSD hadn't been embattled in a lawsuit at the time. As far as today — Linux has far more developers. It has driver support for a wider array of hardware. It gets more and faster vendor driver support (Intel, AMD, Nvidia, etc; even Microsoft) than the BSDs. It scales better on NUMA and on very high core count systems than any BSD. These are all legit reasons people use Linux instead of a BSD. Then there's RHEL and Ubuntu. The BSD world doesn't have anything like either. RHEL is a huge boon to the Linux ecosystem — they take money for support contracts, and invest it in improving the GNU & Linux ecosystem for everyone. Ubuntu is a very beginner-friendly distribution that is serious enough for server use. On the FreeBSD side there's maybe TrueOS (née PC-BSD) but it doesn't attract anything like the audience that Ubuntu does. It also doesn't have Shuttleworth's funding.
- ianai 10y agoIs there a central list of areas/known problems for NUMA/high core count/scaling on *bsd anywhere? Of course anything would do great with more funding/corporate backing.
- loeg 10y agoThere's https://wiki.freebsd.org/NUMA https://wiki.freebsd.org/NUMA . Not sure it's current.
- pvg 10y agoFreeBSD had a pretty decent run after the lawsuit and was probably more common than Linux in Serious Server Deployments™ for a bit. Fundamentally, though, Linus out-organized and out-managed the BSDs, I don't think it it was just the lawsuit.
- empthought 10y agos/Linus/IBM/
- fictioncircle 10y ago> Why doesn't BSD have a greater market share? I just set up an openbsd firewall and loved it. Plus I have experience with zfs on FreeBSD-also loved it. Lawsuits and subpar driver support in the 90s, basically. https://wiki.freebsd.org/Myths https://wiki.freebsd.org/Myths > This is a problem faced by all operating systems - even new versions of Windows. Most of the time, users don't care about the total number of drivers, only if drivers exist for their hardware. There are some omissions in terms of driver support, but FreeBSD supports a wide range of network cards (including an increasing number of 802.11n chipsets), most sound cards, and AMD, Intel and nVidia GPUs. > Device support is a constantly moving target because we can't tell hardware makers to just stop releasing new hardware for a few years while we catch up. New devices do take some time to support, although some manufacturers do provide drivers themselves, for example nVidia provide drivers for their GPUs, and Intel for their newest network and storage controllers. Other manufacturers provide significant help to FreeBSD driver writers, including Broadcom, JMicron, HP, Mellanox, Chelsio and Solarflare. If you find a device that isn't supported, please let the project know and also notify the manufacturer: the only thing that motivates hardware manufacturers to support any operating system is the knowledge that their customers want it. This is much, much less of a problem now than it used to be but I remember building a hobby box in the 90s when I wanted to run FreeBSD and I had to be very, very careful about what hardware I put in it so I ended up installing Debian. (Anecdotal and likely possibly coincidence, but Debian had all the correct drivers.) The net result is no one really switched back to BSD once those issues were (mostly) resolved since too many Devs were bringing out software for Linux by that point. Driver support still lags on the BSDs (although nowhere near as badly as it used to!) so its just easier to use Linux for most people.
- pjmlp 10y agoBecause the way the license works, lots of *BSD users, specially companies selling routers, never contribute anything back. Also the lawsuit with AT&T did not help.
- gonzoua 10y agoAnd lots do. Top 20 sponsored contributions from 01/01/2016 up to now sorted by number of commits (not the best metric, but still) 1031 The FreeBSD Foundation 888 EMC / Isilon Storage Division 379 Microsoft OSTC 339 Microsoft 297 Solarflare Communications, Inc. 277 Dell EMC Isilon 221 DARPA, AFRL 170 Mellanox Technologies 144 Chelsio Communications 128 ABT Systems Ltd 90 Spectra Logic Corp 88 HEIF5 70 Cavium 58 Smartcom - Bulgaria AD 57 Stormshield 48 Netflix 45 Rubicon Communications, LLC (Netgate) 42 Multiplay 38 ScaleEngine Inc. 35 Citrix Systems R&D
- pjmlp 10y agoStill a minority compared with the GNU/Linux contributions, but nice to see some do actually care. "The Trouble with FreeBSD" @ 43:20 https://www.youtube.com/watch?v=Ib7tFvw34DM https://www.youtube.com/watch?v=Ib7tFvw34DM
- gonzoua 10y agoLess companies contribute to FreeBSD because its market share is lower than the one of Linux. And I believe first part of Beno's answer is correct - it's because FreeBSD version of RedHat didn't happened at the right moment. RedHat was there when window of opportunity opened for open source OS and was able to boost linux ecosystem by paying Linux developers which led to higher adoption which led to more contributions from corporate world. GPL does not require contributions. GPL requires access to sources. Not to changes history, only sources. Contributions happen because it's more profitable for company (in long run) to participate in community and influence development than to be a passive actor. My point is: license has very little to do with market share in this case. It's more about being good enough and having certain amount of luck when the right moment arives.
- junk_disposal 10y agoIn my opinion (mostly Debian user with a bit of FreeBSD playing), people use Debian as a server for the same reason a lot of people like MacOS over Linux - It Just Works. 1. For many years, the only way to install software was ports. Now if you're a full time sysadmin with time on his hands, it's great. But if you just need something up and running fast (and if you don't know your software internals, and don't know if you'll need perl's FLAG_ABC) , it's horrible. It just feels like Linux in the 90's (been there), where recompiling the kernel/freex86 was a right-of-passage into Linux hackerdom. Nowadays, most of the time it's just not worth it. 2. apt vs ports/pkg. This is actually the biggest thing keeping me on Debian - stable + backports. If I'm running my server, I want things to be stable. Now I know that there's no other project the size of Debian, which can backport security fixes to two year old software (and sometimes four year old software), but there's nothing like apt update && apt upgrade and 99% of the time have everything update without a hitch. Yes, FreeBSD is more elegant (why couldn't GNU/RedHat have just modeled ifconfig rather than ifconfig, ifup, ip, etc.). Yes, FreeBSD's man pages are amazing (which is quite important, as there's not as many FreeBSD blogs around), but if you're learning a new system (coming from Windows), Linux isn't that much harder to learn than FreeBSD. EDIT And RedHat? They work like Oracle - You pay them, and they'll hold your hand, and (unlike Oracle) they release their software under an OS license. If you're a non-tech Fortune 500, that's very important. Note, by the way, that those two distros have the vast majority of GNU/Linux installs.
- chrisper 10y agoDebian doesn't always just work, because a lot of packages are very old. I think Ubuntu is (or is supposed to be) more "just works." But I think this is a personal point of view thing. Also I think the FreeBSD handbook is awesome, even for newcomers. Is there something like that for Debian?
- fictioncircle 10y agohttps://debian-handbook.info/browse/stable/ https://debian-handbook.info/browse/stable/ https://www.debian.org/doc/books#english https://www.debian.org/doc/books#english
- 10y ago
- jlgaddis 10y agoFor me (network/server guy for a small ISP, with complete decision-making authority in this context), I'd love to run FreeBSD on all my servers and OpenBSD on all my routers (even though I (mostly) make my living from my Cisco knowledge). Here at home, within a six foot radius of me, I've got a nice new (waaaay overbuilt) workstation, a pair of ThinkPads, some cheap Dell laptop, and a rMBP. The Dell and rMBP are rarely used but I had to decide what to run on my three "primary" machines (and the couple of neglected machines in the garage). I'd much prefer to run FreeBSD everywhere but suspend/resume on the laptops is a deal breaker for me. I could run FreeBSD on the workstation (which is always running) but then I've got two operating systems to keep up on instead of one, so instead I just run Linux on all of them. At work, on the servers, my line of thinking is basically the same. I pretty much have to run Linux (over BSD) in a few cases, so do I run FreeBSD where I can and Linux everywhere else or just make things easier on myself and run Linux across the board? Since I'm already running Linux on all my personal machines it makes sense to use the same at work.
- phicoh 10y agoThere are certainly ThinkPads where suspend/resume works with FreeBSD.
- patrickg_zill 10y agoI think the real reason is that in the mid to late 90s, there were several hardware vendors that focused on Linux. One of them at least went public (VA Linux). In fear of losing hardware sales, Dell/HP/Sun (their X86 hardware unit)/ IBM all made sure that their servers could run Linux also. This resulted in a lot of hardware support being added very quickly. FreeBSD never had that "tornado" of uptake from major hardware vendors, and thus, support always lagged, if it was there at all.
- mentat2737 10y agoIt was said already in the past, and I agree. Naming. Too many letters in a *BSD, too scary. Linux is more toy-ish and thus more appealing as a name. Plus the UCL vs BSD legal war, which shifted much of the community towards Linux.