mirror of
https://codeberg.org/Mo8it/How_To_Linux.git
synced 2024-11-22 02:58:03 +00:00
Fix typos
This commit is contained in:
parent
33edf04a72
commit
6aff23c488
1 changed files with 7 additions and 7 deletions
|
@ -25,7 +25,7 @@ Congratulation! You did just say hi to your computer and it did even reply! What
|
|||
|
||||
Well, to be more precise, you gave a command to your computer to say "Hello!" and it did that.
|
||||
|
||||
I know, I did just brake the romance between you and your computer. I appoligize. 😶
|
||||
I know, I did just brake the romance between you and your computer. I apologize. 😶
|
||||
|
||||
`echo` is a command that prints out what you give as an argument. It might not seem to be a useful command. Why would I want the computer to echo my words? The importance of `echo` will be clear mainly when writing scripts. More about this in later sections!
|
||||
|
||||
|
@ -39,7 +39,7 @@ To examine this, lets first create a new directory. Enter the command `mkdir emp
|
|||
|
||||
Is `empty_house` really empty? Lets verify that.
|
||||
|
||||
Enter the command `cd empty_house`. Again, you don't see an output. But maybe you did notice that a part of your prompt changed from `~` to `empty_house`. This indicates that you are in your new directory. `cd` stands for _change directory_. Knowing the meaning of the commands you use which are often abbrevations does help you to memorize them.
|
||||
Enter the command `cd empty_house`. Again, you don't see an output. But maybe you did notice that a part of your prompt changed from `~` to `empty_house`. This indicates that you are in your new directory. `cd` stands for _change directory_. Knowing the meaning of the commands you use which are often abbreviations does help you to memorize them.
|
||||
|
||||
Now enter the command `ls`. You should not be seeing anything because the directory is indeed empty.
|
||||
|
||||
|
@ -186,7 +186,7 @@ Y Yes
|
|||
N No ^C Cancel
|
||||
```
|
||||
|
||||
A buffer is a file that is being edited in the memory. If you klick `N`, then your editions are lost! In our case, we want to save the rules. Therefore, we press `Y`.
|
||||
A buffer is a file that is being edited in the memory. If you click `N`, then your editions are lost! In our case, we want to save the rules. Therefore, we press `Y`.
|
||||
|
||||
Now it shows us:
|
||||
|
||||
|
@ -206,7 +206,7 @@ No zombies!
|
|||
No loud housemates!
|
||||
```
|
||||
|
||||
We did use `cat` to only print the content of the file `rules.txt` without opening it with an editor. `cat` stands for _concatinate_. This does not sound like printing file content!? This is because `cat` can be used to concatinate the content of different files. But this is not relevant for now.
|
||||
We did use `cat` to only print the content of the file `rules.txt` without opening it with an editor. `cat` stands for _concatenate_. This does not sound like printing file content!? This is because `cat` can be used to concatenate the content of different files. But this is not relevant for now.
|
||||
|
||||
### Manuals
|
||||
|
||||
|
@ -366,7 +366,7 @@ $ ls ...
|
|||
ls: cannot access '...': No such file or directory
|
||||
```
|
||||
|
||||
So this does not work. Anything number of dots greater that 2 does not word, except if we use separtors. To access the parent directory of the parent directory, you can use `../..`:
|
||||
So this does not work. Anything number of dots greater that 2 does not word, except if we use separators. To access the parent directory of the parent directory, you can use `../..`:
|
||||
|
||||
```console
|
||||
$ ls ../..
|
||||
|
@ -375,10 +375,10 @@ USERNAME (...)
|
|||
|
||||
You will probably only see your user name as output, but if the system you are using has more than one user, then names of the other users would be in the output, too. Every user has his own home directory under `/home`.
|
||||
|
||||
The usage of `../..` or even more dots like `../../..` is not recommended since you would have to go multiple directories up in your mind and this does not work well! Use the full path for paths not in the current `.` or in the parent direcotry `..`.
|
||||
The usage of `../..` or even more dots like `../../..` is not recommended since you would have to go multiple directories up in your mind and this does not work well! Use the full path for paths not in the current `.` or in the parent directory `..`.
|
||||
|
||||
What we have just learned about paths does not only apply to `cp`, but also to `ls`, `mkdir`, `mv` and other commands that deal with paths.
|
||||
|
||||
One thing has to be mentioned about `cp`: To copy directories instead of just files, use the option/flag `-r` to copy recursively like with `mv`.
|
||||
|
||||
It might be overwhelming for you to memorize all the commands. Again, if a command is an abbrevation, then knowing what it stands for is very helpful. Otherwise, just look up the command you are looking for in this book or in a search engine ;)
|
||||
It might be overwhelming for you to memorize all the commands. Again, if a command is an abbreviation, then knowing what it stands for is very helpful. Otherwise, just look up the command you are looking for in this book or in a search engine ;)
|
||||
|
|
Loading…
Reference in a new issue