I knew that shell files, especially in build systems can get hard to read, but this was absolutely painful to look at from start to finish, even with the very helpful explanations in between. Of course the obfuscation is mostly done by design in this case.

OpenSuse Slowroll does pretty much that, a slightly delayed rolling release.

Why does it say “Texas” on it 6 times?

That’s GDPR coming through.

I really like kitty. It is fast and simple but gives me all the features I would want.

That’s sad that Mozilla has to take it into their own hands to provide a proper alternative to Snap Firefox.

Yeah, not gonna do that.

I have also switched to Colemak and my advice is to just not do that. Just learn Colemak without looking at the keyboard, it’ll make you a better typist anyway and you can get comfortable with it within a few weeks. In particular you don’t want to move the little knobs on the index finger keys (F and J).

The hexagon minecraft one is neat.

I still don’t see how having a flat subvolume layout would make that more problematic. You can still (even better in my opinion) choose what subvolumes to automatically snapshot, which to include in backups etc.

Yes, that seems correct to me. I would also say that the flat layout is preferable because it makes dealing with snapshots later easier. When snapshotting the rootfs subvolume you won’t have to keep track of where exactly the home subvolume is located and it is easier to boot into a different rootfs snapshot.

Hit the right arrow key once (and stop using Twitter).

Is that in reference to the Safety Third podcast?

man -k

My experience is you should try to always use find over ls when writing robust scripts, and consider ls as just an end user tool, not a scripting tool.

In arch/x86/Kconfig of the kernel tree it says for CMDLINE:

	  Enter arguments here that should be compiled into the kernel
	  image and used at boot time.  If the boot loader provides a
	  command line at boot time, it is appended to this string to
	  form the full kernel command line, when the system boots.

	  However, you can use the CONFIG_CMDLINE_OVERRIDE option to
	  change this behavior.

	  In most cases, the command line (whether built-in or provided
	  by the boot loader) should specify the device for the root
	  file system.

and for CMDLINE_OVERRIDE:

	  Set this option to 'Y' to have the kernel ignore the boot loader
	  command line, and use ONLY the built-in command line.

	  This is used to work around broken boot loaders.  This should
	  be set to 'N' under normal conditions.

So both commandlines will probably be used. I don’t think an initramfs will normally interfere with the kernel commandline. In any case you can make sure you got what you wanted with cat /proc/cmdline.

It took roughly 10-15 minutes on a Ryzen 5800X with 32GB RAM. I have compiled other programs before, but none nearly as large and notable as the kernel. I am in fact very close to getting a computer science degree, but that is in no way required to be able to do this. If you are able to follow the wiki-page I linked, you can do it too.

Because even if you pay them, RedHat won’t allow you exercising your GPL rights and redistributing the sources.

Yes, that was my experience as well. And of course there is the added tension that if you mess up somehow your system might become unbootable.

Sure did.