Shell Access: Difference between revisions
No edit summary |
No edit summary |
||
| (7 intermediate revisions by 4 users not shown) | |||
| Line 1: | Line 1: | ||
# Go to a beach (preferably not [[ | # Go to a beach (preferably not [[The beach that makes you old|one that makes you old]]); | ||
# Look for something that looks like this: <br> [[File:Different types of shells.jpg|400px]] | # Look for something that looks like this: <br> [[File:Different types of shells.jpg|400px]] | ||
# The command is <code>ssh</code>. | # The command is <code>ssh</code>. | ||
| Line 6: | Line 6: | ||
=== Open the Terminal === | === Open the Terminal === | ||
You need to open a terminal window to log into the shell. The way you do that is different depending on what your computer is running: | You need to open a terminal window to log into the [[shell]]. The way you do that is different depending on what your computer is running: | ||
==== Windows 11 ==== | ==== [[Windows]] 11 ==== | ||
Open "'''Terminal'''" | Open "'''Terminal'''" | ||
| Line 34: | Line 34: | ||
You can think of the shell as a really fucked up Start Menu. You can type the name of a program at the prompt and press enter, and the shell will attempt to locate and run it. Everything you type after the name of the program is an "argument", which you can use to tell the program what you want it to do. Take this command for example: | You can think of the shell as a really fucked up Start Menu. You can type the name of a program at the prompt and press enter, and the shell will attempt to locate and run it. Everything you type after the name of the program is an "argument", which you can use to tell the program what you want it to do. Take this command for example: | ||
mkdir my_folder | mkdir my_folder | ||
This uses <code>mkdir</code> (short for "Make Directory" ("directory" is another word for "folder")) to create a folder called <code>my_folder</code>. In this example, <code>mkdir</code> is the name of the program and <code>my_folder</code> is the single argument. | This uses <code>mkdir</code> (short for "Make Directory" ("directory" is another word for "folder")) to create a folder called <code>my_folder</code>. In this example, <code>mkdir</code> is the name of the program and <code>my_folder</code> is the single argument. | ||
most people call the first bit the command and also call the whole command a command. good for them :) | |||
== assorted tips == | == assorted tips == | ||
| Line 85: | Line 87: | ||
|<code>cd wacky_folder</code> | |<code>cd wacky_folder</code> | ||
|} | |} | ||
== getting help == | |||
Commands have many options which can be hard to remember. Luckily, there's plenty of resources you can consult for help on how to use a command. | |||
=== man pages === | |||
The <code>man</code> command (short for "manual") lets you search detailed documentation about commands and more. If you're not sure about the <code>ls</code> command, just type <code>man ls</code> and hit enter. You can use the f or b keys to scroll forward and backward and press q when you're ready to quit. | |||
=== tldr pages === | |||
The man pages are super detailed but sometimes all you want are some short examples. If that's the situation you're facing, the [https://tldr.sh/ tldr pages] can help. You can view the results in your browser, or install the tldr software locally. | |||
=== help flag === | |||
Some (but not all) commands have built-in help. How to get this to show up will vary from case to case but often using a flag is all you need to do. For example, if you're confused about the <code>git</code> command <code>git --help</code> can point you in the right direction. | |||
[[Category:Pages with some amount of information in them]] [[Category:Pages that need things added to them]] | [[Category:Pages with some amount of information in them]] [[Category:Pages that need things added to them]] | ||