A Linux Knowledge-base for starting new things quickly.
Go to file
Malin Freeborn 1ba3010b81
edit bash_tricks
2023-06-17 19:02:28 +02:00
basics embiggen time tools 2023-04-13 06:06:54 +02:00
chat embiggen profanity 2022-11-23 22:45:29 +01:00
data general edits 2023-04-20 07:34:56 +02:00
distros add pacdiff tool to arch 2023-05-27 19:07:26 +02:00
hardware remap key as one-liner 2022-12-10 08:02:21 +01:00
networking update agate on arch docs 2023-06-17 18:28:15 +02:00
sound edit basic sound 2023-04-05 00:09:29 +02:00
system edit bash_tricks 2023-06-17 19:02:28 +02:00
vim edit vim 2023-04-16 14:49:47 +02:00
virtualization adjust title 2022-06-18 15:49:30 +02:00
vision general edits 2023-04-20 07:34:56 +02:00
.gitignore ignore gif and jpeg 2023-04-11 12:37:09 +02:00
README.md update readme 2022-12-01 19:53:50 +01:00
_index.md add basic index for lk 2022-01-18 13:24:25 +01:00

README.md

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.

Three Input Types

There are three types of examples:

Fixed input:

ls

Arbitrary Input shows the non-fixed input in italics:

ls myFile.txt

Output shows as unformatted text:

    LK           img
    Mail         kn
    Projects     music

Example

How to see which websites you're actively accessing:

> ss -tr dst :443

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 we relegate to their respective distros, e.g. runit for Void Linux.