A Linux Knowledge-base for starting new things quickly.
Go to file
2024-08-07 18:01:34 +02:00
basics place requirements for at tape 2024-08-07 18:01:34 +02:00
chat split otr from profanity 2024-03-08 23:29:28 +01:00
data Merge branch 'master' into vhs 2024-08-06 20:47:23 +01:00
distros Merge branch 'master' into vhs 2024-06-02 05:27:58 +02:00
hardware change formatting 2023-06-17 21:28:20 +02:00
networking expand making torrents 2024-05-29 17:09:10 +02:00
sound change formatting 2023-06-17 21:28:20 +02:00
system Merge branch 'master' into vhs 2024-06-02 05:27:58 +02:00
vim vim in bash 2023-09-25 00:11:09 +02:00
virtualization place proper variables in xen notes 2023-06-20 15:19:26 +02:00
vision note making easy pdfs 2024-04-10 23:42:21 +02:00
_index.md add basic index for lk 2022-01-18 13:24:25 +01:00
.gitignore ignore gif and jpeg 2023-04-11 12:37:09 +02:00
new.sh write git hooks 2024-04-06 02:00:18 +02:00
README.md formatting 2024-04-19 17:28:37 +02:00

title
Knowledge Base

Linux Knowledgebase

This is a list of quickstart guides for Linux programs, designed to get the user up and running as fast as possible.

Style

Praxis Only

We leave theory alone as much as possible. The documentation should be of the form 'if you want X, type Y'.

We don't need to explain what a program does - anyone looking up 'how to X', already knows what they want to do. We don't even need to explain which program to use - if someone wants to combine an mp4 and webm video into a single video file, they only care about that result, not about learning ffmpeg.

Any interest in these tools only comes after we can use them.

Chronological

Entries should read like scripts - everything in the right order, with small notes on what this does.

The chronology should never branch. If gitea can use three different types of database, the documentation should simply pick one and continue instructions from there. Repetition works better than a reference - if a database requires three commands to set up, it's better to repeat those three commands for every program that requires a database than to just link to another file which discusses databases.


Closing

Introductory documents should show anything required to cleanly uninstall a program, without leaving bulky configuration files behind.

Three Input Types

There are three types of examples:

Fixed input:

ls

Anything with arbitrary input should be shown as a variable.

ls $FILE

Non-commands (e.g. output) should be shown as quoted text:

LK img Mail kn Projects music


Example

How to see which websites you're actively accessing:

` ` `bash
ss -tr dst :$PORT
` ` `   

> State  Recv-Q  Send-Q   Local Address:Port     Peer Address:Port   Process  
> ESTAB  0       0         192.168.0.14:42476  149.154.167.91:https           
> ESTAB  0       0         192.168.0.14:43644   104.17.90.199:https           

What's wrong with everything else?

Man pages

  • Orders items by the alphabet rather than by relevance.
  • Often presumes you know everything except that one program.
  • Often written in the 80's, and it shows.
  • Zero respect for your time.

curl cheat.sh/

  • Doesn't have the programs I like.
  • Too short to get you started on many programs.
  • Poor understanding of priority (git stash is covered before git commit).

Current State

This started as a few personal notes, and will probably continue to look like that for some time. It's a bit of a mess.

Systemd is taken as a default. Non-systemd commands are mentioned when required for a distro, e.g. runit for Void Linux.