News for hackers. Stuff that matters.
Re:Branchless Doom by jghn on Tuesday January 23, 2018 @09:39PM (#16219900)
Several years back I convinced a coworker to try and install that. He had a mac and I was running FreeBSD or something and couldn't run it. He'd been running some sort of simulation for several days on that machine.

So we fired it up and within about 2-3 minutes he managed to shoot PID 1 or something like that as the machine rebooted. Boss was not happy.

Re:Branchless Doom by int0x80 on Wednesday January 24, 2018 @09:54AM (#16223104)
mm usually PID 1 is unkillable even by root AFAIK.
Re:Branchless Doom by jghn on Wednesday January 24, 2018 @02:34PM (#16225605)
Actually you're right. He killed the simulation process now that I'm wracking my brain to remember how that actually worked. That then led to us joking about what it'd be like to force-reboot via the killing.

The key detail I'll never forget is his "Oh fuck!" face when it happened.

Re:Branchless Doom by abofh on Wednesday January 24, 2018 @04:46PM (#16226628)
https://www.freedesktop.org/software/systemd/man/systemd.htm...

Not all signals are blocked by init, if init wants to be signaled :)

Re:Branchless Doom by gerdesj on Wednesday January 24, 2018 @11:19AM (#16223866)
Don't know why you got DVd. This does nothing on a VM running Kali Linux (systemd):

# kill -9 1

Re:Branchless Doom by abofh on Wednesday January 24, 2018 @04:44PM (#16226612)
https://www.freedesktop.org/software/systemd/man/systemd.htm... - See signals

It's init dependent (though I think SIGKILL is blocked at the kernel – I wouldn't swear to it) - sigrtmin+3 will likely kill your init process :)

Re:Branchless Doom by gerdesj on Wednesday January 24, 2018 @07:52PM (#16227820)
Cor, the locals are a bit harsh here.

I've just run # kill -L - there seem to me rather more signals available than I remember from the past. I'm pretty sure I have never even heard of the ones >16 let alone SIGRT{MIN|MAX}{|x}. I've only ever used SIGHUP or SIGKILL in general and SIGUSR1 for dd progress (which now has --progress at last)

Time to dig out the manual 8)

Re:Branchless Doom by int0x80 on Thursday January 25, 2018 @12:59PM (#16232916)
In Linux, from the manpage:

"The only signals that can be sent to process ID 1, the init process, are those for which init has explicitly installed signal handlers. This is done to assure the system is not brought down accidentally."

And SIGKILL can not be captured (enforced by the kernel):

"The signals SIGKILL and SIGSTOP cannot be caught or ignored."

Re:Branchless Doom by rootw0rm on Wednesday January 24, 2018 @06:04AM (#16221822)
wtf, hahaha
Re:Branchless Doom by planteen on Tuesday January 23, 2018 @09:55PM (#16219958)
Haha that made me LOL