Stories
Slash Boxes
Comments
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

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • Crafty, yes ... elegant, yes. But nonetheless, why would anyone want such a program? I remember back in college playing hacking games and doing something similar with shell scripts:

    # 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

    • If you take the output from the program and turn it into a graphic, you get a sort of op- art dealie [generative.net] which is kinda nice. As generative art, it's really pretty elegant: it produces different "art" each time it runs, and it's a simple piece of code that has a lot of sensitive dependence on initial conditions. Admittedly, as a piece of code that someone might idly run "to see what it does", it's a boxful of Denial of Service, and a few precautions might have been in order.

      In defense of the artist (and yes,
      • 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 wri
        • oops, apologies for the lack of line breaks...

          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 t