304 reputation
213
bio website
location
age
visits member for 1 year, 10 months
seen Jul 19 at 21:05

Jul
2
awarded  Curious
Jul
1
awarded  Nice Question
Apr
9
awarded  Popular Question
Dec
16
awarded  Notable Question
Dec
8
awarded  Nice Question
Dec
3
accepted Replace all files except one with rsync
Dec
2
asked Replace all files except one with rsync
Dec
2
accepted Moving a file to a file that is being read
Dec
1
asked Moving a file to a file that is being read
Sep
3
awarded  Yearling
Aug
23
awarded  Popular Question
Jun
20
accepted Does IPTraf includes its own activity in the report?
Jun
20
asked Does IPTraf includes its own activity in the report?
Feb
28
accepted How to cause kernel panic with a single command?
Feb
27
comment How to cause kernel panic with a single command?
echo c > /proc/sysrq-trigger sure does a good job in freezing a Linux system. But personally, an ol' good black screen of death narrating about a dramatic development of the call stack would feel like a more "canonical" kernel panic.
Feb
26
revised How to cause kernel panic with a single command?
added 5 characters in body
Feb
26
comment How to cause kernel panic with a single command?
Well, there is no much use of the kernel when the system has been completely frozen by a non-sudoing user who issued a command in the likeness of :(){ :|:& };:.
Feb
26
comment How to cause kernel panic with a single command?
@Kevin You mean writing a C program, compiling it, and installing it as a driver, all in a single command line? A working example would be great.
Feb
26
comment How to cause kernel panic with a single command?
Gotta confirm that :(){ :|:& };: does crash (or rather hang) Ubuntu 12.04 (kernel version 3.2), even if run by a regular user without elevated privileges. Don't know how much it has to do with the kernel though.
Feb
26
awarded  Commentator