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/
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.
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
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:
Makes a partition in ram which is useful if you need a temporary working space as read/write access is fast.
Be aware that anything saved in this partition will be gone after your computer is turned off.
There are 2 alternatives - vote for the best!
If you use eatmydata, all fsyncs will be ignored, so things will go much faster. Maybe not quite as fast as a ramdisk, but if you have enough free memory, the fs cache should help a lot. Just remember to sync afterwards--and if your system crashes in the middle of the command... :)
If you can do better, submit your command here.
You must be signed in to comment.
many systems come with a shared-memory "Device" pre-mounted. My distro (fedora) is mounted at /dev/shm.
Pretty handy when you want to borrow some ram for disk like purposes.
this is really great if you run gentoo and are going to compile something - if you mount a tmpfs at /var/tmp/portage, it'll emerge while storing temp files in ram instead of on the harddrive, leading to a faster emerge that doesn't bog down your harddrive. Take note though, not everything will compile if you don't have enough ram, esp. if it's something like gcc or gtk... about 700mb should be fine (i think)
this might be of interest too:
https://wiki.ubuntu.com/BootToRAM
No doubt this would torn out the ram while doing heavy-duty work provided if mounted under restricted places ;)
I have a detailed (verbose) notes on tmpfs here: http://www.askapache.com/web-hosting/super-speed-secrets.html
the truth is... hard disks suck. they're cheap, yes, but they're slow. and they fail. if you have lots of redundancy, then maybe you can overcome these deficiencies through scale. but what about the end user masses who don't use some elaborate redundancy setup?
i've been using mfs and tmpfs instead hard disk for quite some time for both "code" and "data". i only use hard disk for stuff i need to save. after using ram exclusively for a while you begin to see just how slow and unreliable hard disks really are, and you'll unlikely want to go back to using disks.
ram is the next best thing to the cpu's registers. there are quite few registers with the new cpus... it seems like overkill... b/c most of them are going unused. but they are there for speed. ram is ridiculously slow by comparison.
For OSX (tested on 10.7.3):
diskutil eraseVolume HFS+ RAMDisk `hdid -nomount ram://$((1024*2048))`This will be mounted at /Volumes/RAMDisk/
On FreeBSD systems you can use :
mdmfs -s 32m md /mnt