cat /dev/urandom

cat /dev/urandom

(while true; do seq -s "x" 2000; seq -s "x" 1000; seq -s "x" 5000;done) | aplay

Like the jingle I came up with, /prog/?

>>2
Awesome code. Great size. Looks concise. Efficient. Elegant. Keep us all posted on your continued progress with any new code factoring or compiler optimization. Show us what you got man. Wanna see how freakin' expressive, efficient, concise and elegant you can get. Thanks for the motivation.

(while true; do fortune | cowsay; done) | aplay

delicious ear rape


sudo cat -v /dev/urandom | cat -v | cat -v | cat -n | cat -n | cat -v | cat -n | cat -n | cat -n | cat -n | cat -n | cat -n | cat -n | cat -n | cat -n | cat -n | cat -n | cat -n | cat -n | cat -n > /dev/dsp


all the line numbers give it a cool sound.

also this is always interesting:

sudo cat /dev/sda > /dev/dsp

The best is to cat video game cds. Sometimes it'll run through all the sound files and you'll hear a bunch of distorted yells, grunts, and clicking sounds.

sudo dd if=/dev/urandom of=/dev/mem bs=65536 seek=10

Guess what it does (hint: convert 65536 * 10 to hexadecimal and then think about memory addresses).

>>7
Writes random trash to your memory-mapped EGA/VGA display adapter.

Only on x86 and only in real mode, which no one here would see.

And then continues on writing, until it overwrites your protected mode's Interrupt Descriptor Table, and disk-writes probably fail, while it attempts to follow the newly-minted pointer you just wrote with with random data, and starts executing shit at a random existent-or-nonexistent memory location, the latter causing a kernel panic due to trying to access invalid memory.

Where do I send your cookie, clever girl?

>>8
only in real mode
No. You can have a EGA/VGA or compatible in protected mode.

>>9
Sure can.

If you're in the correct, ancient video mode, and not using frame-buffering, or have the 64k VGA aperture enabled, and not using frame-buffering, and the OS doesn't remap your video memory to a different location.  Modern cards can map to any location, and use a hell of a lot more than 64k.

And before your command continues on and trashes the operating system.

For instance, dd if=/dev/mem of=/cock skip=10 bs=64K count=2 on my system, shows my video memory contains the very useful:

$ hexdump -C /cock
00000000  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  |................|
*
00010000  ff ff ff ff ff ff ff ff  ff ff ff ff ff ff ff ff  |                |
*
00020000

despite my console having text on it (which is rendered in the alternating ATTR-CHAR-ATTR-CHAR format, in the ancient video mode).

Use the count argument next time, turbo.

>>10
I know about that. But it is possible.

>>11
It's also possible that you may someday know a woman in the carnal sense, but it is as unlikely as anyone being affected by your 15-year-old "exploit".  Sure, this dosemu terminal here cries when I do it at b800:0000 with debug.com, but anyone not still running Windows 98 almost certainly won't even notice anything on their screen, until your runaway command obliterates the rest of their OS.

>>12
Not to harp on technicalities, but wouldn't »his runaway command obliterating the rest of their OS« count as ‘‘being affected’’?

>>13 Ass-burgers: It's what's for dinner.

>>14
Oh, would you fuck off back to the imageboards already.

>>13
Yes, obviously. But you have no reason to be worrying about that. Are you running some ancient version of DOS/Windows on a 486 with an Internet connection? All my 10+ year old machines are pretty much in full retirement.

>>15

>All my 10+ year old machines are pretty much in full retirement.

hook them up on an etharnet and have them do some data mining.

>>16
Look up "data mining", champ.