As I write this, I recognize the truism that exists in the title of this post. Research, real research, takes time, effort, and energy that may be better expended elsewhere. It requires reading, often for extended periods, and is be exhausting. It requires thoughtful insight and introspection into a problem scope that will quickly expand beyond one’s intellectual horizon if unrestrained. It requires challenging mistaken preconceptions–sometimes going so far as to challenge deeply held convictions–and can lead to surprising or uncomfortable conclusions. At its worst, it comprises a seemingly endless path of drudgery; at its best, it can bring new insights.

But is there anything worse than countless hours of research posted freely without gratitude? There is! Derogatory remarks or misinformation posted as established fact whereby it becomes unmistakable that the author hadn’t a clue.

I recently came across a video posted on social media wherein the author spent considerable time whinging over the preliminary Ubuntu 20.10 release notes staking a fallacious claim on their apparent switch away from iptables to nftables. The narrator claimed this was somehow impossible, because it didn’t ship with nftables installed by default.

I won’t link to the video here; I see no purpose in further disseminating or rewarding objectively misinformed YouTubers. What I find incredibly frustrating about posts like his is that in less than 5 minutes’ research, it’s easy to find out what nftables actually is. Hint: It doesn’t replace all of netfilter; it, in fact, uses netfilter under the hood and simply replaces the packet classification framework previous used by iptables. nftables is an incremental improvement over existing tools. That’s it.

In this case, the reason the YouTuber was unable to find the installed tools is because the nftables package is strictly a userspace interface into the netfilter architecture that has shipped as part of Linux since kernel version 3.13. In other words, nftables literally comes in the box.

It’s curious to me that such an egregious mistake could be made when a single search reveals that, what the author thought was a mistaken addition to the preliminary Ubuntu 20.10 release notes (or outright lie?), is strictly a consequence of his understanding. He didn’t know anything about nftables, presuming instead that it cannot exist independently from the installed tools. Apparently, he didn’t know what the tools do either!

I’m aware videos take time to produce, and editing is almost certainly a lion’s share of the process, but failing any sort of due diligence by conducting research into the subject before turning on the microphone and running the screen capture software immediately gives me pause for thought. What other videos did this person post that are full of misinformation or objectively wrong?

Therein lies the rub. Failure to research even a broad understanding of the topic at hand can present a troubling conundrum for the informed reader- or viewership. Without depth of knowledge, what other dangers lurk beneath such troubled waters?

That’s not to say I don’t post things that are demonstrably false. I do precisely that quite often, either by posting conjecture–or my opinions–or by omission. Sometimes, at least on social media, I may be in a hurry to author a quick reply to someone that contains mistakes (and embarrassing typos, but we’ll pretend those didn’t happen). Often on this blog, I forget about posts dating back into my own antiquity that are no longer applicable, and neglect to place a warning that the information contained therein is dated or no longer valid. Essentially, it’s an indirect and unintentional form of dishonesty through omission. Yet readers are more willing to forgo levying judgment for these categories of mistakes if they understand the context (or age) of the post.

For something posted in the here and now, where there’s clearly no effort to conduct even the most basic form of research? That’s almost unforgivable.

Unfortunately, I expect this pattern to get worse, not better. We’ve seen YouTube videos expand to more than 10 minutes in length, because the algorithm rewards long-format content and because monetization options improve as run time increases. What would have taken less than three minutes to present now regularly exceeds 15! Poorly researched videos have greatly outnumbered well-researched competitors for years, and largely because YouTube rewards quantity over quality. Monetization and viewership depends heavily on vast quantities of material such that channels with more content tend to appear in user recommendations more often than those that work to the contrary.

High volume, poor information gets views.

This post isn’t intended to poke fun at anyone in particular (hence why I’m not linking to the guilty party). We’ve all been there. We’ve all been rushed and released things that don’t meet our minimum bar of quality, kicking it out the door and into the world before so much as a single edit. Thinking about it, this post isn’t so much intended itself to be a complaint as much as it is an effort to raise awareness and present a challenge to content creators: You can do better. Don’t post a video to complain about a topic–aim to educate your viewers. If you don’t like something, explain why and dig into the weeds. Raise the signal-to-noise ratio.

Disclosure: I’m not an Ubuntu user, so this post wasn’t authored as a consequence of defending their release notes. I don’t follow Canonical closely and have no idea what their plans are from one release to the next. I also don’t author YouTube videos as of this writing and am yet-another-content-consumer. I have my concerns, and I think we’re heading in the wrong direction.

We can do better.

(Some details have been glossed over to protect the innocent (?).)

About nine months ago I wrote a post title The End of Gentoo. At the time, the article mostly echoed my growing frustrations with the lack of maintainer support for the vast collection of software in Portage, Gentoo’s repository and package management subsystem. Although the gentoo-server mailing list has all but dried up, gentoo-user has seen a marked increase in activity. Whether seasonal or otherwise, I think it’s a positive sign.

Another positive sign that comes to mind is the increased frequency and speed with which package maintainers have been pushing stable (and sometimes unstable) package versions out the door. For example, I was surprised to discover that MongoDB exists in Gentoo at version 1.8.2 as of this writing, which is conveniently the same version in FreeBSD’s ports collection. Ubuntu is decidedly behind the curve, holding in at around version 1.4.x. Of course, with sufficient digging, you can find prebuilt .debs of 1.8.3, or you can always fall back on building from source. Then again, I’m somewhat torn with regards to this: Sure, it brings back memories of earlier days when I often had to build packages by hand just to apply security fixes or obtain new versions, but I also wonder what the value is to it. After all, if I abandoned Gentoo to avoid the nightmare of compile-wait-restart, what’s the point if I leap over to another distribution that is forcing me to do exactly the same thing (except with less automation)?

Given the nature of work and my current projects, I’ve discovered that Gentoo suits my needs best. I can obtain fairly new versions of packages with some degree of customization without the need to manually run the ./configure && make && make install cycle by hand. Downgrading is also fairly easy, provided it doesn’t affect too many packages. However, I’ve found that eselect for those packages it supports can be an exceedingly welcome tool in the developer’s arsenal. I may not use it with any degree of regularity, but the option of setting the system default of a specific package to one version or another is appealing. I suspect this will be mostly useful for any Python-based tools I write in the near future, particularly given the split that is currently underway between 2.x and 3.x, but eselect also works with a handful of other systems that exhibit some degree of change between versions, including PostgreSQL and Boost.

But, I confess that none of this really influences my motivation for writing this post. Well, with the exception of V8 and MongoDB.

I think that much of my decision revolves around familiarity and maybe, if I were to make something of a stretch, annoyance. Ubuntu on the desktop looks absolutely beautiful. I love it. I really do. But the moment you dare to venture beyond the official packages it shipped with (think instant messengers), you begin to encounter various bits of weirdness that fester into a sore. Ubuntu has a great community of developers and supporters, but sometimes more peculiar problems are harder to find via search simply because of the noise level generated by its popularity. There’s nothing wrong with that–in fact, that’s an excellent problem for a distribution to have–but for unusual issues, it often makes finding the answer an uphill battle that is difficult to win without some patience. Add this to the abomination that is NetworkManager (installed and enabled by default), the excessively annoying network configuration borrowed from Debian, and whatever blasphemous modifications have been made to sysvinit, and one starts to see a pattern that makes this distribution more than a little tiring to those who simply wanted something that Just Worked.

It’s ironic in a way. I read an article a couple of weeks ago praising Linux Mint for many of these same reasons that Ubuntu seems deficient. Perhaps I should give it a try…

Yet time and again, I find myself drawn to Gentoo. It’s a rough distribution to maintain. It has many sharp edges. It’s not exceptionally good for use on a server where security updates may need to be applied from upstream regularly. It’s not even really that great for low powered desktops (try compiling Xorg and the desktop manager of your choice on a Netbook without distcc or cross-compilation on another system and then get back with me). Time and again, Gentoo lures me in. Why? Well, I’m starting to think that the answer is more complicated than simply “familiarity.” Perhaps I should take back what I said earlier.

About 8 or 9 years ago, I started toying around with a handful of Linux distributions. The only *nix-based systems I knew at the time were FreeBSD and OpenBSD; I had no idea what Linux really was, why there was such a significant chasm between the userland and kernel, or even really what the differences were between distributions. Superficially, I just assumed that the init systems were largely identical, and individual distributions simply customized various subsystems here and there. I had no idea that the world of Linux was vastly different from that of FreeBSD. In the latter, kernel and userland development is largely one and the same. FreeBSD is the kernel. It’s also the world. From init to various userland tools (yes, even ls) to device drivers (oh fxp0, how I miss you), development continued as a part of a single cohesive continuum. Little did I know, the Linux world is almost the polar opposite of that.

I was introduced to Gentoo by my friend John G. who suggested it as a more “BSD-like” distribution of Linux. He was right–everything about Gentoo seemed to be a GNU-derived analog of the BSD world with the one exception that it was decidedly Linux-flavored. But the most important lesson I took from Gentoo was that of how an operating system is put together–from scratch, but with training wheels. Sure, I knew all of the basic steps: There’s the file system, the kernel, the userland tools, and then there’s various odds and ends here and there that are glued in place to make life easier (or more miserable). In some ways, it’s almost a surprise any of this actually works as well as it does.

Yet I think it was that experience with Gentoo that won my heart. Not only do you have to partition the file systems yourself, but you have to effectively bootstrap the entire system from a live CD (or other Linux distribution), prepare it, and configure it, but you also have to build the kernel and all of the utilities yourself. To this end, I think Gentoo should be a required topic in any operating system course in every CS program at all universities. It’s like Linux From Scratch set to super-easy-mode. It’s no surprise then that any time I want to learn anything new, the best way for me is to pick it up under Gentoo and play with it.

And let’s be honest, Gentoo probably has one of the very best network configuration systems in the Linux world. It better–because it’s the kindred spirit of FreeBSD’s network configuration via rc.conf, except that it’s not. Well, not completely.

This isn’t to say that Gentoo is all sunshine and roses. It certainly does have more than its fair share of sharp edges. I recently reinstalled it on my desktop (no, I still have my Ubuntu install) only to discover that it still takes the better part of a weekend (and then some) to configure, build, and find everything you want, get things situated exactly right, and then discover that there’s one or two minor annoyances still eating away at you. For me, those annoyances are font-related, but I suppose nothing’s perfect. Ubuntu’s fonts are about as close to perfection as possible in the Linux world. Although, I admit that sound and sound support sucks badly in both. Oh, and don’t get me started on media players. I spent most of my free time this week messing around with the damned things only to discover that nearly every single one available is absolutely terrible. I miss Amarock 1.4. They had a good thing going…

The most important lesson I’ve taken from the time period between now and the time I wrote that fairly anti-Gentoo rant is something worth repeating: Nothing perfect. No distribution is perfect, no one distribution will do everything you want, and compromise is always a necessity. I still like Ubuntu for its aesthetics, but Gentoo is still the most appropriate solution for a general purpose workstation. I guess some things never really do change.

So, lesson learned: Rants are stupid. The future you is always the wisest. Sometimes you look back on what you wrote and wonder what the hell you were thinking. Long live Gentoo!

I elected to give myself a little project this weekend and it started with this small mountain of boxes:

Don’t worry, there’s a method to my madness. It isn’t often my crazy ideas have a purpose, so this time I’m making an exception. I also promised to share some of my experiences with a friend of mine who was interested in the project so he could freeload some information share in the learning experience.

The idea started about two weeks ago when I was mulling over some way of providing my mother with an entertainment system that could replace a few aging devices. Since she’ll be having back surgery next week, I figured it would be much easier for her to contend with a single device than to muck about with several. Plus, she has an old video cassette recorder that is on the verge of going wherever it is electronics go when they pass on into the afterlife, and it occurred to me that bringing her kicking and screaming into the digital age might not be such a bad idea. She’s in desperate need for a video recorder of sorts and being as I inherited her frugal nature, I wasn’t about to purchase a TiVo unit for her. TiVos are too limited anyway. She needs a relatively decent computer to sub-in for the period of time she won’t be able to sit at an actual desk. Plus, with her “real” computer being in an upstairs room and her refusal to let us bring it downstairs, I started mulling over a solution.

So far, I’m fairly impressed. There have been some teething problems–the project is still a work-in-progress–hence I’ll be posting this DIY walk-through in multiple parts.

Read more…