Hide

What's this?

commandlinefu.com is the place to record those command-line gems that you return to again and again.

Delete that bloated snippets file you've been using and share your personal repository with the world. 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.


If you have a new feature suggestion or find a bug, please get in touch via http://commandlinefu.uservoice.com/

Get involved!

You can sign-in using OpenID credentials, or register a traditional username and password.

First-time OpenID users will be automatically assigned a username which can be changed after signing in.

Hide

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.

» http://twitter.com/commandlinefu
» http://twitter.com/commandlinefu3
» http://twitter.com/commandlinefu10

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:

Hide

News

2011-03-12 - Confoo 2011 presentation
Slides are available from the commandlinefu presentation at Confoo 2011: http://presentations.codeinthehole.com/confoo2011/
2011-01-04 - Moderation now required for new commands
To try and put and end to the spamming, new commands require moderation before they will appear on the site.
2010-12-27 - Apologies for not banning the trolls sooner
Have been away from the interwebs over Christmas. Will be more vigilant henceforth.
2010-09-24 - OAuth and pagination problems fixed
Apologies for the delay in getting Twitter's OAuth supported. Annoying pagination gremlin also fixed.
Hide

Tags

Hide

Functions

Load file into RAM (cache) for faster accessing for repeated usage

Terminal - Load file into RAM (cache) for faster accessing for repeated usage
cat <file> > /dev/null
2011-11-12 15:45:27
User: totti
Functions: cat
8
Load file into RAM (cache) for faster accessing for repeated usage

Best result when file size less than half of RAM size

Alternatives

There are 2 alternatives - vote for the best!

Terminal - Alternatives

Know a better way?

If you can do better, submit your command here.

What others think

+1 This is a great trick. This works because most OS's these days use memory not used by applications to cache file contents. When a file is read (here using the cat program) its contents are put into the page cache and subsequent accesses to that file don't have to touch disk... For more read this great blog post: http://duartes.org/gustavo/blog/post/page-cache-the-affair-between-memory-and-files

Comment by bwoodacre 153 weeks and 5 days ago

I don't think this will help much. The file will be cached during the first "real" access anyway. You would enter this command only if you have idle time now and already know that you will need a certain file later. But if you have idle, why not just begin the task?

On the other hand, projects like readahead https://fedorahosted.org/readahead/ try to speed up the boot process by preloading files that will be needed during boot.

Comment by hfs 153 weeks and 3 days ago

Suppose

1. The system (HDD) is not idle and i want to copy from an low speed device like CD,pen drive etc to the HDD.

2. I want to edit a big file and save it to the same DISK. (Or just backup it)

Comment by totti 152 weeks and 5 days ago

Your point of view

You must be signed in to comment.

Related sites and podcasts