NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.
All the Perl that's Practical to Extract and Report
Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.
Stupid (Score:1)
# shell script named foo
foo&;foo&;
To get rid of it and the 'bomb', just 'rm' the file. This program is a little more dangerous in that once you execute it, the code will be interpreted and removing the source file will not affect its execution (unless I've got that wrong).
*sigh* - I dunno ... perhaps I'm in a
Re:Stupid (actual esthetic - maybe - results) (Score:1)
In defense of the artist (and yes,
Re:Stupid (actual esthetic - maybe - results) (Score:1)
Re:Stupid (actual esthetic - maybe - results) (Score:1)
it should have been
thanks for that
although my name is on the paper you reference, i contributed ideas rather than words. to be honest, i can't grok that academic language either. the words you cite are largely Geoff's response to the fork bomb, who is neither a sysadmin or a programmer.
i don't think this fork bomb encourages people to crash other peoples systems. it has a built in limitation and a warning, so on both counts it's less dangerous than the simple perl -e 'fork while 1'
i didn't have one motivation for writing this script, it's just a simple hack. it allows many points to be made around it (aka post creative rationalisaion
Reply to This
Parent
Re:Stupid (actual esthetic - maybe - results) (Score:1)
--- Joe M.
Re:Stupid (actual esthetic - maybe - results) (Score:1)
what do you have in mind, Joe?
Re:Stupid (actual esthetic - maybe - results) (Score:1)
I'm working through the design of a virtual studio to experiment with this kind of composition. The idea is to be able to set up several sets of harmonically-related loops of different lengths, which, on