3 ms·
The article is an "ok" intro to the differences between Linux and BSD, but it stays at a pretty high level (and makes it clear that it wasn't intending to go in
by ghshephard 16y ago
The article is an "ok" intro to the differences between Linux and BSD, but it stays at a pretty high level (and makes it clear that it wasn't intending to go into anything more detailed than "principles/design/philosophy"
The article is dated though - it predates GIT, and still refers to the odd/even devel/production numbering in linux, which went out of vogue a couple years ago (at least)
It is, of course, not entirely accurate when discussing BSD as consisting of a system that is designed with all its "core" components by the BSD system. Some of the "base" stuff in BSD is actually still from outside the tree. For example, rtadvd, the IPv6 Router-Ad daemon, originally came from the WIDE Hydrangea IPv6. The rtadvd.conf files, in Open BSD, aren't the elegant/simple OpenBSD standard, but instead use the termcap(5) format. OpenBSD's approach to situations like this is to use the software until someone is inspired to build an "OpenBSD from the ground up" version, rather than mess around too much with upstream contributions to make them look more "OpenBSDsh"
We use OpenBSD a lot where I work - its firewall, and routing configurations are rock solid. And configuring the systems is a dream. I far prefer the OpenBSD /etc/hostname.if approach to the various /etc/sysconfig/network-scripts approach that various RHEL releases have taken (and changed between releases).
For some reason, 95%+ of our deployed systems (around 500) and our target for application development, is Linux though. Probably because there is no equivalent of RHEL/SUSE in the OpenBSD world.