ey b0ss

I live in a constant state of fear and misery

Do ya miss me anymore?

It will cause a critical error during boot if the device isn’t given the nofail mount option, which is not included in the defaults option, and then fails to mount. For more details, look in the fstab(5) man page, and for even more detail, the mount(8) man page.

Found that out for myself when not having my external harddrive enclosure turned on with a formatted drive in it caused the pc to boot into recovery mode (it was not the primary drive). I had just copy-pasted the options from my root partition, thinking I could take the shortcut instead of reading documentation.

There’s probably other ways that a borked fstab can cause a fail to boot, but that’s just the one I know of from experience.

To the feature creep: that’s kind of the point. Why have a million little configs, when I could have one big one? Don’t answer that, it’s rhetorical. I get that there are use cases, but the average user doesn’t like having to tweak every component of the OS separately before getting to doom-scrolling.

And that feature creep and large-scale adoption inevitably has led to a wider attack surface with more targets, so ofc there will be more CVEs, which—by the way—is a terrible metric of relative security.

You know what has 0 CVEs? DVWA.

You know what has more CVEs and a higher level of privilege than systemd? The linux kernel.

And don’tme get started on how bughunters can abuse CVEs for a quick buck. Seriously: these people’s job is seeing how they can abuse systems to get unintended outcomes that benefit them, why would we expect CVEs to be special?

TL;DR: That point is akin to Trump’s argument that COVID testing was bad because it led to more active cases (implied: being discovered).

I’m gonna laugh if it’s something as simple as a botched fstab config.

In the past, it’s usually been the case that the more ignorant I am about the computer system, the stronger my opinions are.

When I first started trying out Linux, I was pissed at it and would regularly rant to anyone who would listen. All because my laptop wouldn’t properly sleep: it would turn off, then in a few minutes come back on; turns out the WiFi card had a power setting that was causing it to wake the computer up from sleep.

After a year of avoiding the laptop, a friend who was visiting from out of town and uses Arch btw took one look at it, diagnosed and fixed it in minutes. I felt like a jackass for blaming the linux world for intel’s non-free WiFi driver being shit. (in my defense, I had never needed to toggle this setting when the laptop was originally running Windows).

The worst part is that I’m a sysadmin, diagnosing and fixing computer problems should be my specialty. Instead I failed to put in the minimum amount of effort and just wrote the entire thing off as a lost cause. Easier then questioning my own infallibility, I suppose.

One last joke played on the colonizers invading them

Debian is the best and I don’t know what to do with it

This is a hypothetical that has no clear bearing connection to common practice.

In other words, I could just reverse this to contradict it and have equal weight to my hypothetical: devs should always use GPL, because if their software gets widely adopted to the point where companies are forced to use it, it’s better that it’s copyleft.

"☹️".reverse() == "☹️"

“I am a new linux user. After 15 minutes of research on google, I found a few forum posts and some niche websites that said SystemD was bad, so I took it as gospel. Now my system doesn’t work as simply as it did with installer defaults? How do I make everything Just Work™ after removing any OS components I don’t understand the need for?”