5 ms·
(Speaking as a FreeBSDer here -- I'll let NetBSD and OpenBSD folks cover those, since I don't follow them closely enough to offer accurate comments.) 1. We don
by cperciva 16y ago
(Speaking as a FreeBSDer here -- I'll let NetBSD and OpenBSD folks cover those, since I don't follow them closely enough to offer accurate comments.)
1. We don't let licenses get in the way of making good technical decisions. This means that, for example, we had no problem with importing DTrace and ZFS.
2. We have more of an emphasis on doing things right. This often means that it takes longer before we acquire new features; but it means that once we acquire new features, they work and aren't likely to be removed or completely rewritten any time soon.
3. We develop the kernel and userland in tandem. This allows new features in the kernel to be accessed from userland faster (usually immediately) whereas in Linux there will often be a significant lag time before your libc supports everything in your new kernel.
4. We have stable development branches, and we're serious about them. Not "stable" in the linux kernel sense of "we think this won't crash" -- stable in the sense of APIs and ABIs, so that code you compile on FreeBSD 8.0 will work without recompiling on FreeBSD 8.4 five years later.
5. Our stable branches apply to the kernel, too. You can compile a kernel module for FreeBSD 8.0 and use it on later versions of FreeBSD 8.x, too -- linux, in contrast, has on occasion broken kernel ABI compatibility in security patches. ("Gee, do I want to apply this security patch, or do I want to keep using the video card driver supplied by my vendor?")
6. Personally I greatly prefer the FreeBSD ports tree over the linux equivalents, but that's just a matter of taste and what you're used to.
- tedunangst 16y agoMost of that applies to OpenBSD as well, except we did let licenses stand in the way of importing DTrace and ZFS.
- konad 16y agoAnd the Plan9 compilers, the OpenSD team wanted to lose GCC and were considering the plan9 toolchain. Turning Plan 9 from open source into Free had plenty of teething troubles, getting the lawyers from Bell-Labs then Lucent then Lucent-Alcatel into the idea took years. Originally Plan 9 was paid for software with full source included. Then from v.3 it was a free download but with its own license which included a "if you make modifications you must send your changes back to Lucent". Then it was lobbied for change and to comply with US munitions law Lucent included the export restrictions proviso OpenBSD's Theo so eloquently argues against : http://groups.google.com/group/comp.os.plan9/browse_thread/thread/d23e576bf06efdfb/84670c239a7f3684 http://groups.google.com/group/comp.os.plan9/browse_thread/t... Ironically the compiler suite became available under GPL / MIT via Vita-Nuova who bought the rights to Inferno. Licensing helped keep Plan9 away from developers at exactly the same time GNU/Linux and OSS exploded on to the scene in much the same way early adopters got interested in GNU/Linux it during the BSD / AT&T lawsuit. How our computing landscape would be different if we all valued freedom.
- vdm 16y ago+1 insightful. Huge missed opportunity.
- SageRaven 16y agoI've used FreeBSD for servers and my personal workstation for quite a few years. I love FreeBSD, and the thought of having to support a Linux variant is not a pleasant one. Not that I have a bone to pick with Linux, since I thought it was an excellent OS for the 10 or so years I used it before trying FreeBSD. But once I tried, and became accustomed to, FreeBSD, there was simply no turning back. However, I take issue with your #1 bullet point above. If the FreeBSD camp truly was about the technical stuff, we wouldn't be stuck with a crusty, substandard version GCC in the base system. For those not in the loop, the last GCC version with a GPLv2 license was 4.2.1 (from 20070719 according to "gcc -v" on my 8.1 machine). Due to not liking the GPLv3, the FreeBSD developers have stuck w/ this old GCC version, denying users the current set of optimizations and architecture support. Sure, we can use GCC from ports, but that's not officially supported for the base system or the ports tree. True, they're working on getting the clang LLVM front-end to be the official base system compiler, it'll be 5 to 10 years before it's as stable and usable as gcc is today. But that is about my only gripe with FreeBSD, and as far as gripes go, it's a relatively minor one.
- avar 16y agoYeah point #1 is odd. GNU/Linux doesn't let licenses get in the way of technical decisions. DTrace and ZFS aren't in Linux because Sun explicitly designed their licensed to be GPL-incompatible. Where that isn't the case nobody is seeking to replace code due to license reasons. E.g. you don't see Linux people trying to replace X11 or Sendmail because of their licenses. But the BSD systems are actively trying to phase out GPL licensed code due to not liking the license.
- jrockway 16y agoExactly. I always read BSD discussions and think "what a bunch of licensing fanbois". I guess since the OS and the license have the same name... Anyway, here's why I support Linux and the GPL: the WRT54G. Linksys would have never released the source code for the router's kernel without being forced to. But when they did it, an amazing thing happened, third-party developers made their product one of the most popular wireless routers ever. With open source, everyone benefited -- users got better products, hackers had fun, an d Linksys made more money. If Linux was BSD-licensed, the WRT54G would be a long-forgotten relic of the past.
- njharman 16y agoI'm not trying to be argumentative, trollish, etc. But, really none of those are very compelling and a couple are negatives. I can see 3,4,5 being important if I developed software that is directly affected by any of that. 1 is a political argument and one that I stand on other side of the fence on. 2 just sounds like it takes longer for stuff to be released. 3 meh. 4,5 extra meh. Recompiling is so trivial that not having to recompile is a non-feature. 6. I never groked ports I might not hate it if someone explained it to me. OTOH rpm and apt made sense from reading docs. My point is, isn't there anything else? Cause if that's it, I totally understand the respective "market share" FreeBSD and Linux have. btw I've used OpenBSD for public facing firewalls way long ago cause it's security emphasis was a huge feature over Linux.
- cperciva 16y agoBut, really none of those are very compelling and a couple are negatives For you, that might be entirely true. We're not fanatics; we have no trouble accepting that for some people FreeBSD isn't the best OS for every task. There are FreeBSD developers who are perfectly happy using Linux, OS X, OpenSolaris, and even Windows on a daily basis.
- palish 16y ago[Taking more time to develop features correctly] just sounds like it takes longer for stuff to be released This attitude demonstrates a pretty significant lack of experience.
- caf 16y agoPoint 4 applies as much in Linux as it does in FreeBSD. I've got binaries I compiled against 2.0 and 2.2 kernels in the mid to late 90s that will still run on 2.6 kernels today. Stable userspace ABIs are something that everyone agrees on.
- dochtman 16y agoFWIW, and I realize not everyone likes it, but Gentoo goes a long way towards making Linux package management more like BSD ports (AFAICT; haven't used *BSD much). I really like that Gentoo encourages me to build my own (lean) kernel and allows me to pick what configure flags each package gets (instead of giving me packages that include everything out there, like in the .deb distributions).
- adbge 16y agoArch Linux allows for ports-style package management with their Arch Build Service. It's more similar to the BSDs, in my experience, than Gentoo.