Compare commits
2 Commits
dev
...
7f9de785df
| Author | SHA1 | Date | |
|---|---|---|---|
7f9de785df
|
|||
|
723024db0b
|
3
.gitignore
vendored
Normal file
3
.gitignore
vendored
Normal file
@@ -0,0 +1,3 @@
|
||||
*.pdf
|
||||
*.gif
|
||||
*.jpeg
|
||||
146
Makefile
146
Makefile
@@ -1,84 +1,71 @@
|
||||
MAKEFLAGS += -j
|
||||
MAKEFLAGS += -s
|
||||
EDITOR ?= vi
|
||||
PAGER ?= less -Ri
|
||||
READER != command -v mdless bat glow less more pg | head -1
|
||||
FZF != command -v fzf sk | head -1
|
||||
|
||||
markdown = $(wildcard */*.md */*/*.md)
|
||||
|
||||
ifeq "$(FZF)" ""
|
||||
$(info Install fzf)
|
||||
endif
|
||||
FZF != command -v sk || command -v fzy || command -v fzf || \
|
||||
{ echo install a fuzzy finder && exit 1 ;}
|
||||
|
||||
ifeq "$(FZF)" "/usr/bin/fzy"
|
||||
FZF += -i
|
||||
else
|
||||
FZF += --print-query | cat
|
||||
endif
|
||||
|
||||
spill_contents = sed -e '1,/---/d'
|
||||
|
||||
help: ## Print the help message
|
||||
help: .git/info/exclude ## Print the help message
|
||||
@awk 'BEGIN {FS = ":.*?## "} /^[0-9a-zA-Z._-]+:.*?## / {printf "\033[36m%s\033[0m : %s\n", $$1, $$2}' $(MAKEFILE_LIST) | \
|
||||
sort | \
|
||||
column -s ':' -t
|
||||
|
||||
articles != find * -type f -name "*.md"
|
||||
|
||||
default += .dbs/notes.rec
|
||||
dirs != ls -d */
|
||||
categories = $(patsubst %/, %, $(dirs))
|
||||
|
||||
databases = $(patsubst %, .dbs/%.rec, $(categories))
|
||||
|
||||
default += $(databases)
|
||||
default += db.rec
|
||||
default += .dbs/map.fmt
|
||||
|
||||
$(foreach dir, $(categories), \
|
||||
$(eval .dbs/$(dir).rec: $(wildcard $(dir)/*)) \
|
||||
)
|
||||
|
||||
%/:
|
||||
.dbs/:
|
||||
mkdir $@
|
||||
echo '*' > $@.gitignore
|
||||
|
||||
include cmd.mk
|
||||
$(databases): .dbs/%.rec: %/ | .dbs/
|
||||
$(info making $(@F))
|
||||
for entry in $(shell find $< -type f -name "*.md") ; do \
|
||||
printf "file: %s\n" "$$entry" ;\
|
||||
sed -n '2,/^---$$/ {/^---$$/d; p}' "$$entry" |\
|
||||
tr -d '[]' | tr -s ' ' |\
|
||||
sed '/tags: /s/, /\ntag: /g ; s/tags:/tag:/ ; /requires/s/, /\nrequires: /g' ;\
|
||||
printf "wordcount: %s\n\n" "$$(wc -w < $$entry)" ;\
|
||||
done > $@
|
||||
|
||||
.dbs/head.rec: | .dbs/ $(lists)
|
||||
# This two-variable read can only happen because of the quotes in the titles.
|
||||
db.rec: $(databases)
|
||||
$(info rebuilding from $? )
|
||||
printf '%s\n' '%rec: guide' > $@
|
||||
printf '%s\n' '%key: path' >> $@
|
||||
printf '%s\n' '%key: title' >> $@
|
||||
printf '%s\n' '%type: requires rec guide' >> $@
|
||||
printf '%s\n' '%type: provides rec guide' >> $@
|
||||
printf '%s\n' '%type: wordcount int' >> $@
|
||||
printf '%s\n\n' '%sort: wordcount' >> $@
|
||||
cat $^ >> $@
|
||||
recsel $@ -e "requires != ''" -CR title,requires |\
|
||||
while read title requires; do \
|
||||
for provider in "$$requires" ; do \
|
||||
recset $@ -e "title = '$${provider}'" -f provides -a "$${title}" ;\
|
||||
done ;\
|
||||
done
|
||||
sed -i 's/"//g' $@
|
||||
recfix --sort $@
|
||||
$(info Created main database: $@)
|
||||
|
||||
.dbs/new.rec: $(markdown) | .dbs/head.rec
|
||||
$(info Updating: $?)
|
||||
grep -q guide $@ 2>/dev/null || cp $| $@
|
||||
@-$(foreach entry, $?, \
|
||||
recdel -t guide $@ -e "path = '$(entry)'" 2>/dev/null ;\
|
||||
)
|
||||
for entry in $? ; do \
|
||||
echo '' ;\
|
||||
printf "path: %s\n" "$$entry" ;\
|
||||
sed -n '2,/^---$$/ {/^---$$/d; p}' "$$entry" |\
|
||||
while read -r line; do if [ -z "$${line#*:}" ] ; then type="$$line"; else echo "$$line" | sed -r "s/- (.*)/$$type \1/" | sed s'/tags: /tag: /' ; fi ; done ;\
|
||||
printf "wordcount: %s\n" "$$(wc -w < $$entry)" ;\
|
||||
echo 'cmd: ' ;\
|
||||
sed '1,/^---$$/d' $$entry | sed 's/^.*/+ &/' ;\
|
||||
echo '' ;\
|
||||
done >> $@
|
||||
|
||||
.dbs/requires.rec: .dbs/new.rec
|
||||
recinf -d $< > $@
|
||||
echo "" >> $@
|
||||
recsel $< -t guide -j requires -G requires -p 'path,title,tag,wordcount,requires_path:requires,requires_requires:requires,cmd' >> $@
|
||||
|
||||
.dbs/notes.rec: .dbs/requires.rec .dbs/new.rec
|
||||
recinf -d $< > $@
|
||||
echo '' >> $@
|
||||
sed '/^%/d' $^ | recsel -G path | recsel -U >> $@
|
||||
|
||||
default += db.rec
|
||||
ignored += db.rec
|
||||
db.rec: command.rec .dbs/notes.rec
|
||||
recinf -d $< > $@
|
||||
echo '' >> $@
|
||||
sed '/^%/d' $^ | recsel -U -p 'title:aim,aim,cmd,note,shell,tag,bin:tag' >> $@
|
||||
$(info Making main database: $@)
|
||||
|
||||
|
||||
.git/info/exclude: $(ignored)
|
||||
.git/info/exclude: $(default)
|
||||
@echo $^ | tr ' ' '\n' > $@
|
||||
|
||||
default += .git/info/exclude
|
||||
@@ -86,41 +73,30 @@ default += .git/info/exclude
|
||||
.PHONY: database
|
||||
database: $(default) ## Make a recfiles database
|
||||
|
||||
.PHONY: article
|
||||
article: ## Write an article
|
||||
@path=$$(find $(categories) -type d | sort | uniq | $(FZF)) ;\
|
||||
read -p "Title: " title ;\
|
||||
filename="$$(echo "$$title" | tr '[:upper:]' '[:lower:]' | tr ' ' '_')" ;\
|
||||
mkdir -p $$path ;\
|
||||
printf '%s\n' '---' >> $$path/$$filename.md ;\
|
||||
printf 'title: "%s"\n' "$$title" >> $$path/$$filename.md ;\
|
||||
printf 'tags: [ "%s" ]\n' "$$path" | tr '[:upper:]' '[:lower:]' | sed 's#\/#", "#g' >> $$path/$$filename.md ;\
|
||||
printf '%s\n\n' '---' >> $$path/$$filename.md ;\
|
||||
$(EDITOR) +5 "$$path/$$filename.md"
|
||||
|
||||
.dbs/map.fmt:| .dbs/
|
||||
printf '%s\n' '[ {{requires[0]}} ] --> [ {{path}} ] {border-style: dashed;}' > $@
|
||||
printf '%s\n' '[ {{requires[1]}} ] --> [ {{path}} ] {border-style: dashed;}' >> $@
|
||||
printf '%s\n' '[ {{requires[2]}} ] --> [ {{path}} ] {border-style: dashed;}' >> $@
|
||||
printf '%s\n' '[ {{requires[3]}} ] --> [ {{path}} ] {border-style: dashed;}' >> $@
|
||||
printf '%s\n' '[ {{requires[4]}} ] --> [ {{path}} ] {border-style: dashed;}' >> $@
|
||||
printf '%s\n' '[ {{requires[0]}} ] --> [ {{title}} ] {border-style: dashed;}' > $@
|
||||
printf '%s\n' '[ {{requires[1]}} ] --> [ {{title}} ] {border-style: dashed;}' >> $@
|
||||
printf '%s\n' '[ {{requires[2]}} ] --> [ {{title}} ] {border-style: dashed;}' >> $@
|
||||
printf '%s\n' '[ {{requires[3]}} ] --> [ {{title}} ] {border-style: dashed;}' >> $@
|
||||
printf '%s\n' '[ {{requires[4]}} ] --> [ {{title}} ] {border-style: dashed;}' >> $@
|
||||
|
||||
.PHONY: map
|
||||
map: .dbs/requires.rec .dbs/map.fmt ## Show knowledge dependency map
|
||||
recsel -t guide $< -e 'requires != ""' -p path,requires | recfmt -f .dbs/map.fmt |\
|
||||
grep -vF '[ ]' | graph-easy --boxart 2>/dev/null | ${PAGER} -S
|
||||
map: db.rec .dbs/map.fmt ## Show knowledge dependency map
|
||||
recsel -t guide $< -e 'requires != ""' -p title,requires | recfmt -f .dbs/map.fmt |\
|
||||
grep -vF '[ ]' | graph-easy --boxart | $${PAGER}
|
||||
|
||||
.PHONY: clean
|
||||
clean: ## Remove all generated files
|
||||
$(RM) -r $(default) .dbs/
|
||||
|
||||
.PHONY: article
|
||||
article: */ */*/ ## Write a new article
|
||||
category=$(shell echo $^ | tr ' ' '\n' | $(FZF) --print-query | tail -1 ) \
|
||||
&& read -p "Article title? " name \
|
||||
&& filename="$$(echo "$$name" \
|
||||
| cut -d: -f1 \
|
||||
| tr '[A-Z ]' '[a-z_]' | tr -cd '[:alpha:]_' )" \
|
||||
&& $(MAKE) -e TITLE="$$name" "$$category"/"$$filename.md"
|
||||
|
||||
.PHONY: all
|
||||
all: $(default) ## All file targets
|
||||
|
||||
|
||||
%.md:
|
||||
[ -d "$(@D)" ] || mkdir $(@D)
|
||||
printf '%s\n' '---' >> $@
|
||||
printf 'title: %s\n' '$(TITLE)' >> $@
|
||||
printf "tags: " >> $@
|
||||
echo $(@D) | sed 's#\b\w#\n- &#g; s/\///g' >> $@
|
||||
printf '%s\n\n' '---' >> $@
|
||||
$(EDITOR) +5 $@
|
||||
|
||||
$(RM) $(default)
|
||||
|
||||
145
README.md
145
README.md
@@ -1,98 +1,61 @@
|
||||
# Linux Knowledge Base
|
||||
---
|
||||
title: "Linux Knowledge Base"
|
||||
---
|
||||
|
||||
These notes Linux programs have grown into a searchable knowledge base.
|
||||
The Linux Knowledge-Base provides quick-start guides for working with terminal programs.
|
||||
|
||||
# Usage
|
||||
If you like this style of short articles with a miniature database, then join me in my quest to remove the nausea of poorly-written documentation.
|
||||
|
||||
## Setup
|
||||
# Setup
|
||||
|
||||
Install `make`, `recutils`, and any a fuzzy-finder (like `fzf` or `sk`).
|
||||
Install `make`, `recutils`, and any fuzzy-finder (i.e. `sk`, `fzy`, or `fzf`).
|
||||
|
||||
To find the options, run `make`.
|
||||
|
||||
## Queries
|
||||
|
||||
The fuzzy finder opens an interactive menu to find information.
|
||||
|
||||
There are two types of notes:
|
||||
|
||||
1. Short commands, catalogued by aim (in `command.rec`).
|
||||
1. Short notes, mostly on getting set up with something (in the markdown files).
|
||||
|
||||
### Short Commands
|
||||
|
||||
Running `make check` will start a search of the snippets, ordered by what you
|
||||
want to do, not by the name of the binary:
|
||||
|
||||
```
|
||||
Hard reset ntp service
|
||||
-> Quickly find and open run-command files
|
||||
Turn markdown into a man page
|
||||
Rotate a video
|
||||
Translate a media file to a new type
|
||||
```
|
||||
|
||||
The output is a couple of lines of code, with changeable components as variables:
|
||||
|
||||
```
|
||||
alias rrc='$PAGER "$(find . -maxdepth 2 -name "*rc" | fzf)"'
|
||||
```
|
||||
|
||||
### The Function
|
||||
|
||||
Running `make function` outputs a shell function which searches through this
|
||||
knowledge base, so you don't have to `cd` to use it.
|
||||
## Usage
|
||||
|
||||
Set up the database and try a few queries:
|
||||
|
||||
```sh
|
||||
lk(){
|
||||
/usr/bin/mdless "$(recsel ${your-path-here}/lk/db.rec \
|
||||
-q "$(recsel ${your-path-here}/lk/db.rec -CP title,tag \
|
||||
| sort -u \
|
||||
| /usr/bin/fzf )" -CP path \
|
||||
| fzf --sync -1 --preview='less -iR {}' )"
|
||||
}
|
||||
```
|
||||
make
|
||||
make database
|
||||
|
||||
Add the function to your bash shell like this:
|
||||
recsel db.rec -m 3
|
||||
recsel db.rec -q database
|
||||
recsel db.rec -e "title = 'ssh'"
|
||||
recsel db.rec -e "title ~ 'ssh'"
|
||||
recsel db.rec -e "title ~ 'bash'" -R title,wordcount
|
||||
|
||||
```bash
|
||||
make function
|
||||
make function >> ~/.bashrc
|
||||
exec bash
|
||||
lk
|
||||
recsel db.rec -t guide -j provides -G title \
|
||||
-e "title = 'ssh'" \
|
||||
-p 'sum(provides_wordcount)'
|
||||
```
|
||||
|
||||
# Style
|
||||
|
||||
## State Knowledge Dependencies
|
||||
|
||||
Articles should never link to other resources part-way through.
|
||||
If the article assumes an understanding of GPG keys, then it should say that at the top.
|
||||
People should be able to read documentation from the beginning, then keep going until the end, and then stop.
|
||||
Setup guides should not send the reader on a detour through labyrinths of links.
|
||||
|
||||
## No History, No Context
|
||||
|
||||
Anyone who wants to read how to use OTP with GPG already knows what those words mean, so guides should not spend time explaining.
|
||||
Anyone who doesn't know what GPG keys are can find the link to using them, which explains them better than using door-blocking devices as a metaphor for prime number factorization.
|
||||
- Nobody cares about how the project started.
|
||||
- Nobody wants to read what `ffmpeg` is, because anyone who wants to use it already knows what it is.
|
||||
|
||||
## Index by Purpose
|
||||
## State Knowledge Dependencies
|
||||
|
||||
Nobody wants to read about `grep`, they want to find words, like 'cat'.
|
||||
They want to 'download a website', not learn about `wget`.
|
||||
Guides should be created and indexed by purpose, not by binary.
|
||||
Articles should state what you need to understand in order to read them *at the start*.
|
||||
They should not assume the reader knows much beyond common terminal commands, and should not provide a link to some other resource half-way through an article.
|
||||
|
||||
People should be able to read an article from the beginning, then keep going until the end, and then stop.
|
||||
Articles should not take a detour through a chain of other articles of unknown size.
|
||||
|
||||
[Do not Jaquays documentation](https://splint.rs/posts/no_links)
|
||||
|
||||
## Be Opinionated
|
||||
|
||||
- Guides should not ask the reader to pick from a list of options.
|
||||
- Guides should not ask the reader to select options half-way through.
|
||||
- Options for different filesystems, databases, et c., should be written as separate guides.
|
||||
|
||||
## Repetition Beats 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.
|
||||
|
||||
## Show Options as Variables
|
||||
## Show Arguments as Variables
|
||||
|
||||
Look at this line:
|
||||
|
||||
@@ -119,61 +82,28 @@ The answer is not obvious.
|
||||
It's better to make all arbitrary values variables.
|
||||
|
||||
```sh
|
||||
name=new
|
||||
git branch ${name}
|
||||
git checkout ${name}
|
||||
git branch $branch_name
|
||||
git checkout $branch_name
|
||||
PAGER='less -R'
|
||||
grep ls --color=always $HISTFILE | $PAGER
|
||||
```
|
||||
|
||||
Now we can see what can be changed.
|
||||
|
||||
### Aim to Script
|
||||
|
||||
Guides should read like a heavily commented script, so CLI commands are preferred to GUI commands.
|
||||
|
||||
- Bad: '*edit the file `.config/tspreed/tspreed.rc` and change `focuscolor` to '2'.*'
|
||||
- Good: `sed -i '/focuscolor/s/=1/=2/' ~/.config/tspreed/tspreed.rc`
|
||||
* `cat !$`
|
||||
|
||||
Despite being 'script-like', interactive bash commands like `cat !$` are still fine just to show how to double-check results when setting things up interactively.
|
||||
|
||||
### Show, Don't Tell
|
||||
## Assume People Follow the Instructions
|
||||
|
||||
Articles should say what to type, not the output.
|
||||
If the command is `ls`, users will see files once they try the command, but the article does not need to provide an example list of files unless an important point has to be made about output.
|
||||
|
||||
Once a user enters a new group, the change doesn't take effect until you log
|
||||
in. This could be explained at length, or the reader can see what this means
|
||||
for themselves:
|
||||
|
||||
|
||||
```sh
|
||||
groups
|
||||
grep audio /etc/group
|
||||
|
||||
sudo usermod -aG audio $USER
|
||||
groups
|
||||
grep audio /etc/group
|
||||
|
||||
su $USER
|
||||
groups
|
||||
grep audio /etc/group
|
||||
```
|
||||
|
||||
Troubleshooting steps can often be implied by adding commands which do nothing but check the results of previous commands.
|
||||
|
||||
# What's Wrong with Everything Else?
|
||||
|
||||
Why bother writing yet another cheat-sheet collection?
|
||||
|
||||
## 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.
|
||||
- Sometimes reference `info` pages (yuck).
|
||||
- Often references `info` pages (yuck).
|
||||
|
||||
## `curl cheat.sh`
|
||||
|
||||
@@ -184,6 +114,9 @@ Why bother writing yet another cheat-sheet collection?
|
||||
|
||||
# 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.
|
||||
If you like the format, send me a pull request.
|
||||
|
||||
Systemd is taken as a default.
|
||||
Non-systemd commands are mentioned when required for a distro, e.g. runit for Void Linux.
|
||||
|
||||
|
||||
@@ -1,8 +1,6 @@
|
||||
---
|
||||
title: at
|
||||
tags:
|
||||
- basics
|
||||
- time
|
||||
title: "at"
|
||||
tags: [ "basics", "time" ]
|
||||
---
|
||||
Install with:
|
||||
|
||||
360
basics/basics.md
Normal file
360
basics/basics.md
Normal file
@@ -0,0 +1,360 @@
|
||||
---
|
||||
title: "Basics"
|
||||
tags: [ "basics" ]
|
||||
---
|
||||
|
||||
You need about a dozen commands to move around Linux.
|
||||
After that, you look up the rest as you go.
|
||||
Don't worry about understanding any of it, just type it in and the habit forms pretty quickly.
|
||||
|
||||
You start in a dark room. You want to know where you are by **p**rinting out your **w**orking '**d**irectory' (i.e. 'location'):
|
||||
|
||||
```sh
|
||||
pwd
|
||||
```
|
||||
|
||||
Have a look at what is here:
|
||||
|
||||
```sh
|
||||
ls
|
||||
```
|
||||
|
||||
If you get no response, the list of items is "", meaning "nothing here".
|
||||
|
||||
Have a look at **a**ll the files:
|
||||
|
||||
```sh
|
||||
ls -a
|
||||
```
|
||||
|
||||
```sh
|
||||
. ..
|
||||
```
|
||||
|
||||
So `.` means 'here' and `..` means 'you see stairs leading downwards' (e.g. 'the directory behind you').
|
||||
|
||||
Change directory (`cd`) down one level:
|
||||
|
||||
```sh
|
||||
cd ..
|
||||
```
|
||||
|
||||
Look where you are again with `pwd`, then go back up. Use `ls`, and if you see `bob`, then:
|
||||
|
||||
```sh
|
||||
cd bob
|
||||
```
|
||||
|
||||
Move around the directories. The place at the bottom is the 'root', and is known as `/`. Go to the root:
|
||||
|
||||
```sh
|
||||
cd /
|
||||
```
|
||||
|
||||
Do `ls` again and `cd` into `etc`. Look at how much space those folders are taking up:
|
||||
|
||||
```sh
|
||||
du iptables
|
||||
```
|
||||
That's the number of kilobytes the file is taking up.
|
||||
Do the same again, but in a human-readable format:
|
||||
|
||||
```sh
|
||||
du -h iptables
|
||||
```
|
||||
|
||||
The `du` program has `-h` for 'human', '-s' for 'short', and a bunch of other commands.
|
||||
Have a look at the manual and try another command:
|
||||
|
||||
```sh
|
||||
man du
|
||||
```
|
||||
|
||||
Once you're done, press 'q' to quit the manual page and try the extra `du` flag you've found.
|
||||
|
||||
Now you can try to gain super-powers and take over the system:
|
||||
|
||||
```sh
|
||||
sudo -i
|
||||
```
|
||||
|
||||
At this point, you are 'root'.
|
||||
All your commands will be executed, even if they're unsafe, or even if you ask to delete the entire machine.
|
||||
Best to exit out of the root account:
|
||||
|
||||
```sh
|
||||
exit
|
||||
```
|
||||
|
||||
Go find a file that isn't a directory. You can tell which is which with:
|
||||
|
||||
```sh
|
||||
ls -l
|
||||
```
|
||||
|
||||
A directory starts with a 'd', like this:
|
||||
|
||||
```sh
|
||||
drwxr-xr-x 79 root root 4096 Jan 3 05:15 /etc/
|
||||
```
|
||||
|
||||
A standard file starts with '-', like this:
|
||||
|
||||
```sh
|
||||
`-rw-r--r-- 1 root root 8 Dec 11 17:26 hostname`
|
||||
```
|
||||
|
||||
Look inside the file /etc/hostname to find out your computer's name:
|
||||
|
||||
```sh
|
||||
cat /etc/hostname
|
||||
```
|
||||
|
||||
Print out the words "hello world":
|
||||
|
||||
```sh
|
||||
echo "hello world"
|
||||
```
|
||||
|
||||
Move back to your home directory:
|
||||
|
||||
```sh
|
||||
cd
|
||||
```
|
||||
|
||||
Take the words 'hello world', and put them in 'my_file':
|
||||
|
||||
```sh
|
||||
echo 'hello world' > my_file
|
||||
```
|
||||
|
||||
Measure the disk usage of that file, then put the results at the bottom of the file:
|
||||
|
||||
```sh
|
||||
du $FILE >> $FILE
|
||||
```
|
||||
|
||||
And check the results:
|
||||
|
||||
```sh
|
||||
cat $FILE
|
||||
```
|
||||
|
||||
# Autocompletion
|
||||
|
||||
Press tab after typing a few keys and bash will guess what you're trying to type.
|
||||
|
||||
# Permissions
|
||||
|
||||
Look at your file's owner:
|
||||
|
||||
```sh
|
||||
ls -l $FILE
|
||||
```
|
||||
|
||||
If it says `-rw-r--r-- 1 root root 8 Dec 11 17:26 hostname` then the file is owned by 'root'.
|
||||
|
||||
Take your file and change the owner to root:
|
||||
|
||||
```sh
|
||||
sudo chown root $FILE
|
||||
```
|
||||
|
||||
Change the same file so it's owned by the group 'audio':
|
||||
|
||||
```sh
|
||||
sudo chown :audio $FILE
|
||||
```
|
||||
|
||||
Check you did that correctly:
|
||||
|
||||
```sh
|
||||
ls -l my_file
|
||||
```
|
||||
|
||||
> -rw-r--r-- 1 root audio 0 Jan 3 19:20 my_file
|
||||
|
||||
Read the start of that line. Root can 'read' and 'write' to or delete the file. Try to remove (delete) it:
|
||||
|
||||
```sh
|
||||
rm $FILE
|
||||
```
|
||||
|
||||
You'll see you're not allowed, because you don't own it.
|
||||
|
||||
Look at which groups you're in:
|
||||
|
||||
```sh
|
||||
groups
|
||||
```
|
||||
|
||||
Change the file so that members of the audio group can write to the file:
|
||||
|
||||
```sh
|
||||
sudo chmod g+w $FILE
|
||||
```
|
||||
|
||||
Check you got it right with `ls -l`:
|
||||
|
||||
```sh
|
||||
-rw-rw-r-- 1 root audio 0 Jan 3 19:20 my_file
|
||||
```
|
||||
|
||||
Try to delete the file again:
|
||||
|
||||
```sh
|
||||
rm my_file
|
||||
```
|
||||
|
||||
If you can't, you're not in the audio group. Add yourself. You'll need to *modify* your *user account*, by **a**ppending 'audio' to your list of groups.
|
||||
Use `-a` to **a**ppend, and `-G`, to say you're modifying groups:
|
||||
|
||||
```sh
|
||||
sudo usermod -a -G audio [ your username here ]
|
||||
```
|
||||
|
||||
Now you should be able to remove (delete) the file. Remember, that using 'rm file' will not send it to a recycling bin. The file is gone.
|
||||
|
||||
# Directories
|
||||
|
||||
Make a directory called 'new test':
|
||||
|
||||
```sh
|
||||
mkdir 'new test'
|
||||
```
|
||||
|
||||
Make two directories, called 'A', and 'Z':
|
||||
|
||||
```sh
|
||||
mkdir A Z
|
||||
```
|
||||
|
||||
Make a single directory called 'A Z'
|
||||
|
||||
```sh
|
||||
mkdir 'A Z'
|
||||
```
|
||||
|
||||
# Text Searches
|
||||
|
||||
Measure the disk usage of everything ('\*' means 'everything'), and put it in a file called 'disk usage.txt':
|
||||
|
||||
```sh
|
||||
du -sch * > A/'disk usage'.txt
|
||||
```
|
||||
|
||||
Look at your file:
|
||||
|
||||
```sh
|
||||
cat A/'disk usage.txt'
|
||||
```
|
||||
|
||||
If you think you have too much information, use `grep` to just get the one line of text you want:
|
||||
|
||||
```sh
|
||||
grep total A/disk\ usage.txt
|
||||
```
|
||||
|
||||
The `grep` program also has a manual ('man page'). You should find out what that `-c` flag does, but the manual is too long to read.
|
||||
|
||||
Start the manual:
|
||||
|
||||
```sh
|
||||
man du
|
||||
```
|
||||
|
||||
Then search for `-c` by pressing `/`. Your final keys should be `man du`, then `/-c`
|
||||
|
||||
Find out if the `ls` program also has a 'human readable' format by using `grep` to search for the word 'human':
|
||||
|
||||
```sh
|
||||
man ls | grep human
|
||||
```
|
||||
|
||||
Now use that flag that you've found in combinatin with the `-l` flag to look at a file.
|
||||
|
||||
Remove the directory 'Z':
|
||||
|
||||
```sh
|
||||
rmdir Z
|
||||
```
|
||||
|
||||
Remove the directory 'Z':
|
||||
|
||||
```sh
|
||||
rmdir Z
|
||||
```
|
||||
|
||||
And then remove all the rest:
|
||||
|
||||
```sh
|
||||
rmdir *
|
||||
```
|
||||
|
||||
The 'A' directory will not budge because it's not empty. Remove it recursively, so the computer will remove the things inside the directory as well as the directory itself:
|
||||
|
||||
```sh
|
||||
rm -r A
|
||||
```
|
||||
|
||||
# Installation
|
||||
|
||||
You get a package manager which installs programs, fonts, et c.
|
||||
If you're on something like Debian, you'll have `apt`, or if you're on something like Red Hat, you'll have `yum`.
|
||||
If unsure, ask where a program is:
|
||||
|
||||
```sh
|
||||
whereis yum
|
||||
```
|
||||
|
||||
```sh
|
||||
whereis apt
|
||||
```
|
||||
|
||||
If you get a hit, you can use whatever program that is to install things.
|
||||
|
||||
Set a reminder of your package manager:
|
||||
|
||||
```sh
|
||||
echo my package manager is yum | lolcat
|
||||
```
|
||||
|
||||
If that failed it's because you don't have `lolcat` installed.
|
||||
Install lolcat:
|
||||
|
||||
```sh
|
||||
sudo apt install lolcat
|
||||
```
|
||||
|
||||
Try the same command again.
|
||||
|
||||
Search for things you want, like `libreoffice`, or `gimp`:
|
||||
|
||||
```sh
|
||||
apt search libreoffice
|
||||
```
|
||||
|
||||
... then install one of them with:
|
||||
|
||||
```sh
|
||||
apt install $PROGRAM
|
||||
```
|
||||
|
||||
Remove `lolcat`, because it's useless:
|
||||
|
||||
```sh
|
||||
sudo apt remove lolcat
|
||||
```
|
||||
|
||||
...and that's pretty much it.
|
||||
You can move, create, destroy, install things, and look things up.
|
||||
|
||||
# Review
|
||||
|
||||
- Search for random things with your package manager and install the interesting ones.
|
||||
* Read the manual with `man thing`
|
||||
* If it's useless, remember to uninstall it.
|
||||
- Have a look around the file system in `/`.
|
||||
- Look in the `.config` folder in your home directory.
|
||||
* If you copy a program's config to another machine, the program will behave just like you set it up in your own machine.
|
||||
|
||||
@@ -1,8 +1,6 @@
|
||||
---
|
||||
title: clock
|
||||
tags:
|
||||
- basics
|
||||
- time
|
||||
title: "clock"
|
||||
tags: [ "basics", "time" ]
|
||||
---
|
||||
|
||||
Show system time:
|
||||
@@ -64,6 +62,6 @@ sudo apt-get install -y ntp
|
||||
The shell command for this is `ntpq`. Monitor the service providers using:
|
||||
|
||||
```sh
|
||||
ntpd -q
|
||||
ntpq -p
|
||||
```
|
||||
|
||||
36
basics/column.md
Normal file
36
basics/column.md
Normal file
@@ -0,0 +1,36 @@
|
||||
---
|
||||
title: "column"
|
||||
tags: [ "basics", "format", "json" ]
|
||||
---
|
||||
|
||||
Put output into column.
|
||||
|
||||
```sh
|
||||
du -h /etc/* | column
|
||||
```
|
||||
|
||||
Reformat file with an explicit separator (`-s`):
|
||||
|
||||
```sh
|
||||
column -ts: /etc/passwd
|
||||
```
|
||||
|
||||
Give columns names (`-N`), so you can hide some (`-H`):
|
||||
|
||||
```sh
|
||||
column -ts: -N User,PW,UID,GID,Description,Home,shell -H PW,GID /etc/passwd
|
||||
```
|
||||
|
||||
Reorder with `-O` (unspecified items remain):
|
||||
|
||||
|
||||
```sh
|
||||
column -ts: -N User,PW,UID,GID,Description,Home,shell -H PW,GID -O User,Description,shell /etc/passwd
|
||||
```
|
||||
|
||||
Output to json format with `-J`:
|
||||
|
||||
```sh
|
||||
column -J -ts: -H PW,GID,shell -N User,PW,UID,GID,Description,Home,shell /etc/passwd
|
||||
```
|
||||
|
||||
@@ -1,7 +1,6 @@
|
||||
---
|
||||
title: conditionals
|
||||
tags:
|
||||
- basics
|
||||
title: "conditionals"
|
||||
tags: [ "basics" ]
|
||||
---
|
||||
# If statements
|
||||
|
||||
@@ -1,7 +1,6 @@
|
||||
---
|
||||
title: eval
|
||||
tags:
|
||||
- basics
|
||||
title: "eval"
|
||||
tags: [ "basics" ]
|
||||
---
|
||||
|
||||
Compose a statement for execution.
|
||||
@@ -1,7 +1,6 @@
|
||||
---
|
||||
title: bash games
|
||||
tags:
|
||||
- fun
|
||||
title: "bash games"
|
||||
tags: [ "games" ]
|
||||
---
|
||||
|
||||
Games are a great way to learn bash.
|
||||
@@ -1,8 +1,6 @@
|
||||
---
|
||||
title: hard links
|
||||
tags:
|
||||
- basics
|
||||
- links
|
||||
title: "hard links"
|
||||
tags: [ "basics", "links" ]
|
||||
---
|
||||
|
||||
A hard link is one file which exists in multiple locations.
|
||||
@@ -1,12 +1,10 @@
|
||||
---
|
||||
title: Joyous ASCII
|
||||
tags:
|
||||
- fun
|
||||
title: "Joyous ASCII"
|
||||
tags: [ "fun" ]
|
||||
---
|
||||
|
||||
- `asciiquarium`
|
||||
- `cbonsai -lim "$(fortune)"`
|
||||
- `printf 'w\na\n' | ssh -tt nethack@alt.org`
|
||||
|
||||
```sh
|
||||
cow=$(cowsay -l | sort -R | head -1)
|
||||
@@ -1,7 +1,6 @@
|
||||
---
|
||||
title: kill
|
||||
tags:
|
||||
- basics
|
||||
title: "kill"
|
||||
tags: [ "basics" ]
|
||||
---
|
||||
|
||||
If you want to kill a program in a graphical environment, open a terminal and type:
|
||||
@@ -1,8 +1,6 @@
|
||||
---
|
||||
title: links
|
||||
tags:
|
||||
- basics
|
||||
- links
|
||||
title: "links"
|
||||
tags: [ "basics", "links" ]
|
||||
---
|
||||
|
||||
There are two types:
|
||||
@@ -1,8 +1,6 @@
|
||||
---
|
||||
title: locale
|
||||
tags:
|
||||
- basics
|
||||
- time
|
||||
title: "locale"
|
||||
tags: [ "basics", "time" ]
|
||||
---
|
||||
|
||||
Your locale tells the computer your location, preferred time-and-date format, standard language, papersize, et c.
|
||||
@@ -1,7 +1,6 @@
|
||||
---
|
||||
title: locating
|
||||
tags:
|
||||
- basics
|
||||
title: "locating"
|
||||
tags: [ "basics" ]
|
||||
---
|
||||
# Type
|
||||
|
||||
@@ -27,3 +26,8 @@ Which one of these is the binary file which you actually use?
|
||||
```sh
|
||||
which grep
|
||||
```
|
||||
|
||||
# More
|
||||
|
||||
- [Search instantly with `plocate`](data/search_system.md)
|
||||
|
||||
@@ -1,7 +1,6 @@
|
||||
---
|
||||
title: ls
|
||||
tags:
|
||||
- basics
|
||||
title: "ls"
|
||||
tags: [ "basics" ]
|
||||
---
|
||||
|
||||
Firstly, your `ls` is probably aliased to something.
|
||||
@@ -1,9 +1,8 @@
|
||||
---
|
||||
title: processes
|
||||
tags:
|
||||
- basics
|
||||
title: "processes"
|
||||
tags: [ "basics" ]
|
||||
---
|
||||
# Processes
|
||||
# Proccesses
|
||||
|
||||
See running items in current terminal with
|
||||
|
||||
186
basics/setup/quality_of_life.md
Normal file
186
basics/setup/quality_of_life.md
Normal file
@@ -0,0 +1,186 @@
|
||||
---
|
||||
title: "Quality of Life"
|
||||
tags: [ "basics", "setup" ]
|
||||
dependencies: [ "vi", "basics" ]
|
||||
---
|
||||
|
||||
This & That
|
||||
===========
|
||||
|
||||
Refer to 'that last thing', and 'the first thing':
|
||||
|
||||
```sh
|
||||
fortune -l > file1
|
||||
cat !$ | tr -d u
|
||||
diff !^ !$
|
||||
```
|
||||
|
||||
**NB:** this can go wrong:
|
||||
|
||||
```sh
|
||||
ls -l file1 file2
|
||||
cat !^
|
||||
```
|
||||
|
||||
Done
|
||||
----
|
||||
|
||||
`<C-d>`
|
||||
|
||||
- If you have a command, Control + d will execute the command.
|
||||
- If you have nothing, `exit`.
|
||||
|
||||
Input Run-Commands (`~/.inputrc`)
|
||||
=================================
|
||||
|
||||
Alias Expansion
|
||||
---------------
|
||||
|
||||
```sh
|
||||
echo '"\C- ": shell-expand-line' >> ~/.inputrc
|
||||
exec bash
|
||||
```
|
||||
|
||||
Now you can expand all aliases with 'Control + Space'.
|
||||
Try just `ls`, then 'Control + Space'.
|
||||
|
||||
Glob Expansion (`*`)
|
||||
--------------------
|
||||
|
||||
```sh
|
||||
echo '"\C-x": glob-expand-word' >> ~/.inputrc
|
||||
exec bash
|
||||
ls *<C-x>
|
||||
```
|
||||
|
||||
- Are you sure you want to delete that?
|
||||
* `rm -r *<C-x>`
|
||||
- Clean up the Downloads folder:
|
||||
* `rm Downloads/*pdf<C-x>`
|
||||
|
||||
Arbitrary Commands
|
||||
------------------
|
||||
|
||||
Use `\n` as a 'newline' character to automatically press `<Return>`.
|
||||
|
||||
```sh
|
||||
echo 'Control-y: "| lolcat\n"' >> ~/.inputrc
|
||||
exec bash
|
||||
ls<C-y>
|
||||
```
|
||||
|
||||
```sh
|
||||
Control-l: "\C-u clear -x && ls\n"
|
||||
exec bash
|
||||
cd /etc/<C-l>
|
||||
```
|
||||
|
||||
Readline as Vi
|
||||
--------------
|
||||
|
||||
```sh
|
||||
echo 'set editing-mode vi' >> ~/.inputrc
|
||||
echo 'set keymap vi-insert' >> ~/.inputrc
|
||||
exec bash
|
||||
```
|
||||
|
||||
The prompt now works according to `vi`-motions.
|
||||
This goes much further than the bash-option, `set -o vi` ('set option: `vi`').
|
||||
It changes the cursor in the terminal, not just bash.
|
||||
|
||||
Try:
|
||||
|
||||
- `ls <C-n>`
|
||||
- `ls <C-p>`
|
||||
- Type some words.
|
||||
- `<Esc>0dw$p`
|
||||
- <Esc> to normal-mode, and go back with 'b', and forward with 'e'.
|
||||
- `4b` to step back four times.
|
||||
- `cE`
|
||||
- `<Esc>kcw`
|
||||
- ls -a<Esc>xxxx
|
||||
|
||||
Readline can work with python one you set `PYTHON_BASIC_REPL` to `true`.
|
||||
|
||||
|
||||
```sh
|
||||
echo 'export PYTHON_BASIC_REPL=true' >> ~/.bashrc
|
||||
exec bash
|
||||
```
|
||||
|
||||
```python
|
||||
im<C-n>os<Return>
|
||||
os.li<C-n><Return>
|
||||
<Esc>kfn
|
||||
<C-d>
|
||||
```
|
||||
|
||||
Fix Globs!
|
||||
----------
|
||||
|
||||
If you tried the previous commands then they will not work any more, because the `vi`-commands overwrite the other commands.
|
||||
Remove them.
|
||||
|
||||
```sh
|
||||
sed '/ vi/d' ~/.inputrc
|
||||
sed -i '/ vi/d' ~/.inputrc
|
||||
|
||||
sed '1 i set editing-mode vi' .inputrc
|
||||
sed -i '1 i set editing-mode vi' ~/.inputrc
|
||||
sed -i '2 i set keymap vi-insert' ~/.inputrc
|
||||
```
|
||||
|
||||
Vi-sibility
|
||||
-----------
|
||||
|
||||
The `readline` prompt becomes confusing if you don't remember if you're in insert or normal mode.
|
||||
But you can show the current mode in the prompt:
|
||||
|
||||
```sh
|
||||
echo 'set show-mode-in-prompt on' >> ~/.inputrc
|
||||
exec bash
|
||||
```
|
||||
|
||||
Set new symbols for normal and insert mode:
|
||||
|
||||
```sh
|
||||
echo 'set vi-ins-mode-string " "' >> ~/.inputrc
|
||||
echo 'set vi-cmd-mode-string " "' >> ~/.inputrc
|
||||
```
|
||||
|
||||
Fuzzy Sort
|
||||
==========
|
||||
|
||||
Check your repos for `sk-im`, and install.
|
||||
The program is called `sk`.
|
||||
|
||||
```sh
|
||||
FUZZY=sk
|
||||
```
|
||||
|
||||
If you don't have it, `fzy` or `fzf` should work the same way.
|
||||
|
||||
```sh
|
||||
FUZZY=fzy
|
||||
```
|
||||
|
||||
Find some 'read-config' files to check out:
|
||||
|
||||
```sh
|
||||
find . -maxdepth 2 -name "*rc"
|
||||
find . -maxdepth 2 -name "*rc" | $FUZZY
|
||||
```
|
||||
|
||||
And read some:
|
||||
|
||||
```sh
|
||||
PAGER='less -R'
|
||||
$PAGER "$(find . -maxdepth 2 -name "*rc" | $FUZZY)"
|
||||
```
|
||||
|
||||
Make the change long-term:
|
||||
|
||||
```sh
|
||||
alias rrc='$PAGER "$(find . -maxdepth 2 -name "*rc" | sk)"'
|
||||
alias | grep rrc= >> ~/.bash_aliases
|
||||
```
|
||||
@@ -1,8 +1,6 @@
|
||||
---
|
||||
title: soft links
|
||||
tags:
|
||||
- basics
|
||||
- links
|
||||
title: "soft links"
|
||||
tags: [ "basics", "links" ]
|
||||
---
|
||||
A soft link is a file which says how to go to another file.
|
||||
When a program encounters a soft link, it will make a guess at whether it should ignore it, or try to get to that file.
|
||||
78
basics/time.md
Normal file
78
basics/time.md
Normal file
@@ -0,0 +1,78 @@
|
||||
---
|
||||
title: "time"
|
||||
tags: [ "basics", "time" ]
|
||||
---
|
||||
# systemd
|
||||
|
||||
Set time to synchronize with an ntp server:
|
||||
|
||||
```sh
|
||||
timedatectl set-ntp true
|
||||
```
|
||||
|
||||
This info stays in `/usr/share/zoneinfo`.
|
||||
|
||||
# Local Time
|
||||
|
||||
Local time is kept in /etc/localtime.
|
||||
|
||||
According to Dave's LPIC guide, you can set the local time by making asymboling link from your timezone to /etc/localtime, as so:
|
||||
|
||||
```sh
|
||||
sudo ln -sf /usr/share/zoneinfo/Europe/Belgrade /etc/localtime
|
||||
```
|
||||
|
||||
...however this produced the wrong time for me. Further, /etc/localtime produces an output with cat, while the zoneinfo files do not.
|
||||
|
||||
# Locale
|
||||
|
||||
See local time, language and character settings with:
|
||||
|
||||
```sh
|
||||
locale
|
||||
```
|
||||
|
||||
List available locales with:
|
||||
|
||||
```sh
|
||||
locale -a
|
||||
```
|
||||
|
||||
To see additional locales which are available (but not necessarily installed):
|
||||
|
||||
```sh
|
||||
cat /usr/share/i18n/SUPPORTED
|
||||
```
|
||||
|
||||
Set a supported locale with:
|
||||
|
||||
```sh
|
||||
locale-gen pl_PL.UTF-8
|
||||
```
|
||||
|
||||
Then set that language, with:
|
||||
|
||||
```sh
|
||||
LANG=pl_PL.UTF-8
|
||||
```
|
||||
|
||||
...then reboot.
|
||||
|
||||
# Network Time Protocol
|
||||
|
||||
Glimpse an overview with:
|
||||
|
||||
```sh
|
||||
ntpq -p
|
||||
```
|
||||
|
||||
Usually this is run as a service, so just start that service.
|
||||
|
||||
# Force Reset
|
||||
|
||||
If your clock drifts too far from the right time, it will not reset happily.
|
||||
For it to reset like this:
|
||||
|
||||
```sh
|
||||
sudo ntpd -q -g -x -n
|
||||
```
|
||||
@@ -1,9 +1,6 @@
|
||||
---
|
||||
title: tree
|
||||
tags:
|
||||
- basics
|
||||
- tree
|
||||
- markdown
|
||||
title: "tree"
|
||||
tags: [ "basics", "tree", "markdown" ]
|
||||
---
|
||||
|
||||
The `tree` utility outputs a full listing of everything in your current directory, and those below.
|
||||
@@ -1,7 +1,6 @@
|
||||
---
|
||||
title: users
|
||||
tags:
|
||||
- basics
|
||||
title: "users"
|
||||
tags: [ "basics" ]
|
||||
---
|
||||
# Basic Information
|
||||
|
||||
@@ -1,7 +1,6 @@
|
||||
---
|
||||
title: yes
|
||||
tags:
|
||||
- basics
|
||||
title: "yes"
|
||||
tags: [ "basics" ]
|
||||
---
|
||||
# The Best Linux Program: `yes`
|
||||
|
||||
@@ -1,16 +1,13 @@
|
||||
---
|
||||
title: profanity
|
||||
tags:
|
||||
- chat
|
||||
- omemo
|
||||
title: "profanity"
|
||||
tags: [ "chat", "omemo" ]
|
||||
---
|
||||
|
||||
# Setup (Commands)
|
||||
|
||||
Sign up to an account somewhere.
|
||||
|
||||
```
|
||||
/connect ${name}@${host}
|
||||
/connect bob@bobserver.org
|
||||
```
|
||||
|
||||
Check if someone wants to be your friend:
|
||||
@@ -22,13 +19,13 @@ Check if someone wants to be your friend:
|
||||
Accept a friend's subscription request:
|
||||
|
||||
```
|
||||
/sub add ${name}@${host}
|
||||
/sub add alice@aliceserver.org
|
||||
```
|
||||
|
||||
Join a room:
|
||||
|
||||
```
|
||||
/join ${room}@${host}
|
||||
/join room1@bobserver.org
|
||||
```
|
||||
|
||||
Save your configuration so you don't have to do this again:
|
||||
@@ -41,14 +38,14 @@ Check your `~/.config/profanity/profrc` for how to data's saved.
|
||||
|
||||
## Automatically Sign In
|
||||
|
||||
To automatically sign in, add your password to [pass](data/pass.md).
|
||||
To automatically sign in, add your password to [pass](../data/pass.md).
|
||||
|
||||
```
|
||||
/account set ${name}@${host} eval_password pass *xmpp*
|
||||
/account set *malin@oosm.org* eval_password pass *xmpp*
|
||||
```
|
||||
|
||||
```
|
||||
/autoconnect set ${name}@${host}}
|
||||
/autoconnect set *malin@oosm.org*
|
||||
```
|
||||
|
||||
```
|
||||
@@ -62,7 +59,7 @@ Remember to save the config for other commands too.
|
||||
## Messages
|
||||
|
||||
```
|
||||
/msg ${name}@${host}}
|
||||
/msg alice@aliceserver.org
|
||||
```
|
||||
|
||||
This opens in a new tab.
|
||||
@@ -99,7 +96,7 @@ Tell it how to save files:
|
||||
Then get the file with:
|
||||
|
||||
```
|
||||
/urlsave <Tab>
|
||||
/urlsave *<Tab>*
|
||||
```
|
||||
|
||||
Same for `/urlopen`
|
||||
@@ -143,3 +140,5 @@ You can ensure omemo automatcally turns on:
|
||||
```
|
||||
/omemo policy automatic
|
||||
```
|
||||
---
|
||||
|
||||
|
||||
@@ -1,15 +0,0 @@
|
||||
---
|
||||
title: profanity automation
|
||||
tags:
|
||||
- chat
|
||||
- omemo
|
||||
requires:
|
||||
- chat/profanity.md
|
||||
---
|
||||
|
||||
Automate profanity with `--cmd`.
|
||||
|
||||
|
||||
```sh
|
||||
profanity --cmd /foo --cmd "/sleep 10" --cmd /quit
|
||||
```
|
||||
@@ -1,76 +0,0 @@
|
||||
---
|
||||
title: Send an email with a CLI command
|
||||
tags:
|
||||
- email
|
||||
requires:
|
||||
- data/pass.md
|
||||
---
|
||||
|
||||
# Setup the Config
|
||||
|
||||
Install `msmtp` and set up the defaults.
|
||||
|
||||
```sh
|
||||
mkdir ~/.config/msmtp/
|
||||
cat > ~/.config/msmtp/config << EOF
|
||||
defaults
|
||||
tls on
|
||||
auth on
|
||||
|
||||
EOF
|
||||
```
|
||||
|
||||
You'll need to fill in some variables, like your provider's hostname and SMTP port.
|
||||
The `${pass_name}` is just the `pass` command which gives your email password.
|
||||
|
||||
```sh
|
||||
name=posteo
|
||||
host=posteo.de
|
||||
port=587
|
||||
user=bob@posteo.net
|
||||
pass_name=posteo.net
|
||||
```
|
||||
|
||||
With those in, add that default account.
|
||||
|
||||
|
||||
```sh
|
||||
cat >> ~/.config/msmtp/config << EOF
|
||||
|
||||
account ${name}
|
||||
host ${host}
|
||||
port ${port}
|
||||
user ${user}
|
||||
from ${user}
|
||||
passwordeval pass ${pass_name}
|
||||
|
||||
```
|
||||
|
||||
Finally, set this as the default account:
|
||||
|
||||
|
||||
```sh
|
||||
account default : ${account} >> ~/.config/msmtp/config
|
||||
```
|
||||
|
||||
# Write an Email
|
||||
|
||||
Fill out the headers in a file called `mail`.
|
||||
|
||||
```
|
||||
From: MSMTP ${user}
|
||||
Subject: Pipes
|
||||
To: ${recipient_name} <${recipient_email}>
|
||||
|
||||
A pipe gives a wise man time to think and a fool something to stick in his
|
||||
mouth.
|
||||
```
|
||||
|
||||
# Send
|
||||
|
||||
Send the email:
|
||||
|
||||
```sh
|
||||
msmtp -t bindrpg@posteo.uk < mail
|
||||
```
|
||||
|
||||
@@ -1,7 +1,6 @@
|
||||
---
|
||||
title: wgetpaste
|
||||
tags:
|
||||
- chat
|
||||
title: "wgetpaste"
|
||||
tags: [ "chat" ]
|
||||
---
|
||||
|
||||
See available pastebins:
|
||||
@@ -28,9 +27,3 @@ Paste in the file then load the result to the right-hand clipboard:
|
||||
wgetpaste -s dpaste -X
|
||||
```
|
||||
|
||||
---
|
||||
title:
|
||||
tags:
|
||||
chat
|
||||
---
|
||||
|
||||
|
||||
41
cmd.mk
41
cmd.mk
@@ -1,41 +0,0 @@
|
||||
|
||||
cmds != recsel command.rec -t command -G bin -CP bin | sort -u
|
||||
lists = $(patsubst %,lists/%.md, $(cmds))
|
||||
|
||||
default += $(lists)
|
||||
|
||||
get_title = printf 'title: %s\n' '${1}'
|
||||
get_tags = recsel -t $(basename $<) $< -G bin \
|
||||
-e 'bin = "$(1)"' -U -CP tag,bin | \
|
||||
sed 's/.*/- &/'
|
||||
|
||||
list_commands = recsel -t $(basename $<) $< -e 'bin = "$(1)"' | \
|
||||
recfmt -f lists.fmt
|
||||
|
||||
$(lists): lists/%.md: command.rec | lists/
|
||||
@printf '%s\n' '---' > $@
|
||||
@$(call get_title,$(basename $(notdir $@))) >> $@
|
||||
@printf '%s\n' 'tags: ' >> $@
|
||||
@$(call get_tags,$(basename $(notdir $@))) >> $@
|
||||
@printf '%s\n' '---' >> $@
|
||||
@$(call list_commands,$(basename $(notdir $@))) >> $@
|
||||
|
||||
.PHONY: cmd
|
||||
cmd: $(lists) ## Big lists of commands
|
||||
|
||||
.PHONY: function
|
||||
function: ## Output a search function for .bashrc
|
||||
${MAKE} --silent --touch query
|
||||
printf '%s\n' 'lk(){'
|
||||
${MAKE} --silent --dry-run query | sed 's/^/\t/'
|
||||
printf '%s\n' '}'
|
||||
|
||||
.PHONY: query
|
||||
query: db.rec ## Search the setup notes
|
||||
passes=0 count=0; until [ "$$count" -eq "1" ] || [ "$$passes" -gt 2 ] ; do \
|
||||
query="$$(recsel "${PWD}"/db.rec -p aim,tag | recsel -iq "$$query" -CP aim,tag | sort -u | fzf --preview='recsel "${PWD}"/db.rec -e "aim~{}"')" \
|
||||
&& count="$$(recsel "${PWD}"/db.rec -q "$$query" -c )" ;\
|
||||
passes=$$(( passes + 1 )) ;\
|
||||
done \
|
||||
&& recsel "${PWD}"/db.rec -q "$$query" | recfmt -f "${PWD}/lists.fmt" | ${PAGER}
|
||||
|
||||
475
command.rec
475
command.rec
@@ -1,475 +0,0 @@
|
||||
%rec: command
|
||||
%doc: shell command examples
|
||||
%type: aim line
|
||||
%allowed: aim cmd bin tag note shell
|
||||
%unique: shell
|
||||
|
||||
aim: Put output into columns
|
||||
cmd: ip a | grep inet | column -ts' '
|
||||
shell: sh
|
||||
bin: column
|
||||
tag: format
|
||||
|
||||
aim: Reformat user accounts with an explicit separator (`-s`)
|
||||
cmd: column -ts: /etc/passwd
|
||||
shell: sh
|
||||
bin: column
|
||||
tag: format
|
||||
|
||||
aim: Sort user accounts into columns with names
|
||||
cmd: column -ts: -N User,PW,UID,GID,Description,Home,shell -H PW,GID /etc/passwd
|
||||
note: Hide some columns with `-H`.
|
||||
shell: sh
|
||||
bin: column
|
||||
tag: format
|
||||
|
||||
aim: Sort user accounts into columns and reorder them
|
||||
cmd: column -ts: -N User,PW,UID,GID,Description,Home,shell -H PW,GID -O User,Description,shell /etc/passwd
|
||||
note: Unspecified items remain.
|
||||
shell: sh
|
||||
bin: column
|
||||
tag: format
|
||||
|
||||
aim: Output user accounts in json format with `-J`
|
||||
cmd: column -J -ts: -H PW,GID,shell -N User,PW,UID,GID,Description,Home,shell /etc/passwd
|
||||
shell: sh
|
||||
bin: column
|
||||
tag: format
|
||||
tag: json
|
||||
|
||||
aim: Make a QR Code image
|
||||
cmd: qrencode 'https://play.google.com/store/apps/details?id=org.briarproject.briar.android' -o "${file}".png
|
||||
shell: sh
|
||||
bin: qrencode
|
||||
tag: qr
|
||||
|
||||
aim: Make a QR Coded message in the terminal
|
||||
cmd: qrencode -t ansi "Hello World"
|
||||
shell: sh
|
||||
bin: qrencode
|
||||
tag: qr
|
||||
|
||||
aim: Read a QR Code image
|
||||
cmd: zbarimg ${file}
|
||||
shell: sh
|
||||
bin: qrencode
|
||||
tag: qr
|
||||
|
||||
aim: Show wifi QR code (only with Network Manager)
|
||||
cmd: nmcli device wifi show-password
|
||||
shell: sh
|
||||
bin: qrencode
|
||||
bin: nmcli
|
||||
tag: qr
|
||||
tag: wifi
|
||||
|
||||
aim: Combine many recfiles of different types into one
|
||||
cmd: sed '1i\ ' *.rec > all.rec
|
||||
shell: sh
|
||||
bin: sed
|
||||
tag: recfiles
|
||||
tag: database
|
||||
|
||||
aim: Combine many recfiles of the same type into one
|
||||
cmd: recinf -d -t ${type} ${one}.rec > ${all}.rec
|
||||
+ sed '/^%/d' ${one}.rec ${two}.rec > all.rec
|
||||
note: The strange syntax used by `sed` only makes sense after using [ed](writing/ed.md)
|
||||
shell: sh
|
||||
bin: sed
|
||||
bin: recinf
|
||||
tag: recfiles
|
||||
tag: database
|
||||
|
||||
aim: Roll a die
|
||||
cmd: echo $(( RANDOM % 6+1 ))
|
||||
shell: bash
|
||||
tag: random
|
||||
|
||||
aim: Remotely edit a file with vim
|
||||
cmd: vim scp://${server}/~/${file}
|
||||
cmd: vim scp://${user}@${server}:${port}//${path}/${file}
|
||||
shell: sh
|
||||
bin: vim
|
||||
bin: scp
|
||||
tag: network
|
||||
|
||||
aim: Find and replace across all files open in vim
|
||||
cmd: :bufdo! %s/${pattern}/${replacement}/g
|
||||
shell: sh
|
||||
bin: vim
|
||||
tag: writing
|
||||
tag: replace
|
||||
|
||||
aim: Find and replace words, but confirm each replacement
|
||||
cmd: vim -c "%s/${pattern}/${replacement}/gc" -c 'wq' ${file}
|
||||
shell: sh
|
||||
bin: vim
|
||||
tag: replace
|
||||
tag: substitution
|
||||
tag: TUI
|
||||
tag: writing
|
||||
|
||||
aim: Hard reset ntp service
|
||||
cmd: sudo ntpd -q -g -x -n
|
||||
bin: ntpd
|
||||
tag: time
|
||||
tag: system
|
||||
|
||||
aim: Check a service
|
||||
cmd: sudo systemctl status mpd
|
||||
shell: sh
|
||||
bin: systemd
|
||||
tag: system
|
||||
tag: service
|
||||
|
||||
aim: Recognize service changes
|
||||
cmd: sudo systemctl daemon-reload
|
||||
shell: sh
|
||||
bin: systemd
|
||||
tag: system
|
||||
tag: service
|
||||
|
||||
aim: Start a service (it stops when the computer shuts down)
|
||||
cmd: sudo systemctl taskd.service start
|
||||
+ sudo systemctl daemon-reload
|
||||
shell: sh
|
||||
bin: systemd
|
||||
tag: system
|
||||
tag: service
|
||||
|
||||
aim: Find out why the computer takes so long to start
|
||||
cmd: sudo systemd-analyze
|
||||
+ sudo systemd-analyze blame
|
||||
shell: sh
|
||||
bin: systemd
|
||||
tag: system
|
||||
tag: boot
|
||||
|
||||
aim: See what the computer is doing
|
||||
cmd: journalctl -f
|
||||
shell: sh
|
||||
bin: journalctl
|
||||
tag: system
|
||||
|
||||
aim: Check your own user services:
|
||||
cmd: journalctl -f
|
||||
shell: sh
|
||||
bin: journalctl
|
||||
tag: system
|
||||
|
||||
aim: Follow the `ssh` daemon service
|
||||
cmd: journalctl -f -u sshd
|
||||
shell: sh
|
||||
bin: journalctl
|
||||
tag: system
|
||||
|
||||
aim: Find errors since a date
|
||||
cmd: date=2027-01-01
|
||||
+ journalctl --since=${date} --grep="EXT4-fs error"
|
||||
shell: sh
|
||||
bin: journalctl
|
||||
tag: system
|
||||
|
||||
aim: Limit the journal's size to 2 gigabytes
|
||||
cmd: journalctl --vacuum-size=2G
|
||||
shell: sh
|
||||
bin: journalctl
|
||||
tag: system
|
||||
|
||||
aim: Log the fact that you've installed your own `dnsmasq` on your system to `journalctl`, so that you can determine why your system's broken later
|
||||
cmd: logger "Installed new dnsmasq"
|
||||
+ sudo journalctl -f
|
||||
shell: sh
|
||||
bin: journalctl
|
||||
tag: system
|
||||
|
||||
aim: Convert markdown table to csv
|
||||
cmd: mlr --imarkdown --ocsv cat ${file}.md
|
||||
bin: mlr
|
||||
tag: csv
|
||||
tag: markdown
|
||||
tag: data
|
||||
|
||||
aim: Convert a csv file to markdown
|
||||
cmd: mlr --icsv --omd cat ${file}.csv
|
||||
bin: mlr
|
||||
tag: csv
|
||||
tag: markdown
|
||||
|
||||
aim: Quickly find and open run-command files
|
||||
cmd: alias rrc='$PAGER "$(find . -maxdepth 2 -name "*rc" | fzf)"'
|
||||
bin: fzf
|
||||
bin: find
|
||||
tag: comfy
|
||||
|
||||
aim: Quickly hunt and kill processes
|
||||
cmd: kill $(pgrep less | fzf -m --preview='ps {}')
|
||||
note: Select many with shift/tab.
|
||||
bin: fzf
|
||||
tag: comfy
|
||||
|
||||
aim: Search for a short word
|
||||
cmd: grep "\b${word}\b" ${file}
|
||||
bin: grep
|
||||
tag: search
|
||||
|
||||
aim: Extract words in quotes
|
||||
cmd: grep -o "\b${word}\b" ${file}
|
||||
bin: grep
|
||||
tag: search
|
||||
|
||||
aim: Reformat variable for shell input
|
||||
cmd: printf "%q\n" "${variable}"
|
||||
bin: printf
|
||||
tag: xargs
|
||||
tag: stdout
|
||||
|
||||
aim: Find your public IP address
|
||||
cmd: dig +short myip.opendns.com @resolver$((RANDOM % 4 + 1)).opendns.com
|
||||
shell: bash
|
||||
bin: dig
|
||||
tag: ip
|
||||
tag: network
|
||||
|
||||
aim: Turn markdown into a man page
|
||||
cmd: man <(lowdown -stman ${file}.md)
|
||||
cmd: top_title="Bugs in netcat"
|
||||
+ someplace=LK
|
||||
+ vol=Security
|
||||
+ sec=6
|
||||
+ lowdown -m manheader="${top_title}" -m source="${someplace}" -m volume="${vol}" -m section=${sec} -stman ${file}.md > ${file}.${sec}
|
||||
+ man ./${file}.${sec}
|
||||
shell: bash
|
||||
bin: lowdown
|
||||
bin: groff
|
||||
bin: man
|
||||
tag: markdown
|
||||
|
||||
aim: Convert jpg to png
|
||||
cmd: magick ${input}.jpg ${output}.png
|
||||
bin: magick
|
||||
tag: vision
|
||||
|
||||
aim: Reduce jpg size by reducing quality
|
||||
cmd: quality=70
|
||||
+ magick ${input}.jpg -quality ${quality} ${output}.jpg
|
||||
cmd: size=50
|
||||
+ magick -resize ${size}% ${input}.jpg ${output}.jpg
|
||||
bin: magick
|
||||
tag: vision
|
||||
|
||||
aim: Reduce png size
|
||||
cmd: magick ${input}.png png8:${output}.png
|
||||
bin: magick
|
||||
tag: vision
|
||||
|
||||
aim: Invert jpg colours
|
||||
cmd: magick ${input}.jpg ${output}.jpg -negate
|
||||
bin: magick
|
||||
tag: vision
|
||||
|
||||
aim: Make jpg smaller
|
||||
cmd: magick ${input}.jpg -resize 25% ${output}.jpg
|
||||
bin: magick
|
||||
tag: vision
|
||||
|
||||
aim: Trim images to border
|
||||
cmd: magick -trim ${image}.png ${output}.png
|
||||
bin: magick
|
||||
tag: vision
|
||||
|
||||
aim: Make the white of an image transparent
|
||||
cmd: magick -transparent white -fuzz 10% ${input}.png ${output}.png
|
||||
bin: magick
|
||||
tag: vision
|
||||
note: The 'fuzz' option tells the computer that 'close to white' is fine. You might want to use 20% or higher fuzz.
|
||||
|
||||
aim: Give transparrent image a dropshadow
|
||||
cmd: magick ${input}.png \( +clone -background black -shadow 50x8+0+5 \) +swap -background none -layers merge +repage ${output}.png
|
||||
bin: magick
|
||||
tag: vision
|
||||
|
||||
aim: Convert every jpg in directory to png
|
||||
cmd: mogrify -format png *.jpg
|
||||
bin: magick
|
||||
tag: vision
|
||||
|
||||
aim: Convert from jpg to svg
|
||||
cmd: magick -flatten ${input}.jpg ${output}.ppm
|
||||
+ potrace -s ${output}.ppm -o ${svgout}.svg
|
||||
bin: magick
|
||||
tag: vision
|
||||
|
||||
aim: Make an image showing day of the week
|
||||
cmd: magick -list font
|
||||
+ font="$(magick -list font | grep -oP 'Font: \K.*' | head -1)"
|
||||
+
|
||||
+ magick -fill blue -font "${font}" -gravity center -pointsize 79 label:$(date +%A) day.png
|
||||
bin: magick
|
||||
tag: vision
|
||||
|
||||
aim: Make a meme
|
||||
cmd: magick ${input} -font impact -fill white -pointsize 84 -stroke black -strokewidth 3 -gravity north -annotate +0+20 'TOP MEME TEXT' -gravity south -annotate +0+20 'BOTTOM MEME TEXT' ${output}
|
||||
bin: magick
|
||||
tag: vision
|
||||
tag: memes
|
||||
|
||||
aim: Rotate a video
|
||||
cmd: ffmpeg -i "${input}" -vf "transpose=1" "${out.mov}"
|
||||
note:
|
||||
+ | No. | Degrees | Flip |
|
||||
+ |:---:|:-------:|:---------------------------------------|
|
||||
+ | 0 | 90 Counterclockwise and verfical flip (default) |
|
||||
+ | 1 | 90 Clockwise |
|
||||
+ | 2 | 90 CounterClockwise |
|
||||
+ | 3 | 90Clockwise and vertical flip |
|
||||
tag: vision
|
||||
tag: video
|
||||
shell: sh
|
||||
|
||||
aim: Translate a media file to a new type
|
||||
cmd: ffmpeg -formats
|
||||
+ ffmpeg -i ${input} ${output}
|
||||
bin: ffmpeg
|
||||
tag: vision
|
||||
tag: music
|
||||
tag: video
|
||||
shell: sh
|
||||
|
||||
aim: Reduce video quality
|
||||
cmd: quality=20
|
||||
+ ffmpeg -i ${input}.mp4 -vcodec libx264 -crf ${quality} ${output}.mp4
|
||||
note: A crf quality of 18 is high, while 24 is low quality.
|
||||
bin: ffmpeg
|
||||
tag: vision
|
||||
tag: video
|
||||
shell: sh
|
||||
|
||||
aim: Convert from mkv to mp4 with a codec
|
||||
cmd: ffmpeg -i ${input}.mkv -codec copy ${output}.mp4
|
||||
note: Both mp4 and mkv are wrappers around other formats, so this conversion loses less quality than other conversion types.
|
||||
bin: ffmpeg
|
||||
tag: vision
|
||||
tag: video
|
||||
shell: sh
|
||||
|
||||
aim: Convert video to audio
|
||||
cmd: ffmpeg -i ${input}.mp4 -vn ${output}.mp3
|
||||
bin: ffmpeg
|
||||
tag: vision
|
||||
tag: video
|
||||
shell: sh
|
||||
|
||||
aim: Convert all mkv files to mp4
|
||||
cmd: for i in *.mkv; do
|
||||
+ ffmpeg -i "$i" -codec copy "${i%.*}.mp4"
|
||||
+ done
|
||||
bin: ffmpeg
|
||||
tag: vision
|
||||
shell: sh
|
||||
|
||||
aim: Change resolution
|
||||
cmd: ffmpeg -i ${input}.mp4 -filter:v scale=1280:720 -c:a copy ${output}.mp4
|
||||
bin: ffmpeg
|
||||
tag: vision
|
||||
shell: sh
|
||||
|
||||
aim: Change video aspect ratio
|
||||
cmd: ffmpeg -i input.mp4 -aspect 16:9 output.mp4
|
||||
bin: ffmpeg
|
||||
tag: vision
|
||||
tag: video
|
||||
shell: sh
|
||||
|
||||
aim: Trim video to start and stop times
|
||||
cmd: start=00:00:50
|
||||
+ stop=50
|
||||
+ ffmpeg -i ${input}.mp4 -ss ${start} -codec copy -t ${stop} ${output}.mp4
|
||||
note: The `$stop` time shows how many seconds after the start you want.
|
||||
bin: ffmpeg
|
||||
tag: vision
|
||||
shell: sh
|
||||
|
||||
aim: Compress a video file
|
||||
cmd: quality=21
|
||||
+ ffmpeg -i ${input}.mp4 -vf scale=1280:-1 -c:v libx264 -preset veryslow -crf ${quality} ${output}.mp4
|
||||
note: A crf quality of 18 is high, while 24 is low quality.
|
||||
bin: ffmpeg
|
||||
tag: vision
|
||||
tag: video
|
||||
shell: sh
|
||||
|
||||
aim: Convert video to a series of images
|
||||
cmd: framerate=1
|
||||
+ format=image2
|
||||
+ ffmpeg -i input.mp4 -r ${framerate} -f ${format} image-%2d.png
|
||||
bin: ffmpeg
|
||||
tag: vision
|
||||
shell: sh
|
||||
|
||||
aim: Add subtitles to a video file
|
||||
cmd: fmpeg -i ${input}.mp4 -i subtitle.srt -map 0 -map 1 -c copy -c:v libx264 -crf 23 -preset veryfast ${output}.mp4
|
||||
bin: ffmpeg
|
||||
tag: vision
|
||||
shell: sh
|
||||
|
||||
aim: Convert a web page to markdown
|
||||
cmd: curl -sL "${url}" | html2markdown > "${file}}".md
|
||||
cmd: curl -sL "${url}" | html2text > "${file}}".md
|
||||
note: The `[html2markdown](https://github.com/JohannesKaufmann/html-to-markdown)` and `html2md` programs works better than any other.
|
||||
bin: html2markdown
|
||||
bin: curl
|
||||
tag: writing
|
||||
tag: web
|
||||
shell: sh
|
||||
|
||||
aim: Decode a URL with function
|
||||
cmd: urldecode() { echo -e "${@//%/\\x}"; }
|
||||
+ urldecode "${magnet}"
|
||||
tag: web
|
||||
shell: bash
|
||||
|
||||
aim: Choose which parts to commit with git
|
||||
cmd: git commit -p
|
||||
note: Use `P` to see big changes which cannot fit on the screen.
|
||||
tag: comfy
|
||||
bin: git
|
||||
shell: sh
|
||||
|
||||
aim: Request a definition from the terminal.
|
||||
cmd: word='abderian'
|
||||
+ curl -s dict://dict.org/define:${word}:
|
||||
cmd: function wotsa(){
|
||||
+ def="$(curl -s dict://dict.org/define:${1// /+}: | grep -vP '^\d\d\d ')"
|
||||
+ if [ "$def" = "" ]; then
|
||||
+ echo no definition
|
||||
+ else
|
||||
+ echo "$def" | $PAGER
|
||||
+ fi
|
||||
+ }
|
||||
bin: curl
|
||||
tag: writing
|
||||
tag: comfy
|
||||
tag: dict
|
||||
shell: sh
|
||||
|
||||
aim: Email a pull request which points to your git server
|
||||
tag: git
|
||||
bin: git
|
||||
tag: email
|
||||
tag: pr
|
||||
cmd: repo=ssh://soft.dmz.rs:2222/mkdots/
|
||||
+ theirHead='HEAD^^^^'
|
||||
+ head=master
|
||||
+ git request-pull "${theirHead}" "${repo}" "${head}"
|
||||
note: You can note where your branch diverged from theirs with a commit hash,
|
||||
+ or a relative position, like `HEAD^^` (e.g. 'two commits before your latest').
|
||||
|
||||
aim: Clean up a bloated git repo
|
||||
cmd: git fsck --full
|
||||
+ git gc --prune=now --aggressive
|
||||
+ git repack
|
||||
bin: git
|
||||
tag: maintenance
|
||||
shell: sh
|
||||
|
||||
@@ -1,16 +1,15 @@
|
||||
---
|
||||
title: Archives
|
||||
tags:
|
||||
- archives
|
||||
- backups
|
||||
title: "Archives"
|
||||
tags: [ "tar", "backups", ".tgz", "tar.gz" ]
|
||||
---
|
||||
# `tar`
|
||||
|
||||
# Create
|
||||
## Create
|
||||
|
||||
Combine many files and directories into a single t-archive file.
|
||||
|
||||
```sh
|
||||
tar cf "${archive}".tar ${dir}
|
||||
tar cf "$ARCHIVE".tar $DIR
|
||||
```
|
||||
You can remember this with the mnemonic '*C*reate *F*ile'.
|
||||
|
||||
@@ -18,13 +17,13 @@ Unfortunately, this stores the full file path, so making a tar archive of `/etc/
|
||||
It's often better to tell tar which path to start from using the `-C` flag.
|
||||
|
||||
```sh
|
||||
tar cf "${archive}".tar -C /etc/ nginx
|
||||
tar cf "$ARCHIVE".tar -C /etc/ nginx
|
||||
```
|
||||
|
||||
Check the contents of your archive with:
|
||||
|
||||
```sh
|
||||
tar tf "${archive}".tar
|
||||
tar tf "$ARCHIVE".tar
|
||||
```
|
||||
|
||||
If you want to store 'everything in a directory', then using `*` will not work, because it will target everything in the *current* directory.
|
||||
@@ -33,26 +32,47 @@ Instead, you can store the target in a variable:
|
||||
|
||||
```sh
|
||||
files=$(ls /etc/nginx)
|
||||
tar cf "${archive}".tar -C /etc/nginx/ $file
|
||||
tar cf "$ARCHIVE".tar -C /etc/nginx/ $file
|
||||
```
|
||||
|
||||
# Extract
|
||||
## Extract
|
||||
|
||||
Extract the tar archive with
|
||||
|
||||
```sh
|
||||
tar xf "${archive}".tar
|
||||
tar xf "$ARCHIVE".tar
|
||||
```
|
||||
|
||||
You can remember this with the mnemonic 'e*X*tract *F*ile'.
|
||||
|
||||
# Compress
|
||||
## Compress
|
||||
|
||||
Create a zip-compressed archive with the `z` flag.
|
||||
|
||||
```sh
|
||||
tar czf "${archive}".tgz -C /etc/nginx/ $file
|
||||
tar czf "$ARCHIVE".tgz -C /etc/nginx/ $file
|
||||
```
|
||||
|
||||
You can use any file ending you want, but sane people like to use '.tgz' or '.tar.tgz'.
|
||||
|
||||
# 7zip
|
||||
|
||||
(also called 'p7zip' or '7z')
|
||||
|
||||
Make archive:
|
||||
|
||||
```sh
|
||||
7za a -tzip -p "$PASSWORD" -mem=AES256 $ARCHIVE.zip $FILE_1 $FILE_2
|
||||
```
|
||||
|
||||
Note that people can still see every filename in your archive, and can change those files.
|
||||
They just can't read the contents.
|
||||
|
||||
Unzip:
|
||||
|
||||
```sh
|
||||
7za x archive.zip
|
||||
```
|
||||
|
||||
7zip will open anything: zip-files, rar-files, a tin of beans, *anything*.
|
||||
However, the extracted tgz files will just be tar files, so you will still need to use tar to extract them (see above).
|
||||
@@ -1,10 +1,6 @@
|
||||
---
|
||||
title: unison
|
||||
tags:
|
||||
- backups
|
||||
- synch
|
||||
requires:
|
||||
- networking/ssh.md
|
||||
title: "unison"
|
||||
tags: [ "backups", "synch" ]
|
||||
---
|
||||
|
||||
Install unison on both machines, and make sure both have the same version of unison, with the same version of the ocaml compiler (the smallest difference will cause problems).
|
||||
@@ -18,7 +14,7 @@ Create the `~/.unison` directory on both machines.
|
||||
Make a job called `backup`:
|
||||
|
||||
```sh
|
||||
job=backup
|
||||
JOB=backup
|
||||
```
|
||||
|
||||
Here is an example job, which synchronizes the `~/music` directory with a remote machine which has the same username.
|
||||
@@ -28,16 +24,16 @@ Here is an example job, which synchronizes the `~/music` directory with a remote
|
||||
echo "
|
||||
auto = true
|
||||
root=$HOME
|
||||
root=ssh://${user}@${ip_address}/$HOME
|
||||
root=ssh://$USER@$IP_ADDRESS/$HOME
|
||||
|
||||
path=music
|
||||
|
||||
ignore=Name *.flac
|
||||
" > ~/.unison/"${job}".prf
|
||||
" > ~/.unison/"$JOB".prf
|
||||
|
||||
```
|
||||
|
||||
Remember to specify `${ip_address}`
|
||||
Remember to specify `$IP_ADDRESS`
|
||||
|
||||
The last command means it will ignore any file with a name ending in `.flac`.
|
||||
|
||||
@@ -47,7 +43,7 @@ The first command means this will run but also confirm which files will be delet
|
||||
Or you can deleted that line in the `.prf` file and run it with a flag:
|
||||
|
||||
```sh
|
||||
unison -batch ${job}.prf
|
||||
unison -batch *backup*.prf
|
||||
```
|
||||
|
||||
Set unison to run with crontab or a systemd unit file to have directories synchronize automatically.
|
||||
@@ -1,7 +1,6 @@
|
||||
---
|
||||
title: Base 16
|
||||
tags:
|
||||
- data
|
||||
title: "Base 16"
|
||||
tags: [ "data" ]
|
||||
---
|
||||
|
||||
Base 16 numbers often use `0x` at the start, so '10' just means '10', but `0x10` means '10 in base 16' which means '16'.
|
||||
|
||||
14
data/calcurse.md
Normal file
14
data/calcurse.md
Normal file
@@ -0,0 +1,14 @@
|
||||
---
|
||||
title: "calcurse"
|
||||
tags: [ "data", "calendar", "daylight savings" ]
|
||||
---
|
||||
|
||||
## Setup
|
||||
|
||||
The UK government keeps an `ics` file with clock.
|
||||
|
||||
```sh
|
||||
wget https://www.gov.uk/when-do-the-clocks-change/united-kingdom.ics
|
||||
calcurse -i united-kingdom.ics
|
||||
```
|
||||
|
||||
@@ -1,34 +0,0 @@
|
||||
---
|
||||
title: Import an ICS file into calcurse
|
||||
tags:
|
||||
- data
|
||||
- calendar
|
||||
- daylight savings
|
||||
requires:
|
||||
- calcurse
|
||||
---
|
||||
|
||||
## Setup
|
||||
|
||||
The UK government keeps an `ics` file with clock.
|
||||
|
||||
```sh
|
||||
wget https://www.gov.uk/when-do-the-clocks-change/united-kingdom.ics
|
||||
calcurse -i united-kingdom.ics
|
||||
```
|
||||
|
||||
If you already have some of these events, and don't want duplicates, import the events into a temporary file.
|
||||
|
||||
|
||||
```sh
|
||||
TMP=$(mktemp)
|
||||
curl -s "$1" | calcurse -q -i - -c "$TMP"
|
||||
```
|
||||
|
||||
Then search for new lines in the new calendar file to put into your appointments file.
|
||||
|
||||
```sh
|
||||
CALDATA=~/.local/share/calcurse/apts
|
||||
grep -vf "$CALDATA" "$TMP" >> "$CALDATA"
|
||||
rm $TMP
|
||||
```
|
||||
@@ -1,8 +1,6 @@
|
||||
---
|
||||
title: e-mail
|
||||
tags:
|
||||
- data
|
||||
- smtp
|
||||
title: "e-mail"
|
||||
tags: [ "data", "smtp" ]
|
||||
---
|
||||
|
||||
This is bare-bones, original, primitive e-mail.
|
||||
|
||||
@@ -1,8 +1,6 @@
|
||||
---
|
||||
title: exiftool
|
||||
tags:
|
||||
- metadata
|
||||
- exifdata
|
||||
title: "exiftool"
|
||||
tags: [ "metadata", "exifdata" ]
|
||||
---
|
||||
|
||||
Find metadata:
|
||||
|
||||
133
data/git.md
133
data/git.md
@@ -1,133 +0,0 @@
|
||||
---
|
||||
title: git
|
||||
tags:
|
||||
- data
|
||||
- setup
|
||||
---
|
||||
|
||||
|
||||
```sh
|
||||
git config --global user.email "${email}"
|
||||
```
|
||||
|
||||
```sh
|
||||
git config --global user.name "${name}"
|
||||
```
|
||||
|
||||
Decide on algorithm:
|
||||
|
||||
- If you're scared of insecure hash-sums, go with `hash=sha256`.
|
||||
- If you don't know what a hash sum is, go with `hash=sha1`.
|
||||
|
||||
## Init the Git
|
||||
|
||||
Start a git in directory `${DIR}`:
|
||||
|
||||
```sh
|
||||
git init --object-format=${hash} ${DIR}
|
||||
cd ${dir}/
|
||||
```
|
||||
|
||||
Make a file explaining what the project does, and tell `git` to track it:
|
||||
|
||||
```sh
|
||||
echo "I hereby solemnly swear never to commit a binary file." > README.md
|
||||
git add README.md
|
||||
```
|
||||
|
||||
Then make the initial commit, explaining the change you just made:
|
||||
|
||||
```sh
|
||||
git commit
|
||||
```
|
||||
|
||||
# Working
|
||||
|
||||
Once you make a change to some file, add it and make a commit explaining it.
|
||||
|
||||
```sh
|
||||
git add ${file}
|
||||
```
|
||||
|
||||
```sh
|
||||
git commit -m"change ${file}"
|
||||
```
|
||||
|
||||
Check your history:
|
||||
|
||||
```sh
|
||||
git log
|
||||
```
|
||||
|
||||
# Remotes
|
||||
|
||||
If you want to keep a copy on a public site such as Gitlab, so others can see it, then go there and create a blank project (no readme, nothing).
|
||||
Give it the same name as the `$DIR` directory, above.
|
||||
|
||||
Add this as a remote:
|
||||
|
||||
```sh
|
||||
remote=gitlab
|
||||
git remote add ${remote} https://gitlab.com/${username}/${dir}
|
||||
```
|
||||
|
||||
Tell git you're pushing the branch 'master' to the remote repo 'origin':
|
||||
|
||||
```sh
|
||||
git push -u master origin
|
||||
```
|
||||
|
||||
Pull down changes that others have made:
|
||||
|
||||
```sh
|
||||
git pull
|
||||
```
|
||||
|
||||
# Branches
|
||||
|
||||
A branch is a full copy of the project to test additional ideas.
|
||||
You can make a new branch called 'featurez' like this:
|
||||
|
||||
```sh
|
||||
git branch ${feature_branch}
|
||||
```
|
||||
|
||||
Have a look at all your branches:
|
||||
|
||||
```sh
|
||||
git branch
|
||||
```
|
||||
|
||||
Switch to your new branch:
|
||||
|
||||
```sh
|
||||
git checkout ${feature_branch}
|
||||
```
|
||||
|
||||
And if your changes are rubbish, checkout the "master" branch again, then delete "featurez":
|
||||
|
||||
```sh
|
||||
git branch -D ${feature_branch}
|
||||
```
|
||||
|
||||
Or if it's a good branch, push it to the remote:
|
||||
|
||||
```sh
|
||||
remote=origin
|
||||
git push $remote ${feature_branch}
|
||||
```
|
||||
|
||||
# Merging
|
||||
|
||||
Once you like the feature, merge it into the main branch. Switch to master then merge it:
|
||||
|
||||
```sh
|
||||
git merge ${feature_branch}
|
||||
```
|
||||
|
||||
And delete the branch, as you've already merged it:
|
||||
|
||||
```sh
|
||||
git branch -d ${feature_branch}
|
||||
```
|
||||
|
||||
202
data/git/basics.md
Normal file
202
data/git/basics.md
Normal file
@@ -0,0 +1,202 @@
|
||||
---
|
||||
title: "git"
|
||||
tags: [ "data" ]
|
||||
---
|
||||
# Starting
|
||||
|
||||
## New Machines
|
||||
|
||||
```sh
|
||||
git config --global user.email "$YOUR_EMAIL"
|
||||
```
|
||||
|
||||
```sh
|
||||
git config --global user.name "$YOUR_NAME"
|
||||
```
|
||||
|
||||
# New Git
|
||||
|
||||
Decide on algorithm:
|
||||
|
||||
- If you're scared of insecure hash-sums, go with `hash=sha256`.
|
||||
- If you don't know what a hash sum is, go with `hash=sha1`.
|
||||
|
||||
## Init the Git
|
||||
|
||||
Start a git in directory `${DIR}`:
|
||||
|
||||
```sh
|
||||
git init --object-format=${hash} ${DIR}
|
||||
cd ${DIR}
|
||||
```
|
||||
|
||||
Make a file explaining what the project does, and tell `git` to track it:
|
||||
|
||||
```sh
|
||||
echo "I hereby solemnly swear never to commit a binary file." > README.md
|
||||
git add README.md
|
||||
```
|
||||
|
||||
Then make the initial commit, explaining the change you just made:
|
||||
|
||||
```sh
|
||||
git commit
|
||||
```
|
||||
|
||||
# Working
|
||||
|
||||
Once you make a change to some file, add it and make a commit explaining it.
|
||||
|
||||
```sh
|
||||
git add $FILE
|
||||
```
|
||||
|
||||
```sh
|
||||
git commit -m"change $FILE"
|
||||
```
|
||||
|
||||
Check your history:
|
||||
|
||||
```sh
|
||||
git log
|
||||
```
|
||||
|
||||
# Remotes
|
||||
|
||||
If you want to keep a copy on a public site such as Gitlab, so others can see it, then go there and create a blank project (no readme, nothing).
|
||||
Give it the same name as the `$DIR` directory, above.
|
||||
|
||||
Add this as a remote:
|
||||
|
||||
```sh
|
||||
REMOTE=gitlab
|
||||
git remote add $REMOTE https://gitlab.com/$USERNAME/$DIR
|
||||
```
|
||||
|
||||
Tell git you're pushing the branch "master" to the remote repo "origin":
|
||||
|
||||
```sh
|
||||
git push -u master origin
|
||||
```
|
||||
|
||||
If someone makes a change on the remote, pull it down with:
|
||||
|
||||
```sh
|
||||
git pull
|
||||
```
|
||||
|
||||
# Branches
|
||||
|
||||
A branch is a full copy of the project to test additional ideas.
|
||||
You can make a new branch called 'featurez' like this:
|
||||
|
||||
```sh
|
||||
git branch $FEATURE_BRANCH
|
||||
```
|
||||
|
||||
Have a look at all your branches:
|
||||
|
||||
```sh
|
||||
git branch
|
||||
```
|
||||
|
||||
Switch to your new branch:
|
||||
|
||||
```sh
|
||||
git checkout $FEATURE_BRANCH
|
||||
```
|
||||
|
||||
And if your changes are rubbish, checkout the "master" branch again, then delete "featurez":
|
||||
|
||||
```sh
|
||||
git branch -D $FEATURE_BRANCH
|
||||
```
|
||||
|
||||
Or if it's a good branch, push it to the remote:
|
||||
|
||||
```sh
|
||||
remote=origin
|
||||
git push $remote $FEATURE_BRANCH
|
||||
```
|
||||
|
||||
## Merging
|
||||
|
||||
Once you like the feature, merge it into the main branch. Switch to master then merge it:
|
||||
|
||||
```sh
|
||||
git merge $FEATURE_BRANCH
|
||||
```
|
||||
|
||||
And delete the branch, as you've already merged it:
|
||||
|
||||
```sh
|
||||
git branch -d $FEATURE_BRANCH
|
||||
```
|
||||
|
||||
# Subtree
|
||||
|
||||
## Pulling another git repo into a subtree
|
||||
|
||||
```sh
|
||||
git subtree add -P config git@gitlab.com:bindrpg/config.git master
|
||||
```
|
||||
|
||||
# Tricks
|
||||
|
||||
## Delete All History
|
||||
|
||||
```sh
|
||||
git checkout --orphan temp
|
||||
```
|
||||
|
||||
```sh
|
||||
git add -A
|
||||
```
|
||||
|
||||
```sh
|
||||
git commit -am "release the commits!"
|
||||
```
|
||||
|
||||
```sh
|
||||
git branch -D master
|
||||
```
|
||||
|
||||
```sh
|
||||
git branch -m master
|
||||
```
|
||||
|
||||
```sh
|
||||
git push -f origin master
|
||||
```
|
||||
|
||||
Gitlab requires more changes, such as going to `settings > repository` and switching the main branch, then stripping protection.
|
||||
|
||||
## Clean up Bloated Repo
|
||||
|
||||
```sh
|
||||
git fsck --full
|
||||
```
|
||||
|
||||
```sh
|
||||
git gc --prune=now --aggressive
|
||||
```
|
||||
|
||||
```sh
|
||||
git repack
|
||||
```
|
||||
|
||||
## Find Binary Blobs
|
||||
|
||||
```sh
|
||||
git rev-list --objects --all \
|
||||
| git cat-file --batch-check='%(objecttype) %(objectname) %(objectsize) %(rest)' \
|
||||
| sed -n 's/^blob //p' \
|
||||
| sort --numeric-sort --key=2 \
|
||||
| cut -c 1-12,41- \
|
||||
| $(command -v gnumfmt || echo numfmt) --field=2 --to=iec-i --suffix=B --padding=7 --round=nearest
|
||||
|
||||
```
|
||||
|
||||
# More
|
||||
|
||||
For big binary files (like images), see [git large-file-storage](git-lfs.md)
|
||||
@@ -1,10 +1,6 @@
|
||||
---
|
||||
title: Commit for Another
|
||||
tags:
|
||||
- data
|
||||
- git
|
||||
requires:
|
||||
- data/git.md
|
||||
title: "Commit for Another"
|
||||
tags: [ "data", "git" ]
|
||||
---
|
||||
|
||||
You can make Alice the author, while you are still the commiter:
|
||||
|
||||
@@ -1,10 +1,7 @@
|
||||
---
|
||||
title: git-lfs
|
||||
tags:
|
||||
- data
|
||||
- git
|
||||
requires:
|
||||
- data/git.md
|
||||
title: "git-lfs"
|
||||
tags: [ "data", "git" ]
|
||||
requires: [ "git" ]
|
||||
---
|
||||
|
||||
Git Large File Storage ('LFS') needs to change your `~/.gitconfig` to check out those binary files:
|
||||
|
||||
@@ -1,9 +1,6 @@
|
||||
---
|
||||
title: git-secret
|
||||
tags:
|
||||
- data
|
||||
- git
|
||||
- review
|
||||
title: "git-secret"
|
||||
tags: [ "data", "git" ]
|
||||
---
|
||||
|
||||
This utility is largely useless, as it can only identify people by their email.
|
||||
|
||||
@@ -1,10 +1,7 @@
|
||||
---
|
||||
title: git stash
|
||||
tags:
|
||||
- data
|
||||
- git
|
||||
requires:
|
||||
- data/git.md
|
||||
title: "git stash"
|
||||
tags: [ "data", "git" ]
|
||||
requires: [ "git" ]
|
||||
---
|
||||
|
||||
Save file-changes without committing anything.
|
||||
|
||||
@@ -1,14 +1,12 @@
|
||||
---
|
||||
title: git hooks
|
||||
tags:
|
||||
- data
|
||||
- git
|
||||
title: "git hooks"
|
||||
tags: [ "data", "git" ]
|
||||
---
|
||||
|
||||
Check out the sample hooks:
|
||||
|
||||
```sh
|
||||
cd ${git_repo}
|
||||
cd $GIT_REPO
|
||||
ls .git/hooks
|
||||
head .git/hooks/pre-commit.sample
|
||||
```
|
||||
@@ -23,9 +21,7 @@ chmod u+x .git/hooks/commit-msg
|
||||
|
||||
## Committing
|
||||
|
||||
The `git hooks` will not work on other people who use the repository, but you
|
||||
can commit them to a repository, then request others add these git hooks to
|
||||
their own branch, by putting a note in the project's `README.md`.
|
||||
Your `git hooks` will not enter the repository, but you can commit them to a repository, then request others add these git hooks to their own branch, by putting a note in the project's `README.md`.
|
||||
|
||||
```markdown
|
||||
The project comes with recommended git hooks.
|
||||
|
||||
34
data/git/subtree.md
Normal file
34
data/git/subtree.md
Normal file
@@ -0,0 +1,34 @@
|
||||
---
|
||||
title: "git subtree"
|
||||
tags: [ "data", "git", "subtree" ]
|
||||
---
|
||||
|
||||
## Pulling a Subtree from an existing git
|
||||
|
||||
The project has subdirectories `sub-1`, `sub-2`, `sub-3`.
|
||||
The first should be its own repository, but should also retain its own history.
|
||||
|
||||
First, we extract its history as an independent item, and make that into a seprate branch.
|
||||
|
||||
```sh
|
||||
git subtree split --prefix=sub-1 -b sub
|
||||
```
|
||||
|
||||
If you want something a few directories deep, you can use `--prefix=sub-1/dir-2/dir-3
|
||||
|
||||
Then go and create a new git somewhere else:
|
||||
|
||||
```sh
|
||||
cd ..;mkdir sub-1;cd sub-1;git init --bare
|
||||
```
|
||||
|
||||
Then go back to your initial git repo, and do the following:
|
||||
|
||||
git push ../subtest sub:master
|
||||
|
||||
Finally, you can clone this repo from your original.
|
||||
|
||||
```sh
|
||||
git clone ../subtest
|
||||
```
|
||||
|
||||
150
data/gpg.md
150
data/gpg.md
@@ -1,149 +1,7 @@
|
||||
---
|
||||
title: GPG Basics
|
||||
tags:
|
||||
- data
|
||||
- GPG
|
||||
title: "gpg"
|
||||
tags: [ "data", "gpg" ]
|
||||
---
|
||||
|
||||
# Making keys
|
||||
|
||||
Generate keys:
|
||||
|
||||
```sh
|
||||
gpg --full-generate-key
|
||||
```
|
||||
|
||||
Follow the guide.
|
||||
|
||||
# Encrypting a file
|
||||
|
||||
```sh
|
||||
gpg -r malinfreeborn@posteo.net -e file
|
||||
```
|
||||
|
||||
`-r` specifies the recipient.
|
||||
|
||||
Check you have an encrypted version of your file.
|
||||
|
||||
# Changing Expiration Dates
|
||||
|
||||
|
||||
```sh
|
||||
gpg --list-keys
|
||||
# or...
|
||||
gpg -k
|
||||
```
|
||||
|
||||
... and then use the second part of 'pub', which is the ID. But that's not appearing here so... on with gpg2?
|
||||
|
||||
# Making encrypted files with a local password
|
||||
|
||||
Make a password with a password (cypher encryption).
|
||||
|
||||
```sh
|
||||
gpg -c --output passwords.txt
|
||||
```
|
||||
|
||||
or
|
||||
|
||||
```sh
|
||||
gpg -c > passwords.txt
|
||||
```
|
||||
|
||||
Put in a password.
|
||||
|
||||
Write message then stop with Ctrl+d.
|
||||
|
||||
Get the message back out the file with:
|
||||
|
||||
```sh
|
||||
gpg -d passwords.txt
|
||||
```
|
||||
|
||||
# Circles of Trust
|
||||
|
||||
Search for a key at any key store:
|
||||
|
||||
```sh
|
||||
gpg --search-keys nestorv
|
||||
```
|
||||
|
||||
Once you've made a decision about someone:
|
||||
|
||||
```sh
|
||||
gpg --list-keys
|
||||
```
|
||||
|
||||
You get something like this:
|
||||
|
||||
```
|
||||
pub rsa3072 2021-08-15 [SC] [expires: 2023-08-15]
|
||||
CD30421FD825696BD95F1FF644C62C57B790D3CF
|
||||
uid [ultimate] Malin Freeborn <malinfreeborn@posteo.net>
|
||||
sub rsa3072 2021-08-15 [E] [expires: after-forever]
|
||||
|
||||
```
|
||||
|
||||
Notice the long, ugly, string - `CD30421FD825696BD95F1FF644C62C57B790D3CF` - and how horribly ugly it is.
|
||||
This is a fingerprint.
|
||||
|
||||
You can now decide the trust level (this stays on your computer).
|
||||
|
||||
```sh
|
||||
gpg --edit-key CD30421FD825696BD95F1FF644C62C57B790D3CF
|
||||
```
|
||||
|
||||
Once you're in the interface, type `trust`.
|
||||
|
||||
```sh
|
||||
gpg --sign-key alice@posteo.net
|
||||
```
|
||||
|
||||
# Swapping Keys
|
||||
|
||||
This system relies on a ring of people swapping key information.
|
||||
|
||||
## Sending
|
||||
|
||||
Send those trusted keys up to a server, so people can see you have verified them:
|
||||
|
||||
```sh
|
||||
gpg --send-keys 024C6B1C84449BD1CB4DF7A152295D2377F4D70F
|
||||
```
|
||||
|
||||
## Upload Your Keys
|
||||
|
||||
## Add More Key Servers
|
||||
|
||||
Key servers often swap keys, but it's best to just send to multiple places immediately.
|
||||
You can add key servers by adding this to `~/.gnupg/gpg.conf`.
|
||||
|
||||
```
|
||||
keyserver hkps://keys.openpgp.org
|
||||
keyserver hkps://mail-api.proton.me
|
||||
keyserver hkps://keys.mailvelope.com
|
||||
```
|
||||
|
||||
# Refresh Keys
|
||||
|
||||
Refreshing keys will tell you if some key you have contains a signature from someone you already trust, or if someone has published a revocation certificate (meaning their key should not be trusted any more).
|
||||
|
||||
```sh
|
||||
gpg --refresh-keys
|
||||
```
|
||||
|
||||
You can use the [crontab](system/cron.md) to refresh keys, but this will mostly fail, since keyservers often don't hold the right data.
|
||||
|
||||
# Export
|
||||
|
||||
Your public key:
|
||||
|
||||
```sh
|
||||
gpg --output me.gpg --armor --export
|
||||
```
|
||||
Alternatively:
|
||||
|
||||
```sh
|
||||
gpg --export -a person@email.tld > my_key.pub
|
||||
```
|
||||
|
||||
- [Setup](gpg/basics.md)
|
||||
- [Extras](gpg/extras.md)
|
||||
|
||||
146
data/gpg/basics.md
Normal file
146
data/gpg/basics.md
Normal file
@@ -0,0 +1,146 @@
|
||||
---
|
||||
title: "GPG Basics"
|
||||
tags: [ "data", "GPG" ]
|
||||
---
|
||||
# Making keys
|
||||
|
||||
Generate keys:
|
||||
|
||||
```sh
|
||||
gpg --full-generate-key
|
||||
```
|
||||
|
||||
Follow the guide.
|
||||
|
||||
# Encrypting a file
|
||||
|
||||
```sh
|
||||
gpg -r malinfreeborn@posteo.net -e file
|
||||
```
|
||||
|
||||
`-r` specifies the recipient.
|
||||
|
||||
Check you have an encrypted version of your file.
|
||||
|
||||
# Changing Expiration Dates
|
||||
|
||||
|
||||
```sh
|
||||
gpg --list-keys
|
||||
# or...
|
||||
gpg -k
|
||||
```
|
||||
|
||||
... and then use the second part of 'pub', which is the ID. But that's not appearing here so... on with gpg2?
|
||||
|
||||
# Making encrypted files with a local password
|
||||
|
||||
Make a password with a password (cypher encryption).
|
||||
|
||||
```sh
|
||||
gpg -c --output passwords.txt
|
||||
```
|
||||
|
||||
or
|
||||
|
||||
```sh
|
||||
gpg -c > passwords.txt
|
||||
```
|
||||
|
||||
Put in a password.
|
||||
|
||||
Write message then stop with Ctrl+d.
|
||||
|
||||
Get the message back out the file with:
|
||||
|
||||
```sh
|
||||
gpg -d passwords.txt
|
||||
```
|
||||
|
||||
# Circles of Trust
|
||||
|
||||
Search for a key at any key store:
|
||||
|
||||
```sh
|
||||
gpg --search-keys nestorv
|
||||
```
|
||||
|
||||
Once you've made a decision about someone:
|
||||
|
||||
```sh
|
||||
gpg --list-keys
|
||||
```
|
||||
|
||||
You get something like this:
|
||||
|
||||
```
|
||||
pub rsa3072 2021-08-15 [SC] [expires: 2023-08-15]
|
||||
CD30421FD825696BD95F1FF644C62C57B790D3CF
|
||||
uid [ultimate] Malin Freeborn <malinfreeborn@posteo.net>
|
||||
sub rsa3072 2021-08-15 [E] [expires: after-forever]
|
||||
|
||||
```
|
||||
|
||||
Notice the long, ugly, string - `CD30421FD825696BD95F1FF644C62C57B790D3CF` - and how horribly ugly it is.
|
||||
This is a fingerprint.
|
||||
|
||||
You can now decide the trust level (this stays on your computer).
|
||||
|
||||
```sh
|
||||
gpg --edit-key CD30421FD825696BD95F1FF644C62C57B790D3CF
|
||||
```
|
||||
|
||||
Once you're in the interface, type `trust`.
|
||||
|
||||
```sh
|
||||
gpg --sign-key alice@posteo.net
|
||||
```
|
||||
|
||||
# Swapping Keys
|
||||
|
||||
This system relies on a ring of people swapping key information.
|
||||
|
||||
## Sending
|
||||
|
||||
Send those trusted keys up to a server, so people can see you have verified them:
|
||||
|
||||
```sh
|
||||
gpg --send-keys 024C6B1C84449BD1CB4DF7A152295D2377F4D70F
|
||||
```
|
||||
|
||||
## Upload Your Keys
|
||||
|
||||
## Add More Key Servers
|
||||
|
||||
Key servers often swap keys, but it's best to just send to multiple places immediately.
|
||||
You can add key servers by adding this to `~/.gnupg/gpg.conf`.
|
||||
|
||||
```
|
||||
keyserver hkps://keys.openpgp.org
|
||||
keyserver hkps://mail-api.proton.me
|
||||
keyserver hkps://keys.mailvelope.com
|
||||
```
|
||||
|
||||
# Refresh Keys
|
||||
|
||||
Refreshing keys will tell you if some key you have contains a signature from someone you already trust, or if someone has published a revocation certificate (meaning their key should not be trusted any more).
|
||||
|
||||
```sh
|
||||
gpg --refresh-keys
|
||||
```
|
||||
|
||||
You can use the [crontab](../../basics/cron.md) to refresh keys, but this will mostly fail, since keyservers often don't hold the right data.
|
||||
|
||||
# Export
|
||||
|
||||
Your public key:
|
||||
|
||||
```sh
|
||||
gpg --output me.gpg --armor --export
|
||||
```
|
||||
Alternatively:
|
||||
|
||||
```sh
|
||||
gpg --export -a person@email.tld > my_key.pub
|
||||
```
|
||||
|
||||
11
data/gpg/extras.md
Normal file
11
data/gpg/extras.md
Normal file
@@ -0,0 +1,11 @@
|
||||
---
|
||||
title: "gpg with vim"
|
||||
tags: [ "vim", "data", "GPG" ]
|
||||
requires: [ "GPG Basics", "vim basics" ]
|
||||
---
|
||||
|
||||
The `vim-gnupg` plugin lets vim edit gpg-encrypted files as if they were unencrypted.
|
||||
|
||||
It's probably in your package manager.
|
||||
If not, you'll need to endure the faff of following the [instructions](http://www.vim.org/scripts/script.php?script_id=3645).
|
||||
|
||||
@@ -1,34 +0,0 @@
|
||||
---
|
||||
title: GPG Password Entry
|
||||
tags:
|
||||
- vim
|
||||
- secrets
|
||||
- TUI
|
||||
requires:
|
||||
- data/gpg.md
|
||||
- writing/vim.md
|
||||
---
|
||||
|
||||
|
||||
Check your current gpg-agent configuration:
|
||||
|
||||
```sh
|
||||
gpgconf --list-options gpg-agent
|
||||
```
|
||||
|
||||
Create file, if it doesn't exit `~/.gnupg/gpg-agent.conf`:
|
||||
|
||||
```
|
||||
# Force terminal prompts for passwords
|
||||
pinentry-mode loopback
|
||||
|
||||
# Optional: specify which pinentry program to use
|
||||
pinentry-program /usr/bin/pinentry-tty
|
||||
```
|
||||
|
||||
Then restart gpg-agent:
|
||||
|
||||
```sh
|
||||
gpg-connect-agent reloadagent /bye
|
||||
```
|
||||
|
||||
@@ -1,17 +0,0 @@
|
||||
---
|
||||
title: Edit gpg encrypted files with vim
|
||||
tags:
|
||||
- vim
|
||||
- data
|
||||
- gpg
|
||||
- comfy
|
||||
requires:
|
||||
- data/gpg.md
|
||||
- writing/vim.md
|
||||
---
|
||||
|
||||
The `vim-gnupg` plug-in lets vim edit gpg-encrypted files as if they were unencrypted.
|
||||
|
||||
It's probably in your package manager.
|
||||
If not, you'll need to endure the faff of following the [instructions](http://www.vim.org/scripts/script.php?script_id=3645).
|
||||
|
||||
@@ -1,9 +1,6 @@
|
||||
---
|
||||
title: groff
|
||||
tags:
|
||||
- documentation
|
||||
- typography
|
||||
- logic
|
||||
title: "groff"
|
||||
tags: [ "data", "logic" ]
|
||||
---
|
||||
# Basic Documents
|
||||
|
||||
@@ -63,6 +60,8 @@ The equation shorthands are predictable:
|
||||
| Not equal | != |
|
||||
| Superscript | sup {thing} |
|
||||
|
||||
- [List of symbols](https://www.math-linux.com/man/man7/groff_char.7.html)
|
||||
|
||||
### Examples
|
||||
|
||||
The fraction 2/5ths:
|
||||
|
||||
@@ -1,11 +1,6 @@
|
||||
---
|
||||
title: Interactive String Substitution
|
||||
tags:
|
||||
- data
|
||||
- vim
|
||||
- substitution
|
||||
- replace
|
||||
- TUI
|
||||
title: "Interactive String Substitution"
|
||||
tags: [ "data", "vim", "substitution" ]
|
||||
---
|
||||
|
||||
Want to find and replace, but also confirm each instance?
|
||||
|
||||
@@ -1,9 +1,6 @@
|
||||
---
|
||||
title: ijq
|
||||
tags:
|
||||
- data
|
||||
- json
|
||||
- TUI
|
||||
title: "ijq"
|
||||
tags: [ "data", "json", "TUI" ]
|
||||
---
|
||||
|
||||
Analyse `json` easier with `ijq`.
|
||||
|
||||
@@ -1,7 +1,6 @@
|
||||
---
|
||||
title: khard
|
||||
tags:
|
||||
- data
|
||||
title: "khard"
|
||||
tags: [ "data" ]
|
||||
---
|
||||
Get the basic config:
|
||||
|
||||
|
||||
@@ -1,7 +1,6 @@
|
||||
---
|
||||
title: newsboat
|
||||
tags:
|
||||
- RSS
|
||||
title: "newsboat"
|
||||
tags: [ "RSS" ]
|
||||
---
|
||||
Create the configuration directory before you start, and add at least 1 URL.
|
||||
|
||||
@@ -13,7 +12,7 @@ mkdir ~/.config/newsboat
|
||||
echo 'https://voidlinux.org/atom.xml foss tech' >> ~/.config/newsboat/urls
|
||||
```
|
||||
|
||||
Start `newsboat` and press `r` to load your feed.
|
||||
Start `newsobat` and press `r` to load your feed.
|
||||
|
||||
To add a feed, you can press `E` to edit that `urls` file.
|
||||
|
||||
|
||||
@@ -1,8 +1,7 @@
|
||||
---
|
||||
title: Newsraft
|
||||
tags:
|
||||
- data
|
||||
- RSS
|
||||
title: "Newsraft"
|
||||
tags: [ "data", "RSS" ]
|
||||
requires: [ "Shell Scripts" ]
|
||||
---
|
||||
|
||||
# Setup
|
||||
@@ -45,24 +44,11 @@ You can get an RSS feed from any YouTube video with this script:
|
||||
```
|
||||
#!/bin/sh
|
||||
|
||||
set -e
|
||||
|
||||
db=~/rec/feeds.rec
|
||||
|
||||
rec="${2:-$db}"
|
||||
|
||||
[ ! -z "$1" ] || {
|
||||
echo "Give me a youtube URL"
|
||||
exit 1
|
||||
}
|
||||
|
||||
[ -w "$rec" ] || touch "$rec"
|
||||
|
||||
CHANNEL_ID="$(curl -s "$1" | tr ',' '\n' | grep -Po 'channelId":"\K[\w+-]+' | tail -1)"
|
||||
URL="https://www.youtube.com/feeds/videos.xml?channel_id=$CHANNEL_ID"
|
||||
Name="$(curl -s "$URL" | grep -m 1 -Po 'title\>\K[\w\s]+')"
|
||||
FEED_URL="https://www.youtube.com/feeds/videos.xml?channel_id=$CHANNEL_ID"
|
||||
CHANNEL_NAME="$(curl -s "$FEED_URL" | grep -m 1 -Po 'title\>\K[\w\s]+')"
|
||||
|
||||
recins --verbose -t Feed -f Name -v "${Name}" -f URL -v "${URL}" -f Category -v Videos -f Rating -v 3 -f Working -v yes "$rec"
|
||||
printf '%s "%s"\n' "$FEED_URL" "$CHANNEL_NAME"
|
||||
```
|
||||
|
||||
|
||||
|
||||
35
data/pass.md
35
data/pass.md
@@ -1,14 +1,10 @@
|
||||
---
|
||||
title: pass
|
||||
tags:
|
||||
- data
|
||||
- credentials
|
||||
- secrets
|
||||
requires:
|
||||
- data/gpg.md
|
||||
title: "pass"
|
||||
tags: [ "data" ]
|
||||
requires: "GPG Basics"
|
||||
---
|
||||
|
||||
Setup [gpg](data/gpg.md) keys.
|
||||
Setup [gpg](./gpg.md) keys.
|
||||
|
||||
Show your gpg secret it:
|
||||
|
||||
@@ -19,37 +15,28 @@ gpg --list-secret-keys
|
||||
Then use the id number under `sec` to make a pass repo:
|
||||
|
||||
```sh
|
||||
key="$(gpg --list-secret-keys | grep -m 1 -A1 '^sec' | tail -n 1)"
|
||||
KEY="$(gpg --list-secret-keys | grep -m 1 -A1 '^sec' | tail -n 1)"
|
||||
```
|
||||
|
||||
```sh
|
||||
pass init $key
|
||||
cat .password-store/.gpg-id
|
||||
pass init $KEY
|
||||
```
|
||||
|
||||
To add a basic password, e.g. for `${website}`:
|
||||
To add a basic password, e.g. for `$WEBSITE`:
|
||||
|
||||
```sh
|
||||
pass ${website}
|
||||
pass $WEBSITE
|
||||
```
|
||||
|
||||
To insert a multi-line password, e.g. with a login name:
|
||||
To insert a multiline password, e.g. with a login name:
|
||||
|
||||
```sh
|
||||
pass add -m ${website}
|
||||
pass add -m $WEBSITE
|
||||
```
|
||||
|
||||
Remove a password:
|
||||
|
||||
```sh
|
||||
pass rm ${website}
|
||||
pass rm $WEBSITE
|
||||
```
|
||||
|
||||
You can generate passwords with `xkcdpass`.
|
||||
|
||||
Automatically insert a password with `pass insert`:
|
||||
|
||||
|
||||
```sh
|
||||
xkcdpass | pass insert --echo ${website}
|
||||
```
|
||||
|
||||
@@ -1,54 +0,0 @@
|
||||
---
|
||||
title: pass with otp
|
||||
tags:
|
||||
- data
|
||||
- credentials
|
||||
- secrets
|
||||
- 2fa
|
||||
- otp
|
||||
requires:
|
||||
- data/pass.md
|
||||
---
|
||||
|
||||
Need a Microsoft or Google authenticator?
|
||||
No you don't.
|
||||
|
||||
These usually come in the form of QR codes.
|
||||
|
||||
|
||||
```qr code
|
||||
|
||||
|
||||
█▀▀▀▀▀█ ▀ ▀▀▀ ▀ ▄ █▀▀▀▀▀█
|
||||
█ ███ █ ▄▄▀▄▄▀▄▄▀ █ ███ █
|
||||
█ ▀▀▀ █ ██ ▀▄██▀▀ █ ▀▀▀ █
|
||||
▀▀▀▀▀▀▀ █ █▄▀ █ █ ▀▀▀▀▀▀▀
|
||||
█▄▄ █▄▀▀██ ▄▄▀▀▄██▀▀██ ▄▀
|
||||
▄██▄▀█▀█ ▀▄▀ █▀▀▀█ ▀▀▀█▄
|
||||
▄ ▄▄█ ▀▀ ▄▄▀▀█▄█ ▀▀ ▄▀▀█▀
|
||||
█ ▀ ▀▀█▀▀ ▄ ▄█▀▄▀██▀█▄
|
||||
▀▀▀ ▀ ▀ █▄▄▀▄▀▀▄█▀▀▀█▀▀
|
||||
█▀▀▀▀▀█ ▀▄ █▀█▀ █ ▀ █▄▄
|
||||
█ ███ █ ▀ ▄ ▀█▄ ████▀▀█▄█
|
||||
█ ▀▀▀ █ ▄▀ ▄ ▄▄ ██▄▄█▄█
|
||||
▀▀▀▀▀▀▀ ▀ ▀▀ ▀▀▀ ▀▀ ▀▀▀
|
||||
|
||||
|
||||
```
|
||||
|
||||
Download the code, and get the information out:
|
||||
|
||||
|
||||
```sh
|
||||
zbarimg qr.png
|
||||
otp="$(zbarimg qr.png | sed 's/QR-Code://')"
|
||||
otp_name=site.org.otp
|
||||
echo "${otp}" | pass otp add --echo "${otp_name}"
|
||||
```
|
||||
|
||||
Show the OTP:
|
||||
|
||||
|
||||
```sh
|
||||
pass otp "${otp_name}"
|
||||
```
|
||||
@@ -1,9 +1,6 @@
|
||||
---
|
||||
title: Convert a scanned pdf to text
|
||||
tags:
|
||||
- data
|
||||
- pdf
|
||||
- ocr
|
||||
title: "pdf to txt"
|
||||
tags: [ "data", "pdf", "ocr" ]
|
||||
---
|
||||
|
||||
How to translate pdfs to text (results are very poor, and will need lots of corrections).
|
||||
|
||||
25
data/pdf-to-txt.sh
Executable file
25
data/pdf-to-txt.sh
Executable file
@@ -0,0 +1,25 @@
|
||||
#!/bin/bash
|
||||
|
||||
pdftoppm -png input.pdf page
|
||||
|
||||
for x in *png; do
|
||||
tesseract -l eng "$x" - >> out.tex
|
||||
done
|
||||
|
||||
rm *png
|
||||
|
||||
sed -i -ze :a -e 's/\([a-z]\)\(-\)\n\+\([a-zA-Z]\)/\1\3/g' out.tex
|
||||
sed -i -ze :a -e 's/\([a-z]\)\n\+\([a-zA-Z]\)/\1 \2/g' out.tex
|
||||
sed -i -ze :a -e 's/\([A-Z]\){3}\+\n/\1 XYZ/g' out.tex
|
||||
sed -i -ze :a -e 's/\n\([A-Z]\{3\}\+\)\n/\\section{\1}\n/g' out.tex
|
||||
sed -i -ze :a -e 's/\([a-z]\)\. \([A-Z]\)/\1\.\n\2/g' out.tex
|
||||
|
||||
sed -i 's/“//g' out.tex
|
||||
sed -i "s/”/''/g" out.tex
|
||||
sed -i "s/’/'/g" out.tex
|
||||
sed -i "s/‘/'/g" out.tex
|
||||
sed -i "s/\.''/''\./g" out.tex
|
||||
sed -i "s/ — / -- /g" out.tex
|
||||
sed -i 's/\$/\\$/g' out.tex
|
||||
sed -i 's/%/\\%/g' out.tex
|
||||
sed -i 's/&/\\&/g' out.tex
|
||||
@@ -1,10 +1,6 @@
|
||||
---
|
||||
title: PDF Metadata Erasure
|
||||
tags:
|
||||
- metadata
|
||||
- ghost script
|
||||
- gs
|
||||
- pdf
|
||||
title: "PDF Metadata Erasure"
|
||||
tags: [ "metadata", "ghost script", "gs", ".pdf" ]
|
||||
---
|
||||
|
||||
You cannot erase pdf metadata with `exiftool` (it only *appends* your changes).
|
||||
|
||||
@@ -1,10 +1,7 @@
|
||||
---
|
||||
title: radicale and nginx
|
||||
tags:
|
||||
- data
|
||||
- calendar
|
||||
requires:
|
||||
- networking/nginx.md
|
||||
title: "radicale and nginx"
|
||||
tags: [ "data", "calendar" ]
|
||||
requires: [ "nginx", "certbot" ]
|
||||
---
|
||||
|
||||
Check before you start:
|
||||
@@ -44,11 +41,10 @@ You might get it in the `apache` package or similar.
|
||||
`htpasswd` allows you to generate passwords for users, and place them in `/etc/radicale/users`.
|
||||
|
||||
```sh
|
||||
pass="$(xkcdpass)"
|
||||
username=alice
|
||||
htpasswd -nb ${username} "${pass}" | sudo tee -a /etc/radicale/users
|
||||
echo "Your username is ${username}"
|
||||
echo "Your password is ${pass}"
|
||||
PASS="$(xkcdpass)"
|
||||
htpasswd -nb $USER "$PASS" | sudo tee -a /etc/radicale/users
|
||||
echo "Your username is $USER"
|
||||
echo "Your password is $PASS"
|
||||
```
|
||||
Right now, you can't sign into the server except through the localhost, which is pointless.
|
||||
So now we add a subdomain to `nginx`.
|
||||
@@ -98,8 +94,8 @@ sudo ln -s /etc/nginx/sites-available/radicale /etc/nginx/sites-enables/
|
||||
Finally, replace the example `DOMAIN` with your actual domain name.
|
||||
|
||||
```sh
|
||||
domain=whatever.com
|
||||
sudo sed -i "s/DOMAIN/${domain}/g" /etc/nginx/sites-available/radicale
|
||||
DOMAIN=whatever.com
|
||||
sudo sed -i "s/DOMAIN/$DOMAIN/g" /etc/nginx/sites-available/radicale
|
||||
```
|
||||
|
||||
(optional: replace that `cal.` prefix with anything else)
|
||||
@@ -112,7 +108,7 @@ sudo nginx -t
|
||||
You will almost certainly need a new SSL certificate for the site:
|
||||
|
||||
```sh
|
||||
sudo certbod -d cal.${domain}
|
||||
sudo certbod -d cal.$DOMAIN
|
||||
```
|
||||
|
||||
Start or restart both services:
|
||||
|
||||
@@ -1,8 +1,6 @@
|
||||
---
|
||||
title: Recfiles
|
||||
tags:
|
||||
- data
|
||||
- database
|
||||
title: "Recfiles"
|
||||
tags: [ "data", "database" ]
|
||||
---
|
||||
|
||||
Create:
|
||||
@@ -45,8 +43,8 @@ recset -f "$new_field" --delete $database
|
||||
```
|
||||
|
||||
- [Extended example](recfiles/extended.md)
|
||||
- [Playing with board games data](recfiles/board_games.md)
|
||||
- [Playing with IP addresses](recfiles/ip_asn.md)
|
||||
- [Playing with board games data](recfiles/Board_Games.md)
|
||||
- [Playing with IP addresses](recfiles/IP_ASN.md)
|
||||
- [Manage LaTeX Bibliographies](recfiles/bibliography.md)
|
||||
- [Fixes](recfiles/recfixes.md)
|
||||
|
||||
|
||||
@@ -1,14 +1,7 @@
|
||||
---
|
||||
title: Recfile Bibliography for TeX
|
||||
tags:
|
||||
- data
|
||||
- database
|
||||
- recfiles
|
||||
- tex
|
||||
requires:
|
||||
- data/recfiles.md
|
||||
- writing/tex.md
|
||||
- system/makefiles.md
|
||||
title: "Recfile Bibliography for TeX"
|
||||
tags: [ "data", "database", "recfiles", "tex" ]
|
||||
requires: [ "Recfiles", "TeX", "Makefile" ]
|
||||
---
|
||||
|
||||
Store your bibliography in a `recfile` database, then extract any part with `make`.
|
||||
|
||||
@@ -1,11 +1,7 @@
|
||||
---
|
||||
title: Board Games with Recfiles
|
||||
tags:
|
||||
- data
|
||||
- recfiles
|
||||
- games
|
||||
requires:
|
||||
- data/recfiles.md
|
||||
title: "Board Games with Recfiles"
|
||||
tags: [ "data", "recfiles", "games" ]
|
||||
requires: "Recfiles"
|
||||
---
|
||||
|
||||
You can play with a board games database from boardgamegeek.com.
|
||||
|
||||
@@ -1,11 +1,6 @@
|
||||
---
|
||||
title: Recfiles Extended Example
|
||||
tags:
|
||||
- data
|
||||
- database
|
||||
- recfiles
|
||||
requires:
|
||||
- data/recfiles.md
|
||||
title: "Recfiles Extended Example"
|
||||
tags: [ "data", "database", "recfiles" ]
|
||||
---
|
||||
|
||||
## Create
|
||||
|
||||
@@ -1,11 +1,7 @@
|
||||
---
|
||||
title: IP Addresses with Recfiles
|
||||
tags:
|
||||
- data
|
||||
- recfiles
|
||||
- games
|
||||
requires:
|
||||
- data/recfiles.md
|
||||
title: "IP Addresses with Recfiles"
|
||||
tags: [ "data", "recfiles", "games" ]
|
||||
requires: "Recfiles"
|
||||
---
|
||||
|
||||
## Download the Database
|
||||
|
||||
@@ -1,70 +0,0 @@
|
||||
---
|
||||
title: nginx logs with recfiles
|
||||
tags:
|
||||
- data
|
||||
- recfiles
|
||||
- logs
|
||||
requires:
|
||||
- data/recfiles.md
|
||||
- networking/nginx.md
|
||||
---
|
||||
|
||||
The standard `nginx` log format has such a lack of consistency or meaning that you might squint your face into a whirlpool making sense of them:
|
||||
|
||||
|
||||
```nonsense
|
||||
18.97.14.85 - - [16/Nov/2025:00:52:12 +0100] "GET /posts/learning_without_experts/content.html HTTP/1.1" 200 1704 "-" "CCBot/2.0 (https://commoncrawl.org/faq/)"
|
||||
57.141.0.25 - - [16/Nov/2025:00:52:18 +0100] "GET /posts/hope_you_win/ HTTP/1.1" 200 61997 "-" "meta-externalagent/1.1 (+https://developers.facebook.com/docs/sharing/webmasters/crawler)"
|
||||
201.17.157.249 - - [16/Nov/2025:00:52:19 +0100] "GET https://ttrpgs.com/post/wp/ HTTP/1.1" 200 45202 "-" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/125.0.0.0 Safari/537.36"
|
||||
47.246.164.151 - - [16/Nov/2025:00:52:22 +0100] "GET https://ttrpgs.com/css/styles.dc38388a8f0b890e788bd3a99b7495d14e7d5ac4359ed3b49abeb778497863b284ad4cc7e496ef58c84139295f9bafed82f5a41345eda86bd2d429cccb7c2596.css HTTP/1.1" 200 27109 "https://ttrpgs.com/post/wp/" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/125.0.0.0 Safari/537.36"
|
||||
47.246.164.154 - - [16/Nov/2025:00:52:22 +0100] "GET https://ttrpgs.com/fonts/Metropolis-MediumItalic.woff2 HTTP/1.1" 200 28100 "https://ttrpgs.com/css/styles.dc38388a8f0b890e788bd3a99b7495d14e7d5ac4359ed3b49abeb778497863b284ad4cc7e496ef58c84139295f9bafed82f5a41345eda86bd2d429cccb7c2596.css" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/125.0.0.0 Safari/537.36"
|
||||
47.246.164.135 - - [16/Nov/2025:00:52:22 +0100] "GET https://ttrpgs.com/fonts/Metropolis-Regular.woff2 HTTP/1.1" 200 24152 "https://ttrpgs.com/css/styles.dc38388a8f0b890e788bd3a99b7495d14e7d5ac4359ed3b49abeb778497863b284ad4cc7e496ef58c84139295f9bafed82f5a41345eda86bd2d429cccb7c2596.css" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/125.0.0.0 Safari/537.36"
|
||||
```
|
||||
|
||||
Someone created this logging format on purpose, to make sure nobody could parse it with a hundred `column`, `cut`, or `awk` pipes.
|
||||
|
||||
The problem lies in `/etc/nginx/nginx.conf`:
|
||||
|
||||
|
||||
```conf
|
||||
log_format main '$remote_addr - $remote_user [$time_local] "$request" '
|
||||
'$status $body_bytes_sent "$http_referer" '
|
||||
'"$http_user_agent" "$http_x_forwarded_for"';
|
||||
```
|
||||
|
||||
Despite a request of three strings, this format returns one string.
|
||||
|
||||
It can output to recfile format like this:
|
||||
|
||||
|
||||
```conf
|
||||
log_format main '\nIP: $remote_addr\n'
|
||||
'User: $remote_user\n'
|
||||
'Date: $time_local\n'
|
||||
'Request: $request\n'
|
||||
'Status: $status\n'
|
||||
'Bytes: $body_bytes_sent\n'
|
||||
'Referrer: $http_referer\n'
|
||||
'Agent: $http_user_agent\n'
|
||||
'XForward: $http_x_forwarded_for\n';
|
||||
|
||||
access_log /var/log/nginx/access.rec main;
|
||||
```
|
||||
|
||||
Note the newline (`\n`) symbol, required to start a new entry on a new line.
|
||||
|
||||
1. `cp /etc/nginx.conf /etc/nginx.conf.bak`
|
||||
1. Change `/etc/nginx.conf` to match the format above.
|
||||
1. Check the file works with `nginx -t`.
|
||||
1. Restart the `nginx` service.
|
||||
1. Access that web page to make sure that at least one log exists.
|
||||
1. Check the file with `recfix /var/log/nginx/access.rec`.
|
||||
|
||||
Once it works, you can add the usual recfile headers:
|
||||
|
||||
|
||||
```sh
|
||||
sed -i '1 i \ ' /var/log/nginx/access.rec
|
||||
sed -i '1 i %rec: Weblog' /var/log/nginx/access.rec
|
||||
sed -i '2 i %doc: nginx access logs' /var/log/nginx/access.rec
|
||||
```
|
||||
@@ -1,10 +1,7 @@
|
||||
---
|
||||
title: Recfixes
|
||||
tags:
|
||||
- data
|
||||
- recfiles
|
||||
requires:
|
||||
- data/recfiles.md
|
||||
title: "Recfixes"
|
||||
tags: [ "data", "recfiles" ]
|
||||
requires: "Recfiles"
|
||||
---
|
||||
|
||||
Sometimes `recsel` chokes on a large query, and you need to break the query into chunks with a pipe.
|
||||
|
||||
@@ -1,14 +1,11 @@
|
||||
---
|
||||
title: sc-im
|
||||
tags:
|
||||
- TUI
|
||||
- data
|
||||
- spreadsheet
|
||||
- csv
|
||||
requires:
|
||||
- writing/vim.md
|
||||
title: "sc-im"
|
||||
tags: [ "TUI", "data", "spreadsheet", ".csv" ]
|
||||
requires: [ "vim basics" ]
|
||||
---
|
||||
|
||||
- [Sample file](sc-im/sample.sc)
|
||||
|
||||
# Basic Commands
|
||||
|
||||
## See Cells
|
||||
|
||||
@@ -1,8 +1,6 @@
|
||||
---
|
||||
title: Convert Spreadsheets
|
||||
tags:
|
||||
- data
|
||||
- sc-im
|
||||
title: "Convert Spreadsheets"
|
||||
tags: [ "data", "sc-im" ]
|
||||
---
|
||||
|
||||
Convert between spreadsheet formats with `sc-im`.
|
||||
|
||||
38
data/sc-im/sample.sc
Normal file
38
data/sc-im/sample.sc
Normal file
@@ -0,0 +1,38 @@
|
||||
# This data file was generated by the Spreadsheet Calculator Improvised (sc-im)
|
||||
# You almost certainly shouldn't edit it.
|
||||
|
||||
newsheet "Sheet1"
|
||||
movetosheet "Sheet1"
|
||||
offscr_sc_cols 0
|
||||
offscr_sc_rows 0
|
||||
nb_frozen_rows 1
|
||||
nb_frozen_cols 0
|
||||
nb_frozen_screenrows 2
|
||||
nb_frozen_screencols 0
|
||||
format A 14 1 0
|
||||
format B 18 2 0
|
||||
format 0 2
|
||||
freeze 0
|
||||
label A0 = "Food by Weight"
|
||||
leftstring B0 = "No. Meals"
|
||||
leftstring A1 = "Ajvar"
|
||||
let A1 = 5
|
||||
let B1 = A1*$A$10
|
||||
leftstring A2 = "Apples"
|
||||
let A2 = 3
|
||||
let B2 = A2*$A$10
|
||||
leftstring A3 = "Rocket"
|
||||
let A3 = 0.2
|
||||
let B3 = A3*$A$10
|
||||
leftstring A4 = "Beli Cheese"
|
||||
let A4 = 1
|
||||
let B4 = A4*$A$10
|
||||
leftstring A6 = "Total"
|
||||
let A6 = @sum(A1:A4)
|
||||
leftstring B6 = "Total"
|
||||
let B6 = @sum(B1:B4)
|
||||
leftstring A7 = "Average"
|
||||
let A7 = @avg(A1:A4)
|
||||
leftstring A10 = "Weight of Meal"
|
||||
let A10 = 0.3
|
||||
goto A0
|
||||
@@ -1,12 +1,7 @@
|
||||
---
|
||||
title: Search System
|
||||
tags:
|
||||
- data
|
||||
- search
|
||||
- locate
|
||||
- plocate
|
||||
requires:
|
||||
- system/cron.md
|
||||
title: "Search System"
|
||||
tags: [ "data", "search", "locate", "plocate" ]
|
||||
requires: "cron"
|
||||
---
|
||||
|
||||
You can search every file on the computer instantly by installing `plocate`.
|
||||
@@ -26,7 +21,7 @@ Once you have the database, you can find nearly any file instantly.
|
||||
- Search for jpg images with 'dog' or 'Dog' in the name: `locate -i dog jpg`
|
||||
- Search for videos: `plocate --regex '.mp4$|.mkv$|.wmv$|.webm$|.mov$|.avi$'`
|
||||
|
||||
For best results, run `updatedb` regularly, perhaps in [crontab](system/cron.md).
|
||||
For best results, run `updatedb` regularly, perhaps in [crontab](../system/cron.md).
|
||||
|
||||
## Search More Places
|
||||
|
||||
|
||||
@@ -1,8 +1,6 @@
|
||||
---
|
||||
title: Search Video Audio
|
||||
tags:
|
||||
- data
|
||||
- video
|
||||
title: "Search Video Audio"
|
||||
tags: [ "data", "video" ]
|
||||
---
|
||||
|
||||
Check subtitles available:
|
||||
|
||||
@@ -1,9 +1,6 @@
|
||||
---
|
||||
title: Sharing Secrets
|
||||
tags:
|
||||
- data
|
||||
- death
|
||||
- secrets
|
||||
title: "Sharing Secrets"
|
||||
tags: [ "data", "death", "secrets", "ssss" ]
|
||||
---
|
||||
|
||||
You can share parts of a secret with multiple people, so only some of them need to agree to see the secret.
|
||||
|
||||
@@ -1,14 +0,0 @@
|
||||
---
|
||||
title: Soft-Serve
|
||||
tags:
|
||||
- data
|
||||
- git server
|
||||
- lfs
|
||||
- TUI
|
||||
requires:
|
||||
- data/git.md
|
||||
- networking/nginx.md
|
||||
---
|
||||
|
||||
- [Soft-Serve with https](soft-serve/soft_https.md)
|
||||
- [Maintenance](soft-serve/soft_maintenance.md)
|
||||
@@ -1,12 +1,7 @@
|
||||
---
|
||||
title: Soft Serve Maintenance
|
||||
tags:
|
||||
- data
|
||||
- git server
|
||||
- maintenance
|
||||
requires:
|
||||
- data/git.md
|
||||
- networking/nginx.md
|
||||
title: "Soft Serve Maintenance"
|
||||
tags: [ "data", "git server", "maintenance" ]
|
||||
requires: [ "git", "nginx" ]
|
||||
---
|
||||
|
||||
Over time git repositories become bloated with old data, but never get cleaned.
|
||||
@@ -1,12 +1,7 @@
|
||||
---
|
||||
title: Soft Serve through https
|
||||
tags:
|
||||
- data
|
||||
- git server
|
||||
- lfs
|
||||
requires:
|
||||
- data/git.md
|
||||
- networking/nginx.md
|
||||
title: "Soft Serve through https"
|
||||
tags: [ "data", "git server", "lfs" ]
|
||||
requires: [ "git", "nginx" ]
|
||||
---
|
||||
|
||||
## `http` Setup
|
||||
@@ -41,7 +36,7 @@ git clone http://localhost:23232/${some_repo}.git
|
||||
|
||||
### `https` Setup
|
||||
|
||||
Put this file at `/etc/nginx/sites-enabled/$DOMAIN.tld`, then set up standard certificates with [nginx](networking/nginx.md).
|
||||
Put this file at `/etc/nginx/sites-enabled/$DOMAIN.tld`, then set up standard certificates with [nginx](../networking/website/nginx.md).
|
||||
|
||||
(replace `${DOMAIN_NAME}` with your domain's name).
|
||||
|
||||
|
||||
8
data/soft.md
Normal file
8
data/soft.md
Normal file
@@ -0,0 +1,8 @@
|
||||
---
|
||||
title: "Soft-Serve"
|
||||
tags: [ "data", "git server", "lfs", "TUI" ]
|
||||
requires: [ "git", "nginx" ]
|
||||
---
|
||||
|
||||
- [Soft-Serve with https](soft-serve/soft_https.md)
|
||||
- [Maintenance](soft-serve/maintenance.md)
|
||||
@@ -1,7 +1,6 @@
|
||||
---
|
||||
title: sqlite
|
||||
tags:
|
||||
- data
|
||||
title: "sqlite"
|
||||
tags: [ "data" ]
|
||||
---
|
||||
|
||||
Work with a database:
|
||||
|
||||
34
data/task/contexts.md
Normal file
34
data/task/contexts.md
Normal file
@@ -0,0 +1,34 @@
|
||||
---
|
||||
title: "Taskwarrior Contexts"
|
||||
tags: [ "data", "task" ]
|
||||
requires: [ "Taskwarrior" ]
|
||||
---
|
||||
|
||||
# Contexts
|
||||
|
||||
Set three contexts by their tags:
|
||||
|
||||
```sh
|
||||
task context define work +sa or +hr
|
||||
```
|
||||
|
||||
```sh
|
||||
task context define study +ed or +void or +rat
|
||||
```
|
||||
|
||||
```sh
|
||||
task context define home -sa -hr -ed -void -rat
|
||||
```
|
||||
|
||||
Change to the first context.
|
||||
|
||||
```sh
|
||||
task context work
|
||||
```
|
||||
|
||||
Then stop.
|
||||
|
||||
```sh
|
||||
task context none
|
||||
```
|
||||
|
||||
115
data/task/task.md
Normal file
115
data/task/task.md
Normal file
@@ -0,0 +1,115 @@
|
||||
---
|
||||
title: "Taskwarrior"
|
||||
tags: [ "data", "organization" ]
|
||||
---
|
||||
|
||||
Set up the configuration file:
|
||||
|
||||
```sh
|
||||
task
|
||||
```
|
||||
|
||||
Taskwarrior published a new feature to synchronize tasks others, but the feature was not ready.
|
||||
The server's default installation instructions assume that users pay for hosting services.
|
||||
All listed providers run proprietary software and actively support genocide.
|
||||
|
||||
|
||||
To ignore the synchronization, tell the configuration file to use a local synchronization file.
|
||||
|
||||
```sh
|
||||
task config sync.local.server_dir
|
||||
task config data.location ~/.local/state/
|
||||
```
|
||||
|
||||
Add a task:
|
||||
|
||||
```sh
|
||||
task add update linux
|
||||
```
|
||||
|
||||
See which task is next:
|
||||
|
||||
```sh
|
||||
task next
|
||||
```
|
||||
|
||||
Note the id number.
|
||||
|
||||
Mark a task as started:
|
||||
|
||||
```sh
|
||||
task start 1
|
||||
```
|
||||
|
||||
Once finished:
|
||||
|
||||
```sh
|
||||
task 1 done
|
||||
```
|
||||
|
||||
# Projects
|
||||
|
||||
Add a project:
|
||||
|
||||
```sh
|
||||
task add project:house buy potted plant
|
||||
task add proj:house.repair buy screwdriver
|
||||
task add proj:house.repair buy shelf brackets
|
||||
task add pro:house.paint buy white paint
|
||||
|
||||
for t in "buy red paint" "buy black paint" "buy brushes" ; do
|
||||
task add pro:house.paint $t
|
||||
done
|
||||
```
|
||||
|
||||
## Summary
|
||||
|
||||
```sh
|
||||
task pro:house sum
|
||||
task burndown.daily pro:house
|
||||
```
|
||||
|
||||
The summaries will show how fast a project is being completed, and when you can expect it to finish at the present rate.
|
||||
|
||||
# Tags
|
||||
|
||||
|
||||
```sh
|
||||
task add +buy toothbrush
|
||||
task +buy
|
||||
```
|
||||
|
||||
# Review
|
||||
|
||||
View list of tasks completed in the last week:
|
||||
|
||||
```sh
|
||||
task end.after:today-1wk completed
|
||||
```
|
||||
|
||||
# User Defined Attributes
|
||||
|
||||
Define a new attribute for tasks called 'size'.
|
||||
The 'user defined attribute' (UDA) needs a `type` and `label`.
|
||||
|
||||
```sh
|
||||
task config uda.size.type string
|
||||
task config uda.size.label Size
|
||||
```
|
||||
You can also ensure task tasks can only be `large`, `medium`, or `small`, then set a default.
|
||||
|
||||
```sh
|
||||
task config uda.size.values large,medium,small
|
||||
uda.size.default=medium
|
||||
```
|
||||
|
||||
# Tricks
|
||||
|
||||
This command shows tasks I'm most interested in:
|
||||
|
||||
```sh
|
||||
task next +ACTIVE or +OVERDUE or due:today or scheduled:today or pri:H
|
||||
```
|
||||
|
||||
The command is long, so `alias` is your friend.
|
||||
|
||||
20
data/task/taskwarrior_configuration.md
Normal file
20
data/task/taskwarrior_configuration.md
Normal file
@@ -0,0 +1,20 @@
|
||||
---
|
||||
title: "Taskwarrior Configuration"
|
||||
tags: [ "data", "task" ]
|
||||
requires: [ "Taskwarrior" ]
|
||||
---
|
||||
|
||||
Show your current config:
|
||||
|
||||
|
||||
```sh
|
||||
task show
|
||||
```
|
||||
|
||||
Use machine-readable output to make a config file with all configuration keys shown, then make it your configuration file.
|
||||
|
||||
```sh
|
||||
task _show > ${file}
|
||||
mv ${file} ~/.config/task/taskrc
|
||||
```
|
||||
|
||||
172
data/task/timew.md
Normal file
172
data/task/timew.md
Normal file
@@ -0,0 +1,172 @@
|
||||
---
|
||||
title: "timewarrior"
|
||||
tags: [ "data", "tracking", "time", "timew" ]
|
||||
---
|
||||
# Summaries
|
||||
|
||||
Try:
|
||||
|
||||
```sh
|
||||
timew summary :yesterday
|
||||
```
|
||||
|
||||
You can also use :week, :lastweek, :month, :quarter, :year, or a range such as:
|
||||
|
||||
```sh
|
||||
timew summary today to tomorrow
|
||||
timew today - tomorrow
|
||||
2018-10-15T06:00 - 2018-10-17T06:00
|
||||
```
|
||||
|
||||
Each of these can gain with the :ids tag.
|
||||
|
||||
# Basics
|
||||
|
||||
```sh
|
||||
timew start
|
||||
timew stop
|
||||
timew continue
|
||||
timew summary
|
||||
timew tags
|
||||
```
|
||||
|
||||
And add ids with:
|
||||
|
||||
```sh
|
||||
timew summary :ids
|
||||
timew track 10am - 1pm timewarrior
|
||||
timew track 1pm for 2h walk
|
||||
```
|
||||
|
||||
# Adjusting Timewarrior
|
||||
|
||||
First get ids.
|
||||
|
||||
```sh
|
||||
timew summary :ids
|
||||
```
|
||||
|
||||
Then if we're looking at task @2:
|
||||
|
||||
```sh
|
||||
timew move @2 12:00
|
||||
timew lengthen @2 3mins
|
||||
```
|
||||
|
||||
```sh
|
||||
time shorten @2 40mins
|
||||
```
|
||||
|
||||
# Forgetting
|
||||
|
||||
```sh
|
||||
timew start 1h ago @4
|
||||
```
|
||||
|
||||
Or if your action actually had a break:
|
||||
|
||||
```sh
|
||||
timew split @8
|
||||
```
|
||||
|
||||
Or maybe not?
|
||||
|
||||
```sh
|
||||
timew join @4 @8
|
||||
timew @8 delete
|
||||
```
|
||||
|
||||
Start at previous time
|
||||
|
||||
```sh
|
||||
timew start 3pm 'Read chapter 12'
|
||||
timew start 90mins ago 'Read chapter 12'
|
||||
```
|
||||
|
||||
Cancel currently tracked time.
|
||||
|
||||
```sh
|
||||
timew cancel
|
||||
```
|
||||
|
||||
# Backdated tracking
|
||||
|
||||
> timew untag @3
|
||||
|
||||
|
||||
# Hints
|
||||
|
||||
* :quit - for automation
|
||||
|
||||
* :yes
|
||||
|
||||
* :color
|
||||
|
||||
* :fill - expand the time to fill out available time
|
||||
|
||||
* :adjust - automatically correct overlaps
|
||||
|
||||
* :ids - show id numbers
|
||||
|
||||
|
||||
# Times
|
||||
|
||||
* :yesterday
|
||||
|
||||
* :day
|
||||
|
||||
* :week
|
||||
|
||||
* :month
|
||||
|
||||
* :quarter
|
||||
|
||||
* :lastweek
|
||||
|
||||
* :lastmonth
|
||||
|
||||
* :lastquarter
|
||||
|
||||
* :lastyear
|
||||
|
||||
|
||||
|
||||
# Mistakes
|
||||
|
||||
task end.after:2015-05-01 and end.before:2015-05-31 completed
|
||||
|
||||
task end.after:today-1wk completed
|
||||
|
||||
# Errors with Python3
|
||||
|
||||
Replace
|
||||
|
||||
> os.system('timew start ' + combined + ' :yes')
|
||||
|
||||
with:
|
||||
|
||||
> os.system('timew start ' + combined.decode() + ' :yes')
|
||||
|
||||
and
|
||||
|
||||
> os.system('timew stop ' + combined + ' :yes')
|
||||
|
||||
with:
|
||||
|
||||
> os.system('timew stop ' + combined.decode() + ' :yes')
|
||||
|
||||
# Fixing Errors
|
||||
|
||||
```sh
|
||||
curl -O https://taskwarrior.org/download/timew-dbcorrection.py
|
||||
```
|
||||
|
||||
```sh
|
||||
python timew-dbcorrections.py
|
||||
```
|
||||
|
||||
# Setup
|
||||
|
||||
With taskwarrior installed as well, `locate on-modify-time`, then add it to ~/.task/hooks and make it executable.
|
||||
This will track the time of any tasks used with [taskwarrior](task.md).
|
||||
|
||||
@@ -1,14 +1,11 @@
|
||||
---
|
||||
title: View Torrents
|
||||
tags:
|
||||
- data
|
||||
- transmission
|
||||
- torrenting
|
||||
title: "View Torrents"
|
||||
tags: [ "data", "transmission", "torrenting" ]
|
||||
---
|
||||
|
||||
|
||||
```sh
|
||||
transmission-show ${file}.torrent | less
|
||||
transmission-show $file.torrent | less
|
||||
```
|
||||
|
||||
`TRACKERS` shows where transmission will ask who has the torrent, but will probably be out of date.
|
||||
|
||||
@@ -1,7 +1,6 @@
|
||||
---
|
||||
title: w3m
|
||||
tags:
|
||||
- browser
|
||||
title: "w3m"
|
||||
tags: [ "browsers" ]
|
||||
---
|
||||
Open a search tab:
|
||||
|
||||
|
||||
@@ -1,9 +1,6 @@
|
||||
---
|
||||
title: ssh to phone
|
||||
tags:
|
||||
- networking
|
||||
- ssh
|
||||
- android
|
||||
title: "ssh to phone"
|
||||
tags: [ "networking", "ssh", "android" ]
|
||||
---
|
||||
|
||||
1. Install fdroid on phone.
|
||||
|
||||
@@ -1,9 +1,6 @@
|
||||
---
|
||||
title: Arch on a Raspberry Pi 4
|
||||
tags:
|
||||
- distros
|
||||
- raspberry pi
|
||||
- rpi
|
||||
title: "Arch on a Raspberry Pi 4"
|
||||
tags: [ "distros", "raspberry pi", "rpi" ]
|
||||
---
|
||||
|
||||
The [Official Instructions](https://archlinuxarm.org/platforms/armv8/broadcom/raspberry-pi-4) for a Raspberry pi 4 do not allow for working sound from the headphone jack, unless you use the aarch64 Installation.
|
||||
|
||||
@@ -1,8 +1,6 @@
|
||||
---
|
||||
title: autologin
|
||||
tags:
|
||||
- distros
|
||||
- arch
|
||||
title: "autologin"
|
||||
tags: [ "distros", "arch" ]
|
||||
---
|
||||
|
||||
# Automatic Login
|
||||
|
||||
@@ -1,9 +1,7 @@
|
||||
---
|
||||
title: Install Arch
|
||||
tags:
|
||||
- arch
|
||||
requires:
|
||||
- system/partitions.md
|
||||
title: "Install Arch"
|
||||
tags: [ "arch" ]
|
||||
requires: [ "partitions", "time" ]
|
||||
---
|
||||
Keyboard layout changed.
|
||||
|
||||
@@ -131,7 +129,7 @@ vi /etc/locale.gen
|
||||
locale-gen
|
||||
```
|
||||
|
||||
Make your keyboard changes permanent with:
|
||||
Make your keyboard changes permenent with:
|
||||
|
||||
```sh
|
||||
vi /etc/vconsole.conf
|
||||
@@ -1,7 +1,6 @@
|
||||
---
|
||||
title: fonts
|
||||
tags:
|
||||
- distros
|
||||
title: "fonts"
|
||||
tags: [ "distros" ]
|
||||
---
|
||||
# Basics
|
||||
|
||||
|
||||
@@ -1,10 +1,6 @@
|
||||
---
|
||||
title: Arch Linux GPU Setup
|
||||
tags:
|
||||
- arch
|
||||
- GPU
|
||||
requires:
|
||||
- distros/arch/install_yay.md
|
||||
title: "Ach Linux GPU Setup"
|
||||
tags: [ "arch", "GPU" ]
|
||||
---
|
||||
# Step 1: Multilib
|
||||
|
||||
|
||||
@@ -1,31 +1,27 @@
|
||||
---
|
||||
title: Install yay
|
||||
tags:
|
||||
- distros
|
||||
- arch
|
||||
requires:
|
||||
- distros/arch/basic_install.md
|
||||
title: "Install yay"
|
||||
tags: [ "distros", "arch" ]
|
||||
requirements: [ "pacman" ]
|
||||
---
|
||||
|
||||
```sh
|
||||
pacman --sync --noconfirm --needed base-devel gcc git
|
||||
git clone https://aur.archlinux.org/yay.git
|
||||
cd yay
|
||||
makepkg -si
|
||||
git clone https://aur.archlinux.org/yay.git /tmp/yay
|
||||
makepkg -C !$ -si
|
||||
```
|
||||
|
||||
The flags are mostly the same as in `pacman`.
|
||||
But running `yay` without flags will do the update like `yay -Syu` and with package name it will search packages in the AUR and `pacman` repos, and let you choose which to install.
|
||||
|
||||
```sh
|
||||
yay ${search_term}
|
||||
yay <search_term>
|
||||
```
|
||||
|
||||
Building the package can usually take some time, and after the build it will ask for the `sudo` password.
|
||||
If you leave, the installation will fail.
|
||||
To avoid this, you can use the flag `--sudoloop` and enter the `sudo` password initially and it will loop it until the installation is finished.
|
||||
To avoid this, you can use the flag `--sudoloop` and enter the sudo password initially and it will loop it until the installation is finished.
|
||||
|
||||
```sh
|
||||
yay -S --noconfirm --sudoloop ${package_name}
|
||||
yay -S --noconfirm --sudoloop <package_name>
|
||||
```
|
||||
|
||||
|
||||
@@ -1,10 +1,7 @@
|
||||
---
|
||||
title: Arch Maintenance
|
||||
tags:
|
||||
- arch
|
||||
requires:
|
||||
- pacman
|
||||
- vim
|
||||
title: "Arch Maintenance"
|
||||
tags: [ "arch" ]
|
||||
requirements: [ "pacman" ]
|
||||
---
|
||||
|
||||
# Package Cache
|
||||
|
||||
@@ -1,9 +1,7 @@
|
||||
---
|
||||
title: pacman
|
||||
tags:
|
||||
- distros
|
||||
requires:
|
||||
- distros/arch/basic_install.md
|
||||
title: "pacman"
|
||||
tags: [ "distros" ]
|
||||
requirements: [ "Install Arch" ]
|
||||
---
|
||||
|
||||
Packages are kept in /var/cache/pacman/pkg.
|
||||
|
||||
@@ -1,9 +1,7 @@
|
||||
---
|
||||
title: pacman - Extras
|
||||
tags:
|
||||
- distros
|
||||
requires:
|
||||
- distros/arch/pacman.md
|
||||
title: "pacman - Extras"
|
||||
tags: [ "distros" ]
|
||||
requirements: [ "pacman" ]
|
||||
---
|
||||
|
||||
## Unattended Actions
|
||||
@@ -25,7 +23,7 @@ You can tell `pacman` that this is a dependency for another package:
|
||||
|
||||
|
||||
```sh
|
||||
pacman -S --noconfirm --asdeps ${weird_music_player}
|
||||
pacman -S --noconfirm --asdeps <weird music player>
|
||||
```
|
||||
|
||||
When you [remove orphaned packages](pacman.md), the package will be automatically uninstalled.
|
||||
|
||||
@@ -1,15 +1,12 @@
|
||||
---
|
||||
title: Arch maintenance with yay
|
||||
tags:
|
||||
- arch
|
||||
- maintenance
|
||||
requires:
|
||||
- distros/arch/maintenance.md
|
||||
title: "Arch Maintenance with yay"
|
||||
tags: [ "arch" ]
|
||||
requirements: [ "Arch Maintenance" ]
|
||||
---
|
||||
|
||||
# Package Cache
|
||||
|
||||
Just like `[pacman](distros/arch/pacman.md)` with a couple of extras.
|
||||
Just like `pacman`
|
||||
|
||||
```sh
|
||||
ls ~/.cache/yay/ | wc -l
|
||||
|
||||
@@ -1,13 +1,15 @@
|
||||
---
|
||||
title: apt troubleshooting
|
||||
tags:
|
||||
- debian
|
||||
title: "apt"
|
||||
tags: [ "distros" ]
|
||||
---
|
||||
## apt
|
||||
|
||||
### Configurations?
|
||||
|
||||
Messed up a package's configuration files?
|
||||
|
||||
```sh
|
||||
sudo apt-get purge ${package}
|
||||
sudo apt-get purge [thing]
|
||||
```
|
||||
|
||||
```sh
|
||||
@@ -17,16 +19,16 @@ sudo apt autoremove
|
||||
Check if you still have related things:
|
||||
|
||||
```sh
|
||||
apt search ${package}
|
||||
apt search [thing]
|
||||
```
|
||||
|
||||
```sh
|
||||
sudo apt-get install ${package}
|
||||
sudo apt-get install [ thing ]
|
||||
```
|
||||
|
||||
Still have problems?
|
||||
|
||||
```sh
|
||||
sudo dpgk --force-confmiss -i /var/cache/apt/archives/${package}
|
||||
sudo dpgk --force-confmiss -i /var/cache/apt/archives/[thing]
|
||||
```
|
||||
|
||||
|
||||
@@ -1,9 +1,7 @@
|
||||
---
|
||||
title: Aeroplane Mode in Void
|
||||
tags:
|
||||
- void
|
||||
title: "Aeroplane Mode in Void"
|
||||
tags: [ "void" ]
|
||||
---
|
||||
|
||||
Put your device in 'aeroplane' mode (e.g. where no trace of signal leaves it) by turning off Wi-Fi and blue-tooth.
|
||||
|
||||
```sh
|
||||
|
||||
@@ -1,54 +1,34 @@
|
||||
---
|
||||
title: Void Autologin
|
||||
tags:
|
||||
- void
|
||||
- autologin
|
||||
title: "Void Autologin"
|
||||
tags: [ "void" ]
|
||||
---
|
||||
|
||||
The virtual terminals are run as services.
|
||||
Make a new service by making symbolic links to the generic one.
|
||||
Make the autologin service:
|
||||
|
||||
```sh
|
||||
login=agetty-autologin
|
||||
sudo cp -rs /etc/sv/agetty-generic/ /etc/sv/${login}/
|
||||
|
||||
cp -R /etc/sv/agetty-tty1 /etc/sv/agetty-autologin-tty1
|
||||
```
|
||||
|
||||
Copy the configuration file for the `agetty-tty1` service, and add the `--autologin` argument.
|
||||
|
||||
```sh
|
||||
sed "s/--noclear/--autologin ${USER} &/" /etc/sv/agetty-tty1/conf | sudo tee /etc/sv/${login}/conf
|
||||
|
||||
```
|
||||
|
||||
It should look like this:
|
||||
|
||||
|
||||
```
|
||||
if [ -x /sbin/agetty -o -x /bin/agetty ]; then
|
||||
# util-linux specific settings
|
||||
if [ "${tty}" = "tty1" ]; then
|
||||
GETTY_ARGS="--autologin ${your_username} --noclear"
|
||||
GETTY_ARGS="--noclear"
|
||||
fi
|
||||
fi
|
||||
|
||||
GETTY_ARGS="--autologin [ your username ] --noclear"
|
||||
BAUD_RATE=38400
|
||||
TERM_NAME=linux
|
||||
|
||||
```
|
||||
|
||||
If you see the actual variable `${USER}` then you probably used the wrong quotes.
|
||||
|
||||
Disable the `tty1` service (because the login takes its place).
|
||||
|
||||
Then stick this at the end of the bashrc:
|
||||
|
||||
```sh
|
||||
sudo touch /etc/sv/agetty-tty1/down
|
||||
# autologin on tty1
|
||||
if [ -z "$DISPLAY" ] && [ "$(fgconsole)" -eq 1 ]; then
|
||||
exec startx
|
||||
fi
|
||||
|
||||
```
|
||||
|
||||
Enable your `${login}` service:
|
||||
|
||||
|
||||
```sh
|
||||
sudo ln -s /etc/sv/${login} /var/service/
|
||||
```
|
||||
|
||||
Reboot.
|
||||
|
||||
Pizza party for one.
|
||||
|
||||
Some files were not shown because too many files have changed in this diff Show More
Reference in New Issue
Block a user