Earlier quoted context omitted.
> On Debian, it very much is saved to disk by default. Only relatively modern Debian versions. And even then, blame Debian, not systemd. > It's downright dangerous to change the expectations that have held true for 30+ years without even a warning somewhere - e.g. running unmount popping warning Firstly, umount “popping a warning” would break so many things, and then you really would have something to complain about.…
No, I'll blame systemd. I've been using Debian for 25 years and we've only had systemd forced on us in the last maybe 5. OK, yeah, you're right. I'll blame Debian for forcing systemd on us, which is exactly the problem that Devuan is fixing. Actually, I've been using SunOS and Solaris even longer than Debian. Putting scripts in /etc/init.d / /etc/rc .d isn't "new". It's been standard for at least 30 years. Actually,…
Well, maybe. But what constitutes an “interactive tty”? Stdout or stdin? I’ve had problems where most things, including tty(1), tests stdin for TTY-ness, but if I’ve redirected stdout to a file I get all interactive questions to a file, and a pausing system waiting for input for a question not visible on screen.
> Having filesystems randomly mount themselves after you have deliberately unmounted them is actually dangerous.
The automounter, present in SunOS with NIS and NFS for 30 years, also does that, no?
> How about you consider having some manners?
Technology is constantly changing. Since your complaint was simply that technology has changed and is forcing you to learn something new, I think that’s an appropriate response. If you have more detailed complaints, those might be deserving of more respectful responses, but a “my 30 year old UNIX™ is changing and forcing me to learn new things, oh noes!” gets, and deserves, nothing better than a “git gud”.