he set up us the bomb
I laughed so hard on that one.
]]>For those who don't know the game: http://uk.youtube.com/watch?v=qItugh-fFgg
It was a Japanese game with a very poor translation.
yeah! you are on the way to destruction!
]]>-> grep -r "your base are" *
Binary file openbox/.libs/openbox matches
openbox/mainloop.c: fprintf(stderr, "How are you gentlemen? All your base are"
Binary file openbox/openbox_openbox-mainloop.o matches
->
Hm, maybe someone decided to get all funny with their error messages like the OB devs did... or maybe it was the other way around.
The most likely cause is that this message is a SIGSEGV (segmentation fault) trap - a message that is printed to std{out|err} when the app crashes, since OB prints the AYB when it's crashed too.
You can actually segfault apps manually with `kill -SIGSEGV <PID>' or killall -SIGSEGV <processname>'
-dav7
]]>Anyway, since I posted earlier I actually got the message myself. Turns out Openbox prints it when it crashes, as a sort of easter egg.
]]>$ cd vlc-0.8.6f/
$ fgrep -R 'All your base' .
./doc/ChangeLog-2001: * All your base are belong to us.
$
It's not from VLC. I suggest grepping the source of other software you were running.
]]>Do we have a developer with a sense of humour or is this something I should be worried about?
I never run the system as root although I usually leave a root terminal open.
Bizarre.
]]>