{"id":64785,"date":"2022-06-02T09:00:31","date_gmt":"2022-06-02T09:00:31","guid":{"rendered":"https:\/\/www.cryptocabaret.com\/?p=64785"},"modified":"2022-06-02T09:00:31","modified_gmt":"2022-06-02T09:00:31","slug":"the-only-linux-command-you-need-to-know","status":"publish","type":"post","link":"https:\/\/www.cryptocabaret.com\/?p=64785","title":{"rendered":"The only Linux command you need to know"},"content":{"rendered":"

The only Linux command you need to know<\/span>
\nSeth Kenlon<\/a><\/span>
\nThu, 06\/02\/2022 – 03:00<\/span><\/p>\n

\n
1 reader likes this<\/div>\n
1 reader likes this<\/div>\n<\/div>\n
\n

Information about Linux and open source abounds on the internet, but when you’re entrenched in your work there’s often a need for quick documentation. Since the early days of Unix, well before Linux even existed, there’s been the man<\/code> (short for “manual”) and info<\/code> commands, both of which display official project documentation about commands, configuration files, system calls, and more.<\/p>\n

There’s a debate over whether man<\/code> and info<\/code> pages are meant as helpful reminders for users who already know how to use a tool, or an intro for first time users. Either way, both man<\/code> and info<\/code> pages describe tools and how to use them, and rarely address specific tasks and how to accomplish them. It’s for that very reason that the cheat<\/code> command was developed.<\/p>\n

For instance, suppose you can’t remember how to unarchive a tar file<\/a>. The man<\/code> page provides you with all the options you require, but it leaves it up to you to translate this information into a functional command:<\/p>\n

\n
tar<\/span> -A<\/span> [<\/span>OPTIONS]<\/span> ARCHIVE ARCHIVE
tar<\/span> -c<\/span> [<\/span>-f ARCHIVE]<\/span> [<\/span>OPTIONS]<\/span> [<\/span>FILE...]<\/span>
tar<\/span> -d<\/span> [<\/span>-f ARCHIVE]<\/span> [<\/span>OPTIONS]<\/span> [<\/span>FILE...]<\/span>
tar<\/span> -t<\/span> [<\/span>-f ARCHIVE]<\/span> [<\/span>OPTIONS]<\/span> [<\/span>MEMBER...]<\/span>
tar<\/span> -r<\/span> [<\/span>-f ARCHIVE]<\/span> [<\/span>OPTIONS]<\/span> [<\/span>FILE...]<\/span>
tar<\/span> -u<\/span> [<\/span>-f ARCHIVE]<\/span> [<\/span>OPTIONS]<\/span> [<\/span>FILE...]<\/span>
tar<\/span> -x<\/span> [<\/span>-f ARCHIVE]<\/span> [<\/span>OPTIONS]<\/span> [<\/span>MEMBER...]<\/span><\/div><\/div><\/pre>\n
That’s exactly what some users need, but it confounds other users. The cheat sheet for tar, by contrast, provides complete common commands:<\/p>\n
\n
$ cheat tar<\/span>

# To extract an uncompressed archive:<\/span>
tar<\/span> -xvf<\/span> \/<\/span>path\/<\/span>to\/<\/span>foo.tar

# To extract a .tar in specified Directory:<\/span>
tar<\/span> -xvf<\/span> \/<\/span>path\/<\/span>to\/<\/span>foo.tar -C<\/span> \/<\/span>path\/<\/span>to\/<\/span>destination\/<\/span>

# To create an uncompressed archive:<\/span>
tar<\/span> -cvf<\/span> \/<\/span>path\/<\/span>to\/<\/span>foo.tar \/<\/span>path\/<\/span>to\/<\/span>foo\/<\/span>

# To extract a .tgz or .tar.gz archive:<\/span>
tar<\/span> -xzvf<\/span> \/<\/span>path\/<\/span>to\/<\/span>foo.tgz
tar<\/span> -xzvf<\/span> \/<\/span>path\/<\/span>to\/<\/span>foo.tar.gz
[<\/span>...]<\/span><\/div><\/div><\/pre>\n
It’s exactly what you need, when you need it.<\/p>\n<\/p>\n
\n
More Linux resources<\/div>\n
\n
Linux commands cheat sheet<\/a><\/div>\n
Advanced Linux commands cheat sheet<\/a><\/div>\n
Free online course: RHEL technical overview<\/a><\/div>\n
Linux networking cheat sheet<\/a><\/div>\n
SELinux cheat sheet<\/a><\/div>\n
Linux common commands cheat sheet<\/a><\/div>\n
What are Linux containers?<\/a><\/div>\n
Our latest Linux articles<\/a><\/div>\n<\/p><\/div>\n<\/p><\/div>\n
The Linux cheat command<\/h2>\n
The cheat<\/code> command is a utility to search for and display a list of example tasks you might do with a Linux command. As with many Unix commands, there are different implementations of the same concept, including one written in Go<\/a> and one, which I help maintain, written in just 100 lines of Bash<\/a>.<\/p>\n
To install the Go version, download the latest release<\/a> and put it somewhere in your path<\/a>, such as ~\/.local\/bin\/<\/code> or \/usr\/local\/bin<\/code>. To install the Bash version, download the latest release and run the install-cheat.sh<\/code> script:<\/p>\n
\n$ <\/span>sh<\/span> .\/<\/span>install-cheat.sh<\/code><\/span><\/pre>\n
\n
$ aclocal<\/span> ; autoconf<\/span>
\n$ automake<\/span> --add-missing<\/span> ; autoreconf
\n$ .\/<\/span>configure --prefix<\/span>=$HOME<\/span>\/<\/span>.local
\n$ make<\/span>
\n$ make<\/span> install<\/span><\/div><\/div><\/pre>\n
Get cheat sheets for your Linux terminal<\/h2>\n
Cheat sheets are just plain text files containing common commands. The main collection of cheat sheets is available at Github.com\/cheat\/cheatsheets<\/a>. The Go version of cheat downloads cheatsheets for you when you first run the command. If you’re using the Bash version of cheat, the --fetch<\/code> option downloads cheatsheets for you:<\/p>\n
\n$ <\/span>cheat --fetch<\/span><\/code><\/span><\/pre>\n
As with man<\/code> pages, you can have multiple collections of cheat sheets on your system. The Go version of cheat uses a YAML<\/a> config file to define where each collection is located. The Bash version defines the path during the install, and by default downloads the Github.com\/cheat\/cheatsheets<\/a> collection as well as Opensource.com<\/a>‘s own Gitlab.com\/opensource.com\/cheatsheets<\/a> collection.<\/p>\n
List cheat sheets<\/h2>\n
To list the cheat sheets on your system, use the --list<\/code> option:<\/p>\n
\n
$ cheat --list<\/span>
\n7z
\nab
\nacl
alias<\/span>
\nansi
\nansible
\nansible-galaxy
\nansible-vault
\napk
[<\/span>...]<\/span><\/div><\/div><\/pre>\n
View a Linux cheat sheet<\/h2>\n
Viewing a cheat sheet is as easy as viewing a man<\/code> or info<\/code> page. Just provide the name of the command you need help with:<\/p>\n
\n
$ cheat alias<\/span>

# To show a list of your current shell aliases:<\/span>
alias<\/span>

# To alias `ls -l` to `ll`:<\/span>
alias<\/span> ll<\/span>='ls -l'<\/span><\/div><\/div><\/pre>\n
By default, the cheat<\/code> command uses your environment’s pager. Your pager is set with the PAGER<\/code> environment variable<\/a>. You can override that temporarily by redefining the PAGER<\/code> variable before running the cheat<\/code> command:<\/p>\n
\n$ <\/span>PAGER<\/span>=most cheat less<\/span><\/code><\/span><\/pre>\n
\n$ <\/span>cheat --cat<\/span> less<\/span><\/code><\/span><\/pre>\n
It’s not actually cheating<\/h2>\n
The cheat system cuts to the chase. You don’t have to piece together clues about how to use a command. You just follow the examples. Of course, for complex commands, it’s not a shortcut for a thorough study of the actual documentation, but for quick reference, it’s as fast as it gets.<\/p>\n
You can even create your own cheat sheet just by placing a file in one of the cheat sheet collections. Good news! Because the projects are open source, you can contribute your personal cheat sheets to the GitHub collection. And more good news! When there’s a new Opensource.com cheat sheet<\/a> release, we’ll include a plain text version from now on so you can add that to your collection.<\/p>\n
The command is called cheat<\/code>, but as any Linux user will assure you, it’s not actually cheating. It’s working smarter, the open source way.<\/p>\n<\/div>\n
\n
The Linux cheat command is a utility to search for and display a list of example tasks you might do with a command.<\/p>\n<\/div>\n
\n
\n
  \"Command<\/div>\n
Image by: <\/span><\/p>\n
Opensource.com<\/p>\n<\/div>\n<\/article>\n<\/div>\n
\n
Linux<\/a><\/div>\n<\/p><\/div>\n
What to read next<\/div>\n

\n        \"Creative<\/a>This work is licensed under a Creative Commons Attribution-Share Alike 4.0 International License.<\/div>\n
\n
\n
Register<\/a> or Login<\/a> to post a comment.<\/div>\n<\/p><\/div>\n<\/section>\n
Powered by WPeMatico<\/a><\/small><\/p>\n","protected":false},"excerpt":{"rendered":"
The only Linux command you need to know Seth Kenlon Thu, 06\/02\/2022 – 03:00 1 reader likes this 1 reader likes this Information about Linux and open source abounds on the internet, but when you’re entrenched in your work there’s often a need for quick documentation. Since the early days of Unix, well before Linux […]<\/p>\n","protected":false},"author":1,"featured_media":64786,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[307],"tags":[],"class_list":["post-64785","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-open-source"],"_links":{"self":[{"href":"https:\/\/www.cryptocabaret.com\/index.php?rest_route=\/wp\/v2\/posts\/64785","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.cryptocabaret.com\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.cryptocabaret.com\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.cryptocabaret.com\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.cryptocabaret.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=64785"}],"version-history":[{"count":0,"href":"https:\/\/www.cryptocabaret.com\/index.php?rest_route=\/wp\/v2\/posts\/64785\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.cryptocabaret.com\/index.php?rest_route=\/wp\/v2\/media\/64786"}],"wp:attachment":[{"href":"https:\/\/www.cryptocabaret.com\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=64785"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.cryptocabaret.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=64785"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.cryptocabaret.com\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=64785"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}
If you just want to cat<\/a> the cheat sheet into your terminal without a pager, the Bash version has a --cat<\/code> option for convenience:<\/p>\n
Or to configure the installation, use Autotools<\/a>:<\/p>\n