Linux Command Line Cheat Sheet

could you please add ll comand

check this sheet! https://cheatography.com/sathyanarayanan/cheat-sheets/linux-command-line/

thanks Dave besides ^w my most used nano commands: Alt+Space Go back one word Ctrl+Space Go forward one word

thank you very much Dave

All links for download are dead, pleas fix this issue ASAP. Would be greatly appreciated, thanks.

Good for quick reference Thank you

I think the colour pdf link directs back to the original page

Good job Dave, Thank you :)

Thank you, Natalie!

thank you for this really useful sheet ! The download button seems to be broken though :(

Hey GloObi, thanks for the heads up about the broken download button on this cheatsheet. We'll get it fixed and I'll let you know when its been done. Have a great day.

Hi GloObi, This is now fixed. Please let me know if you have any more problems. Nat

Can't download. Sad.

Thanks d.falkovsky, I will let Dave know the download button on this cheat sheet needs to be fixed. I will let you know once he has fixed it :). Sorry for the inconvenience.

Hi d.falkovsky, This is now fixed, you should now be able to download. Please let me know if you have any more problems. Nat

Could you add "passwd" to the file? :)

Love the colour, but could it be a slightly darker/stronger green? It comes out almost impossible to read on my colour printer. I tried outputting in greyscale, but the green-on green sections are still unreadable. Needs more contrast. Alternatively, change all the green texts to black and keep the backgrounds green?

I agree, it's not a great colour. I've changed it.

'echo $SHELL' actually prints the default shell, 'ps -p $$' will print the current shell

would be good to add Ctrl-left/right for jumping arguments, Ctrl-home/end for jumping whole line.

ls -h? human readable?

head -n1 /etc/issue as a means to access distribution name isn't reliable, since the post-login screen could have been customized. A more reliable version would be sed -nr 's/^PRETTY_NAME=(.*)/\1/p' /etc/os-release . This should be true even for distros using legacy init (i.e., current Debian, Gentoo and even Slackware).

I've always found `mkdir -p path/to/directory` to be useful.

theres also a good one here: http://www.techietek.com/2014/04/29/linux-cli-cheat-sheet-wallpaper/

Command that might be used to test connectivity of Linux box to the Internet, get logged on user info, and get TCP/IP configuration info. Can anyone help me?

add task manage comman: gnome-system-monitor

Great resource - thanks a lot Dave!

Great reference! The section on Screen is missing "Ctrl-A d" for detaching.

I would suggest to put in screen <tty.device> <baudrate> – just in case anybody needs to connect to some serial console…

grep -B# This shows what you are searching plus additional lines where number is added. Great for DHCP lease searching.

Hi, handy sheet. Just one thing. Find will do a recursive search by default. In the find /dir -name name* should be in double quotes if you want it to recursively find all files starting with name: find /dir/ -name "name*" That's because, without the quotes, the shell will expand the wildcard before handing the parameters to find. To unexpected things might happen if you don't have the quotes. Please see the examples below: $ find . . ./name1 ./name2 ./dir1 ./dir1/name3 ./dir1/name1 ./dir1/test3 ./test1 $ find . -name name* find: paths must precede expression: name2 Usage: find [-H] [-L] [-P] [-Olevel] [-D help|tree|search|stat|rates|opt|exec] [path...] [expression] $ find . -name "name*" ./name1 ./name2 ./dir1/name3 ./dir1/name1 $ touch dir1/fred1 $ find . . ./name1 ./name2 ./dir1 ./dir1/name3 ./dir1/name1 ./dir1/test3 ./dir1/fred1 ./test1 $ find . -name name* find: paths must precede expression: name2 Usage: find [-H] [-L] [-P] [-Olevel] [-D help|tree|search|stat|rates|opt|exec] [path...] [expression] $ find . -name "name*" ./name1 ./name2 ./dir1/name3 ./dir1/name1 $ find . -name fred* ./dir1/fred1 $ find . -name "fred*" ./dir1/fred1 $

Good job on the cheatsheet - this will definitely come in handy for my Linux exam next week. Some commands on umask would be a good addition to this cheatsheet :).

There is no commands for shutdown or reboot..

thank you very much, it is great

This is bash-tastic!

Or if the PDF at least split into 2 pages (so it could be a laminated 2-sided sheet) without cutting commands in half.

Nice work, but it would be best as a single page PDF.

Missing: sed find -exec

What about CTRL+y to paste the stuff you cut back in? How can you leave that out? CTRL+a/e and CTRL+u/y are the pairs I remember.

Great resource - thanks for taking the time and trouble to put this out there. My favorite ls options are '-ltr' . The t sorts files by time, and r reverses that, so newest files show up right above the prompt, no matter how long the listing is.

Nice one...really helpful

I would also add the tar command. No sysadmin would survive without it. To extract tar.gz archive tar xvzf archive.tar.gz To extract tar.bz2 archive tar xvjf archive.tar.bz2 To extract tar archive tar xvf archive.tar To create archive tar cvzf archive.tar.gz /file_or_folder/to/archive

This cheat-sheet is very good! Thanks for that. However, I don't like the "chmod" commands you are using. I don't think anybody should use the numeric version of chmod anymore. Your example "chmod -R 600 folder", is the best way to lock yourself out of your own folder and loose any executable bits on the scripts. I would rather use the symbolic version: chmod -R u+rw folder # Add read-write for user on all files in folder chmod -R og-rwx # Remove read write and execute bits for "other" and "group" on all files in folder And my all-time favorite: chmod -R og=u-w folder # Give other and group the same rights as user, but removing writing rights. Of course, this also handles t and s bits: chmod u+s file chmod o+t folder

Show human readable format (kb, mb...) ls -lh

CTRL-Z sleeps (stops) the running process. fg [#] brings it back to foreground. top CTRL-Z ps aux | grep top fg

hi!.these are useful cheat sheet .

you need to figure out how to split your command sheet as a pdf

Excellent Stuff man.. I think these are the most commonly used commands.. Good Effort.

I just wanted to take a moment to thank you for putting this together. This is a big help to me I am new to OpenFiler witch I believe uses bash at the core so I am of course new to Linux. I didn't really think it would be quite so difficult to find resources that one can use to navigate the command line but I guess most folks use the GUI. But, I'm not most folks when I bought my first IBM 8088 I started with DOS.Anyway, thanks for the time and effort you put into this, sorry about digressing there.

I'd just like to point out a trick I use with the head and tail commands: First, you can designate the number of lines to return, like so: head -100 filename I often use both head and tail together to get a section of a file by piping the output of one into the other. The following command gets 100 lines, starting 1000 lines before the end of the file: tail -1000 filename | head -100 You could, of course, reverse the commands to get a section near the top of the file. To get lines 91-100: head -100 filename | tail -10

Love your work....it is so ....so helpful! I would like to format a MicroDisk using Linux Centros. When I look at the Partition on the MicroDisk, I see the following comment....(non-Linux). This makes sense, since I formatted with a computer running Win 7! I want to use it on my Linux system but do not know how to do it. I tried format /dev/scd1 but no joy! Thank you Don

Hi, Fantastic good job.. Thanks

Good work. Thanks, its helpful.

download PDF is broken

Awesome job! This will definitely come in handy

Thanks a lot for your sheet, I just need such a linux command summary such as this sheet.

I think the "Bash Shortcuts" part is a little misleading. The "ctrl-a", "ctrl-e", "ctrl-k" is in emacs mode. But there should be many people preferring vim-mode or some thing like that.

ls -h is handy - changes sizes to human readable formats. Goes along good with -S. If I'm using it it is generally a ls -alhS

On the redirects, the one I most commonly use is ignoring errors (2>/dev/null, or more succinctly 2>&- ). For example, if I'm looking for files and I don't care that I haven't access to parts of the filesystem, we might do something like: find / -name "*.html" 2>&-

How are the indented lines added several of the cells like Screen Shortcuts? RE: http://getsatisfaction.com/cheatography/topics/adding_a_two_line_entry_in_a_list

Those indented bits are a "question and answer" format box.

Ah, Q&A means I would be able to cheat with it and use it for two column with an extra line. Thanks for the info. (Replying to my original post seems unintuitive for trying to reply under your post, but not to the overall thread... assuming this post as I'm thinking it might.)

The I/O redirection section could use "2>" and "&>" examples, I always forget how to redirect stderr

Good idea - I'll add that (once I remember how they work myself ... :) )

I've updated that section to include stderr redirection. :)

Thanks for creating this cheat-sheet Dave. The one thing I missed was "grep -o"; Show only the part of a matching line that matches PATTERN

I've added "grep -o" to the cheat sheet :)