I know you're joking around here, but you don't have to upgrade every two years. You can use an LTS release instead, or, on the opposite of the spectrum, a rolling release.
Release schedule and duration of support should always be factored into the decision of choosing a distro.
Millenials - Load"$โ,8 LIST LOAD"LEISURESUIT*โ,8,1 (wait 10 min.) RUN
Even the oldest millennials were just toddlers when the C64 was relevant, so this is not a typical millennial experience at all. It's really a GenX thing... so once again we are forgotten.
I would say millennials' computer experience starts in the late DOS/Win3.11 era at the very earliest, but more typically in the Windows 9x and early XP era. So even IRQ/DMA/config.sys/autoexec.bat fuckery is not that typical.
A core memory of mine is getting flung off of one of these things because of the centrifugal force, falling on my back, and being unable to breathe for like 20-30 seconds ... until I screamed at the top of my lungs, and things slowly returned to normal, while the teacher just went: oh you're fine, don't be a baby. I was 6.
It's a bit more complicated than that with transplants. Should people for example be able to sell their kidney to the highest bidder? That's also "my body, my choice". And should doctors be forced to participate in such a scheme?
A transplant system should consider fairness, equality and possible abuse. Obviously I think it should be possible to donate to a loved one, but we should also be careful not to create a system where the rich get priority, because they can pay more, and where poor people could be financially pressured to give up their bodily integrity by having to sell an organ.
The flag is called --no-preserve-root, but the flag wouldn't do anything here because you're not deleting root (/), you're deleting all non-hidden files and directories under root (/*), and rm will just let you do it.
In Unix/Linux, a removed file only disappears when the last file descriptor to it is gone. As long as the file /usr/bin/rm is still opened by a process (and it is, because it is running) it will not actually be deleted from disk from the perspective of that process.
This also why removing a log file that's actively being written to doesn't clear up filesystem space, and why it's more effective to truncate it instead. ( e.g. Run > /var/log/myhugeactivelogfile.log instead of rm /var/log/myhugeactivelogfile.log), or why Linux can upgrade a package that's currently running and the running process will just keep chugging along as the old version, until restarted.
Sometimes you can even use this to recover an accidentally deleted file, if it's still held open in a process. You can go to /proc/$PID/fd, where $PID is the process ID of the process holding the file open, and find all the file descriptors it has in use, and then copy the lost content from there.
DefederateLemmyMl @ SpaceCadet @feddit.nl Posts 1Comments 584Joined 2 yr. ago
In Linux, everything is a file.
So if you have a problem, it will be in a file somewhere.
So logically every problem can be equalled to one or more files.
Therefore it follows: no files = no problems. And no problems = no headache.