If you have any suggestions or criticisms, feel free to comment them.
Being plain text, it’s much easier to read on a wide screen, or on something without line wrapping.
^S - stop terminal IO
^Q - resume terminal IO (if your terminal looks frozen, this is the one to try)
alt-b, alt-f - jump back/forward one wordcd -changes to the previous directoryDoes
cd +work to go forward after usingcd -?
What do you mean about “/ root directory, eg /usr/bin/bash”? / is /, just the top-most directory
Yes, the top most directory, /, is the root directory.
Each directory is a branch in one giant tree structure. For example, if you have a directory containing two other directories, that is a branch that is splitting into two branches. All directories are descendants of the same root.
I added more detail to the description and made a more relevant example. (I think)
I find the references to file extension kinda confusing. Extensions mean a lot less in Linux cli, but I can tell youre just using them for examples. Maybe give more concrete examples instead.
ls *.shto list all the files ending in.shI updated various examples, and replaced <file extension> with <text> in most places and removed it from the legend.
Interesting compilation, there is cheat.sh, tldr and others though
I made this just as much for me as I did for others. Writing things down myself really helps me memorize them.
Cool, thank you!
Thanks for all the feedback! I’m much happier with it now, and I’ll probably continue to make small changes over time.
Nice work.
My tiny nitpick is that “touch” will create the file you specify if it doesn’t exist. I’ve seen this usage a lot, so your example may benefit from mentioning it.
This is fantastic. Just at a glance I already learned something new! Definitely keeping this for reference.
This is really nice!
would you upload this on github?
Done? I’ve never uploaded to GitHub before, and I was just doing what I thought I should do. I’ll do my best to keep it updated with the version on my website.
https://github.com/ordinarybyte/linux_cheat_sheet
Is there a way to make GitHub automatically detect changes to the file at cerium.cc and update the repo? Or do they not allow that? I know a scheduled script would be able to work but I don’t really want to have to run it myself.
I’ve been using Linux for decades and I bet that’ll still come in handy.
Oh. My. Gosh. I love this. Thank you. And thank you for being
--verboseabout the provenance and history of the document. And big big thank yous for the Internet Archive links. Bravo.Wow. I’ll definitely avoid Linux now. I had heard Linux was supposed to be easy to use now.
All this terminal stuff is absolutely not necessary for an average user; graphical applications are often more than enough
@ian @asciiandarch If all you do is web browsing, document processing and graphical games you may never ever touch the terminal ;)
It is not as complicated as it looks! As a long time windows user I’m in the process of getting used to the command line and I love the simplicity and direct way of doing things. For some tasks and small programs it is amazing. Grep for example is something amazing that you couldn’t do in a windows type UI.
For other stuff like visualizing a directory tree you can always use a mouse interface. You’re rarely forced to use the terminal.
Makes as much sense as saying “I’ll definitely avoid Windows now. I had heard that Windows was supposed to be easy to use”, since most of this also applies to WSL2.
Maybe the guide is not intended for some beginners after all?
I suppose. If your criticism is that it could have been more specific as to what you are a supposed “beginner” in, then I agree.
This is really helpful, thank you.
