The past year or two I've found several stores where they are abandoning it. I presume because people carrying cash, especially coins, is becoming rarer and they don't want to inconvenience their customers?
Strangely enough, carts still get returned even at these stores.
Even if her partner could donate his own liver, it should still go to a better recipient
That's nonsense, because the partner would not donate his liver if it went to someone else.
Or ctrl+w to close the fucking site and never come back.
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.
It’s apparently a hobby and to be competitive, you need to be able to spew bullshit at amazing rates. Personally I’ve maxed out at 140 wpm
I'm limited by the rate at which I can think of bullshit.
yet all I needed is a "this side up" symbol ...
Since you forgot to add - - preserve-root It won’t go too far
Go on then ... try it.
Or don't because you will erase your system. (Hint: it's in the asterisk)
as the binary is already loaded into memory
That’s not the reason why it continues. It’s because there’s still a file descriptor open to rm.
That’s not the reason why it continues. It’s because there’s still a file descriptor open to rm.
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.
We're explicitly talking about a situation where the donor is suitable. So I don't know what kind of information you're trying to add here.