11 ms·
The trouble with FreeBSD
- Girlang 10y agoI like FreeBSD. We use it. The fact that some woman wants "FreeBSD" to police the Internet (not just the official FreeBSD communications channels) is a red herring. Ignore her.
- saurabhjha 10y agoI clicked on this expecting some technical stuff and all I got was this BS social/community whining. Well, even in the worst case where FreeBSD community is trash, they have one of the best kernel implementations and one of the best open source OS documentation.
- simias 10y agoI agree, it was a disappointing article. Even the technical section about source control at the beginning seems a bit odd. First they note how huge the codebase is, then move on to compare the project to Django and Python? Let's remember that FreeBSD is an entire OS, not just a kernel. If you want to compare it to the linux world you have to imagine the kernel + the GNU userland + the distro specific utilities and package management of something like debian or red hat. It's not really surprising that the codebase ends up being huge and that you can't just change the architecture and tooling around it to use the trending software stack of the day. On the other hand the fact that FreeBSD is so comprehensive is the killer feature for me when compared to something like Linux. It's a full OS, with everything (usually) playing nice with each other, a single documentation for the entire base system etc... I also find that the kernel code is generally a little nicer than linux's, although linux is more featureful overall. Yes, FreeBSD is slower moving than Linux and generally more conservative. That's not a bug, that's a feature.
- jeamland 10y agoHi. OP (original presenter?) here. The whole idea of this talk was about the community side of the project. I make exactly the points you're making regarding code size but that just speaks to the difficulty of managing a community looking after a codebase of that size. I'm also not criticizing the pace of FreeBSD development so much as I'm criticizing the pace of its leadership (of which I'm a member, don't forget) to deal with issues that would make FreeBSD more fun to work on.
- simias 10y agoThank you for taking the time to reply. It was just a bit of a surprising read from my point of view, as somebody who's not directly involved in the project (like you are) but who's been observing it since around ~2004. There are three main points in this article: the issue of version control, the "Dragonfly BSD incident", and the GamerGate garbage fire. Regarding the first issue, while it was sad to see a good dev like Matthew Dillon leave the project, what do you think should have been done better by the leaders of the project? Clearly there was an incompatibility here, maybe having Dillon work on his own project (and then sometimes have a back and forth between Dragonfly and FreeBSD) was the right solution? Would Linux for instance have dealt with the issue better? I recall many personality clashes amongst the Linux "elite", some not so long ago. The migration away from CVS sure did take a long time, but as you mention yourself the technical challenge was pretty high. Lest we forget, Linus ended up writing his own version control system because the existing solution were not deemed satisfying. And FreeBSD is significantly bigger than linux's codebase. Regarding the test suite, testing operating systems is notoriously difficult (you can't easily abstract away from the hardware to run well contained unit tests). I don't recall Linux having an extensive test suite either. The GamerGate thing I won't touch with a hundred kilometer pole. How an operating system project got dragged into that I still can't fathom. So in the end, I don't think those issues are that big of a deal on their own. IMHO the main "trouble" with FreeBSD is simply that its market share is tiny compared to Linux. I'm a big fan of FreeBSD but my IRL job is linux kernel dev, not FreeBSD kernel dev. More and more first party vendors support linux, not any of the *BSDs. "Netcraft confirms it - BSD is dying". There's a momentum problem and I'm not sure switching to github or adding a test suite are going to solve it. FreeBSD is betamax, linux is VHS. FreeBSD is mercurial, linux is git. That being said, I don't have a solution either.
- inopinatus 10y agoFreeBSD is pretty common in some market segments, especially infrastructure appliances and devices. It's an easy choice for NAS controllers, internet core routers, email gateways, firewalls, messaging platforms, CDNs. Not to forget the humongous chunk of FreeBSD that is in OSX. If you think it has a small market share, you're looking at the wrong market.
- deleted 10y ago[deleted]
- Thaxll 10y ago"the best kernel implementations" it's a bold statement.
- angry-hacker 10y agoSame, I do my best to stay away from politics but even a damn BSD story ends up with politics. It's not so much complaint to author but just a grim realization...
- akerro 10y agoThe talk was here 2weeks ago in TOP, most of the article is just rewrite of what he said. It's wired to read the same words.
- problems 10y agoWhat's the deal with all this anti-meritocracy stuff? Can't we all just work on a level playing field and move past this junk? Seems like not doing so causes a lot more problems than it solves.
- HerraBRE 10y agoI think many people feel "meritocracy" has become a code-word for "allowing technical contributions to justify and excuse bad social behaviour." Important free Software and Open Source projects are almost always community efforts. Ignoring bad behaviour which harms the community may have technical benefits in the short term (assuming the people behaving badly are skilled hackers), but in the long term their contributions may not be worth the harm they do by excluding and driving away other potential contributors. A hostile work environment is rightly considered a problem that needs to be fixed in a professional context. For those of us doing FOSS as a hobby, it's even more important - few will spend time on a hobby where they are treated badly. I also like the meritocracy concept. But I feel rather strongly that it is important that the "metrics" are not just technical, but social as well.
- problems 10y agoI hear you, I definitely agree with your premise, but my worry is that this will basically boil down to a political test to participate in many FOSS communities. At what point do you deem social behavior unacceptable? It's a fine line to draw and one that might be difficult for many communities to do correctly.
- HerraBRE 10y agoDrawing that line is exactly what codes of conduct are supposed to do - and like everything else in our community, these are documents which are copied, forked and improved by pull requests.
- problems 10y agoThe problem is it still needs to be up to project leaders to make a determination of whether or not the behavior violates those codes of conduct. And they might not be particularly well equipped for that. What's considered "harassment" for example? Does 1 off comment count or does it need to be systemic? What if it was a heat of the moment situation and an apology was made afterwards? Does expressing an opinion less than the generally accepted one about a rape case for example count as misogyny? What about mental health comments not in line with generally accepted opinions, but which might still hold some validity? How about defending political opinions based on your religion? There are too many questions that I know many people would respond very differently to.
- AndyMcConachie 10y agoI fucking love FreeBSD. Seriously, I use it any chance I can. I have a Debian VM that I use to do development on because of the tool chain I have to use. But for my production personal websites that I run I choose FreeBSD. Nothing in this article makes me want to change my mind. On the contrary seeing this article on a 'Linux' website generally lowers my opinion of both the 'Linux Community' and LWN. If LWN had fewer articles like this, and more articles actually communicating useful information to me, I might actually read it more. I used to use Debian almost exclusively, but ever since this systemd BS I've gone FreeBSD as much as possible. This isn't about personalities, it's about me not caring about the problems that systemd is trying to solve.
- floatboth 10y agoThe article isn't bad tho… it's pretty much a transcript of a talk with the same title by a FreeBSD Core member. The comments… yeah, there are people whining about "Marxists" "ruining projects" or something. Welp.
- GFK_of_xmaspast 10y agoHN has those kind of people too.
- justin66 10y agoLWN comments don't get any better when they stick to technical matters, sadly.
- ue_ 10y agoAs a semi-Marxist myself, I just laugh at such comments.
- Anthony-G 10y agoI skimmed through the comments and most of them seem to be at odds with the content of the article (which seems to offer constructive opinion). The very first comment is frankly bizarre.
- autoreleasepool 10y ago
- jxy 10y agoThe article shows an excellent example of 'moving fast and breaking things': < In comparison, Python started on CVS, moved to Subversion < in 2004, then to Mercurial in 2009, and is now moving < over to GitHub. I used Python around 2004 and 2005, and never went back to it for my personal projects. I would rather prefer 'moving slow and preserving things'. Any body here remembered how things went when Linux moved from OSS to ALSA? And now there's this systemd.
- gcp 10y agoIt's going to be really funny when you discover PulseAudio, ha, ha...ha...
- digler999 10y agoyou just made my blood pressure go up a few points. The "killer feature" in PA is it's "uninstall" button. I've literally had my sound not work after an ubuntu installation, uninstalled PA, and it immediately worked fine.
- gcp 10y agoI've had audio problems with OSS and ALSA too, in the past. Mostly with ALSA. Overall, PA is an improvement over those, but of course every change can bring new breakage, which was the original point.
- jstimpfle 10y agoI would not count your example as one of moving fast and breaking things. What was really broken by changing the VCS? If you still prefer CVS over git for lame super-conservative reasons that's your choice. Speaking as a python user, I guess your way of development is then to still code everything in C and sh? No thanks. I'm willing to update my code to newer, less insane, versions of a language - if the benefits outweigh the pain of course.
- dorfsmay 10y agoYou stopped using python because they changed the VCS they used for the language? If you're not working on python itself, the language, why does the VCS they use matter to you? Python is usually considered the one language that moves slowly, exactly to preserve compatibility. Can you explain why you "never went back to it"?
- mcguire 10y ago"One day [Randi Harper] decided to block the Gamergate "trash humans" out with a Perl script; it worked, causing them to lose their minds, Rice said, at which point they started attacking FreeBSD." Anyone have more info about this? Especially the "Perl script"?
- masklinn 10y agoIsn't it GGAutoBlocker? https://github.com/freebsdgirl/ggautoblocker https://github.com/freebsdgirl/ggautoblocker
- loeg 10y agoYes.
- makomk 10y agoShe wrote a script that found every Twitter account that followed 2 or more people from her list of supposed Gamergate figures (which included at least one major celebrity) and encouraged people to mass block all the accounts it found as an anti-harassment/anti-Gamergate measure. The result, in social terms, was that everyone was forced to choose between listening to one side or the other, including journalists who wanted to report on Gamergate, and their entire view of the other side was filtered through what that side said about it. It was, hands down, the single most clever and effective use of a technical tool to increase polarization and hostility online I have ever seen. (Especially since it had little impact on either determined axe-grinders who wanted to cause trouble by digging up inflammatory remarks and quoting them out of context or actual harassers.)
- brennen 10y agoIt was, hands down, the single most clever and effective use of a technical tool to increase polarization and hostility online I have ever seen. This seems like a nonsensical assessment at best. Use of the script was voluntary, and GG was an organized mass-harassment campaign premised on polarizing and hateful nonsense. The whole social phenomenon consisted of a distributed wave of hostility. I wound up adapting the script myself at one point to mass-block followers of a YouTube/Instagram celebrity who shares my first name and triggers a neverending stream of namespace collisions. It's a reasonable brute-force hack in an environment that lacks real features for dealing with a large population of griefers.
- JdeBP 10y agoDuplicates https://news.ycombinator.com/item?id=13550908 https://news.ycombinator.com/item?id=13550908
- ceratopisan 10y agoPetty history aside, the project needs to be more open in communication. There's too many secret mailing lists and mystery discussion, which is a common thread in all the problems the list describes.
- arca_vorago 10y agoMy early hacking days were primarily on FreeBSD, and though I idealogically agree with RMS and therefore GPL, which is why I push myself onto GNU ecosystems, I must admit the one thing that often tempts me back to bsd land is the consistentcy in system tools and functions, even across other BSD's. I have seen GNU/Linux abused just like I feared BSD systems were going to be, so for practicality purposes I'm seeing less and less of a difference, but oh what I would give for a GPL focused BSD like ecosystem focused Linux effort.
- TazeTSchnitzel 10y agoThis reminds me of the problems the PHP project faces. It has the same lack of leadership and just goes by consensus, with the same problems (i.e. little gets done when hard decisions must be made; the system for voting on things has helped a little, though, because it means people who are bold can sometimes get things in). There was also an attempt to adopt a code of conduct and, in its failure, it exposed why the project could benefit from one in the first place. I suspect a lot of open-source projects have similar issues.
- angry-hacker 10y agoWhy did it fail and what was in the code?
- TazeTSchnitzel 10y agoWell, there was quite a hostile response from some to it, so its proponent dropped it. What was interesting about the response was how specific individuals did not respond civilly (personal attacks, framing it as a political conspiracy, etc.), thus demonstrating why a code of conduct might be useful. The original proposal was this: https://wiki.php.net/rfc/adopt-code-of-conduct?rev=1451940622 https://wiki.php.net/rfc/adopt-code-of-conduct?rev=145194062...
- innocentoldguy 10y agoI love FreeBSD, and I felt like the author of this article does too. It didn't come across as a rant to me, but rather an explanation, and some constructive criticism, of what the author thinks the FreeBSD project could do better. As with all constructive criticism, you absorb what you feel will help you reach your goals, and reject what doesn't. It is always a good thing to have those insights and options though, I think.
- alberth 10y agoDragonFlyBSD vs FreeBSD Since Dillon was discussed in the article and given he split from FreeBSD 11 years ago ... which OS now is in better shape overall (technically)? DragonFlyBSD or FreeBSD?
- yellowapple 10y agoI don't think criticizing FreeBSD's "age" is exactly reasonable in this context, seeing as how Linux is two years older (and GNU even older than that).
- loeg 10y agoFreeBSD is a derivative of BSD, which has history going back to 1977. It long predates Linux (1991) and even predates public announcement of GNU (1983).
- yellowapple 10y agoI personally don't consider that to be exactly relevant (if it were, then we could say that macOS is also older than GNU, which is sufficiently unintuitive to be misleading). It'd be more relevant if FreeBSD was actually maintained by UC Berkeley's CSRG as an official successor to BSD itself; otherwise, we're dealing with a kind of ship of Theseus situation where things are replaced and rewritten and "age" becomes very ambiguous. I also don't really consider "age" in and of itself to be a real factor at all here anyway. It implies (probably not intentionally, but the implication is there nonetheless) that things should be rewritten from scratch all the time in order to avoid "old" things, which would be silly.