24 ms·
Technical reasons to choose FreeBSD over GNU/Linux
- gigatexal 7y agoUse the best tool for the job I say. If it’s BSD for you or your project then so be it. If it’s Linux then use that.
- afc 7y agoAnd use this article to figure out whether BSD is better than Linux for you or your project, right?
- noodlesUK 7y agoAs a longtime user of both FreeBSD and various Linux distros, I agree with a lot of points regarding the coherence and ergonomics of FreeBSD’s design. However, I don’t generally run FreeBSD anymore, despite enjoying using it more, simply for the reason of security. I don’t feel (and maybe this is just a feeling) that security is a first class citizen on FreeBSD the way it is in Linux distros like Fedora or Ubuntu. Things can be slow to be patched and the defaults aren’t always particularly secure. I really miss ZFS though. Btrfs just isn’t as nice to work with.
- Kenji 7y agoReally? Here I thought FreeBSD puts security before everything. This comment is surprising to me.
- alexfromapex 7y agoYeah I don’t think one or the other is inherently better but Linux definitely gets more users and is more “tested” so things like drivers and software will have better support.
- ohlookabird 7y agoWhy not use ZFS on Linux?
- asveikau 7y agoIt will never be in-tree, short of an act by Larry Ellison. Depending on an out-of-tree module can get pretty crappy on Linux. The upstream kernel will break you a lot. If your distro is on top of keeping your out-of-tree feature working then great. It gets messy whenever that is not the case and/or suddenly you want a driver or feature only available in a newer kernel.
- dbuder 7y agoFilesystem and Distro/OS are part of one choice imo.
- p_l 7y agoLarry Ellison can't relicense ZoL - they'd have to start from scratch porting the code from Solaris
- _-david-_ 7y agoI think people typically mean that Larry Ellison could come out and say there are no issues with incorporating CDDL code into a GPLv2 code base. Ideally in a document signed by him and lawyers at Oracle given to the Linux Foundation. If that happened I don't think people would have an issue adding ZoL to the kernel.
- p_l 7y agoThere are no issues on the side of CDDL anyway. Larry can't change the fact that GPL is the source of incompatibility - the general interpretation is that GPLv2 forbids code that has stricter licensing terms than GPLv2, and CDDL happens to have that - in form of patent grant. It's also why GPLv3 code has a license issue with Linux kernel, which is GPLv2.
- dragonsh 7y agoBeen a FreeBSD user for very long time besides Linux Slackware distributions since kernel 1.0. Started with Walnut Creek CD distributions. In early years it was much better than Linux with its fast networking stack and filesystem. Also it gives a sense of conceptual integrity as distribution is not just kernel but all the utilities, they work together in unison. But than it also hamper innovation due to design by committee vs the best tool for the job. Now with time and various flavours of Linux from NixOS, GuixSD, Gentoo, LFS, Slackware, arch, Debian, Ubuntu, CentOS, OracleOS etc., it is in many case a better choice than FreeBSD. In most benchmarks and hardware support it has surpassed FreeBSD. I still hope FreeBSD continue to grow and innovate, but it’s not a viable choice in many areas of modern computing. Hopefully it can catch up. It still is a very viable choice in building network devices, but there also with modern hardware support Linux is giving it a tough competition. I still use FreeBSD, but my majority production workload now is Linux with some firewall and networking related stuff in FreeBSD and openBSD. I did try portable FreeBSD based version like dragonfly and pcbsd. But now I don’t use them that often.
- proverbialbunny 7y agoAs a counter to this, if you're working on network software that uses a lot of bandwidth and a lot of open connections, BSD is a bit more stable than Linux, so it's generally a better choice for that at least.
- jauer 7y agoThis hasn't been a significant issue for a while now, to the point that Linux is used on cache appliances from the FAANG (though Netflix is notable for using FreeBSD in that role).
- dsies 7y agoThis is dangerous advice. BSD networking stack may have been superior at some point but that hasn’t been the case for many years now. You are very likely to run into issues trying to do filtering and/or routing at anything >1Gbps on commodity hardware (ie. e1000 nics). Pf is pretty but it’s not worth trading stability for.
- djsumdog 7y agoI would be totally on board with using FreeBSD as my primary server OS .. if it had a container engine. There was a port of Docker to FreeBSD, but it's ancient and unmaintained (before Docker did their big modular refactor). In theory, you could implement a lot of the Docker Engine API for FreeBSD and on the backend use jails instead of namespaces/cgroups and ZFS if you wanted implement the same layering. Some of the security and cgroup limits may not be implementable on FreeBSD, but with the Linux binary emulation layer, you should still be able to run a lot of containers without modification (unless they need certain filecaps or privileges). I had OpenBSD on a laptop once, but without 802.11ac support, you'll either have to downgrade the Wi-Fi card in newer laptops or use a USB adapter.
- phonethrowaway 7y agohuh, watchutalkinbout? https://en.m.wikipedia.org/wiki/Bhyve https://en.m.wikipedia.org/wiki/Bhyve
- twblalock 7y agoThat's a hypervisor. It's not the same thing as Docker. Docker is more like jails.
- twblalock 7y agoThe fact that the Docker port was allowed to die is a pretty good indicator of how little interest there is in using FreeBSD in the industry, particularly in cloud environments.
- tramtrist 7y agoSlackware lines up more with the original philosophy this article talks about. I like taking Slackware in either stable or -current and running it in this article instead of Debian ... If you wanna run Linux with a distro that hasnt changed its overall philosophy, structure, or hell even core software you should be looking at Slackware again. 15 will likely be out this year.
- deleted 7y ago[deleted]
- uk_programmer 7y agoI've been a long time OpenBSD, FreeBSD and Linux user (I use Windows for mainly for work though). I've given up with the BSDs tbh. While I like that I can understand these systems. Linux is just easier to get things working on. There is just more information now out there for Linux as it is the defacto *nix out there. So it may well be that BSD has many technical merits, they tend not to be all that useful when you are trying to get stuff done.
- kylek 7y agoIt's been said a million times- FreeBSD is an operating system, Linux is a kernel. ("GNU/Linux" is a strange beast- kernel+libc or what?). It's a tough direct comparison to make especially when you consider things like documentation (which FreeBSD is often cited as being exceptional)
- hvis 7y ago> ("GNU/Linux" is a strange beast- kernel+libc or what?) Kernel plus userspace: the standard command-line tools, compilers and some additional stuff. Such as GNOME, for instance (it's considered a part of the GNU project).
- asveikau 7y agoIt's a little weird to not put some of these headliner features at the top of the list. Like ZFS (in-tree, on the default installer, without licensing issues or hostile team dynamics). On the other hand there are things in this list which are just the FreeBSD equivalent of something Linux has in some form. The ports tree is good, and I like that you can customize options etc., and now pkg is pretty good, but are you really going to miss that if you have apt or similar?
- ianai 7y agoAren’t Linux and freebsd using the same zfs fork at this point though?
- asveikau 7y agoI am not following closely enough to know when that makes it into a stable FreeBSD release, but yes it will be. Except for one point: the zfs on Linux work is not in the mainline kernel, and won't be. A strict interpretation of your comment would actually be "no" - can it really be said that "Linux is using it" in that case? You need out-of-tree kernel support which is very difficult to maintain.
- viraptor 7y agoI find some points... debatable. For example software: > Normally when you install software on a Unix operating system you find and download the software. According to the title, this is about choosing FreeBSD over Linux, not over Unix. That means the normal way to install is "<package_manager> install <package_name>". For the end user this is just like ports without having to compile anything. Once you don't have the package or the port available, you end up in the same situation: download the source and compile (which is more likely to work on Linux OOTB simply due to popularity). > Poudriere is a utility for creating and testing FreeBSD packages. It utilize the FreeBSD jail system to set up isolated compilation environments. In Debian-like systems you can use pbuilder in the same way. Each package is built in the same clean choot. I suspect RH has something similar? > bhyve They don't list anything technically better about bhyve. Why would I use this over xen or kvm? > FreeBSD has three different firewalls built into the base system: PF, IPFW, and IPFILTER, also known as IPF. Ok. Linux has iptables and now nftables/bpfilter. It's also got queuing, stateless and stateful features, protocol tracking, etc. CARP can be done in userland, or via other solutions like linux-ha/stonith. What are the reasons to choose FreeBSD here? (also, mentioning 3 firewalls after being excited about well-designed system that just comes together rather than being glued together from third-party software just sounds weird) > BSD init They haven't listed what's actually technically better about it than in systemd. (not subjectively) > Jails Jails as described in the article, have the same features as lxc. Lxd provides zfs-as-a-backing-store option as well. > FreeBSD has over five hundred system variables that can be read and set using the sysctl utility. Ok. On my Fedora system "sysctl -a | wc -l" gives 2093. > For example, on top of the geom_mirror module an encryption module can be added, such as geom_eli to provide a mirrored and encrypted volume. So how is it better than lvm with its layers dm-raid and dm-crypt? I get that people are excited about FreeBSD and I'd love to learn what are the technically better sides of it. But this article really doesn't list that many.
- msla 7y ago> They haven't listed what's actually technically better about it than in systemd. (not subjectively) And even to avoid running headlong into this troll pit: Linux distros without systemd exist. It's dishonest to compare FreeBSD to Linux and then only focus on a subset of Linux distros.
- dzonga 7y agotechnical merits, can be plenty. however how does freeBSD integrate with the rest of the I wanna get things done ecosystem of people n software. Can I easily install it on a laptop such as a thinkpad and have a plug and play experience. Can I easily update and find packages | software I need. if Open source software approached things from the usability view, we wouldn't be beholden to corporate interests. I personally, use KDE on a thinkpad
- pnako 7y agoFreeBSD marketing: - FreeBSD is like Linux but <> - It is more <> than Linux - It is less <> than Linux - It has more <> than Linux - It has less <> than Linux - Linux LINUX Linux LINUX LINUX OpenBSD marketing: Look, cute fish.
- msla 7y ago> OpenBSD marketing: OPENBSD IS SECURE. ARE YOU SECURE? ARE YOU WORTHY? OPENBSD: SO SECURE WE DO NOT NEED YOU!
- deleted 7y ago[deleted]
- qplex 7y agoFreeBSD and Linux have pretty cute mascots too. Puffy is exclusive to OpenBSD. Tux and Beastie are more generic. Also: "Early versions of OpenBSD (2.3 and 2.4) used a BSD Daemon with a halo, and briefly used a daemon police officer for version 2.5. Then, however, OpenBSD switched to Puffy, a blowfish, as a mascot." [0] [0] https://en.wikipedia.org/wiki/BSD_Daemon https://en.wikipedia.org/wiki/BSD_Daemon Edit: You're absolutely right that there seems to be some kind of power fantasy among the FreeBSD crowd about crushing Linux. Just do an image search for "BSD Daemon" and see the g(l)orious fan-art.
- reilly3000 7y agoI run Ubuntu as my daily driver primarily for its broad 3rd party application support. As such I tend to run Ubuntu on servers as well, so I'm usually in familiar territory. I have a smart friend who extols the benefits of FreeBSD, but I haven't ever given it a serious go. Is there a canonical/non-hacky way to run debian packages on FreeBSD? Like can I run Slack and Zoom? Steam?
- softwarejosh 7y agoid rather see this on openbsd
- pnako 7y agoLinux is a Boeing (a 737 Max, if you ask certain people), OpenBSD is a Cessna. If you do a direct comparison, OpenBSD would lose in terms of benchmarks, hardware support, software support, features, etc. But OpenBSD is more a philosophy, a particular way to approach computing that works for some people. OpenBSD is basically a continuation of Unix from the 80s, where the admin/user (no distinction in reality) is expected to do some work from the command line. Thus it's a great user experience. The config files tend to have the same syntax, and it's human-friendly syntax, not some XML or YAML crap designed for a tool. Things are kept simple so human brains can understand them. But the trade-off is basically features, performance, hardware and software support. It's a bitter pill but, again, it works for some people. I use OpenBSD full time on my router, but I tend to switch back and forth on laptop and servers (with Debian).
- ben_bai 7y agoWhen Linux is a Boeing 737Max, then FreeBSD is a Airbus A380 and OpenBSD is a A-10 Warthog. xD
- maallooc 7y agoPractical reasons to choose linux over freebsd 1. People use linux more than freebsd Nothing's more important than this.
- greymeister 7y agoSounds straight from a 90's Microsoft marketing department, I'm glad not everyone listened back then. More users is definitely a feature though.
- maallooc 7y agotbh microsoft was the best choice in the 90s. the only reason linux became useful is because it became popular.
- _emacsomancer_ 7y agoonly for very particular, and peculiar, senses of 'best'
- doctor_eval 7y agoFor some domains, But certainly not all, Windows was arguably a better choice, but even then it was more Windows NT vs Novell than Unix. I don’t recall Microsoft ever getting much traction in the racks of ISPs or in “big iron” installations, not until the late 90s... and even then it was tenuous. Microsoft was a terrible choice for IP networking, for example. Changing the IP address of a server would require a reboot. The majority of the work I did in the 90s was on HPUX and DGUX, but also a bunch of others. There was a lot more OS diversity back in the day.
- justinmeiners 7y agoMight as well at not choose to do anything then. Just use whatever everyone else does. We need people trying out better ideas even if they aren't as popular or easy.
- zelly 7y agoI have dabbled in BSDs (mainly OpenBSD) but can't stick with any of them because Docker doesn't work without virtualizing Linux. If I have to have a separate setup for "real work" versus hobby work, then it's a non-starter for me; I don't have enough time or brain capacity. I like the idea of BSDs as this self-contained system (like the polish of Apple's walled garden but without the tyranny), but it is too far behind the cutting edge.
- mappu 7y agoI don't think the parts about ZFS being "better integrated" on FreeBSD are really true any more. For one thing, ZFS-on-Linux is now the canonical, upstream OpenZFS implementation - https://utcc.utoronto.ca/~cks/space/blog/solaris/ZFSOnLinuxNowOpenZFS?showcomments#comments https://utcc.utoronto.ca/~cks/space/blog/solaris/ZFSOnLinuxN... For another, Ars Technica recently reviewed FreeBSD 12.1-RELEASE and found poor ZFS integration in the installer and in mount(8): > Eventually, I realized that FreeBSD's mount command didn't really understand my ZFS root filesystem. -- https://arstechnica.com/gadgets/2020/04/not-actually-linux-distro-review-freebsd-12-1-release/ https://arstechnica.com/gadgets/2020/04/not-actually-linux-d... Compare that with the relatively streamlined ZFS-on-root install support built into Ubuntu: https://arstechnica.com/information-technology/2019/10/a-detailed-look-at-ubuntus-new-experimental-zfs-installer/ https://arstechnica.com/information-technology/2019/10/a-det... (I'm sticking with ext4 until kvdo, bcachefs, or maybe tux3 is mainlined.)
- viraptor 7y ago> (I'm sticking with ext4 until kvdo, bcachefs, or maybe tux3 is mainlined.) I haven't heard of kvdo before - thanks for bringing it up! I'll add stratis-storage to this mix too. (Although I'm contributing to the bcachefs development and really want it to succeed)
- rashkov 7y agowhy not use zfs, since it does the things that kvdo, bcachefs, and tux3?
- dragonsh 7y agoOnly one reason of Oracle law suite sword hanging over neck. Even if canonical gives guarantee they will fight with Oracle, if a small company is dragged by oracle in a court room it's hard to fathom the expenses. So yes there is a need for zfs alternative. So far stayed away from it and using btrfs which works well, except for some RAID limitations.
- p_l 7y ago
- detaro 7y agoHow do e.g. the sections about bhyve and Bastille describe Technical reasons to choose FreeBSD over GNU/Linux? The describe features, but they tell me nothing about why those might be better than counterparts in the Linux world.
- ianai 7y agoWow I see no mention of no systemd in FreeBSD here. I love how unified the freebsd maintenance and just general system utilities are. The documentation doesn’t lie. I’ve never had a bsd box stop booting because of a wonky system change either.
- progval 7y ago> Wow I see no mention of no systemd in FreeBSD here. The author wrote about it in the "part 1" article linked in the introduction.
- Hello71 7y agoI started using FreeBSD a few months ago for a Tor relay, trying to promote OS diversity. I had read these types of articles about how FreeBSD is so much cleaner and well documented than Linux, and I wanted to try it out. Honestly, I found it seriously lacking. It always seemed to me like most of those article writers had poor understanding of Linux, and now it seems to me like they have poor understanding of FreeBSD too. For example, this article, like many, touts the high quality of FreeBSD documentation. I found it to be similar to Linux documentation: a few excellent pages, mostly good pages, some mediocre pages, and lots of undocumented stuff. People (including me) often complain about the quality of Linux networking documentation, which is unquestionably terrible, but I found that FreeBSD isn't really that much better overall. Better in some places, worse in others, often you have to give up and go find the source code. Another thing often touted is the centralized development of FreeBSD making it more organized. This article betrays itself here by explaining that FreeBSD has three different firewalls, one originating locally, one forked from OpenBSD, and one forked from some dude. Now, to be fair, Linux is far from clean here: between ipchains, iptables, nftables, and bpfilter, Linux has gone through a lot of change. At least with Linux though there are at most two practical options at any given time, and there is a clear forward progression. With FreeBSD, I spent several hours trying to figure out the differences between each, which wasn't helped by the documentation problems: manual pages being fragmented and incomplete and the handbook being woefully out of date on this subject. It also seems like a lot of the hyped FreeBSD features are actually far behind Linux features. As other commenters have mentioned, Linux has device-mapper, which is similar to GEOM, and is used for LVM and modern RAID setups. Jails came before containers, but Linux namespaces are now far more powerful than jails, which aren't that much more than chroots. bhyve is nice, but lags behind QEMU/KVM. Poudriere is fine but most Linux distros have chroot builders too now. In conclusion, I don't find FreeBSD particularly attractive for any of the reasons that I hear often touted.
- RandomTisk 7y agoAny Linux or BSD distro could achieve best-in-class documentation for new users by simply adding example usages for most commands to the top of their man pages. Man pages tend to read more encyclopedias than practical guidance, and FreeBSD was no exception last I looked. Command xyz Common usage: xyz -s source_ip -d dest_ip:port
- scythe 7y ago>The kernel and base system is completely separated from the third party applications and base system configuration goes into /etc while all third party configuration goes into /usr/local/etc. Everything you can configure and everything you can tune or setup is very well documented in the man pages. One thing I find ironic about BSDs is that their top billing feature is being a "complete integrated (base) operating system" rather than a collection of software maintained by different projects, but at the same time, they're almost always discussed as server/poweruser operating systems rather than desktop operating systems. This seems completely backwards to me. If I'm a sysadmin running a server, I probably know what I'm doing and feel confident replacing parts of it. I likely studied this and relative to a typical person I'm much more likely to find the way it works to be interesting. By contrast if I'm a desktop user there's a very good chance I don't know what I'm doing and don't really want to. It seems like the second situation is the one where you benefit more from having a wall up that separates the system from the userlibs. There have been fleeting attempts to make desktop-forward BSD distributions over the years, including PC-BSD and a few short-lived initiatives by the NetBSD project, but it never gets off the ground. Is this a missed opportunity?
- GolDDranks 7y agoWhat usage this article is talking about? For a server? For a desktop environment? For servers, me and my colleagues use Linux, and not being able to use Docker is a tough call, our workflow is very Docker-centered. I know that Jails exist, but it's not just about containment, it's about packaging, building and deploying too, and having ready-made tools (and a lot of existing Dockerfiles) for that. For desktop, I use macOS, and I'm not willing to change if it worsens the experience, which I suspect it will do. I wonder what would be the killer use for FreeBSD today? I'd be eager to try, since I'm eager to try all kinds of stuff, but I fail to find any place I could easily stray from my current OS combination.
- 0x1ch 7y agoThis seems more so like a list of differences, without any details as to what makes them different, let alone which is better...
- new_realist 7y agoIf Linux were a railroad, FreeBSD would be a model railroad club. Nice stuff, in a way, and very similar to the real thing, but lacking a certain industrial usefulness.
- sgt 7y agoNot at all. FreeBSD is without doubt on equal footing with Linux in terms of industrial usefulness, assuming the features you seek are available. Large companies use FreeBSD in production for mission critical apps but are generally less vocal about it.
- lasermike026 7y agoWhatevery floats your boat. I use linux, docker and kubernetes all in the cloud. I'm getting more distant from underlying OS everyday. BSD is a fine operating system. There is nothing wrong with it. Linux is a good operating system and gets the job done. Whatever works. I think what is more concerning is that we really haven't had a big leap in hardware, OS, and system design for sometime. When are we going to have the guts to make the next step?
- kvz 7y agoI’d argue NixOS is a huge step that a lot of people still have to catch on to (to be fair: that includes more contributors to improve documentation and ergonomics, but it is already valuable and workable as it is)
- lasermike026 7y agoWhat can we do beyond posix?
- ghuntley 7y agoWorking on this! Check out the NixOS for existing sysadmins workshop over at https://github.com/ghuntley/workshops/tree/master/nixos-workshop https://github.com/ghuntley/workshops/tree/master/nixos-work... If you want a TL;DR overview of NixOS then start here https://github.com/ghuntley/workshops/tree/master/nixos-workshop/modules/01-introduction-to-nixos https://github.com/ghuntley/workshops/tree/master/nixos-work...
- GordonS 7y agoSomething I wonder about after reading your overview - software from outwith the package manager. It's quite often that the package manager in the Linux distro I'm using has an old version of Nginx, PHP, or whatever, and so I have to build my own, or at least use an alternative package source. How is this kind of thing handled with NixOS config? (if it is)
- 7y ago
- ggm 7y agoI'm seriously unconvinced there are any aside from personal preference and I've been using BSD since 4.1 on a vax. I still think 32v was near perfect.
- yubiox 7y agoIt has been a couple of months since I messed with it, but I don't remember there being a way to do source based, weighted, or blackhole routes on freebsd.
- DeathArrow 7y agoWhile I like more FreeBSD than Linux, I say Linux is generally a better choice for servers. Better performance, better hardware support, more refined tools, easier to set up, and the list goes on. This is part due to popularity but mainly because what author hates: software written by companies willing to earn money in contrast to software written solely by passion. If it weren't for corporate money, Linux would be in a much poorer state. Neither one is ready as a desktop operating system. Linus Torvalds said that himself about Linux. Since FreeBSD lags behind Linux, it's safe to assume that is true for FreeBSD, too. Fast reading the author's previous articles on FreeBSD VS Linux, it's easy to see that it's dislike for Linux and praise for FreeBSD it's based solely on politics. He hates Windows 10 which he names an "horrible operating system" and now he hates Linux too. And that is just because Linux has big contributions by companies willing to gain money, in contrast to software written solely for passion, which he deems much better. He even goes as far as state that technical merits matter much less than politics. That I regard as pretty immature. Now the author struggles to come up with technical reasons to pick FreeBSD over Linux. If he succeeds on that, that is for any reader to judge. Rants like the author's previous articles on Linux VS FreeBSD seem to make even Richard Stallman an reasonable man in contrast. Some developers, some companies are providing software for free, both as in "free beer" and as in "free speech". That means time and money. He thinks that he and other users are entitled to much more than that. He feels like he should say to others in what way should they contribute to free software.
- goodcanadian 7y agoNeither one is ready as a desktop operating system. This is a particular bugbear of mine. If Linux isn't ready as a desktop system, how is it that I have been using it as such for 15 years? I get that it isn't all things to all people, but it has long fulfilled my needs; I've always been able to find a good quality tool for any task I want to do. Generally speaking, I'm happier with Linux than Windows or Mac OS, though I'm sure familiarity is part of the equation.
- petepete 7y agoIt comes down to the hardware you choose. I'm using a 7th Gen Lenovo X1 Carbon. When I got it everything worked out of the box with Fedora. Without coming pre-installed, I don't see how it can be readier. Of course if you buy a machine with exotic hardware (cough Broadcom) then it'll be a pain.
- jedberg 7y agoI prefer BSD because I find managing kernel modules and system startup much more straightforward. I also like that the placement of different kinds of files is much more standardized, which makes them easier to find and it also makes it a lot easier to manager a cluster of developer machines where each dev has different needs, because you can still be reasonably sure that all of their customizations will be in /usr/local. The other thing I'll throw out here is that Netflix chose BSD for their base system on OpenConnect because they were unable to get Linux to match the networking performance of BSD when delivering large files.
- peter_retief 7y agoI am running both at the moment but I must say that I am warming more to FreeBSD, reminds me of the early Linux days, before the systemd wars.
- gorgoiler 7y agoThe distinction between /etc and /usr/local/etc is the headline fact here. As a sysadmin, your goal for long term stability is to separate the important bits from the volatile bits to stop them from treading on each other’s toes. Separation of the core OS from the services it is running is the key to keeping a hygienic separation between components sharing the same file system. Debian — of which I was a long time fan — solves this by having a culture of pretty neat gardening, keeping each package separate in /var/spool/foo, /etc/foo, /usr/libexec/foo, but not /usr/sbin. But it’s all so old fashioned now that we live in the utopia of (1) machines that are spun up and then deleted automatically and (2) LXC means I have a fleet of “hosts” providing ns0.domain ns1.domain, mx.domain, www.domain, db01.int.domain all as containers on the sanctity of a relatively unchanging base host, analogous to packages installed on the sanctity of the FreeBSD base operating system, and all edited as config files that can rebuild everything except the /data and /log directories in a matter of minutes.
- IshKebab 7y agoIt only sounds like a partial solution really. You'll still end up with a load of random files in `/usr/local/etc` and unless you maintained a 100% strict policy of only installing using Ports (yeah right) you will eventually get some files of unknown origin. The proper solution is proper separation of app files, as found on Mac (more or less), NixOS, Android and iOS. I guess FreeBSD is still stuck in the 90s with Linux (except NixOS).
- mrighele 7y agoI always thought that /usr/local in FreeBSD was meant only for ports, not for custom software, and that is supposed to go in /opt. In any case I agree with the need of proper separation of app files. If we could adapt a bit the base tools of the OS, I think we could get there at least half-way there easily. For example if I could write something like PATH=$PATH:/opt/*/bin I wouldn't need to symlink every custom binary that I install (and similarly for man pages, service files etc.)
- danieldk 7y agoThis The thing I dislike about this kind of article is that they contain enumerations of relatively small deltas between systems. Things that you can bicker over for hours ("look, FreeBSD has better ZFS support", "but FreeBSD is actually rebasing on ZFS on Linux"). But they do not matter that much in the end. FreeBSD does not provide any meaningful changes compared to Linux that will convince most Linux users; and vice versa. These discussions usually boil down to some form of tribalism. For me the excitement is in projects that radically change FLOSS systems, addressing their shortcomings. For example: - Docker, despite its shortcomings, drastically changed how software is deployed in most companies (most FreeBSD folks don't seem to get this, it's not about "we had jails earlier", it's all about the ease of packaging/deployment). - Nix and Guix completely change package management, by treating packages as values built by pure functions. Allowing using several (isolated) versions of packages in parallel, reproducibility, per-project environments, fully declarative system configuration, atomic upgrades/rollbacks. - Fedora Silverblue takes Fedora, but changes it to a stacking of OSTree snapshots, providing a largely read-only root filesystem, with atomic upgrades and rollbacks. Applications are installed through Flatpak. Development is done through rootless containers with Podman. Not all of these projects and ideas may end up being adopted industry-wide, but they explore exiting new directions in packaging, system management, etc. Which to me is far more interesting than bickering over which kernel is slightly better in which use case, or separation between a base system and third-party ports which don't solve the 99 problems in packaging that actually matter (such as: this old project needs an ancient Boost version and in my 'global FHS namespace' package manager having two versions of Boost is conflicting). I am currently using NixOS and Nix on Mac, but I am also actively tracking Guix and Silverblue because these projects are so damn exciting.
- drosan 7y agoThese are hardly "reasons", more like "the list of comparable freebsd analogues of some common tech solutions implemented in gnu/linux".
- perlgeek 7y agoI'm kinda confused. The author berates Debian for patching many upstream software packages to conform to "the Debian way", and then says: > The kernel and base system is completely separated from the third party applications and base system configuration goes into /etc while all third party configuration goes into /usr/local/etc. Doesn't that mean that FreeBSD has to patch all third-party software to look for its configuration in /usr/local/etc, creating a "FreeBSD way" that is just as much at risk as breaking upstream software, making its documentation not apply etc. as the Debian software? Or is there a real, technical difference that makes one kind of modification less intrusive than the other?
- Carpetsmoker 7y agoMost software can be compiled with --prefix=/usr/local, and then it will store stuff in /usr/local/share, /usr/local/etc, and so forth. In fact, /usr/local is actually the default for a lot of programs; you manually have to specifically --prefix=/usr if you want to use that. I used to maintain a bunch of FreeBSD ports, and whenever this wasn't supported I'd send a patch upstream, which was pretty much always accepted. In a few cases: yeah, you'll have to patch the paths, which is not ideal, but it's a lot less patching than what Debian does, which often has more changes and backports security fixes etc.
- icedchai 7y agoWhen you build a package from source with ./configure, it generally defaults to /usr/local/etc. Oddly, the Linux way of putting all third party configs in /etc is actually what's weird.
- throwaway2048 7y agoConsidering most unix software is written on linux for linux these days, and has been for many years, its extremely unlikely what you say is true.
- icedchai 7y agoTake a look here: https://www.gnu.org/prep/standards/html_node/Directory-Variables.html https://www.gnu.org/prep/standards/html_node/Directory-Varia... "The default value of prefix should be /usr/local" On traditional Unix systems, /usr was reserved for the operating system. /usr/local is 3rd party software. This is how Solaris behaves. This is how the BSD's behave. The Linux approach is the exception, not the rule.
- giantrobot 7y agoIn a perfect world I'd probably use FreeBSD in all the places I currently use Linux. I however don't live in a perfect world so I haven't used FreeBSD for anything significant in over a decade. My number one problem with FreeBSD (and OpenBSD) has been hardware support. I got an HPE Microserver to use as a compact centralized storage. No matter what I could not get FreeBSD even booting on the machine. It's got an AMD APU and apparently FreeBSD has zero support for it. With Ubuntu I had zero installation issues and still got to use ZFS for storage. Similarly I have a SFF AMD box to use as a router. While FreeBSD would boot on it, every few weeks it would kernel panic and need to be power cycled because FreeBSD shit the bed with the Ethernet cards in it. Ubuntu with the same exact usage patterns has given me absolutely no trouble. I've never been able to get FreeBSD fully working on a laptop. Something is always broken (usually WiFi) and power management sucks. It's also entirely inconvenient to have to power down the laptop because it won't wake up when opening the lid. My second major problem has been a lot of seemingly advanced features in FreeBSD are very experimental or simply difficult to use properly. While FreeBSD's Jails are very sophisticated they are a pain in the ass to manage and there's multiple management tools available with wildly different levels of functionality. I want FreeBSD to exist and keep pushing forward but I've given up on using it. None of its technical features can make up for the fact it won't run or run well on hardware I actually own. Advanced features don't mean much to me if I can't use them effectively. I'm not developing FreeBSD (or Linux), my interest in them extends about as far as launching other pieces of software I want to use or that I'm writing. I'm not typically pushing the limits of the systems so interesting optimizations around edge cases don't mean much to me. I don't get paid to support myself or my personal projects so I'm just going to go with the system offering the least hassle. That hasn't been FreeBSD since the 4.x days (compared to contemporary Linux distros).
- non-entity 7y ago>It's got an AMD APU and apparently FreeBSD has zero support for it. When's the last time you tried. I don't remember if I've run FreeBSD on it, but I have a cheap board with an AMD APU that's run NetBSD within the last year. > I've never been able to get FreeBSD fully working on a laptop. Something is always broken (usually WiFi) Yeah WiFi support is super shaky seemingly across all BSDs. I had to make a small patch to an existing kernel driver to get it to work with one of my Realtek cards in FreeBSD. To my knowledge the same card will cause panics in NetBSD when the driver is attached and I have an Intel WiFi card broken in DragobflyBSD.
- pjmlp 7y agoAnd in UNIX tradition, zero reasons for anyone that cares about graphics and multimedia.
- peter_d_sherman 7y agoExcerpt: "With jail it is possible to create various virtual machines, each having its own set of utilities installed and its own configuration. This makes it a safe way to try out software. For example, it is possible to run different versions or try different configurations of a web server package in different jails. And since the jail is limited to a narrow scope, the effects of a misconfiguration or mistake (even if done by the in-jail superuser) does not jeopardize the rest of the system's integrity. Since nothing has actually been modified outside of the jail, "changes" can be discarded by deleting the jail's copy of the directory tree."
- _paulc 7y agoI've been a FreeBSD user since 2.05 (1995) and a strong supporter - FreeBSD still excels as an ultra-stable 'old-school' UNIX server OS (which to be honest meets a lot of use-cases more simply than a lot of modern alternatives). That being said this sort of post isn't helpful as advocacy - as others have notes it is pretty shallow and to be honest most people are probably better off running Linux if this is what they are used to.
- ncmncm 7y agoUltimately, when we are being honest, there are no technical reasons to prefer FreeBSD. Or Linux. Both work. You can probably build whatever you need to on either one (with a few exceptions, e.g. AMD) and both will work about as well. There are differences, but the importance of each difference is a matter of preference, environment, and history.
- henvic 7y agoLicensing should also be considered a technical reason. - Shameless plug: a few years ago, I fought the decision of my former employer's licensing counsel. He had ties with FSF Europe, and asked me to relicense my code from BSD to LGPL before publishing it (was private). I vehemently objected and asked to keep my code private instead – on the grounds of permissiveness and technicalities. They conceded. Two years passed, and I got in touch with the company and had the software released using BSD. I share a few details of my reasoning here: https://medium.com/@henvic/opensource-and-go-what-license-f6b36c201854 https://medium.com/@henvic/opensource-and-go-what-license-f6...
- AsyncAwait 7y agoLicensing should absolutely be considered. In fact copyleft is one of the main reasons I'd go with Linux over BSD anytime. If I am going to invest my precious free time into software development, I want to guarantee to my users that my software will always remain free, (as in freedom). There's also a community aspect to the BSDs that I strongly don't align with, which is the sort of 'practical, above the fray' mentality that seems to disregard all political/real-world happenings around privacy, encryption, patents, censorship etc. and instead focus purely on the code. To the point of praising any piece of closed-source that has a bit of BSD in it. While this is perfectly valid short-term, I do think that a movement that goes beyond code and has some ideological foundations is needed.
- tomxor 7y ago> I want to guarantee to my users that my software will always remain free [...] I always found this argument for GPL a little uncomfortable because of what it implies... let's be more precise: the existing code you publish whether using GPL or BSD will always remain free (it is irrevocably free); copyleft makes a distinction for freedom of derivatives i.e GPL forces people to make all future code free as well, this is about enforcing future investment not remaining free. To be clear I'm not dogmatic about either, I think both copyleft and permissive licenses have their place - it's simply subjective - some software feels more suited to GPL and others more suited to BSD.
- 7y ago
- AsyncAwait 7y agoWhat I dislike about these sorts of articles is that they try to pretend as if *BSDs weren't heavily dependent on the wider FLOSS community, which is mostly Linux-based. They instead focus on minuscule differences, which you could maybe argue are a bit better from a design perspective, (the default file system layout for example), but in practical terms matter little. On the other hand, they don't mention the fact that the reason OpenBSD is so "secure", is because their marketing focuses on the default install, which has almost nothing. So the moment you install the minimum amount of packages to get your work done, the "only two remote holes" thing no longer holds. When you point out the practically abyssal modern laptop support in FreeBSD, they just shrug because "macOS's also BSD". Then there's the whole smugness towards Linux as if they weren't dependent on GCC for years, as if GNOME/KDE etc. wasn't a primarily Linux effort and as if ZFS was somehow their invention. They'll sing about BSD Jails and how Docker is strictly inferior, (also ignoring LXC), while not having any even remotely equivalent frontend for BSD Jails. They'd laugh at the systemd debates, while talking openly about maybe them doing something similar. Now Linux also heavily depends on some parts of BSD, but you'd see hardly anybody thrashing OpenSSH, just because it's BSD. It's just not a community I want to be a part of, that's before I get into the whole BSD vs GPL debate, but I do understand that the appeal is there for some and that's perfectly fine.
- sbuk 7y agoFor what it’s worth, we see this level of “smugness” from GPL proponents everywhere. Especially the self-superiority. It’s what puts me (not that that has a massive impact on what anyone thinks!), and I’m sure others, off being part of the Linux community. In truth, what we are both seeing is a minority of loud voices that force their opinions, often as fact (this article being an excellent example), onto the world at large and taint it for all concerned. Freedom, especially of speech should never be expressed as a right. It’s a privilege that is all to often abused.
- robertlagrant 7y ago> Freedom, especially of speech should never be expressed as a right. Wow, an attack on free speech! Luckily you're allowed to voice it with no repercussions.
- stefantalpalaru 7y ago> The FreeBSD Ports collection is an amazing feat of engineering. No, it's an ugly hack that somehow remained unchanged. Look at Gentoo Portage for a better implementation.
- hkt 7y agoI don't disagree, but are there business reasons to do it? As far as I can tell there aren't, but there are good reasons not to, such as hiring and support. Are there any people here who could make a business case as well as a technical case? I'd be fascinated to hear it.
- netmonk 7y agoWho care about OSes, when you have container, and VM ?
- DCKing 7y agoThis is a good list for differences between FreeBSD and Linux distros, but describing them as advantages FreeBSD has over Linux seems problematic to me. Except for firewalls and core documentation (but what about "community documentation"?) nearly every item is highly debatable whether using FreeBSD has an advantage in the first place, and many I would argue Linux has obviously better options for [1]. To me, lists like this sadly highlights that FreeBSD has extremely few unique selling points left. I accept its superiority for network infrastructure type roles, but that's about it. As a Linux user, there's nothing on this list that makes me consider switching [2]. [1]: Anything to do with package management, containers and VMs and even filesystems Linux system can either do better out of the box or can easily be augmented if you need it. I also think systemd is better than shell script based inits. But there's a reason this is a footnote, this is not the thing I want to argue here. [2]: Besides it taking effort to switch, FreeBSD has the additional problems that it has poor hardware support for desktop usage (PLEASE get your wifi act together), and software support is also substantially worse - with FreeBSD lagging behind with stuff like Electron, Wayland, desktop virtualization and desktop containerization (Flatpak, Snaps, Appimage even). The point here isn't these details, but FreeBSD winning over Linux people is an increasing uphill struggle.
- deleted 7y ago[deleted]
- rvz 7y agoEven as an occasional Ubuntu user, it's already an effort for even some desktop developers to use GNU/Linux given that Windows and macOS are actually being sane desktops just to get work done. I just can't see any user wanting to use or switch to either Linux or BSD to sanely 'use' their computer for being productive in their daily work other than programming in vim or emacs; because they are still desktops for programmers. The BSDs now have the same Linux desktop argument of having 'choice' which has made it a blessing for its tinkerers and a curse for commercial desktop app developers as highlighted in [2]. You have 3 ways to package an app, many desktop environment choices like GNOME, KDE, Xfce and the windowing managers like X11, Wayland to test for and you then ask why your favourite software application isn't on X Linux distro or X BSD distro. I won't be looking forward to testing or bug hunting for my GUI app on either system since their desktop stacks aren't integrated well or have a stable 'SDK' unlike with Windows and macOS. GNU/Linux and the BSDs are pretty much still fragmented ecosystems. The BSDs in particular will always be behind, since the same developers who have always used Linux and were part of the FOSS community are the same ones that still contribute and pushed for it in their companies like Google, Facebook, Microsoft and Amazon, etc. Thus, some will only accept upstream patches for Windows, Mac and Linux. The BSDs will then be left in the sand with atrocious software support and their patches will be rejected as the maintainers will be unwilling to upstream these patches due to this.
- lllr_finger 7y agoMost of these points are debated in Brendan Gregg's "Solaris to Linux Migration" blog post from 2017: http://www.brendangregg.com/blog/2017-09-05/solaris-to-linux-2017.html http://www.brendangregg.com/blog/2017-09-05/solaris-to-linux... The only point of Brendan's that I don't agree with is ZFS as it really doesn't have a strong competitor (yet). Thankfully, it also doesn't need to be on every machine - my desktops/laptops/deployed servers are treated like cattle not pets. I love FreeBSD/OpenBSD's simplicity and principled design, but I've sadly relegated them to specific purpose servers at work and at home because I kept hitting enough speedbumps that IMO preclude them from being used in a more general sense.
- cassepipe 7y agoWow it really sounds like FreeBSD is the-right-thing to choose. Except I can't tell anyone I know to install it because it does not come with a simple installer or a working desktop. I got interested in Windows because I grew up with it, and only later I got curious of how it worked behind the scenes. When I first installed Linux I had no idea on how to use the terminal, what a package manager was, compile programs or even what a DE was. I learned it because I was able to install it on my machine in less that an hour. It doesn't matter how good your train engine is, if it ain't got no seats, people won't come aboard. https://en.m.wikipedia.org/wiki/Worse_is_better https://en.m.wikipedia.org/wiki/Worse_is_better
- Koshkin 7y agoFreeBSD used to be a Swiss watch of an OS - I used 4.8 (IIRC) to run a VPS for a few years and couldn't be happier; nowadays, looks like FreeBSD is on par or even lagging behind Linux in all respects.
- znpy 7y agoTechnical reasons to choose gnu/Linux over freebsd: I can choose among one of the top distros, boot the installer on my laptop and most (if not all) the hardware will be detected and will work properly.
- jesse_m 7y agoIs the ports system similar to Gentoo's portage/ebuild system? I can get sources, configure the build, or get binaries (for some things) pretty easy through it. The QA with the build farm would be nice though.
- sam_lowry_ 7y ago"...there isn't such as thing as "the Arch way". The Arch Linux distribution want third party software to be as upstream has made them, so they do not change anything unless absolutely necessary" Gosh! This is exactly how I feel about Arch. And FreeBSD seems consistent until you step outside of the base, and then, it's just a pain in the pass, because so many software nowadays is build on the assumption of running Linux/bash/gnu textutils, etc.
- INTPenis 7y agoI know people who insist on using FreeBSD, or worse OpenBSD, and they often have issues with their work systems. This is unacceptable to me. My work system must work. So I don't care about your theoretical list because I know for a fact that Linux is better for me in practice.
- ori_b 7y agoI keep fixing my colleagues Linux issues. In practice, I have spent less time fixing my own BSD systems. I usually end up stuck with Linux systems at work because of proprietary code which doesn't run on BSD.
- CIPHERSTONE 7y agoMy frustration with BSD is in the desktop arena when wanting to use a laptop. Want to use modern laptop hardware? Good luck. I get that this use isn't the core that BSD focuses on, but seriously, it's a huge potential market for people that want a secure/stable system. Right now you either need to use extremely old hardware (Thinkpad T60 era) or face many obstacles. Which is a pity.
- davisr 7y agoThis is a lie: no you don't need to use old hardware. I use a Thinkpad X1 Carbon (5th gen) and everything sans-fingerprint-reader works perfectly with FreeBSD 12.1, entirely built from source and ports. The trackpad even works buttery smooth, with inertial scrolling using the Synaptics X driver.
- jccalhoun 7y agoFunny coincidence. Last night before I went to sleep I was looking up the differences between BSD and Linus.
- otterpro 7y agoOnly thing that is holding me back from using FreeBSD (and other BSD) is hardware compatibility. Linux supports far more hardware devices, such as SATA controller/HBA and network cards, it seems. I've used FreeBSD (and other BSD) and it was really pleasant to see a well laid out and well thought out OS, unlike Linux which felt like a collection of after thoughts.
- rooam-dev 7y agoLong time "intermittent" FreeBSD user here. I always liked the naming (e.g. NICs) and location of things in FreeBSD, felt more natural to me. It may not be a (good) technical reason, but it makes live so much easier when you know that if I install something it's in '/usr/local'. That said, not sure if it's fair to compare FreeBSD (1 distro) with Linux (many distros).
- xyproto 7y agoIn the context of PF: > Logs may be monitored using standard utilities such as tcpdump. This sounds unusual and not entirely practical?
- jeffrallen 7y agoIn 2000, I was working on a large Solaris x86 system. It was a daily struggle to get and keep anything at all working. I needed a VNC server to hold state across laptop crashes, sleeps, wifi glitches, etc. I chose FreeBSD because I just needed one thing in my work life that actually worked. I loved it then, and I'd choose it again today.
- gurleen_s 7y agoThe moment I stopped caring about these arguments is the moment I got a little more happiness in my life.
- passthejoe 7y agoIf you really like Windows and/or MacOS, you will probably be disappointed in the desktops available on Linux and FreeBSD. But the opposite is also true. After years running Xfce and GNOME in Linux, I went back to Windows 10. First I had to replicate my workflow, which meant using a lot of programs that could be run on any system. Then, aside from the Microsoft updates and all the problems they cause, the total lack of package management for applications makes even more work. I had WSL, and that is great, but running a terminal in Linux (or MacOS, even) is just easier when everything can be accessed by any program in or out of the console. Eventually I realized I was fighting Windows with little upside. I got an M.2 SSD, installed Debian Stable (after 2 years of Windows, I REALLY didn't want a lot of updates), and everything is running great. If you depend on Microsoft Office and/or Adobe Creative Suite apps, that's a reason to prefer Windows or MacOS. Otherwise, you can do very well — and maybe even better — with the Linux desktop of your choice. My current laptop is three years old. GNOME 3 runs great. It's extremely responsive, and I like the way it works with the "hot corner," super key and desktop search. I use a few GNOME Shell Extensions, but not too many. I really don't understand why developers are so enamored with Apple. Unless you are developing for Mac or iPhone, a good Linux distro, or even Windows 10, seems to be a better if not equal choice. I managed to get my hands on an iMac, and I set it up to see how I'd like MacOS. Getting it "right" was harder than Windows, and I was really surprised at how super slow Homebrew could be. It really made me appreciate Debian's apt — and even Fedora's dnf. Mac's Finder doesn't compare well to Windows' File Explorer (is that what they call it?) or Nautilus/Files in GNOME. One thing Windows 10 and MacOS do well is support HD and UHD screens without fiddling. Linux desktop developers need to finally realize that HD (1920x1080) is now the baseline, and 4K-ish resolutions are common and should be completely supported out of the box. My comfort level with Linux is high, and when I spend most of my time in the same web browsers, in addition to the file manager and text editors, it made sense for me to switch back. Windows is too much work with too little upside.