Create a bunch of dummy text files

for i in {1..4096}; do base64 /dev/urandom | head -c 8192 > dummy$i.rnd ; done
Using the 'time' command, running this with 'tr' took 28 seconds (and change) each time but using base64 only took 8 seconds (and change). If the file doesn't have to be viewable, pulling straight from urandom with head only took 6 seconds (and change)

2 Alternatives + Submit Alt

What Others Think

Following on from your speed test... If you use direct IO in dd, you can halve the time. for i in {0001..4096}; do dd if=/dev/urandom direct bs=8K count=1 of=dummy$i.rnd &> /dev/null; done This takes under 3 secs, versus about 6 secs for your command.
flatcap · 445 weeks and 1 day ago
Sorry, ignore that comment completely. (it was faster because it wasn't doing anything at all) /me is embarrassed
flatcap · 445 weeks and 1 day ago

What do you think?

Any thoughts on this command? Does it work on your machine? Can you do the same thing with only 14 characters?

You must be signed in to comment.

What's this? is the place to record those command-line gems that you return to again and again. That way others can gain from your CLI wisdom and you from theirs too. All commands can be commented on, discussed and voted up or down.

Share Your Commands

Stay in the loop…

Follow the Tweets.

Every new command is wrapped in a tweet and posted to Twitter. Following the stream is a great way of staying abreast of the latest commands. For the more discerning, there are Twitter accounts for commands that get a minimum of 3 and 10 votes - that way only the great commands get tweeted.


Subscribe to the feeds.

Use your favourite RSS aggregator to stay in touch with the latest commands. There are feeds mirroring the 3 Twitter streams as well as for virtually every other subset (users, tags, functions,…):

Subscribe to the feed for: