Back then I was testing modelines to see the maximum I could push to my 14" monitor. I then backed it with a 1200x1600 virtual screen.
My girlfriend got sick from watching me scrolling around and bought me a 19" display which could do that resolution - and ended up frustrated when I added a larger virtual screen.
killall typically sends SIGTERM by default. It accepts a single argument, the signal to send - so shutdown would call it once with SIGTERM, then with SIGKILL. killall is not meant to to be called interactively - which worked fine, until people who had their first contact with UNIX like systems on Linux started getting access to traditional UNIX systems.
It used to be common to discourage new Linux users from using killall interactively for exactly that reason. Just checked, there’s even a warning about that in the killall manpage on Linux.
On a real UNIX (not only AiX) killall is part of the shutdown process - it gets called by init at that stage when you want to kill everything left before reboot/shutdown.
Linux is pretty unique in using that for something else.
Make sure you use a long extension cord to a fuse without RCD for the hair dryer, though - otherwise the constant resetting of the breaker will eat up all your time savings.
CUPS is horrible, and also had its share of critical vulnerabilities. It is just better than the LPD mess we had before.
It is not a Linux specific thing - it was developed when there still were a lot of UNIX variants around. Apple was a very early contributor, and had quite a bit of influence in making it successful.
I’m using opensuse tumbleweed a lot - this summer I’ve found an installation not touched for 2 years. Was about to reinstall when I decided to give updating it a try. I needed to manually force in a few packages related to zypper, and make choices for conflicts in a bit over 20 packages - but much to my surprise the rest went smoothly.
Also quite important to make sure we don’t have just a single strong x86 vendor - even though currently looking at price/performance you’d almost always go for AMD.
The time before ryzen was horrible - a 4-core-CPU was considered high end, and if you needed something more you needed to go for ridiculously overpriced Xeons. Similar for servers - you could get slightly higher core counts there, but when going for more than 8 cores it’d also get expensive very quickly.
Now we’re talking about 16 cores in high end notebook, and 64 cores in still reasonably priced pro workstations.
It’s a similar thing with four leaf clovers - I never in my life found one, even during periods where I’ve been scanning every bit of green while hiking. But then we had a friend who isn’t really paying attention to her surroundings, and just randomly goes ‘oh, moment’, and picks up a four leave clover from a few metres away.
Seems my daughter is also developing that talent - last summer she picked up a few while playing outside.
It shows a message which wastes valuable screen estate, especially on low resolution terminals, containing a message I have to read every single time because the keys are not in muscle memory, and never will because the bindings are stupid.
On systems I have control over the reaction to nano popping up is exiting, removing it, making sure the package system blocks reinstallation attempts, and go back to what I was initially doing in a sane editor.