Compare commits

...

42 Commits

Author SHA1 Message Date
596a4a9746 ansible: store host password 2025-08-23 18:59:47 +02:00
af52292ef8 tempfs article 2025-08-22 16:18:28 +02:00
865b4a2da1 remove duplicate entry 2025-08-22 16:02:19 +02:00
8eea348112 change ``bash headers to ``sh 2025-08-22 15:59:04 +02:00
3e049e1687 introduce ansible with docker 2025-08-21 23:00:43 +02:00
d1a1146260 allow ascii dependency map 2025-08-18 01:37:40 +02:00
3dface826f playing with ansible 2025-08-16 02:54:41 +02:00
a55712032b make all file names lowercase 2025-08-14 06:35:44 +02:00
33a959fcea note makefile warning 2025-08-13 22:09:48 +02:00
4ed4c87acf improve group logins 2025-08-13 22:09:12 +02:00
68f9eb2a7d note ijq for json 2025-08-06 05:28:58 +02:00
c407e8be9e note git requirement for lfs 2025-07-29 16:38:28 +02:00
f52b241dc2 write make a gif 2025-07-29 16:38:18 +02:00
c0755da29f fix ffmpeg headers 2025-07-29 16:31:02 +02:00
c3afb4b562 add git stash 2025-07-24 07:23:42 +02:00
f5b3d969fd grok vi 2025-07-14 12:42:45 +02:00
7e2487f0d3 formatting 2025-06-05 20:46:33 +02:00
3fec180a14 add python projects with Makefiles 2025-06-05 20:46:13 +02:00
c08ad6f175 update taskwarrior 2025-05-25 20:10:05 +02:00
1a17ffda7f do not jaquays the docs 2025-05-24 23:27:45 +02:00
556dba6f29 scan ports with havn 2025-05-24 23:27:06 +02:00
b7a79951c5 adjust LaTeX notes 2025-05-21 16:11:11 +02:00
2d95304da4 rejig git 2025-05-18 00:01:48 +02:00
8e64f8f58e note how to use git with sha256 2025-05-14 21:33:16 +02:00
3b04aaf8be add string substitution 2025-05-06 16:41:57 +02:00
1dfdac516b add basic vim requirements to vim 2025-04-30 15:39:11 +02:00
63e4c409bb fix missing links 2025-04-30 15:39:05 +02:00
98dbb5e3d6 write sc-im conversions 2025-04-15 13:51:33 +02:00
45eae50c24 typo 2025-04-09 15:40:38 +02:00
24bb7014f9 write tex setup 2025-04-02 01:11:02 +02:00
92145ac4b7 make a writing category 2025-04-01 23:29:17 +02:00
7292e0625e formatting 2025-04-01 15:06:21 +02:00
ffa4dbc51a commit for another 2025-04-01 15:02:26 +02:00
641b8fb825 update vim syntax 2025-03-26 14:07:27 +01:00
a6b8420c26 update warrior syntax 2025-03-26 13:51:17 +01:00
68d3a850c0 how to show torrents 2025-03-26 13:46:04 +01:00
7e75763cee expand on readme style 2025-03-22 23:45:43 +01:00
2d3961e0f5 update readme 2025-03-22 23:41:04 +01:00
72ad0786c8 allow joins on related articles 2025-03-22 23:26:20 +01:00
b64d9de0c4 bad.horse bad.horse 2025-03-20 13:10:43 +01:00
fa9c8edb1d edit Makefile intro 2025-03-18 18:54:17 +01:00
741e988536 base 16 notes 2025-03-18 18:11:57 +01:00
124 changed files with 1739 additions and 907 deletions

View File

@@ -6,7 +6,7 @@ FZF != command -v sk || command -v fzy || command -v fzf || \
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
@@ -19,6 +19,8 @@ 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)/*)) \
@@ -26,6 +28,7 @@ $(foreach dir, $(categories), \
.dbs/:
mkdir $@
$(databases): .dbs/%.rec: %/ | .dbs/
$(info making $(@F))
for entry in $(shell find $< -type f -name "*.md") ; do \
@@ -38,8 +41,11 @@ $(databases): .dbs/%.rec: %/ | .dbs/
# This two-variable read can only happen because of the quotes in the titles.
db.rec: $(databases)
$(warning rebuilding from $? )
printf '%s\n' '%rec: guide' > $@
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 $^ >> $@
@@ -53,10 +59,8 @@ db.rec: $(databases)
recfix --sort $@
$(info Created main database: $@)
default += db.rec
.git/info/exclude: $(default)
echo $^ | tr ' ' '\n' > $@
@echo $^ | tr ' ' '\n' > $@
default += .git/info/exclude
@@ -74,6 +78,18 @@ article: ## Write an article
printf '%s\n\n' '---' >> $$path/$$filename.md ;\
$(EDITOR) +5 "$$path/$$filename.md"
.dbs/map.fmt:| .dbs/
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: 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) $(default)

View File

@@ -4,23 +4,29 @@ title: "Linux Knowledge Base"
The Linux Knowledge-Base provides quick-start guides for working with terminal programs.
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
Install `make`, `recutils`, and any fuzzy-finder (i.e. `sk`, `fzy`, or `fzf`).
## Usage
Set up the database and try a few queries:
```sh
make
make database
recsel db.rec -m 3
recsel db.rec -q database
recsel db.rec -q gpg
recsel db.rec -e "title = 'ssh'"
recsel db.rec -e "title ~ 'ssh'"
recsel db.rec -e "title ~ 'bash'" -R title,wordcount
recsel db.rec -m 1 -P content | less -R
recsel db.rec -t guide -j provides -G title \
-e "title = 'ssh'" \
-p 'sum(provides_wordcount)'
```
# Style
@@ -30,6 +36,16 @@ recsel db.rec -m 1 -P content | less -R
- 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.
## State Knowledge Dependencies
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 select options half-way through.
@@ -74,6 +90,11 @@ grep ls --color=always $HISTFILE | $PAGER
Now we can see what can be changed.
## 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.
# What's Wrong with Everything Else?
## Man pages

View File

@@ -4,43 +4,43 @@ tags: [ "basics", "time" ]
---
Install with:
```bash
```sh
sudo apt install at
```
Enable the daemon service with:
```bash
```sh
sudo systemctl enable --now atd
```
Then jobs can be specified with absolute time, such as:
```bash
```sh
at 16:20
```
```bash
```sh
at noon
```
```bash
```sh
at midnight
```
```bash
```sh
at teatime
```
Type in your command, e.g.:
```bash
```sh
touch /tmp/$FILE.txt
```
The jobs can also be specified relative to the current time:
```bash
```sh
at now +15 minutes
```
@@ -50,7 +50,7 @@ Finally, accept the jobs with ^D.
Display a list of commands to run with:
```bash
```sh
atq
```
@@ -58,7 +58,7 @@ atq
This will print all pending IDs. Remove a job by the ID with:
```bash
```sh
atrm 2
```
@@ -68,7 +68,7 @@ Check `/var/spool/atd/` to see the jobs.
Automatically add a job for later, by setting the date, then using echo for the command.
```bash
```sh
t="$(date -d "2 minutes" +%R)"
echo "fortune > ~/$FILE" | at "$t"
watch cat $FILE

View File

@@ -9,13 +9,13 @@ Don't worry about understanding any of it, just type it in and the habit forms p
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'):
```bash
```sh
pwd
```
Have a look at what is here:
```bash
```sh
ls
```
@@ -23,11 +23,11 @@ If you get no response, the list of items is "", meaning "nothing here".
Have a look at **a**ll the files:
```bash
```sh
ls -a
```
```bash
```sh
. ..
```
@@ -35,38 +35,38 @@ So `.` means 'here' and `..` means 'you see stairs leading downwards' (e.g. 'the
Change directory (`cd`) down one level:
```bash
```sh
cd ..
```
Look where you are again with `pwd`, then go back up. Use `ls`, and if you see `bob`, then:
```bash
```sh
cd bob
```
Move around the directories. The place at the bottom is the 'root', and is known as `/`. Go to the root:
```bash
```sh
cd /
```
Do `ls` again and `cd` into `etc`. Look at how much space those folders are taking up:
```bash
```sh
du iptables
```
That's the number of kilobytes the file is taking up.
Do the same again, but in a human-readable format:
```bash
```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:
```bash
```sh
man du
```
@@ -74,7 +74,7 @@ Once you're done, press 'q' to quit the manual page and try the extra `du` flag
Now you can try to gain super-powers and take over the system:
```bash
```sh
sudo -i
```
@@ -82,61 +82,61 @@ 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:
```bash
```sh
exit
```
Go find a file that isn't a directory. You can tell which is which with:
```bash
```sh
ls -l
```
A directory starts with a 'd', like this:
```bash
```sh
drwxr-xr-x 79 root root 4096 Jan 3 05:15 /etc/
```
A standard file starts with '-', like this:
```bash
```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:
```bash
```sh
cat /etc/hostname
```
Print out the words "hello world":
```bash
```sh
echo "hello world"
```
Move back to your home directory:
```bash
```sh
cd
```
Take the words 'hello world', and put them in 'my_file':
```bash
```sh
echo 'hello world' > my_file
```
Measure the disk usage of that file, then put the results at the bottom of the file:
```bash
```sh
du $FILE >> $FILE
```
And check the results:
```bash
```sh
cat $FILE
```
@@ -148,7 +148,7 @@ Press tab after typing a few keys and bash will guess what you're trying to typ
Look at your file's owner:
```bash
```sh
ls -l $FILE
```
@@ -156,19 +156,19 @@ If it says `-rw-r--r-- 1 root root 8 Dec 11 17:26 hostname` then the file is own
Take your file and change the owner to root:
```bash
```sh
sudo chown root $FILE
```
Change the same file so it's owned by the group 'audio':
```bash
```sh
sudo chown :audio $FILE
```
Check you did that correctly:
```bash
```sh
ls -l my_file
```
@@ -176,7 +176,7 @@ ls -l my_file
Read the start of that line. Root can 'read' and 'write' to or delete the file. Try to remove (delete) it:
```bash
```sh
rm $FILE
```
@@ -184,32 +184,32 @@ You'll see you're not allowed, because you don't own it.
Look at which groups you're in:
```bash
```sh
groups
```
Change the file so that members of the audio group can write to the file:
```bash
```sh
sudo chmod g+w $FILE
```
Check you got it right with `ls -l`:
```bash
```sh
-rw-rw-r-- 1 root audio 0 Jan 3 19:20 my_file
```
Try to delete the file again:
```bash
```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:
```bash
```sh
sudo usermod -a -G audio [ your username here ]
```
@@ -219,19 +219,19 @@ Now you should be able to remove (delete) the file. Remember, that using 'rm fi
Make a directory called 'new test':
```bash
```sh
mkdir 'new test'
```
Make two directories, called 'A', and 'Z':
```bash
```sh
mkdir A Z
```
Make a single directory called 'A Z'
```bash
```sh
mkdir 'A Z'
```
@@ -239,19 +239,19 @@ mkdir 'A Z'
Measure the disk usage of everything ('\*' means 'everything'), and put it in a file called 'disk usage.txt':
```bash
```sh
du -sch * > A/'disk usage'.txt
```
Look at your file:
```bash
```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:
```bash
```sh
grep total A/disk\ usage.txt
```
@@ -259,7 +259,7 @@ The `grep` program also has a manual ('man page'). You should find out what tha
Start the manual:
```bash
```sh
man du
```
@@ -267,7 +267,7 @@ Then search for `-c` by pressing `/`. Your final keys should be `man du`, then
Find out if the `ls` program also has a 'human readable' format by using `grep` to search for the word 'human':
```bash
```sh
man ls | grep human
```
@@ -275,25 +275,25 @@ Now use that flag that you've found in combinatin with the `-l` flag to look at
Remove the directory 'Z':
```bash
```sh
rmdir Z
```
Remove the directory 'Z':
```bash
```sh
rmdir Z
```
And then remove all the rest:
```bash
```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:
```bash
```sh
rm -r A
```
@@ -303,11 +303,11 @@ 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:
```bash
```sh
whereis yum
```
```bash
```sh
whereis apt
```
@@ -315,14 +315,14 @@ If you get a hit, you can use whatever program that is to install things.
Set a reminder of your package manager:
```bash
```sh
echo my package manager is yum | lolcat
```
If that failed it's because you don't have `lolcat` installed.
Install lolcat:
```bash
```sh
sudo apt install lolcat
```
@@ -330,13 +330,13 @@ Try the same command again.
Search for things you want, like `libreoffice`, or `gimp`:
```bash
```sh
apt search libreoffice
```
... then install one of them with:
```bash
```sh
apt install $PROGRAM
```

View File

@@ -5,37 +5,37 @@ tags: [ "basics", "time" ]
Show system time:
```bash
```sh
date
```
Show hardware time:
```bash
```sh
sudo hwclock -r
```
Change system time to match hardware time:
```bash
```sh
sudo hwclock --hctosys
```
Change hardware time to match system time:
```bash
```sh
sudo hwclock --systohc
```
Manually set the hardware time to a specified date:
```bash
```sh
sudo hwclock --set --date="8/25/19 13:30:00"
```
## Normal Date
```bash
```sh
date +%d/%m/%y
```
@@ -45,7 +45,7 @@ Computers started counting time on January 1st, 1970, and added one second-per-s
Track the time in Unix-time:
```bash
```sh
date +%s
```
@@ -55,13 +55,13 @@ Servers which take their time from an observatory we call Stratum 1 servers. Se
Install ntp with:
```bash
```sh
sudo apt-get install -y ntp
```
The shell command for this is `ntpq`. Monitor the service providers using:
```bash
```sh
ntpq -p
```

View File

@@ -5,32 +5,32 @@ tags: [ "basics", "format", "json" ]
Put output into column.
```bash
```sh
du -h /etc/* | column
```
Reformat file with an explicit separator (`-s`):
```bash
```sh
column -ts: /etc/passwd
```
Give columns names (`-N`), so you can hide some (`-H`):
```bash
```sh
column -ts: -N User,PW,UID,GID,Description,Home,shell -H PW,GID /etc/passwd
```
Reorder with `-O` (unspecified items remain):
```bash
```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`:
```bash
```sh
column -J -ts: -H PW,GID,shell -N User,PW,UID,GID,Description,Home,shell /etc/passwd
```

View File

@@ -46,7 +46,7 @@ esac
# While and Until
This prints from 1 until 9.
```bash
```sh
COUNTER=1
while [ $COUNTER -lt 2 ]; do
> ((COUNTER++))
@@ -58,7 +58,7 @@ There's also 'until', which stops when something is true, rather than keeping go
# For
```bash
```sh
for i in $( ls ); do
> du -sh $i
> done
@@ -70,19 +70,19 @@ The sequences tool counts up from X in jumps of Y to number Z.
Count from 1 to 10.
```bash
```sh
seq 10
```
Count from 4 to 11.
```bash
```sh
seq 4 11
```
Count from 1 to 100 in steps of 5.
```bash
```sh
seq 1 5 100
```

View File

@@ -1,129 +0,0 @@
---
title: "cron"
tags: [ "basics", "time" ]
---
# Cronie
The `cronie` program is also known as `crond`.
## Install
```bash
sudo apt search -n ^cron
```
Once installed, search for the service name, and start it.
```bash
sudo systemctl list-unit-files | grep cron
sudo systemctl enable --now $NAME
```
## Usage
Show your current crontab:
```bash
crontab -l
```
You can put this in a file and edit it:
```bash
crontab -l > $filename
echo '39 3 */3 * * /bin/tar czf /tmp/etc_backup.tgz /etc/' >> $filename
```
Then apply that crontab:
```bash
crontab $filename
rm $filename
```
The `cron` program will check your syntax before adding the tab.
Your crontab file sits somewhere in `/var/spool/`.
Probably in `/var/spool/cron`.
## Syntax
`* * * * *`
These five points refer to:
`minute hour day month weekday`
So '3pm every Sunday' would be:
`0 15 * * 7`
Here 'Sunday' is indicated by "7", and '3pm' is 'the 15th hour'.
The minute is '0' (i.e. '0 minutes past three pm').
Doing the same thing, but only in February, would be:
`0 15 * 2 7`
### Variables
`cronie` doesn't know where you live, so to put something in your `$HOME` directory, you have to tell it:
```bash
echo "HOME=$HOME" > $filename
crontab -l >> $filename
crontab $filename
```
`cronie` doesn't know where anything lives, including programs.
You can give it your usual `$PATH` variable like this:
```bash
echo $PATH > $filename
crontab -l >> $filename
crontab $filename
```
Now instead of doing this
`40 */3 * * * /usr/bin/du -sh $HOME/* | sort -h > $HOME/sum.txt`
You can simply do this:
`40 */3 * * * du -sh $HOME/* | sort -h > $HOME/sum.txt`
## Run as Root
You can execute a script as root by putting it into a directory, instead of in the tab.
Look at the available cron directories:
```bash
ls -d /etc/cron.*
```
Make a script which runs daily:
```bash
f=apt_update.sh
echo '#!/bin/bash' > $f
echo 'apt update --yes' >> $f
chmod +x $f
sudo mv $f /etc/cron.daily/
```
### Testing with runparts
Run-parts runs all executable scripts in a directory.
```bash
run-parts /etc/cron.hourly
```
# Troubleshooting
### `date` Commands
Cron doesn't understand the `%` sign, so if you want to use `date +%R`, then it should be escaped with a backslash: `date +\%R`.

View File

@@ -5,7 +5,7 @@ tags: [ "basics" ]
Compose a statement for execution.
```bash
```sh
x='echo $y'
echo $x
y=dragon
@@ -14,7 +14,7 @@ eval "$x"
The results remain in the current shell, unlike sub-shells.
```bash
```sh
b=basilisk
sh -c 'echo $b'
eval "g=goblin"

View File

@@ -11,20 +11,20 @@ This ID is called the 'inode'.
Create a file, and a hard link:
```bash
```sh
fortune > $file_1
mkdir -p x/y/z/
ln $file_1 x/y/z/$file_2
```
Have a long look at the file with the `-l` flag, and check the inode with `-i`:
```bash
```sh
ls -li $file_1 x/y/z/$file_2
```
Since they are the same file, you can make a change to one, and it changes both:
```bash
```sh
fortune | tee x/y/z/$file_2
cat $file_1
cat x/y/z/$file_2

View File

@@ -7,7 +7,7 @@ If you want to kill a program in a graphical environment, open a terminal and ty
# Graphical Programs
```bash
```sh
xkill
```
@@ -17,7 +17,7 @@ Then click on the application which you want to kill.
To kill a program, find it with:
```bash
```sh
pgrep discord
```
@@ -25,7 +25,7 @@ This will give you the UUID, e.g. `19643`.
Kill the program with:
```bash
```sh
kill 19643
```
@@ -33,7 +33,7 @@ kill 19643
To see an ordered list of termination signals:
```bash
```sh
kill -l
```
@@ -49,7 +49,7 @@ Higher numbers are roughly equivalent to insistence.
For example:
```bash
```sh
kill -1 3498
```
@@ -57,7 +57,7 @@ This roughly means 'maybe stop the program, if you can, maybe reload'.
Or the famous:
```bash
```sh
kill -9 3298
```

View File

@@ -8,25 +8,25 @@ A list of supported locales is available at /usr/share/i18n/SUPPORTED
See a full list with:
```bash
```sh
cat /usr/share/i18n/SUPPORTED
```
Take the first portion to generate full locale information for a region:
```bash
```sh
locale-gen ru_RU.UTF-8
```
Then use this for the current shell session with
```bash
```sh
LANG=ru_RU.utf8
```
Expand this to the entire system with:
```bash
```sh
export LANG=ru_RU.utf8
```
@@ -34,7 +34,7 @@ You can make this permanent for one user by adding this line to the ~/.profile o
Make it permanent for the entire system by editing:
```bash
```sh
sudo vim /etc/defaults/locale
```

View File

@@ -8,13 +8,13 @@ Firstly, your `ls` is probably aliased to something.
Check it with:
```bash
```sh
alias ls
```
If the prompt shows some alias, then start by removing it:
```bash
```sh
unalias ls
```
@@ -23,24 +23,24 @@ Now we can begin.
Check the most recently modified file:
```bash
```sh
ls -t
```
Reverse this with `tac` to see the file which has been unmodified the longest:
```bash
```sh
ls -t | tac
```
Group files by extension:
```bash
```sh
ls -X
```
Sort largest files first:
```bash
```sh
ls -X
```

View File

@@ -6,31 +6,31 @@ tags: [ "basics" ]
See running items in current terminal with
```bash
```sh
ps
```
or more with
```bash
```sh
ps -a
```
Or the entire system with
```bash
```sh
ps -e
```
Or the entire system with more information, BSD style, with:
```bash
```sh
ps aux
```
And then search for a particular program with
```bash
```sh
ps aux | grep cmus
```
@@ -40,19 +40,19 @@ Pause a job with ^z. Put it in the background with the '&' suffix.
List jobs in the current shell with
```bash
```sh
jobs
```
And then you can pull number 1 up again with
```bash
```sh
fg 1
```
Or continue running a stopped job with:
```bash
```sh
bg 1
```
@@ -62,31 +62,31 @@ This changes how nice a program is, from -20 to 19.
Install a program, but nicely, at nice value '10':
```bash
```sh
nice -10 sudo apt -y install libreoffice
```
Aggressively use Steam, with a nice value of '-13'.
```bash
```sh
nice --13 steam&
```
Find out that Steam's fucking everything up, so you change its nice value with 'renice':
```bash
```sh
renice --5 -p 3781
```
Nerf all of roach-1's processes:
```bash
```sh
renice 10 -u roach-1
```
... or the entire group
```bash
```sh
renice -14 -g hackers
```

View File

@@ -9,7 +9,7 @@ This & That
Refer to 'that last thing', and 'the first thing':
```bash
```sh
fortune -l > file1
cat !$ | tr -d u
diff !^ !$
@@ -17,7 +17,7 @@ diff !^ !$
**NB:** this can go wrong:
```bash
```sh
ls -l file1 file2
cat !^
```
@@ -36,7 +36,7 @@ Input Run-Commands (`~/.inputrc`)
Alias Expansion
---------------
```bash
```sh
echo '"\C- ": shell-expand-line' >> ~/.inputrc
exec bash
```
@@ -47,7 +47,7 @@ Try just `ls`, then 'Control + Space'.
Glob Expansion (`*`)
--------------------
```bash
```sh
echo '"\C-x": glob-expand-word' >> ~/.inputrc
exec bash
ls *<C-x>
@@ -63,13 +63,13 @@ Arbitrary Commands
Use `\n` as a 'newline' character to automatically press `<Return>`.
```bash
```sh
echo 'Control-y: "| lolcat\n"' >> ~/.inputrc
exec bash
ls<C-y>
```
```bash
```sh
Control-l: "\C-u clear -x && ls\n"
exec bash
cd /etc/<C-l>
@@ -78,7 +78,7 @@ cd /etc/<C-l>
Readline as Vi
--------------
```bash
```sh
echo 'set editing-mode vi' >> ~/.inputrc
echo 'set keymap vi-insert' >> ~/.inputrc
exec bash
@@ -115,7 +115,7 @@ 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.
```bash
```sh
sed '/ vi/d' ~/.inputrc
sed -i '/ vi/d' ~/.inputrc
@@ -130,14 +130,14 @@ 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:
```bash
```sh
echo 'set show-mode-in-prompt on' >> ~/.inputrc
exec bash
```
Set new symbols for normal and insert mode:
```bash
```sh
echo 'set vi-ins-mode-string " "' >> ~/.inputrc
echo 'set vi-cmd-mode-string " "' >> ~/.inputrc
```
@@ -148,33 +148,33 @@ Fuzzy Sort
Check your repos for `sk-im`, and install.
The program is called `sk`.
```bash
```sh
FUZZY=sk
```
If you don't have it, `fzy` or `fzf` should work the same way.
```bash
```sh
FUZZY=fzy
```
Find some 'read-config' files to check out:
```bash
```sh
find . -maxdepth 2 -name "*rc"
find . -maxdepth 2 -name "*rc" | $FUZZY
```
And read some:
```bash
```sh
PAGER='less -R'
$PAGER "$(find . -maxdepth 2 -name "*rc" | $FUZZY)"
```
Make the change long-term:
```bash
```sh
alias rrc='$PAGER "$(find . -maxdepth 2 -name "*rc" | sk)"'
alias | grep rrc= >> ~/.bash_aliases
```

View File

@@ -7,7 +7,7 @@ When a program encounters a soft link, it will make a guess at whether it shoul
To make a soft link to a file in the current directory, linking is easy:
```bash
```sh
fortune > $file_1
ln -s $file_1 $link_1
```
@@ -27,14 +27,14 @@ dir_0/
Inside `dir_1`, making a soft link to `dir_0/file_1` would mean putting the directions to that file:
```bash
```sh
cd dir_1
ln -s ../file_1 link_1
```
The real content of the file is just '`../file_1`, so making it from another directory would mean writing exactly the same address to that file:
```bash
```sh
ln -s ../file_1 dir_2/link_2
```
@@ -54,7 +54,7 @@ dir_0/
Since it's just an address, you can delete the original file, then make another.
```bash
```sh
rm file_1
ls -l dir_1/
fortune > file_1
@@ -65,7 +65,7 @@ cat dir_1/link_1
Last, let's make a link from `dir_2/link_2` to `dir_1/file_1` (this will delete the old link):
```bash
```sh
ln -s -f ../dir_1/file_1 dir_2/link_2
cat dir_2/link_2
```

View File

@@ -6,7 +6,7 @@ tags: [ "basics", "time" ]
Set time to synchronize with an ntp server:
```bash
```sh
timedatectl set-ntp true
```
@@ -18,7 +18,7 @@ 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:
```bash
```sh
sudo ln -sf /usr/share/zoneinfo/Europe/Belgrade /etc/localtime
```
@@ -28,41 +28,41 @@ sudo ln -sf /usr/share/zoneinfo/Europe/Belgrade /etc/localtime
See local time, language and character settings with:
```bash
```sh
locale
```
List available locales with:
```bash
```sh
locale -a
```
To see additional locales which are available (but not necessarily installed):
```bash
```sh
cat /usr/share/i18n/SUPPORTED
```
Set a supported locale with:
```bash
```sh
locale-gen pl_PL.UTF-8
```
Then set that language, with:
```bash
```sh
LANG=pl_PL.UTF-8
```
... then reboot.
...then reboot.
# Network Time Protocol
Glimpse an overview with:
```bash
```sh
ntpq -p
```
@@ -73,6 +73,6 @@ Usually this is run as a service, so just start that service.
If your clock drifts too far from the right time, it will not reset happily.
For it to reset like this:
```bash
```sh
sudo ntpd -q -g -x -n
```

View File

@@ -28,7 +28,7 @@ Each description-line starts with a tab.
To represent a file structure as a nested series of markdown lists, you can try this horrifying `sed` one-liner:
```bash
```sh
tree -tf --dirsfirst --gitignore --noreport --charset ascii | \
sed -e 's/| \+/ /g' \
-e 's/[|`]-\+/ */g' \

View File

@@ -6,23 +6,23 @@ tags: [ "basics" ]
Let's get some entries with 'getent', e.g. passwd or group.
```bash
```sh
getent passwd
```
```bash
```sh
getent group
```
Obviously:
```bash
```sh
getent shadow
```
## Examples
```bash
```sh
sudo adduser maestro
```
@@ -30,71 +30,71 @@ add user 'maestro'
This depends upon the settings in the /etc/default/useradd file and /etc/login.defs
```bash
```sh
sudo useradd -m pinkie
```
add user 'pinkie' with a home directory
```bash
```sh
sudo adduser -m -e 2017-04-25 temp
```
add expiry date to user
```bash
```sh
userdel maestro
```
delete maestro
```bash
```sh
userdel -r maestro
```
delete maestro and hir homefolder
```bash
```sh
groups
```
find which group you are in
```bash
```sh
id
```
same
```bash
```sh
id -Gn maestro
```
Find which groups maestro is in
```bash
```sh
deluser --remove-home maestro
```
delete user maestro
```bash
```sh
usermod -aG sudo maestro
```
Add user maestro to group sudo:
```bash
```sh
cat /etc/passwd
```
list users' passwords (and therefore users)
```bash
```sh
groupadd awesome
```
@@ -104,33 +104,33 @@ Passwords are stored in /etc/shadow.
There are user accounts for processes such as 'bin' and 'nobody' which are locked, so they're unusable.
```bash
```sh
passwd -l bin
```
Lock the user 'bin'.
```bash
```sh
more /etc/passwd | grep games
```
we find the name, password and user id of the user 'games'. I.e. the password is 'x', and the user id is '5'. The password is an impossible hash, so no input password could match.
```bash
```sh
groupdel learners | delete the group 'learners'
```
```bash
```sh
gpasswd -d pi games | remove user 'pi' from the group 'games'
```
```bash
```sh
id games
```
find the id number of group 'games' (60)
```bash
```sh
usermod -aG sudo maestro
```
@@ -156,7 +156,7 @@ Alternatively, change the shell in /etc/passwd.
Usermod also lets you change a user's username:
```bash
```sh
usermod -l henry mark
```
@@ -170,7 +170,7 @@ usermod -L henry
-G or -groups adds the user to other groups:
```bash
```sh
usermod -G sudo henry
```
@@ -186,13 +186,13 @@ In /etc/group, a group file may look like this:
We can use groupmod, like like usermod, e.g. to change a name:
```bash
```sh
groupmod -n frontoffice backoffice
```
Delte a group:
```bash
```sh
groupdel frontoffice
```
@@ -200,37 +200,37 @@ groupdel frontoffice
See list of logged on users.
```bash
```sh
w
```
See last logons:
```bash
```sh
last
```
or all logon attempts, including bad attempts:
```bash
```sh
lastb
```
List recently accessed files:
```bash
```sh
last -d
```
See files opened by steve
```bash
```sh
lsof -t -u steve
```
See files opened by anyone but steve
```bash
```sh
lsof -u ^steve
```
@@ -240,19 +240,19 @@ Some files can be executed by people as if they had super user permissions, and
Let's start with files executable by user:
```bash
```sh
sudo find / -type f -perm -g=s -ls
```
And then those executable by the group:
```bash
```sh
find / -type f -perm -g=s -ls
```
And finally, worrying files, executable by anyone as if sie were the owner:
```bash
```sh
find / -xdev \( -o -nogroup \) -print
```
@@ -260,7 +260,7 @@ Then have a look at resource usage per user.
# SGID
```bash
```sh
sudo chmod u+s process.sh
```

View File

@@ -11,14 +11,14 @@ This is extremely powerful.
If you ever want to automatically install something which persistently nags you with `do you want to do the thing? [y/N]?`, then you can just pipe `yes` into that program, and it will answer 'yes' to all questions.
```bash
```sh
yes | $INSTALL_SCRIPT_FILE.sh
```
This works best for disposable systems, like VMs or containers.
Try this on a live system, and you might find out that you should have read that message fully.
```bash
```sh
yes | yay
```

View File

@@ -142,4 +142,3 @@ You can ensure omemo automatcally turns on:
```
---
'OTR' encryption is mostly dead, but you can find the old instructions [here](profanity-otr).

View File

@@ -3,6 +3,24 @@ title: "Base 16"
tags: [ "data" ]
---
```bash
Base 16 numbers often use `0x` at the start, so '10' just means '10', but `0x10` means '10 in base 16' which means '16'.
For small numbers, use `printf`.
```sh
printf "%x" $NUMBER
```
For any number, use `bc`.
```sh
fortune | md5sum | cut -d' ' -f1 | tr [:lower:] [:upper:] | bc
```
- Inputting base 16 uses `ibase=16`.
- Outputting base 10 uses `ibase=10`
```sh
echo 'ibase=16;' $(echo cbb478ac825f0dce7671254be035d0bc | tr [:lower:] [:upper:]) | bc
```

View File

@@ -6,41 +6,40 @@ tags: [ "data" ]
## New Machines
```bash
```sh
git config --global user.email "$YOUR_EMAIL"
```
```bash
```sh
git config --global user.name "$YOUR_NAME"
```
# New Git
Start a git in directory `$DIR`:
Decide on algorithm:
```bash
mkdir $DIR && cd $DIR
- 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}
```
```bash
git init
```
Make a file explaining what the project does, and tell `git` to track it:
Make a file explaining what the project does:
```bash
vim README.md
```
Add this to the git:
```bash
```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:
```bash
```sh
git commit
```
@@ -48,17 +47,17 @@ git commit
Once you make a change to some file, add it and make a commit explaining it.
```bash
```sh
git add $FILE
```
```bash
```sh
git commit -m"change $FILE"
```
Check your history:
```bash
```sh
git log
```
@@ -69,20 +68,20 @@ Give it the same name as the `$DIR` directory, above.
Add this as a remote:
```bash
```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":
```bash
```sh
git push -u master origin
```
If someone makes a change on the remote, pull it down with:
```bash
```sh
git pull
```
@@ -91,31 +90,31 @@ git pull
A branch is a full copy of the project to test additional ideas.
You can make a new branch called 'featurez' like this:
```bash
```sh
git branch $FEATURE_BRANCH
```
Have a look at all your branches:
```bash
```sh
git branch
```
Switch to your new branch:
```bash
```sh
git checkout $FEATURE_BRANCH
```
And if your changes are rubbish, checkout the "master" branch again, then delete "featurez":
```bash
```sh
git branch -D $FEATURE_BRANCH
```
Or if it's a good branch, push it to the remote:
```bash
```sh
remote=origin
git push $remote $FEATURE_BRANCH
```
@@ -124,13 +123,13 @@ git push $remote $FEATURE_BRANCH
Once you like the feature, merge it into the main branch. Switch to master then merge it:
```bash
```sh
git merge $FEATURE_BRANCH
```
And delete the branch, as you've already merged it:
```bash
```sh
git branch -d $FEATURE_BRANCH
```
@@ -138,7 +137,7 @@ git branch -d $FEATURE_BRANCH
## Pulling another git repo into a subtree
```bash
```sh
git subtree add -P config git@gitlab.com:bindrpg/config.git master
```
@@ -146,27 +145,27 @@ git subtree add -P config git@gitlab.com:bindrpg/config.git master
## Delete All History
```bash
```sh
git checkout --orphan temp
```
```bash
```sh
git add -A
```
```bash
```sh
git commit -am "release the commits!"
```
```bash
```sh
git branch -D master
```
```bash
```sh
git branch -m master
```
```bash
```sh
git push -f origin master
```
@@ -174,21 +173,21 @@ Gitlab requires more changes, such as going to `settings > repository` and switc
## Clean up Bloated Repo
```bash
```sh
git fsck --full
```
```bash
```sh
git gc --prune=now --aggressive
```
```bash
```sh
git repack
```
## Find Binary Blobs
```bash
```sh
git rev-list --objects --all \
| git cat-file --batch-check='%(objecttype) %(objectname) %(objectsize) %(rest)' \
| sed -n 's/^blob //p' \

View File

@@ -0,0 +1,22 @@
---
title: "Commit for Another"
tags: [ "data", "git" ]
---
You can make Alice the author, while you are still the commiter:
```sh
name="Alice Bobinson"
email="alice@email.com"
git add ${file}
git commit --author="${name} <${email}>"
```
Or, make Alice both the committer and the author:
```sh
git -c user.name="${name}" -c user.email="${email}" commit -m "${message}"
```

View File

@@ -1,6 +1,7 @@
---
title: "git-lfs"
tags: [ "data", "git" ]
requires: [ "git" ]
---
Git Large File Storage ('LFS') needs to change your `~/.gitconfig` to check out those binary files:

69
data/git/git_stash.md Normal file
View File

@@ -0,0 +1,69 @@
---
title: "git stash"
tags: [ "data", "git" ]
requires: [ "git" ]
---
Save file-changes without committing anything.
Change a file:
```sh
file=README.md
fortune >> ${file}
git diff
git stash save
```
List which stashes you have:
```sh
git stash list
stash@{1}: WIP on master: c21f102 init git
```
Make a new file, then stash it:
```sh
otherfile=file.log
fortune > ${otherfile}
git add ${otherfile}
stashname=logfile
git stash save ${stashname}
```
Now you can see two stashed changes, and the most recent has a name:
```sh
git stash list
stash@{0}: On master: logfile
stash@{1}: WIP on master: c21f102 init git
```
You can delete a stash by referring to its index number, or name (if it has one).
```sh
choice=1
git stash drop ${choice}
choice=${stashname}
git stash drop ${choice}
```
Or just run `git stash drop` to remove the most recent (labelled `{0}`).
Return stashed changes with an index number (or the most recent).
```sh
git stash pop ${choice}
```
Delete all stashes:
```sh
git stash clear
```

View File

@@ -5,7 +5,7 @@ tags: [ "data", "git" ]
Check out the sample hooks:
```bash
```sh
cd $GIT_REPO
ls .git/hooks
head .git/hooks/pre-commit.sample
@@ -13,7 +13,7 @@ head .git/hooks/pre-commit.sample
Add a hook to check the shell scripts in `$GIT_REPO` before making a commit:
```bash
```sh
echo '#!/bin/sh
shellcheck *.sh' > .git/hooks/commit-msg
chmod u+x .git/hooks/commit-msg

View File

@@ -10,7 +10,7 @@ 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.
```bash
```sh
git subtree split --prefix=sub-1 -b sub
```
@@ -18,7 +18,7 @@ If you want something a few directories deep, you can use `--prefix=sub-1/dir-2/
Then go and create a new git somewhere else:
```bash
```sh
cd ..;mkdir sub-1;cd sub-1;git init --bare
```
@@ -28,7 +28,7 @@ git push ../subtest sub:master
Finally, you can clone this repo from your original.
```bash
```sh
git clone ../subtest
```

View File

@@ -6,7 +6,7 @@ tags: [ "data", "GPG" ]
Generate keys:
```bash
```sh
gpg --full-generate-key
```
@@ -14,7 +14,7 @@ Follow the guide.
# Encrypting a file
```bash
```sh
gpg -r malinfreeborn@posteo.net -e file
```
@@ -25,7 +25,7 @@ Check you have an encrypted version of your file.
# Changing Expiration Dates
```bash
```sh
gpg --list-keys
# or...
gpg -k
@@ -37,13 +37,13 @@ gpg -k
Make a password with a password (cypher encryption).
```bash
```sh
gpg -c --output passwords.txt
```
or
```bash
```sh
gpg -c > passwords.txt
```
@@ -53,7 +53,7 @@ Write message then stop with Ctrl+d.
Get the message back out the file with:
```bash
```sh
gpg -d passwords.txt
```
@@ -61,13 +61,13 @@ gpg -d passwords.txt
Search for a key at any key store:
```bash
```sh
gpg --search-keys nestorv
```
Once you've made a decision about someone:
```bash
```sh
gpg --list-keys
```
@@ -86,13 +86,13 @@ This is a fingerprint.
You can now decide the trust level (this stays on your computer).
```bash
```sh
gpg --edit-key CD30421FD825696BD95F1FF644C62C57B790D3CF
```
Once you're in the interface, type `trust`.
```bash
```sh
gpg --sign-key alice@posteo.net
```
@@ -104,7 +104,7 @@ This system relies on a ring of people swapping key information.
Send those trusted keys up to a server, so people can see you have verified them:
```bash
```sh
gpg --send-keys 024C6B1C84449BD1CB4DF7A152295D2377F4D70F
```
@@ -125,7 +125,7 @@ keyserver hkps://keys.mailvelope.com
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).
```bash
```sh
gpg --refresh-keys
```
@@ -135,12 +135,12 @@ You can use the [crontab](../../basics/cron.md) to refresh keys, but this will m
Your public key:
```bash
```sh
gpg --output me.gpg --armor --export
```
Alternatively:
```bash
```sh
gpg --export -a person@email.tld > my_key.pub
```

View File

@@ -0,0 +1,19 @@
---
title: "Interactive String Substitution"
tags: [ "data", "vim", "substitution" ]
---
Want to find and replace, but also confirm each instance?
```sh
vim -c "%s/${pattern}/${replacement}/gc" -c 'wq' ${file}
```
Notice that double-quotes (`"`) in the first command (`-c`).
Alternatively, check with an example string:
```sh
sed "s/${pattern}/ARGLEBARGLE/g" ${file} | grep 'ARGLEBARGLE'
```

13
data/json.md Normal file
View File

@@ -0,0 +1,13 @@
---
title: "ijq"
tags: [ "data", "json", "TUI" ]
---
Analyse `json` easier with `ijq`.
```sh
column -J -ts: -H PW,GID,shell -N User,PW,UID,GID,Description,Home,shell /etc/passwd > host.json
ijq !$
```
If you get stuck, try adding `.[]`.

View File

@@ -4,11 +4,11 @@ tags: [ "RSS" ]
---
Create the configuration directory before you start, and add at least 1 URL.
```bash
```sh
mkdir ~/.config/newsboat
```
```bash
```sh
echo 'https://voidlinux.org/atom.xml foss tech' >> ~/.config/newsboat/urls
```
@@ -28,7 +28,7 @@ You can input a Youtube channel by adding this, with the channel's ID at the end
To get the channel ID without hunting:
```bash
```sh
curl *'https://www.youtube.com/@1minfilms'* | grep -oE 'browseId":"U\w+"' | tail | cut -d'"' -f3
```

View File

@@ -13,11 +13,11 @@ Arch: tesseract-data-eng and poppler-utils
## Script
```bash
```sh
pdftoppm -png *file*.pdf test
```
```bash
```sh
for x in *png; do
tesseract -l eng "$x" - >> out.txt
done

View File

@@ -23,6 +23,6 @@ Make a text file called 'pdfmark.txt'.
Then run:
```bash
```sh
gs -o output.pdf -sDEVICE=pdfwrite "$FILE".pdf pdfmark.txt
```

View File

@@ -16,7 +16,7 @@ The standard `radicale` package should come with a nice `systemd` service file.
If the service comes already-started, stop it immediately:
```bash
```sh
sudo systemctl stop radicale
```
@@ -40,7 +40,7 @@ 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`.
```bash
```sh
PASS="$(xkcdpass)"
htpasswd -nb $USER "$PASS" | sudo tee -a /etc/radicale/users
echo "Your username is $USER"
@@ -93,7 +93,7 @@ sudo ln -s /etc/nginx/sites-available/radicale /etc/nginx/sites-enables/
Finally, replace the example `DOMAIN` with your actual domain name.
```bash
```sh
DOMAIN=whatever.com
sudo sed -i "s/DOMAIN/$DOMAIN/g" /etc/nginx/sites-available/radicale
```
@@ -102,18 +102,18 @@ sudo sed -i "s/DOMAIN/$DOMAIN/g" /etc/nginx/sites-available/radicale
Check nginx is happy:
```bash
```sh
sudo nginx -t
```
You will almost certainly need a new SSL certificate for the site:
```bash
```sh
sudo certbod -d cal.$DOMAIN
```
Start or restart both services:
```bash
```sh
sudo systemctl start radicale
sudo systemctl restart nginx
```

View File

@@ -7,7 +7,7 @@ tags: [ "data", "database", "recfiles" ]
Make a database for your boardgames, specifying only one field and value:
```bash
```sh
database=games.rec
n=Name
g=Vojvodina
@@ -18,21 +18,21 @@ recsel $database
Insert a few more, with the estimated playtime:
```bash
```sh
recins -f Name -v Saboter -f Playtime -v 30 $database
recins -f Name -v Chess -f Playtime -v 30 $database
```
View all games, or select one by number:
```bash
```sh
recsel $database
recsel -n 0 $database
```
Each game should note whether or not you have played it yet, so you can add that field and set the default to `yes`.
```bash
```sh
f=played
v=yes
recset -f $f -a $v $database
@@ -40,7 +40,7 @@ recset -f $f -a $v $database
...but the field is wrong, it should have a capital letter:
```bash
```sh
new_field=Played
recset -f $f --rename $new_field
```
@@ -49,19 +49,19 @@ recset -f $f --rename $new_field
Check how many records the database has:
```bash
```sh
recinf $database
```
Look at just the games you've never played:
```bash
```sh
recsel --expression="Played = 'no'" $database
```
Print how many, then just print the names:
```bash
```sh
recsel -e "Played = 'no'" --count $database
recsel -e "Played = 'no'" --print=Name $database
```
@@ -70,7 +70,7 @@ recsel -e "Played = 'no'" --print=Name $database
To change a game's `Played` field from `no` to `yes`, use `recset` to specify the number, and change that field.
```bash
```sh
num=0
f=Played
value=yes
@@ -80,14 +80,14 @@ recset --number=$num -f $f --set=$value $database
Find all games with a playtime of `30`, and set the field `Max_Players` to `4`.
```bash
```sh
recset -e "Playtime = 40" -f Max_Players --set 50 games.rec
```
This doesn't work, because that field does not exist.
You can `--set-add` the field, to add it wherever it does not exist.
```bash
```sh
recset -e "Playtime = 40" -f Max_Players --set-add 50 games.rec
```
@@ -95,14 +95,14 @@ recset -e "Playtime = 40" -f Max_Players --set-add 50 games.rec
Remove `Played` record from first game:
```bash
```sh
num=0
recset --number=$num -f Played --delete $database
```
You can comment the line instead of deleting it:
```bash
```sh
num=1
recset --number=$num -f Played --delete $database
recsel $database
@@ -111,7 +111,7 @@ cat $database
Delete an entire record:
```bash
```sh
num=2
recdel --number=$num $database
```

View File

@@ -15,7 +15,7 @@ Change this with `:set autowrap`.
Make `sc-im` always autowrap:
```bash
```sh
mkdir .config/sc-im/bash
echo 'set autowrap' >> .config/sc-im/scimrc
```

View File

@@ -0,0 +1,13 @@
---
title: "Convert Spreadsheets"
tags: [ "data", "sc-im" ]
---
Convert between spreadsheet formats with `sc-im`.
```sh
sc-im --quiet --quit_afterload --nocurses --export_csv ${file}.xlsx
sc-im --quiet --quit_afterload --nocurses --export_tab ${file}.sc
sc-im --quiet --quit_afterload --nocurses --export_mkd ${file}.csv
sc-im --quiet --quit_afterload --nocurses --export_txt ${file}.tsv
```

View File

@@ -33,7 +33,7 @@ By default, the `/mnt` directory is 'pruned' from the database.
So if you want to search `/mnt` for videos, remove the word `/mnt` from the configuration file.
```bash
```sh
su root
cat /etc/updatedb.conf
sed -i 's#/mnt/##' /etc/updatedb.conf

View File

@@ -7,7 +7,7 @@ You can share parts of a secret with multiple people, so only some of them need
Install `ssss`, then decide on the total number of secrets (`N`), and the threshold of people who must share their shard of the secret in order to reveal the secret.
```bash
```sh
N=5
T=3
FILE=secret.txt
@@ -17,7 +17,7 @@ Each shard is a line inside secret.txt.
Check it's working:
```bash
```sh
head -n $T $FILE | ssss-combine -t $T
tail -n $T $FILE | ssss-combine -t $T
```

View File

@@ -30,7 +30,7 @@ http:
Restart the `soft-serve` service, then check it's working by cloning from localhost:
```bash
```sh
git clone http://localhost:23232/${some_repo}.git
```

View File

@@ -5,7 +5,7 @@ tags: [ "data" ]
Work with a database:
```bash
```sh
sqlite3 "$FILE".sqlite3
```
Compress the database:

34
data/task/contexts.md Normal file
View 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
```

View File

@@ -1,23 +1,35 @@
---
title: "task"
tags: [ "organization" ]
title: "Taskwarrior"
tags: [ "data", "organization" ]
---
Set up the configuration file:
```bash
```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:
```bash
```sh
task add update linux
```
See which task is next:
```bash
```sh
task next
```
@@ -25,13 +37,13 @@ Note the id number.
Mark a task as started:
```bash
```sh
task start 1
```
Once finished:
```bash
```sh
task 1 done
```
@@ -39,23 +51,21 @@ task 1 done
Add a project:
```bash
```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
task add pro:house.paint buy red paint
task add pro:house.paint buy black paint
task add pro:house.paint buy brushes
for t in "buy red paint" "buy black paint" "buy brushes" ; do
task add pro:house.paint $t
done
```
## Summary
```bash
```sh
task pro:house sum
```
```bash
task burndown.daily pro:house
```
@@ -63,69 +73,33 @@ The summaries will show how fast a project is being completed, and when you can
# Tags
```bash
```sh
task add +buy toothbrush
```
You can then see only tasks which involve buying something with:
```bash
task +buy
```
# Contexts
Set three contexts by their tags:
```bash
task context define work +sa or +hr
```
```bash
task context define study +ed or +void or +rat
```
```bash
task context define home -sa -hr -ed -void -rat
```
Change to the first context.
```bash
task context work
```
Then stop.
```bash
task context none
```
# Review
View list of tasks completed in the last week:
```bash
```sh
task end.after:today-1wk completed
```
# User Defined Attributes
Make a UDA 'size'.
Define a new attribute for tasks called 'size'.
The 'user defined attribute' (UDA) needs a `type` and `label`.
```bash
```sh
task config uda.size.type string
```
```bash
task config uda.size.label Size
```
You can also ensure task tasks can only be `large`, `medium`, or `small`, then set a default.
```bash
```sh
task config uda.size.values large,medium,small
```
```bash
uda.size.default=medium
```
@@ -133,7 +107,7 @@ uda.size.default=medium
This command shows tasks I'm most interested in:
```bash
```sh
task next +ACTIVE or +OVERDUE or due:today or scheduled:today or pri:H
```

View 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
```

View File

@@ -6,13 +6,13 @@ tags: [ "data", "tracking", "time", "timew" ]
Try:
```bash
```sh
timew summary :yesterday
```
You can also use :week, :lastweek, :month, :quarter, :year, or a range such as:
```bash
```sh
timew summary today to tomorrow
timew today - tomorrow
2018-10-15T06:00 - 2018-10-17T06:00
@@ -22,7 +22,7 @@ Each of these can gain with the :ids tag.
# Basics
```bash
```sh
timew start
timew stop
timew continue
@@ -32,7 +32,7 @@ timew tags
And add ids with:
```bash
```sh
timew summary :ids
timew track 10am - 1pm timewarrior
timew track 1pm for 2h walk
@@ -42,50 +42,50 @@ timew track 1pm for 2h walk
First get ids.
```bash
```sh
timew summary :ids
```
Then if we're looking at task @2:
```bash
```sh
timew move @2 12:00
timew lengthen @2 3mins
```
```bash
```sh
time shorten @2 40mins
```
# Forgetting
```bash
```sh
timew start 1h ago @4
```
Or if your action actually had a break:
```bash
```sh
timew split @8
```
Or maybe not?
```bash
```sh
timew join @4 @8
timew @8 delete
```
Start at previous time
```bash
```sh
timew start 3pm 'Read chapter 12'
timew start 90mins ago 'Read chapter 12'
```
Cancel currently tracked time.
```bash
```sh
timew cancel
```
@@ -157,11 +157,11 @@ with:
# Fixing Errors
```bash
```sh
curl -O https://taskwarrior.org/download/timew-dbcorrection.py
```
```bash
```sh
python timew-dbcorrections.py
```

11
data/view_torrents.md Normal file
View File

@@ -0,0 +1,11 @@
---
title: "View Torrents"
tags: [ "data", "transmission", "torrenting" ]
---
```sh
transmission-show $file.torrent | less
```
`TRACKERS` shows where transmission will ask who has the torrent, but will probably be out of date.

View File

@@ -4,7 +4,7 @@ tags: [ "browsers" ]
---
Open a search tab:
```bash
```sh
w3m ddg.gg
```

View File

@@ -7,7 +7,7 @@ tags: [ "distros", "arch" ]
Edit `/etc/systemd/system/getty@tty1.service.d/override.conf` by typing:
```bash
```sh
sudo systemctl edit getty@tty1
```

View File

@@ -5,17 +5,17 @@ requires: [ "partitions", "time" ]
---
Keyboard layout changed.
```bash
```sh
ls /usr/share/kbd/keymaps/**/*.map.gz
```
```bash
```sh
loadkeys uk.map.gz
```
Check if boot mode is UEFI
```bash
```sh
ls /sys/firmware/efi/efivars
```
@@ -23,115 +23,115 @@ Without efivars, the system must boot with BIOS.
# Check network's up
```bash
```sh
ping archlinux.org
```
Set system clock properly
```bash
```sh
timedatectl set-ntp true
```
Check disks
```bash
```sh
lsblk
```
Make partition
```bash
```sh
parted -s /dev/sda mklabel gpt
```
```bash
```sh
parted -s /dev/sda mklabel msdos
```
```bash
```sh
parted -s /dev/sda mkpart primary ext4 512 100%
```
```bash
```sh
parted -s /dev/sda set 1 boot on
```
```bash
```sh
mkfs.ext4 /dev/sda1
```
Use pacstrap to get the base install.
```bash
```sh
mount /dev/sda1 /mnt/
```
```bash
```sh
pacstrap /mnt base base-devel vim linux linux-firmware
```
Make fstab notes for new system.
```bash
```sh
genfstab -U /mnt >> /mnt/etc/fstab
```
```bash
```sh
arch-chroot /mnt
```
```bash
```sh
echo 'en_GB.UTF-8' > /etc/default/locale
```
```bash
```sh
pacman -Sy networkmanager grub
```
For legacy:
```bash
```sh
grub-install --target=i386-pc /dev/sda
```
For EFI:
```bash
```sh
sudo pacman -S efibootmgr
```
```bash
```sh
mkdir /boot/efi
```
```bash
```sh
grub-install --target=x86_64-efi --efi-directory=/boot/efi --bootloader-id=GRUB --remmovable
```
```bash
```sh
grub-mkconfig -o /boot/grub/grub.cfg
```
set local time
```bash
```sh
ln -sf /usr/share/zoneinfo/Europe/Belgrade /etc/localtime
```
Find the desired locale's and uncomment them.
```bash
```sh
vi /etc/locale.gen
```
```bash
```sh
locale-gen
```
Make your keyboard changes permenent with:
```bash
```sh
vi /etc/vconsole.conf
```
@@ -140,13 +140,13 @@ unsure about this bit - is this name just for the loadkeys function?
Make a hostname
```bash
```sh
echo pc > /etc/hostname
```
Set hostnames for network, or at least your own.
```bash
```sh
vi /etc/hosts
```
@@ -160,27 +160,27 @@ If the system has a permanent IP address, it should be used instead of localhost
Ping some sites to make sure the network's working
```bash
```sh
passwd
```
```bash
```sh
exit
```
```bash
```sh
umount -R /mnt
```
Remove that awful beep sound:
```bash
```sh
rmmod pcspkr
```
...and make the change permanent:
```bash
```sh
sudo echo "blacklist pcspkr" >> /etc/modprobe.d/nobeep.conf
```

View File

@@ -13,7 +13,7 @@ Include = /etc/pacman.d/mirrorlist
And update:
```bash
```sh
sudo pacman -Syu
```
@@ -21,7 +21,7 @@ sudo pacman -Syu
Check your graphics card type:
```bash
```sh
lspci | grep VGA
```
@@ -31,7 +31,7 @@ lspci | grep VGA
If you see `Nvidia`, then install the intel drivers:
```bash
```sh
sudo pacman -S --needed lib32-mesa vulkan-intel lib32-vulkan-intel vulkan-icd-loader lib32-vulkan-icd-loader
```
@@ -39,7 +39,7 @@ sudo pacman -S --needed lib32-mesa vulkan-intel lib32-vulkan-intel vulkan-icd-lo
If you see `Intel`, then install the intel drivers:
```bash
```sh
sudo pacman -S --needed lib32-mesa vulkan-intel lib32-vulkan-intel vulkan-icd-loader lib32-vulkan-icd-loader xf86-video-intel
```
@@ -47,16 +47,16 @@ sudo pacman -S --needed lib32-mesa vulkan-intel lib32-vulkan-intel vulkan-icd-lo
If you see `AMD`, then check your card support `vulkan`:
```bash
```sh
yay -S gpu-viewer
```
```bash
```sh
vulkaninfo | grep 'VkPhysicalDeviceVulkanMemoryModelFeatures' -A 3
```
You should see 'true' here.
```bash
```sh
sudo pacman -S --needed lib32-mesa vulkan-radeon lib32-vulkan-radeon vulkan-icd-loader lib32-vulkan-icd-loader xf86-video-amdgpu
```

View File

@@ -7,14 +7,14 @@ tags: [ "arch" ]
Clean the cache of old packages in `/var/cachepacman/pkg/`:
```bash
```sh
ls /var/cache/pacman/pkg/ | wc -l
sudo pacman -Sc
ls /var/cache/pacman/pkg/ | wc -l
```
And the same for `yay` (with `-Yc` to remove old dependencies):
```bash
```sh
ls ~/.cache/yay/ | wc -l
yay -Sc
yay -Yc
@@ -27,7 +27,7 @@ If you chance a configuration file, such as `/etc/environment`, and `pacman` wan
Check the new files, then look at the difference between the `pacman` version, and your version.
```bash
```sh
sudo find /etc/ /var/ /usr/ -name "*.pacnew"
diff /etc/pacman.d/mirrorlist*
```
@@ -36,7 +36,7 @@ Either,
- Update the files manually,
```bash
```sh
sudo -e /etc/pacman.d/mirrorlist
sudo rm /etc/pacman.d/mirrorlist.pacnew
```
@@ -46,7 +46,7 @@ Or,
- use a tool like `pacdiff` to view the changes next to each other, and select them with `vim`.
```bash
```sh
sudo pacman -S pacman-contrib
sudo pacdiff
```

View File

@@ -7,13 +7,13 @@ Packages are kept in /var/cache/pacman/pkg.
Delete unused old packages with:
```bash
```sh
sudo pacman -Sc
```
Signatures are handled by the pacman-key, initially set up with:
```bash
```sh
sudo pacman-key --populate archlinux
```
@@ -23,31 +23,31 @@ sudo pacman-key --refresh-keys
If you have usigned keys, you can refresh with:
```bash
```sh
sudo pacman -Sc
```
or
```bash
```sh
sudo pacman -Scc
```
Reset all keys with:
```bash
```sh
sudo rm -r /etc/pacmand.d/gnupg/ && sudo pacman-key --init
```
If you're constantly getting 'everything corrupted, nothing upgraded', try running:
```bash
```sh
sudo pacman -S archlinux-keyring
```
List all orphaned packages:
```bash
```sh
sudo pacman -Qtdq
```

View File

@@ -5,7 +5,7 @@ tags: [ "void" ]
Make the autologin service:
```bash
```sh
cp -R /etc/sv/agetty-tty1 /etc/sv/agetty-autologin-tty1
```

View File

@@ -7,24 +7,24 @@ To automatically stick the logo onto your background, do these commands in the d
Get the void linux logo from wikipedia
```bash
```sh
wget https://upload.wikimedia.org/wikipedia/commons/thumb/0/02/Void_Linux_logo.svg/256px-Void_Linux_logo.svg.png?20170131170632
```
Rename it, and resize it (the standard size is too small for most wallpapers)
```bash
```sh
convert -resize 200% '256px-Void_Linux_logo.svg.png?20170131170632' void-logo.png
```
Download a pretty wallpaper
```bash
```sh
wget http://wallpapercave.com/wp/Wlm9Gv0.jpg
```
Put the void logo on all *jpg and *png images
```bash
```sh
for x in *.jpg
do
composite -compose multiply -gravity Center void-logo.png "$x" "$x"

View File

@@ -6,13 +6,13 @@ tags: [ "void" ]
All possible services are in:
```bash
```sh
ls /etc/sv
```
The computer only uses those in /var/service, so symbolic links are made to start and stop services.
```bash
```sh
ls /var/service
```
@@ -20,13 +20,13 @@ ls /var/service
Enable the sshd service, so that ssh will work every time you boot up:
```bash
```sh
sudo ln -s /etc/sv/sshd /var/service
```
Then start the service:
```bash
```sh
sudo sv start sshd
```
@@ -34,19 +34,19 @@ sudo sv start sshd
Stop `mpd` with:
```bash
```sh
sudo sv stop mpd
```
And stop it automatically loading at startup with:
```bash
```sh
sudo rm /var/service/mpd
```
You can also just make a file called 'down':
```bash
```sh
sudo touch /var/service/mpd/down
```
@@ -63,7 +63,7 @@ If unsure, use `#!/bin/bash` as the first line. When Void Linux says `sh`, it m
Confirm the shell you'll use:
```bash
```sh
ls -l $(which sh)
```

View File

@@ -6,7 +6,7 @@ tags: [ "void" ]
Update all packages with
```bash
```sh
sudo xbps-install -Su
```
@@ -17,7 +17,7 @@ See [xbps](xbps.md) for more.
Void keeps *every* version of everything you install, so you can roll back to them.
Remove old packages with:
```bash
```sh
sudo xbps-remove -O
```
@@ -25,19 +25,19 @@ sudo xbps-remove -O
Old Void kernels are left on the boot partition. List them with:
```bash
```sh
vkpurge list
```
Remove one with:
```bash
```sh
vkpurge 2.8.2_4
```
Remove all but the latest with:
```bash
```sh
vkpurge rm all
```
@@ -48,7 +48,7 @@ You can change this number to change the screen brightness.
For an easy utility, install `brightnessctl`.
```bash
```sh
brightnessctl s 10%-
brightnessctl s 10%+
```
@@ -57,5 +57,5 @@ brightnessctl s 10%+
- [autologin](autologin.md)
- [services](sv.md)
- [wifi](wpa_cli.md)
- [wifi](../../networking/wpa_supplicant.md)

View File

@@ -6,50 +6,50 @@ tags: [ "void" ]
Look for cowsay in the repository:
```bash
```sh
xbps-query --repository --search cowsay
```
Short version:
```bash
```sh
xbps-query -Rs cowsay
```
Search with regex:
```bash
```sh
xbps-query --regex -Rs 'cow(s)?\w'
```
List what's required for cowsay
```bash
```sh
xbps-query -x cowsay
```
What packages are orphaned (i.e. installed as a dependency for another package, which has since been removed)?
```bash
```sh
xbps-query -O
```
Show cowsay's dependencies.
```bash
```sh
xbps-query -x cowsay
```
This shows `perl`.
To see what else depends on perl:
```bash
```sh
xbps-query -X perl
```
List all manually installed software.
```bash
```sh
xbps-query -m
```
@@ -57,14 +57,14 @@ xbps-query -m
Install cowsay
```bash
```sh
xbps-install cowsay
```
Upgrade current packages.
`-R` looks at repositories, `-s` makes a sloppy search (for rough matches).
```bash
```sh
xbps-install -Suv
```
@@ -72,19 +72,19 @@ xbps-install -Suv
Remove cowsay
```bash
```sh
xbps-remove cowsay
```
...and all dependencies
```bash
```sh
xbps-remove -R cowsay
```
Remove all orphaned dependencies.
```bash
```sh
xbps-remove -o
```
@@ -94,19 +94,19 @@ Show information about cowsay
Reinstall cowsay
```bash
```sh
xbps-install -f cowsay
```
Look for broken packages.
```bash
```sh
sudo xbps-pkgdb -a
```
And if you've found any, you might reconfigure all packages forcefully:
```bash
```sh
sudo xbps-reconfigure -af
```

20
networking/bad_horse.md Normal file
View File

@@ -0,0 +1,20 @@
---
title: "Mapping the Net"
tags: [ "networking", "graph", "fun" ]
---
Find the path to a domain:
```sh
domain=bad.horse
max_hops=50
tracepath -m $maximum_hops $domain
```
If you're on Debian, you can use `graph-easy` and `dothost` to make an instant diagram:
```sh
domain=dice.camp
dothost $domain | graph-easy --boxart
```

View File

@@ -5,7 +5,7 @@ requires: [ "ssh" ]
---
# SSH Daemon Jail
```bash
```sh
sudo cp /etc/fail2ban/jail.conf /etc/fail2ban/jail.d/ssh.local
```
@@ -17,15 +17,15 @@ ignoreip = 127.0.0.1/8 ::1,192.168.0.0/16 ::1
```
```bash
```sh
sudo systemctl restart fail2ban
```
```bash
```sh
sudo fail2ban-client status
```
```bash
```sh
sudo fail2ban-client status sshd
```

View File

@@ -18,7 +18,7 @@ Set up a file like this, called `troubleshooting.txt`.
Then translate it with:
```bash
```sh
graph-easy troubleshooting.txt --as boxart
```

View File

@@ -8,7 +8,7 @@ This is a basic Linux firewall program.
Look at your firewalls:
```bash
```sh
iptables -L
```
@@ -18,7 +18,7 @@ We see the output of input, output and forwarding rules.
I don't need any forwarding, so I'm going to drop all forwarding:
```bash
```sh
iptables -P FORWARD DROP
```
@@ -26,17 +26,17 @@ iptables -P FORWARD DROP
Let's 'A'dd, or 'A'ppend a rule with -A. Let's drop all input from a nearby IP
```bash
```sh
iptables -A INPUT -s 192.168.0.23 -j DROP
```
Or we can block all input from a particular port on the full Network.
```bash
```sh
iptables -A INPUT -s 192.168.0.0/24 -p tcp --destination-port 25 -j DROP
```
```bash
```sh
iptables -A INPUT --dport 80 -j ACCEPT
```
@@ -47,13 +47,13 @@ However, rules are accepted in order - so a packet cannot be rejected and then a
To delete rule 2 from the INPUT chain:
```bash
```sh
iptables -D INPUT 3
```
Alternatively, you can 'I'nsert a rule at the start, rather than 'A'ppending it.
```bash
```sh
iptables -I INPUT -s 192.168.0.13 DROP
```
@@ -67,7 +67,7 @@ The -j flag accepts ACCEPT/REJECT/DROP. The last two are identical except that
Flush all existing rules with:
```bash
```sh
iptables -F
```

View File

@@ -5,7 +5,7 @@ tags: [ "networking" ]
Example:
```bash
```sh
nmap 192.168.1.1/24
```
@@ -17,6 +17,6 @@ Flags:
Look for a web server, which has ports 80 and 443 open:
```bash
```sh
nmap 192.168.1.1/24 -p 80,443 --open
```

View File

@@ -6,19 +6,19 @@ tags: [ "distros" ]
## Arch
```bash
```sh
yay -S pi-hole-server
```
```bash
```sh
sudo systemctl enable --now pihole-FTL
```
```bash
```sh
sudo systemctl disable --now systemd-resolved
```
```bash
```sh
sudo rm -f /dev/shm/FTL-\*
```
@@ -26,32 +26,32 @@ sudo rm -f /dev/shm/FTL-\*
Debian has a long, boring setup.
```bash
```sh
sudo apt-get install wget curl net-tools gamin lighttpd lighttpd-mod-deflate
curl -sSL https://install.pi-hole.net | PIHOLE_SKIP_OS_CHECK=true sudo -E bash
```
# Setup
```bash
```sh
sudo usermod -aG pihole $USER
```
Remove that google dns server.
```bash
```sh
pihole -a setdns 9.9.9.9 1.0.0.1
```
Disable pihole password by setting a blank password.
```bash
```sh
pihole -a -p
```
Get a new list of blocked domains, then reload:
```bash
```sh
pihole -g -r
```
@@ -61,13 +61,13 @@ Every so often, run `pihole -g` again (perhaps put it in crontab).
Observe the pihole's output while you ask it a question:
```bash
```sh
pihole -t
```
Then ask the question from another computer:
```bash
```sh
dig @[ pihole ip ] archlinux.org
```

25
networking/port_scan.md Normal file
View File

@@ -0,0 +1,25 @@
---
title: "Port Scan"
tags: [ "networking" ]
repo: 'https://github.com/mrjackwills/havn/'
---
`havn` scans ports.
It's not in many repos, but if you can `cargo install havn`.
```sh
havn -h
havn -a
domain=splint.rs
havn -p 19-90 ${domain}
```
That last command doesn't work reliably, so increase the number of retries (`-r`), or decrease concurrent requests (`-c`).
```sh
havn -p 19-443 -r 6 ${domain}
havn -p 1-1000 -c 500 -r 5 ${domain}
```

View File

@@ -9,71 +9,71 @@ We'll assume a folder in Google Drive called 'test', and local folder called 'fo
Generate a config file with:
```bash
```sh
rclone config
```
Look at the contents of Google Drive:
```bash
```sh
rclone ls gd:/
```
If rclone loses authorization:
```bash
```sh
rclone authorization
```
List only directories:
```bash
```sh
rclone lsf -dirs-only google:/
```
Mount the remote location on /tmp/google with:
```bash
```sh
rclone mount google /tmp/google
```
Copy the contents of 'foo' to 'test'.
```bash
```sh
rclone copy foo/ google:test
```
Sync contents of foo and test with a progress bar (will delete Google items):
```bash
```sh
rclone sync foo google:test -P
```
Remove all duplicates
```bash
```sh
rclone dedupe google:test
```
Delete contets of a remote file:
```bash
```sh
rclone delete n:test
```
Or delete the folder and contents as well:
```bash
```sh
rclone purge n:test
```
Copy to and from with:
```bash
```sh
rclone copyto google:test foo
```
or
```bash
```sh
rclone copyto foo google:test

View File

@@ -3,7 +3,7 @@ title: "Download Website"
tags: [ "networking", "scraping" ]
---
```bash
```sh
domain=splint.rs
mkdir $domain
cd $domain

View File

@@ -4,25 +4,25 @@ tags: [ "scraping" ]
---
Install `yt-dlp`.
```bash
```sh
yt-dlp --write-auto-sub *<URL>*
```
It will default to English, but you can specify another language with the flag --sub-lang:
```bash
```sh
youtube-dl --sub-lang sv --write-auto-sub *<URL>*
```
You can list all available subtitles with:
```bash
```sh
yt-dlp --list-subs *<URL>*
```
It's also possible to skip the video and only download the subtitle if you add the flag --skip-download:
```bash
```sh
yt-dlp --sub-lang sv --write-auto-sub --skip-download *<URL>*
```

View File

@@ -15,12 +15,12 @@ tags: [ "networking", "host" ]
Query a host with the `host` command.
```bash
```sh
host $domain.$tld
```
```bash
```sh
host $domain.$tld 9.9.9.9
```
@@ -34,7 +34,7 @@ You can also add a specific nameserver:
Request a specific record type (`CNAME`, `TXT`, et c.):
```bash
```sh
torsocks host -T -t $RECORD_TYPE $domain
```

View File

@@ -5,7 +5,7 @@ requires: [ "ssh" ]
---
# Mount
```bash
```sh
sshfs $USER@$IP_ADDRESS:$DIR
```
@@ -16,7 +16,7 @@ Various flags:
# Unmount
```bash
```sh
fusermount3 -u $DIR
```

View File

@@ -6,25 +6,25 @@ requires: [ "ssh" ]
Mount a remote filesystem locally with fuse-sshfs:
```bash
```sh
sshfs *user*@192.168.0.10:/home/*user* /tmp/mnt
```
Unmount with:
```bash
```sh
fusermount -u /tmp/mnt
```
Set it up on /etc/fstab with:
```bash
```sh
sshfs#bkp@bkp.a-server.ninja:/media/store1/bkp /backup fuse defaults,allow_other,reconnect,delay_connect 0 0
```
Make image backup of sda1 and sda2 from one machine and pass it through ssh to another.
```bash
```sh
for i in {1,2};do sudo dd if=/dev/sda$i | ssh -C *user*@192.168.0.10 "dd of=/mnt/Backup/winback-oct-\"$i\".img" status=progress; done
```

View File

@@ -5,7 +5,7 @@ tags: [ "networking" ]
# Get a Hostname
```bash
```sh
sudo vim /etc/tor/torrc
```

View File

@@ -22,29 +22,29 @@ Install it then start the service.
Arch Linux:
```bash
```sh
sudo systemctl start transmission
```
Debian:
```bash
```sh
sudo systemctl start transmission-daemon
```
Add a torrent by the .torrent file, or a magnet link, like this:
```bash
```sh
transmission-remote -a 'magnet:?xt=urn:btih:05547db7c0c5fbbe50f00212ee43e9cec5b006fa&dn=Sita+Sings+the+Blues+%281080P+official+release%29&tr=udp%3A%2F%2Ftracker.leechers-paradise.org%3A6969&tr=udp%3A%2F%2Ftracker.openbittorrent.com%3A80&tr=udp%3A%2F%2Fopen.demonii.com%3A1337&tr=udp%3A%2F%2Ftracker.coppersurfer.tk%3A6969&tr=udp%3A%2F%2Fexodus.desync.com%3A6969'
```
```bash
```sh
transmission-remote -a sita.torrent
```
Now let's check that the torrent's been added successfully.
```bash
```sh
transmission-remote -l
```
@@ -53,7 +53,7 @@ To see the torrents, go to /var/lib/transmission/Downloads
If you don't have permission, either add the directory to the group made for your username, or add yourself to the `:transmission` group, or otherwise make sure that you can read that directory, and the user `transmission` can read, write and execute.
E.g.:
```bash
```sh
sudo usermod -aG transmission $USER
```
@@ -63,7 +63,7 @@ Log in again for the changes to take effect (or open a new TTY with `Ctrl+Alt+F2
If you don't want to have a file active as a torrent, get it's number with `transmission-remote -l`, then, if it were number '4', do:
```bash
```sh
transmission-remote -t 4 -r
```
@@ -71,7 +71,7 @@ You can now move the file, and the torrent will not be confused.
To both **r**emove **a**nd **d**elete a file, use `-rad`:
```bash
```sh
transmission-remote -t 4 -rad
```
@@ -82,7 +82,7 @@ If the file is in your home - `~` - but `transmission` is not allowed in your ho
Next, find the torrent's number. You can use multiple numbers, separated with a comma:
```bash
```sh
transmission-remote -t 3,5,8 --move $HOME/music
```
@@ -90,7 +90,7 @@ transmission-remote -t 3,5,8 --move $HOME/music
The `transmission` user has a home configuration file, like any other user, with all the transmission settings.
```bash
```sh
cd /var/lib/transmission/.config/transmission-daemon/
$EDITOR settings.json
@@ -105,14 +105,14 @@ When it doubt, just place the files in `transmission`'s home directory.
Create a torrent of file or directory `Memes` with:
```bash
```sh
sudo chown -R :transmission Memes
transmission-create $(pwd)/Memes
```
Add a tracker to the torrent, to make sure others can find you easily:
```bash
```sh
transmission-create --comment 'My Memes collection' -t 'udp://tracker.publicbt.com:80' -t 'udp://tracker.openbittorrent.com:80' --anonymize Memes
```
@@ -141,7 +141,7 @@ Without the `--anonymize` flag, the torrent file output will have a 'created by'
Add your torrent and notes its number:
```bash
```sh
transmission-remote -a "$file".torrent
transmission-remote -l
transmission-remote -t "$number" -i
@@ -149,19 +149,19 @@ transmission-remote -t "$number" -i
The information in the last command shows that it's not verified, so you can verify with `-v`.
```bash
```sh
transmission-remote -t "$number" -v
```
If transmission cannot find it, then tell it where to find the torrent:
```bash
```sh
transmission-remote -t "$number" --find "$(pwd)"
```
...and of course, make sure the permissions allow transmission to see the target.
```bash
```sh
ls -ld "$file"
```

View File

@@ -7,19 +7,19 @@ tags: [ "networking" ]
If not, try checking out what your local networking interfaces are, then check if they have been picked up:
```bash
```sh
dmesg | grep eth0
```
# Display Active Ports
```bash
```sh
netstat -l
```
...or maybe narrow it down to http:
```bash
```sh
netstat -l | grep http
```

View File

@@ -4,35 +4,35 @@ tags: [ "networking", "web" ]
---
Install nginx:
```bash
```sh
sudo apt-get install nginx
```
```bash
```sh
sudo apt-get enable --now nginx
```
Put a website somewhere:
```bash
```sh
mkdir /var/www/html/mysite/
```
Put an index file there:
```bash
```sh
vim /var/www/html/mysite/index.html
```
Make the owner `www-data`
```bash
```sh
chown -R www-data:www-data /var/www/html/mysite/
```
Make a configuration file for nginx:
```bash
```sh
vim /etc/nginx/sites-available/mysite.conf
```
@@ -54,13 +54,13 @@ server {
Make the site available:
```bash
```sh
ln -s /etc/nginx/sites-available/mysite.conf /etc/nginx/sites-enabled/
```
Test it's working:
```bash
```sh
nginx -t
```
@@ -82,17 +82,17 @@ Buy some DNS online, then check it's working.
*Once it's working*, use certbot:
```bash
```sh
apt install certbot
```
You may need to install an nginx python module:
```bash
```sh
apt install python3-certbot-nginx
```
```bash
```sh
domain=example.com
my_email=me@posteo.uk
certbot --nginx -d "$domain" --non-interactive --agree-tos -m "$my_email"

View File

@@ -7,27 +7,27 @@ tags: [ "networking" ]
Stats on local net usage within domain.
```bash
```sh
iftop -p -n
```
```bash
```sh
whois domain.com
```
Info on domain, whether it's taken, et c.:
```bash
```sh
dig domain.com
```
```bash
```sh
ifconfig
```
Versatile wifi tool:
```bash
```sh
nmcli
```
@@ -35,7 +35,7 @@ nmcli
You want to connect to the internet.
```bash
```sh
sudo iwconfig
```
@@ -61,7 +61,7 @@ Get knowledge of wireless state. The output might be:
This tells you that your ESSID is 'Gandalf WajFaj', and the access point name is 10:05:......
```bash
```sh
nmcli radio
```
@@ -69,23 +69,23 @@ You get an overview of your radio devices.
You're told that eth0 deals with your ethernet and `wlan0` deals with wifi.
`wlan0` is a file which represents your wifi device.
```bash
```sh
nmcli wlan0 wifi rescan
```
```bash
```sh
nmcli device wifi list
```
Now to connect.
```bash
```sh
nmcli device wifi connect [SSID] [your password] [wifi password]
```
Alternatively, you can use
```bash
```sh
nmcli -ask device wifi connect [SSID]
```

View File

@@ -9,13 +9,13 @@ Check with `which pulseaudio`. No output means you need to use alsa (below).
# Volume Control
```bash
```sh
pactl set sink @DEFAULT_SINK@ +5%
```
Find working outputs:
```bash
```sh
aplay -l
```
@@ -30,7 +30,7 @@ amixer scontrols
# Change a Sound setting
```bash
```sh
amixer set Master 5%-
```
@@ -42,19 +42,19 @@ pulseaudio -k && sudo alsa force-reload
Toggle, mute, increase or decrase audio:
```bash
```sh
amixer sset Master toggle
```
```bash
```sh
amixer sset Master mute
```
```bash
```sh
amixer sset Master 5%+
```
```bash
```sh
amixer sset Master 5%-
```
@@ -62,14 +62,14 @@ amixer sset Master 5%-
Start with:
```bash
```sh
alsamixer
```
Then press `F6` to see available Sound cards.
If you find a Sound card called 'PinePhone', then you can select an audio source there, and adjust with:
```bash
```sh
amixer -c PinePhone set 'Headphone' 50%
```

View File

@@ -40,13 +40,13 @@ You can use alsa instead of pulse, but don't unless you're on a Pi.
Since this is run as the mpd user, you'll need to grant that user pulse acceess, often with the user-group `pulse` or `pulse-access`, but your distro may vary.
```bash
```sh
sudo usermod -aG pulse-access mpd
```
Working with mpd will be easier if you have access to its files, so maybe:
```bash
```sh
sudo usermod -aG mpd $USER
```
@@ -56,7 +56,7 @@ sudo usermod -aG mpd $USER
Install `mpd-notification` and then start the service:
```bash
```sh
systemctl --user enable mpd-notification
```

View File

@@ -17,7 +17,7 @@ I couldn't change volume, so in mpd.conf I uncommented the pulse audio lines and
Also, make sure the user mpd is part of the group pulse:
```bash
```sh
sudo adduser mpd pulse
```

View File

@@ -8,31 +8,31 @@ tags: [ "system", "phone" ]
Install:
```bash
```sh
yay -S simple-mtpfs
```
List available phones:
```bash
```sh
simple-mtpfs -l
```
Make a mount point:
```bash
```sh
mkdir phone
```
Check your phone, and tell it to allow access to the USB.
```bash
```sh
simple-mtpfs --device 1 phone
```
## Stop
```bash
```sh
fusermount -u phone
rmdir phone
```

View File

@@ -0,0 +1,90 @@
---
title: "Ansible Basics"
tags: [ "system", "ansible", "orchestration" ]
requires: [ "ssh" ]
---
# Start Locally
Start by doing normal actions on the computer.
Say 'hello' to yourself:
```sh
ansible --module-name=ping localhost
```
Upgrade through the package manager.
`packager=apt` (or `pacman` or `xbps`,...)
```sh
packager=apt
ansible --module-name=${packager} --args "upgrade=yes" localhost
```
This fails because you have not 'become root'.
So, '*become*'!
```sh
ansible --become -m ${packager} -a "upgrade=true" localhost
```
# Passwords
Typing the password is dull.
You might shift it to the command line:
ansible-playbook t.yaml -i hosts.yaml -e "ansible_become_password=${password}"
...this is also dull.
If you have a password store, like `pass`, you can put that in a script:
```sh
echo "#!/bin/sh
pass $HOSTNAME" > pass.sh
chmod u+x !$
ansible --become --module-name=pacman --args "upgrade=true" localhost
```
# Other Hosts
Find something you can `ssh` into.
Ansible will use your `/etc/hosts` file, and `~/.ssh/config`.
## Make a Hosts File
You can use the `.ini` format:
```sh
echo '[phones]
192.168.0.20' > hosts
```
But everything uses `yaml` nowadays, so may as well be consistent:
```yaml
all:
children:
phones:
children:
pine:
ansible_host: 192.168.0.20
```
Check the inventory in yaml format:
```sh
ansible-inventory --list -y -i
```
```sh
ansible-vault view sec.yml --vault-pass-file pass.sh
```
community.general.say voice=en_GB msg="Testing 123"

View File

@@ -0,0 +1,118 @@
---
title: "Ansible with Docker"
tags: [ "system", "ansible", "docker" ]
requires: [ "Docker" ]
---
'Docker module', you say?
No need for that fancy stuff.
We're just going to set up a couple of docker containers and connect to them like any other machine.
Set up two containers: `deb` and `arch`, add them to an `ansible` hosts file, then do a 'ping' to see if they respond.
## Required Packages
- `ansible`
- `jq`
- `docker`
## Debian Container
```sh
docker run -di --rm --name deb --hostname deb debian
docker exec -it deb sh -c 'apt update && apt -y install openssh-server python3 sudo'
```
Generate the host's ssh keys, then start the ssh daemon:
```sh
docker exec -it deb sh -c 'ssh-keygen -A'
docker exec -d deb /usr/sbin/sshd -D
```
## Arch Linux Container
```sh
docker run -di --rm --name arch --hostname arch archlinux
docker exec -it arch sh -c 'pacman -Syu --noconfirm python sudo openssh'
docker exec -it arch sh -c 'ssh-keygen -A'
docker exec -d arch /usr/sbin/sshd -D
```
## `ssh` Keys
Copy across your public ssh key to the container's `authorized_keys` file:
```sh
pubkey=~/.ssh/id_rsa.pub
for hostname in arch deb; do
docker cp $pubkey $hostname:/root/.ssh/authorized_keys
docker exec -it $hostname sh -c "chown -R root:root /root/.ssh/"
docker exec -it $hostname sh -c "chmod -R 700 /root/.ssh/"
done
```
## Hosts File
Find name of containers' IPv4 addresses.
```sh
docker network inspect bridge
```
The output is awful.
Use `jq` to parse the `json`:
```sh
docker network inspect bridge | jq -r '.[].Containers | .[].IPv4Address'
```
Now put those into a host file:
```sh
docker_hosts=hosts.txt
echo '[containers]' > $docker_hosts
docker network inspect bridge | \
jq -r '.[].Containers | .[] | "root@" + .IPv4Address' | \
cut -d/ -f1 >> $docker_hosts
```
You may need to add those host keys to your known hosts file.
Either connect interactively, or (for scripts):
```sh
hosts="$(docker network inspect bridge | jq -r '.[].Containers | .[] | .Name + " " + .IPv4Address' | \
cut -d/ -f1)"
echo "$hosts"
echo "$hosts" | while read hostname ip; do
printf "%s" "$ip"
key="$(docker exec $hostname cat /etc/ssh/ssh_host_ed25519_key.pub)"
echo "$ip $key" >> ~/.ssh/known_hosts
done
```
Check if they ping:
```sh
ansible -i $docker_hosts all -m ping
```
This command produces an irritating warning about the python interpreter (i.e., `python3`).
Make the warning shut-up:
```sh
echo '
[containers:vars]
ansible_python_interpreter=/usr/bin/python3.13' >> $docker_hosts
```
Now the ping is cleaner:
```sh
ansible -i $docker_hosts all -m ping
```

View File

@@ -0,0 +1,75 @@
---
title: "Store Host Password"
tags: [ "system", "ansible" ]
---
Make a hosts file with one host (your computer) and one variable, just to test:
```sh
hosts_file=hosts
fort="$(fortune -s | head -1)"
cowvar=cowsays
echo "[cows]
$HOSTNAME $cowvar='${fort}'" > "${hosts_file}"
```
Now ansible should be able to show that '${cowvar}' in a debug message:
```sh
ansible -i "$hosts_file" -m debug -a "msg='{{ ${cowvar} }}'" $HOSTNAME
```
Now to convert the hosts file to yaml, because it's very fashionable:
```sh
yaml_hosts=hosts.yaml
ansible-inventory -i ${hosts_file} --list -y | tee "${yaml_hosts}"
```
Now you should see where the `cowsays` variable goes.
You can safely place your `sudo` password next to that variable goes with `ansible-vault`, which will encrypt just that string.
```sh
pass="your password"
ansible-vault encrypt_string --name='ansible_sudo_pass' "${pass}"
```
If that works, you can add the password, but in `yaml` format.
You can do this manually, or use `gawk` to add ten spaces in front of the lines:
```sh
pass="your password"
ansible-vault encrypt_string --name='ansible_sudo_pass' "${pass}" | awk '{print " " $0}' >> "${yaml_hosts}"
```
Now to check that the inventory file works okay:
```sh
ansible-inventory -i ${yaml_hosts} --list -y
ansible -i "$hosts_file" -m debug -a "msg='{{ ${cowvar} }}'" $HOSTNAME
```
If that works, you can echo the debug message while becoming root.
Just add the `-J` flag so it will ask for the password:
```sh
ansible -i "${yaml_hosts}" -m debug -a "msg='{{ ${cowvar} }}'" $HOSTNAME --become -J
ansible -i "${yaml_hosts}" -m debug -a "msg={{ ansible_sudo_pass }}" $HOSTNAME --become -J
```
Now you can update using Ansible.
For Arch Linux:
```sh
ansible -i "${yaml_hosts}" -m community.general.pacman -a 'upgrade=true update_cache=true' $HOSTNAME --become -J
```
For Debian:
```sh
ansible -i "${yaml_hosts}" -m ansible.builtin.apt -a 'upgrade=full' $HOSTNAME --become -J
```

View File

@@ -8,25 +8,25 @@ See a file's contents:
Return full contents of a string:
```bash
```sh
awk '{ print }' file
```
Print the first and second column:
```bash
```sh
awk '{print$1$2}'
```
Return every line with the word 'the' (like grep):
```bash
```sh
awk '/the/{print}' file
```
Print everything containing a lowercase letter:
```bash
```sh
awk '/[a-z]/{print}' file
```
@@ -34,7 +34,7 @@ Same with numbers [0-9], or using a caret we can show lines starting with a numb
# Conditionals
```bash
```sh
awk '{ if($1 ~ /123/) print }' file
```
@@ -42,19 +42,19 @@ Check if the first column is equal to 1 or 2 or 3, and if so then print that lin
Grep for 'hawk' in a story:
```bash
```sh
awk '/hawk/' story.txt
```
Return any line with one or more "&" sequences:
```bash
```sh
awk '/&+/' script.sh
```
The pipe is used for 'or', so 'Orcs or drums' would be:
```bash
```sh
awk '/Orcs|Drums/' story.txt
```

View File

@@ -47,7 +47,7 @@ The `rm' program takes arguments, but not `stdin' from a keyboard, and therefore
To fix this, use `xargs` to turn the stdin into an argument.
For example, if we have a list of files called `list.txt' then we could use cat as so:
```bash
```sh
cat list.txt | xargs rm
```
@@ -81,13 +81,13 @@ x=$(( x*x ))
## Finding Duplicate Files
```bash
```sh
find . -type f -exec md5sum '{}' ';' | sort | uniq --all-repeated=separate -w 15 > all-files.txt
```
## Output random characters
```bash
```sh
cat /dev/urandom | tr -cd [:alnum:] | dd bs=1 count=200 status=none && echo
```
@@ -95,13 +95,13 @@ cat /dev/urandom | tr -cd [:alnum:] | dd bs=1 count=200 status=none && echo
Try something out in a random directory in `/tmp` so the files will be deleted when you next shut down.
```bash
```sh
mktemp -d
```
That gives you a random directory to mess about in.
```bash
```sh
dir=$(mktemp -d)
for x in {A..Z}; do
fortune > "$dir"/chimpan-$x

View File

@@ -0,0 +1,20 @@
---
title: "Clean Your Downloads"
tags: [ "system", "tmpfs" ]
---
'Downloads` directory always too full of crap?
Make it a temporary filesystem!
Everything will be deleted whenever you reboot.
```sh
rm -rf ~/Downloads # Be brave!
mkdir Downloads
cp /etc/fstab /tmp/
echo "tmpfs $HOME/Downloads tmpfs defaults,size=1G 0 0" | sudo tee -a /etc/fstab
sudo systemctl daemon-reload # Ignore this if you don't use systemd
sudo mount -a
mount | tail -1
```

View File

@@ -1 +0,0 @@
../basics/cron.md

129
system/cron.md Normal file
View File

@@ -0,0 +1,129 @@
---
title: "cron"
tags: [ "basics", "time" ]
---
# Cronie
The `cronie` program is also known as `crond`.
## Install
```sh
sudo apt search -n ^cron
```
Once installed, search for the service name, and start it.
```sh
sudo systemctl list-unit-files | grep cron
sudo systemctl enable --now $NAME
```
## Usage
Show your current crontab:
```sh
crontab -l
```
You can put this in a file and edit it:
```sh
crontab -l > $filename
echo '39 3 */3 * * /bin/tar czf /tmp/etc_backup.tgz /etc/' >> $filename
```
Then apply that crontab:
```sh
crontab $filename
rm $filename
```
The `cron` program will check your syntax before adding the tab.
Your crontab file sits somewhere in `/var/spool/`.
Probably in `/var/spool/cron`.
## Syntax
`* * * * *`
These five points refer to:
`minute hour day month weekday`
So '3pm every Sunday' would be:
`0 15 * * 7`
Here 'Sunday' is indicated by "7", and '3pm' is 'the 15th hour'.
The minute is '0' (i.e. '0 minutes past three pm').
Doing the same thing, but only in February, would be:
`0 15 * 2 7`
### Variables
`cronie` doesn't know where you live, so to put something in your `$HOME` directory, you have to tell it:
```sh
echo "HOME=$HOME" > $filename
crontab -l >> $filename
crontab $filename
```
`cronie` doesn't know where anything lives, including programs.
You can give it your usual `$PATH` variable like this:
```sh
echo $PATH > $filename
crontab -l >> $filename
crontab $filename
```
Now instead of doing this
`40 */3 * * * /usr/bin/du -sh $HOME/* | sort -h > $HOME/sum.txt`
You can simply do this:
`40 */3 * * * du -sh $HOME/* | sort -h > $HOME/sum.txt`
## Run as Root
You can execute a script as root by putting it into a directory, instead of in the tab.
Look at the available cron directories:
```sh
ls -d /etc/cron.*
```
Make a script which runs daily:
```sh
f=apt_update.sh
echo '#!/bin/bash' > $f
echo 'apt update --yes' >> $f
chmod +x $f
sudo mv $f /etc/cron.daily/
```
### Testing with runparts
Run-parts runs all executable scripts in a directory.
```sh
run-parts /etc/cron.hourly
```
# Troubleshooting
### `date` Commands
Cron doesn't understand the `%` sign, so if you want to use `date +%R`, then it should be escaped with a backslash: `date +\%R`.

View File

@@ -7,13 +7,13 @@ tags: [ "system", "deduplicate", "maintenance", "storage" ]
Ask if a directory has duplicates (`rdfind` will not delete anything):
```bash
```sh
rdfind $dir
$EDITOR results.txt
```
Replace the duplicated files with [hard links](../basics/hard_links.md).
```bash
```sh
rdfind -makehardlinks true $dir
```

View File

@@ -9,19 +9,19 @@ Install the package `xdg-utils`, then make very liberal use of the tab button.
Ask what type of application opens an mkv file:
```bash
```sh
xdg-mime query default video/mkv
```
Same with pdf:
```bash
```sh
xdg-mime query default application/pdf
```
Ask what file-type `book.pdf` uses.
```bash
```sh
xdg-mime query filetype *book.pdf*
```
@@ -29,7 +29,7 @@ xdg-mime query filetype *book.pdf*
Set the mime type of mp4 videos to mpv.
```bash
```sh
xdg-mime default mpv.desktop video/mp4
```
@@ -37,7 +37,7 @@ You'll need to use the tab key a lot here, and remember many items start with `o
You can use an asterisk for everything in a category.
```bash
```sh
xdg-mime default org.gnome.font-viewer.desktop font/\*
```

View File

@@ -7,25 +7,25 @@ tags: [ "file browser", "TUI" ]
If you don't have a `~/.config/lf/lfrc` file, you can probably find an example in `/usr/share/examples/lf`.
```bash
```sh
cp -r /usr/share/examples/lf ~/.config/
```
Go straight to root with two keys.
```bash
```sh
map g/ cd /
```
Have lf open a file with the default program when you press 'o', using the program `mimeo`.
```bash
```sh
map o &mimeo $f
```
Change that default text editor to look at the extension first.
```bash
```sh
cmd open ${{
case $(file --mime-type $f -b) in
application/x-sc) sc-im $fx;;
@@ -52,7 +52,7 @@ That leaves it as a small initial pane, a medium pane, and a large pane for file
The standard renaming is bad, because you have to re-type the file extension.
Use this instead:
```bash
```sh
# rename current file without overwrite
cmd rename %echo 'name: ' ; read name ; extension="${f##*.}" && newname="$name.$extension"; [ "$f" = "$extension" ] && newname="$name"; [ ! -e "$newname" ] && mv "$f" "$newname" || echo file exists
map r push :rename<enter>
@@ -65,7 +65,7 @@ If you try to rename `image_1.png` with this command, you can type in `cats`, an
First, install `ueberzug` (to show images).
Then clone the lfrun repo.
```bash
```sh
git clone https://github.com/cirala/lfimg.git
cd lfimg

View File

@@ -23,7 +23,8 @@ Using four spaces will not work!
## Dependency Files
Now we've made a `README.md` file, we can show how a makefile looks in the README:
Now we've made a `README.md` file, we can show how a makefile looks in the README file.
Add these lines to the `Makefile`:
```make
README.md: Makefile
@@ -44,7 +45,7 @@ Note the order:
Notice that the file above can print into the README by using `echo "" >> $@`.
The `$@` stands for 'the file which we want', and `$<` stands for 'the first dependency file'.
The `make` program starts by replacing those variables, and the result it:
The `make` program starts by replacing those variables, so when you run `make`, the program looks like this:
```make
README.md: Makefile
@@ -54,7 +55,6 @@ README.md: Makefile
cat Makefile >> README.md
echo '```' >> README.md
```
| Sigil | Meaning |
@@ -71,7 +71,6 @@ README.md: Makefile
You can assign a variable normally, but must refer to it in brackets.
```make
storage_directory = backups
@@ -182,4 +181,3 @@ In this case, the makefile can see that `backup` depends on the current backup f
- [File patterns](Makefiles/patterns.md)
- [Makefile graphs](Makefiles/graph-easy.md)
- [In-build help](Makefiles/help.md)
- [Makefile graphs](Makefiles/graph-easy.md)

View File

@@ -7,7 +7,7 @@ If you have `graph-easy` (often in the package `perl-graph-easy` or similar), yo
Start with the command to 'make all targets' (`-B`), and 'do a dummy run' (`-n`) with debug into (`-d`):
```bash
```sh
make -Bnd
make -Bnd | make2graph
make -Bnd | make2graph | graph-easy --boxart

View File

@@ -1,4 +1,3 @@
---
title: "Makefile Patterns"
tags: [ "system", "make" ]

View File

@@ -0,0 +1,98 @@
---
title: "Python Projects with Makefiles"
tags: [ "tutorial", "system", "makefiles", "graphviz", "python" ]
requires: [ "Makefiles" ]
---
If you have a python script which requires a packages - e.g. `graphviz` - you can automate the setup with a `Makefile`.
The `Makefile` will:
1. Make three copies of an 8-line installer script.
2. Use one of the installer script to install local packages.
3. Install a symbolic link to python.
3. Make a script called `activate`, which tells python to use
# Context
Python coders don't like updating their projects, they just expect everyone to install the same version of everything that they have.
Historically, people dealt with this by installing only half a dozen copies of `graphviz`; but now each python project uses a local environment, with a local copy of `graphviz`, which means everyone gets to install a new copy of `graphviz` every time they try out a project.
Downloading 40MB of software for each 40-line script you write is called 'virtual environments' because it sounds cool.
We can make it even cooler with `make`, but not yet, because python - like the fae of old - will not fetch anything until you know its true name.
# Setup
```sh
command -v python
realpath `!!`
```
You must reveal that true path, because `python` is always a relative symbolic link, to an absolute symbolic link, which leads to a shortcut.
We can finally let `make` know how to invoke python, and where it will install `graphviz`.
If your python's version is '3.14', then python needs its packages placed in `${somewhere}/lib/python3.14/site-packages/`.
You must create a new, local, name for these packages, because - like the fey of old - python demands a private name in return for revealing its true name.
I'll call mine `camelot`, because the path is long and arduous.
Set up the Makefiles like this:
```make
py_link != command -v python
py != realpath $(py_link)
version != basename $(py)
virtenv = camelot
```
Now you can ask for a local `pip` script, which can install the python packages:
```make
[...]
$(virtenv)/bin/pip:
$(py) -m venv $(virtenv)
```
Finally, list the packages you want in `requirements.txt`, and make `pip` install from it.
```sh
ppkg=graphviz
echo ${ppkg} > requirements.txt
```
```make
[...]
pkgs = $(virtenv)/lib/$(version)/site-packages/
$(pkgs): $(virtenv)/bin/pip
$(pkgs): requirements.txt
$(virtenv)/bin/pip install -r $<
```
The complete Makefile looks like this:
```make
all: .default
py_link != command -v python
py != realpath $(py_link)
version != basename $(py)
virtenv = camelot
$(virtenv)/bin/pip:
$(py) -m venv $(virtenv)
pkgs = $(virtenv)/lib/$(version)/site-packages/
$(pkgs): $(virtenv)/bin/pip
$(pkgs): requirements.txt
$(virtenv)/bin/pip install -r $<
.PHONY: .default
.default: $(pkgs)
```

View File

@@ -17,10 +17,10 @@ Remove yourself from all groups, and add yourself back to only `wheel`, `audio`,
sudo usermod --groups wheel,audio,$USER
```
Add yourself to the `wheel` group:
Add yourself to the `docker` group:
```sh
su root -c "usermod --append --groups wheel $USER"
su root -c "usermod --append --groups docker $USER"
```
Add yourself to the `network` group:
@@ -28,5 +28,11 @@ Add yourself to the `network` group:
sudo usermod -aG network $USER
```
The changes will not take effect until you log in again, so reboot or log into `localhost` with [ssh](../networking/ssh.md).
The changes have not taken effect, so log into your own account again with `su`:
```sh
groups
sudo su $USER
groups
```

Some files were not shown because too many files have changed in this diff Show More