To be fair it also makes it possible for good-faith contributors to evade sanction faggotry.
They should have either banned all control bytes 1-31 or not banned newlines at all. Now you have the downsides of both: Breaking changes to the definition of filename, but naive scripts will still do dumb shit when they encounter escape codes and so on.
To add arbitrary restrictions without fixing any fundamental problems. That is the POSIX way. They'd really be better off with fewer restrictions. They don't mandate a character set, but then they de facto mandate one compatible with ASCII through the two and now three disallowed characters. There are two few restrictions to be useful, and just enough to get in the way. It's been like this since its inception, and will never change.
You write a program and run it on your filesystems. Then you enforce by writing angry electronic mail letters to your users. Wait, what year is it? 1979?
You haven't updated or installed any packages in over five years? Why?
It ain't broke. Haven't updated any packages on my postmarketos install for more than half a year now.
Oh noes they found my browsing history.
The browser bugs alone should be enough to update for, unless you have them properly containerized (though even so, why run browsers with known exploits)
Its not your browser history anyone wants, its browser escapes that end up running arbitrary code as your user.
Im part of the botnet now
Don't worry. I don't have drivers for the Wi-Fi chip, and the shitty dongle I bought broke years ago. It doesn't touch the Internet anymore.
Maybe try nix / guix or something? Nixos is the first solution I've found to that problem, since its very easy to roll back if the packagers fuck something up (again) until its fixed.
Honestly based but I can't stand elisp/emacs. Unfortunately I can't stand any other editor even more than I can't stand emacs.
The main system under discussion here is running GuixSD. It broke anyway. It would probably work better if I installed a newer version, but I don't feel like it.
How'd it break? Curious because I've never had nix manage to get itself into a state that couldn't be rolled back.
I don't recall the details, but I think I got one of those "gee, this wasn't supposed to happen" error messages at one point in the dmesg output or from the guix command output. I was running a really early version of GuixSD, so it would probably work if I wiped and upgraded, but that's such a hassle.
You probably don't need to wipe, good chance just running the install tools from a drive + your configuration works. Still annoying though.
