drummyfish/less_retarded_wiki
5
1
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity

Update

Browse source
This commit is contained in:
Miloslav Ciz 2025-03-01 01:35:35 +01:00
parent d89468d6da
commit 521e728375
39 changed files with 2037 additions and 1973 deletions
Download patch file Download diff file Expand all files Collapse all files

3
unix.md
View file

@ -33,7 +33,7 @@ UNDER CONSTRUCTION
*Note: here by "Unix" we will assume a system conforming to the POSIX standard from 2001.*
This section will help complete noobs kickstart their journey with a Unix-like system such as [GNU](gnu.md)/[Linux](linux.md) or [BSD](bsd.md). Please be aware that each system has its additional specifics, for example [package managers](package_manager.md), init systems and so on -- these you must learn about elsewhere as here we may only cover the core parts those systems inherited from the original Unix. Having learned this though you should be able to somewhat fly any Unix like system.
This section will help complete noobs kickstart their journey with a Unix-like system such as [GNU](gnu.md)/[Linux](linux.md) or [BSD](bsd.md). Please be aware that each system has its additional specifics, for example [package managers](package_manager.md), init systems and so on -- these you must learn about elsewhere as here we may only cover the core parts those systems inherited from the original Unix. Having learned this though you should be able to somewhat fly any Unix like system. Obviously we'll be making some simplifications here too.
Learning to use Unix practically means **learning the [command line](cli.md)** plus a few extra things (such as various concepts, philosophies, conventions, file system structure etc.). Your system will have a way for you to enter the command line where you can interact with it only through textual commands (i.e. without [GUI](gui.md)). Sometimes the system boots up to command line, sometimes you must click some icon (usually called *terminal*, *term*, *shell*, *command line* etc.), sometimes you can switch [TTY](tty.md)s with *CTRL+ALT+Fkeys* etc. To command line virgins this will seem a little intimidating but it's absolutely required to know at least the basics, on Unices the command line is extremely powerful, efficient and much can only ever be achieved through command line.
@ -45,6 +45,7 @@ You run a utility simply by writing its name, for example typing `ls` will show
Unix utilities (and other programs) can also be invoked with **arguments** that specify more detail about what should be done. Arguments are written after the utility name and are separated by spaces (if the argument itself should contain space, it must be enclosed between double quotes, e.g. `"abc def"`). For example the `cd` (change directory) utility must be given the name of a directory to go to, e.g. `cd mydirectory`.
Some arguments start with one or two minus characters (`-`), for example `-h` or `--help`. These are usually called **flags** and they serve either to set something on/off or to name other parameters. For example many utilities accept a `-s` flag which means "silent" and tells the utility not to write anything out. A flag oftentimes has a short and long form (the long form starts with two minus characters), so `-s` and `--silent` are the same thing. The other type of flag says what kind of argument the following argument is -- for example a common flag is `--output` (or `-o`) with which we specify the name of the output file, so for instance running a C compiler may look like `cc myprogram.c --output myprogram`. Flags accepted by utilities along with their meanings are documented in the manual pages (see above).
TODO: utils, shell, sh (running programs, ...), usual "workflows" (man pages, history, arrows, tab-completion, ...), often used commands, examples, permissions