This is a list of quickstart guides for Linux programs, designed to get the user up and running as fast as possible.
- Minimal theory, maximum practical.
- The statements should go in order of how likely they are to be used: if
git addhas to be used by everyone, then it should go first.
- Documents should be similar to well-documented scripts.
- No explanations for the program. This isn’t an introduction or advert, it’s a guide for someone who already wants to use a program but doesn’t know how.
- It’s better explain how to set something up three times than to link or reference a setup.
- If general knowledge must be presumed, it should be placed into a file named ‘basics’.
How to see which websites you're actively accessing: > ss -tr dst :443
What’s wrong with everything else?
- 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.
- Doesn’t have the programs I like.
- Too short to get you started on many programs.
- Poor understanding of priority (
git stashis covered before
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.