You know, I don't think I've seen that in years. Do CentOS and Debian have it disabled? I know some distros have a graphical boot thing, but even if I switch to text I don't remember seeing Tux.
Both the text and graphical installers do. You can also do it afterwards by installing or removing some meta packages or package groups, not sure which one Debian uses.
Regular Fedora should be perfectly fine. I'd ensure a separate /home partition and a backup for ease of reinstallation if it gets wrecked. Yes, an atomic distro or btrfs snapshots could do that too, but like you mentioned, there are other considerations for atomic distros. And a separate /home partition eases installation of other distros if Fedora doesn't do it for him for some reason.
That depends on whether you are using the colloquial and international law definition, or the US formal definition. It's only a war if Congress declares it, else it's just a sparkling police action.
That's for Arch, but it's pretty standard, unless Ubuntu/Mint have deviated from tradition. Getty is what manages the TTYs. I assume running under X or Wayland is not what you're looking for.
No, in nearly every case, you never want a hard link. You want one file, and symlinks to it. (Technically every file is a hard link to an inode, and subsequent ones are just additional links to the same inode.) In ext4, you can't easily get a list of links to an inode, you have to scan the filesystem and look for duplicates. Other filesystems might make this easier.
You shouldn't try to use a tree filesystem to approximate a tagged database. Use the appropriate tool for the job.
It's not like it, it's exactly it. The output from find is text, - means read stdin, so file told you the text in stdin was text. You'll have to see if it takes a list of files as an option, otherwise just use a for loop.
If it's maintainable, I don't think there's an issue (aside from the usual license violations in LLM training). The big problem is when people send giant unmaintainable patches that they can't even explain themselves.
https://www.gnu.org/software/bash/manual/bash.html#Looping-Constructs