Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[SolarShado]

I'm running it with n=16 now; been going for ~15-25 minutes now and not done. It uses very little CPU time (only ~25% of 1 core on my laptop) and even as long as it's been going its temp directory is only ~2.4MB.

There's one "flaw" for using it as an actual bomb: the final archive includes other archives, so the "victim" would have to either use a program that recursively decompresses everything, or stupidly decompress each one manually.

I don't know of a program that'll do that (there may be a command line program that'll do it...) and I don't think there are any users stupid enough to manually decompress it all...

Then again, these "flaws" may be a good thing...

EDIT: 4x ninja'd >_>

[Virex]

It might be very memory-speed intensive, meaning that your RAM just can't pass the data to your CPU fast enough, hence the low speed even with a low CPU usage.


Also, this is probably a proof of concept. A real cyberweapon like this would probably not result in a compressed file, but go straight to an unpacked file.

[ILikePie]

n=32 has been running for about 20mins here too, it's up to the 16th iteration at the moment, 16 more to go. You can check where it's at by looking in ./container.
Another flaw is that each "boom.tgz" (bottom level) has three directories, container/temporary/boom, instead of just boom. No idea why.
I'm gonna take a shower, hopefully it'll finish when I'm out.

e, It's done:

Code: [Select]

ron@Tux ~/code/bash $ genbomb 32
created file: 8976090 bytes in size
    DO NOT uncompress!
2gbs compressed into 8.6 megs. Took about 40 minutes

[ChairmanPoo]

You missed the Lebowski jokes pages ago.

You're tearing me apart Lisa

[BigJake]

Catching up on 30 Rock.

Tracy: Why is that baby covered with goop?

Dr. Spaceman: Because everything about this is disgusting!

[SolarShado]

It might be very memory-speed intensive, meaning that your RAM just can't pass the data to your CPU fast enough, hence the low speed even with a low CPU usage.

I suspect the reason it's so slow is because it's written as a shell script: each iteration through the loop involves running a separate instance of a program, be it echo, cp, etc. That means creating a new process, loading the program into RAM, running it, unloading it... lots and lots of system calls.

A C program could probably do the job in considerably less time.

Plus, I'm running through Cygwin...

[ein]

My guitar strap arrived today.
It's just as badass as I expected.

[sonerohi]

Finally done with all the funeral stuff for my uncle. During the procession, I saw some people that I know that were just driving around for their normal day. It was at a stoplight, and they ditched their car to come over and hug me through the window.

[Jackrabbit]

This campaign is ridiculous, why am I even trying to push a story. All the conflict is right here.

[Duke 2.0]

 DAMMIT PEOPLE STOP TRYING TO BATHE MY CHARACTER. I KNOW I MADE THE ONLY FEMALE ONE BUT FUCK.

[Cthulhu]

I would bathe any character who needs bathing.

Also, I've made it my mission in Morrowind to purchase a hooker of every race.  Just three to go.

[KaguroDraven]

Don't get a hairball.

[Virex]

It might be very memory-speed intensive, meaning that your RAM just can't pass the data to your CPU fast enough, hence the low speed even with a low CPU usage.

I suspect the reason it's so slow is because it's written as a shell script: each iteration through the loop involves running a separate instance of a program, be it echo, cp, etc. That means creating a new process, loading the program into RAM, running it, unloading it... lots and lots of system calls.

A C program could probably do the job in considerably less time.

Plus, I'm running through Cygwin...

Considering it's essentially tail recursion, Scheme would probably be the best choice for a program like this, unless you're going to muck with assembly, in which case you can probably abuse the stack so horrible even reality cringes at the thought. On CPU's that prefetch the program you might even be able to do it all in the prefetch, which would be lightning-fast and almost uninterruptable, though I don't know if most CPU's support backwards jumps in the prefetch.

[Realmfighter]

Thats a guy.

Holy shit.

[Jackrabbit]

I love how I can go, "holy shit I would do that in a heart beat" and then do a double take and go "holy shit I would do that in a heart beat". It happens all the time.

Also I bet he has a lovely personality and yeah yeah whatever he's hot.