3 ms·
This article makes several misstatements or factual errors, unfortunately. > What I failed to realize back then was that FreeBSD was (and it still is) designed
by loeg 7y ago
This article makes several misstatements or factual errors, unfortunately.
> What I failed to realize back then was that FreeBSD was (and it still is) designed as a complete multi-purpose operating system meant to be setup and tuned according to specific use cases.
IMO, if it needs to be manually tuned, that's a bug, not a feature. (And I'm speaking as a FreeBSD developer on that.)
> FreeBSD sets the kernel and the base system apart from third party packages. This is unique to FreeBSD and none of the other BSDs do that.
Um, nope, this is how all of the BSDs do it.
> FreeBSD is installed only with the features you enable and nothing is running that you don't know about.
sendmail, cron, and ntpd run out of the box, to name a few.
> The FreeBSD code is meticulously maintained and very well documented.
Not really (especially in random drivers) and usually not (in the code, anyway). We have pretty decent manual pages.
> The FreeBSD rc system that reads this file understands dependencies between services and it can automatically launch them in parallel, or wait until one is finished before starting the things that it needs.
The parallelism part is not true.
> I believe it is important to understand that FreeBSD is not like a GNU/Linux distribution.
Not really true? In a lot of ways FreeBSD is like a GNU/Linux distribution; it just happens to bundle the equivalent of coreutils, binutils, gcc, etc with the kernel.
> FreeBSD is an operating system made by developers who are also system administrators.
Definitely not true (or at least, in no respect different than the developers of the broader Linux ecosystem).
> A Linux distribution is a collection of tools written by different groups of people, often with conflicting interests and priorities.
This is true! Especially for core bits of the system, like glibc and the kernel.
> A Linux distribution needs ..., additional third party software, the X Window System, a window manager, and a desktop environment, and it then needs to combine these different components into the resulting distribution.
This is of course no different than FreeBSD's ports system; we face the same integration challenges as Linux distributions.
> there are no conflicting interests in the [FreeBSD] project
Ha. ha. ha.
- jpeeler 7y agoAs a FreeBSD developer, perhaps you know what tunables are being talked about for specific use cases? Unrelated, I find it surprising that any major operating system these days need rebooting because "every third day or so otherwise the performance degraded a lot". Or maybe they just didn't increase the sysctl var kern.full_performance_days high enough ;)
- alacombe 7y agoI've been running Fedora for ~10 years (switching away from {Net,Free}BSD, I was fed-up to re-invent the wheel and the general poor design of the OS / high inertia of the community), and never rebooted once for "performance reason". My average uptime is in the couple of month, always for hardware / maintenance reason. Even my Windows 10 machines is never rebooted because of performance issue. I don't think I've had much system failure / panics either.
- toast0 7y agoI wouldn't worry too much about that claim. It seems like a poorly remembered claim about about a very old version. I'm sure somebody has the battlescars and could tell you what it was exactly. My guesses would be a memory leak somewhere, some yucky disk controller bug I didn't run into, or possibly the TCP LAST_ACK state accumulation https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=25986 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=25986 This has since been fixed, although it did take an annoyingly long time; but before it was fixed, you could address it by tuning socket buffers to be smaller --- it seemed to be less likely for clients to disappear with unacked data, but also, when they did, it wasn't as noticeable. Most things are tuned pretty well by autotuning these days though. If your work is more I/O limited than CPU limited though, tuning is more likely to be useful.
- loeg 7y ago> As a FreeBSD developer, perhaps you know what tunables are being talked about for specific use cases? There are tons of knobs and I don't set or know anything about any of them in particular, sorry. > Unrelated, I find it surprising that any major operating system these days need rebooting because "every third day or so otherwise the performance degraded a lot". Me too. I assumed the author was talking about some (awful) historic bug rather than an ongoing issue they're having. Kinda sounds like a kernel memory leak, but it could be anything.
- alacombe 7y ago>> A Linux distribution is a collection of tools written by different groups of people, often with conflicting interests and priorities. >This is true! Especially for core bits of the system, like glibc and the kernel. Come on, of course this is blatantly false. There is plenty of politics. I've experienced it first hand. FreeBSD developers are most definitively driven by some agenda other than the selfless "the common good". >> there are no conflicting interests in the [FreeBSD] project > Ha. ha. ha. My point exactly !
- loeg 7y agoI didn't try to say FreeBSD doesn't have detracting politics (I don't think I said that) — you're absolutely right; it does. My understanding, and let me know if I'm totally wrong, is that most glibc developers are not Linux kernel developers, and that most kernel developers are not glibc developers. In FreeBSD, I think there's more crossover of developers working on both userspace and kernel components. The monorepo design helps foster that (again, subjective, IMO).
- alacombe 7y agoThe monorepo is actually a downside as it weaken any form of backward compatibility one could legitimately expect. The general answer in these case "rebuild", but it completely ignores binary-only software which exists in the real world and which is to a large extend completely ignored by commiters. At some point, you want to spend CPU cycle on something else than "rebuilding world". Also, there is de-facto no competition, short of a hard fork, in the software shipped. You can't just "switch to uclibc" if an embedded platform has memory constraint.
- loeg 7y agoI don't know if you're familiar with FreeBSD's approach to backwards compatibility in general, or just making a general statement about monorepos. It doesn't seem like you're familiar with FreeBSD in practice; apologies if I guessed wrong. FreeBSD has strong backwards compatibility at the shared library level, across all versions. Support for BSD 4.3 (as in, 1986, pre-FreeBSD) compatibility is slowly being phased out in 2019. Grep around for COMPAT_FREEBSD, for example. This compatibility (for existing stable releases) is by and large maintained in the development branch. FreeBSD's also got a Linux syscall emulation layer, which implements (some of) the Linux kernel's (stable) ABI. > The general answer in these case "rebuild", but it completely ignores binary-only software which exists in the real world and which is to a large extend completely ignored by commiters. At some point, you want to spend CPU cycle on something else than "rebuilding world". That really isn't true. The point of the stable/ branches is the kernel KBI is stable for the lifetime of the branch. > Also, there is de-facto no competition, short of a hard fork, in the software shipped. Sure. But you can implement a patch and advocate for it against the existing implementation? Also, there is a lot of support for installing alternatives from ports. Doesn't seem that major of a gap.
- jedberg 7y ago> > FreeBSD is an operating system made by developers who are also system administrators. > Definitely not true (or at least, in no respect different than the developers of the broader Linux ecosystem). Maybe not so true today, but back when Linux first started, one of the main differences between Linux and FreeBSD was that BSD was written mostly by coders who worked as professional sysadmins, and Linux was written by coders who were mostly software engineers. That's why Linux had all the new features, and BSD had all the stability. Because sysadmins cared about stability more than features. It's sort of why their respective philosophies diverged. I know because I spent a lot of time in the late 90s with the core committers who had been working on BSD since the 70s and 80s at Berkeley. They were all sysadmins.