@A.B. Well, Mudit asked how Linux can be cruel and I answered that it's easy, just run echo "rm r -rf ~/" >> ~/.bashrc and then open a new terminal. I assumed he would know what that command meant and wouldn't actually run it.
I'm afraid there's no general way to "log" init's reaction. First, there's the fact that kill won't deliver any signals to init that init isn't handling (from man 2 kill):
NOTES
The only signals that can be sent to process ID 1, the init process,
are those for which init ha...
Is there any real difference in running a pipe in a subshell which forks into two subshells vs. running a command in a subshell which then uses a process substitution?
> It appears that qTox has to use the old tox1 protocol to access DNS record of your friend's Tox ID. Unfortunately tox1 is not secure, and you are at risk of someone hijacking what is sent between you and ToxDNS service. Should tox1 be used anyway? If unsure, press “No”, so that request to ToxDNS service will not be made using unsecure protocol.
@Fabby I think I've found how can root be logged in without showing up in the last command (which is what the OP wants, last reads the wtmp log , right ? ) . But I think I'm not gonna post it, it kinda smell fishy to me. There's a good (security) reason to keep track of all logins
I'm afraid there's no general way to "log" init's reaction. First, there's the fact that kill won't deliver any signals to init that init isn't handling (from man 2 kill):
NOTES
The only signals that can be sent to process ID 1, the init process,
are those for which init ha...
Using sed:
sed '/^/ r h.txt' k.txt
or with ed
(echo '0a'; cat k.txt; echo '.'; echo 'wq') | ed -s h.txt
