8 ms·
Great guide. It tells me how. Is there a similar document that tells me why? The main thing I can think of is kqueue, but I'd love to see a list of all the fea
by yummyfajitas 16y ago
Great guide. It tells me how. Is there a similar document that tells me why?
The main thing I can think of is kqueue, but I'd love to see a list of all the features BSD gives me but linux doesn't (and vice versa).
- silentbicycle 16y agoRelevant previous discussion: http://news.ycombinator.com/item?id=1569559 http://news.ycombinator.com/item?id=1569559
- gbrindisi 16y agoOne big reason should be ZFS. And the ports. I love ports.
- yummyfajitas 16y agoHow do BSD ports differ from apt/yum?
- kroger 16y agoWith BSD ports you compile the packages. The advantage is that you can select the compilation flags and choose dependencies and options. For instance, want to build emacs without X support? Just run WITHOUT_X11=yes make install clean. With apt you typically have packages like emacs-nox for special cases.
- eru 16y agoSounds like Gentoo's system to me. (And, of course, my BSD-loving friends hold Gentoo to be the most bearable Linux.)
- superjared 16y agoGentoo effectively copied FreeBSD's port system.
- apotheon 16y agos/effectively/ineffectively/
- superjared 16y agoTouché :)
- SwellJoe 16y agoAnd they both suck. ports and portage are horrible excuses for package management.
- swolchok 16y agoThat's why Gentoo's system is called Portage.
- xiongchiamiov 16y agoOr Arch's ABS, to a lesser extent.
- apotheon 16y agoThere are a lot of reasons. The ports system has already been mentioned, and some people really like ZFS. More to the point, though, licensing differences ensure that more software (like ZFS) is legally compatible with FreeBSD than with any typical Linux+GNU distribution. It has also been mentioned that FreeBSD is "a sysadmin's dream". A big part of the reason for this is its userland. The truth of the matter is that BSD tools are often much more consistent and less overly complex, and have better thought out basic functionality and interfaces, than GNU tools. BSD Unix systems also resist the influence of the GNU project where many Linux distributions do not. For instance, in some distributions you will find far too many pieces of software that have nothing for man pages except a reference to how the real information is in a GNU Info page. The GNU project very much as a "not invented here" problem, where it not only wants to replace everything in the world -- even when it's "free software" -- with something weird and less usable that bears the GNU stamp on it. Meanwhile, the various BSD Unix systems insist on standardized tools and documentation that is easy to use, like man pages instead of Info pages. Speaking of documentation, that's another good reason to use FreeBSD (or OpenBSD, for that matter). The big BSD Unix systems are among the best-documented OSes I have ever seen, and I have seen quite a few operating systems. Consider the completeness and helpfulness of the FreeBSD Handbook, which is actually one of the best pieces of documentation on the Web even for many Linux distributions, but is even more helpful for FreeBSD (of course). Also . . . this is not comprehensive, but it might serve as a nice introduction to the whys and wherefores: http://www.over-yonder.net/~fullermd/rants/bsd4linux/bsd4linux1.php http://www.over-yonder.net/~fullermd/rants/bsd4linux/bsd4lin... I wrote a comparison as well, once, but I seem to have misplaced it.
- Nick_C 16y agoAlso, (I haven't run a BSD for several years, but, from memory) one of the biggest philosophical differences is that *BSD runs a monolithic kernel whereas Linux runs a modular kernel. Might not sound like much, but it is very different mindset when it comes to security, user-land and such. Is that still the case?
- koenigdavidmj 16y agoAll three of the major BSD derivatives have the ability to put parts of themselves in modules. They are all monolithic kernels, as is Linux. Monolithic, in kernel speak, does not refer to having everything compiled in; it is more concerned about what is in kernel space (can do anything it wants with the hardware) and what is in user space (what is restricted at the hardware level to playing in its own memory). Monolithic kernels have pretty much everything in memory, and microkernels have pretty much everything in moderately-privileged userspace processes that talk to each other via message passing.
- bapadna 16y agoIn my experience, FreeBSD's greatest asset doesn't fit well on a feature list. It's that it has a different attitude towards change than Linux. Linux is a diverse ecosystem, with tons of experiments driving it forward. Different package managers, different kernel patches, different userland configurations, different means of administration... and that's a great thing. FreeBSD is not diverse or experimental. FreeBSD is a deliberately moving beast, that adopts technologies and ideas in a more methodical manner, often after other OS's (OpenBSD / NetBSD / DragonflyBSD / Solaris / Linux / OS X) have proved that the ideas are solid, and lasting, and then it integrates them carefully, so it still looks like FreeBSD (but with some new capabilities, or better performance, or whatever), rather than having drastically different administration mechanisms, or performance characteristics, or anything else. Personally, I like this stability. I like that it's a platform that once learned, can be largely forgotten about. But that said, it does require learning first, and while it's powerful, it's not shiny or sexy. But even excluding the man pages and documentation, zfs, the pf firewall, and many other things I like about FreeBSD, this is the winner for me. I just love that it doesn't change unless the change is a large win.