Compare commits

..

27 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
114 changed files with 1443 additions and 775 deletions

View File

@@ -6,7 +6,7 @@ FZF != command -v sk || command -v fzy || command -v fzf || \
spill_contents = sed -e '1,/---/d' 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) | \ @awk 'BEGIN {FS = ":.*?## "} /^[0-9a-zA-Z._-]+:.*?## / {printf "\033[36m%s\033[0m : %s\n", $$1, $$2}' $(MAKEFILE_LIST) | \
sort | \ sort | \
column -s ':' -t column -s ':' -t
@@ -19,6 +19,8 @@ categories = $(patsubst %/, %, $(dirs))
databases = $(patsubst %, .dbs/%.rec, $(categories)) databases = $(patsubst %, .dbs/%.rec, $(categories))
default += $(databases) default += $(databases)
default += db.rec
default += .dbs/map.fmt
$(foreach dir, $(categories), \ $(foreach dir, $(categories), \
$(eval .dbs/$(dir).rec: $(wildcard $(dir)/*)) \ $(eval .dbs/$(dir).rec: $(wildcard $(dir)/*)) \
@@ -26,6 +28,7 @@ $(foreach dir, $(categories), \
.dbs/: .dbs/:
mkdir $@ mkdir $@
$(databases): .dbs/%.rec: %/ | .dbs/ $(databases): .dbs/%.rec: %/ | .dbs/
$(info making $(@F)) $(info making $(@F))
for entry in $(shell find $< -type f -name "*.md") ; do \ for entry in $(shell find $< -type f -name "*.md") ; do \
@@ -38,6 +41,7 @@ $(databases): .dbs/%.rec: %/ | .dbs/
# This two-variable read can only happen because of the quotes in the titles. # This two-variable read can only happen because of the quotes in the titles.
db.rec: $(databases) db.rec: $(databases)
$(warning rebuilding from $? )
printf '%s\n' '%rec: guide' > $@ printf '%s\n' '%rec: guide' > $@
printf '%s\n' '%key: title' >> $@ printf '%s\n' '%key: title' >> $@
printf '%s\n' '%type: requires rec guide' >> $@ printf '%s\n' '%type: requires rec guide' >> $@
@@ -55,10 +59,8 @@ db.rec: $(databases)
recfix --sort $@ recfix --sort $@
$(info Created main database: $@) $(info Created main database: $@)
default += db.rec
.git/info/exclude: $(default) .git/info/exclude: $(default)
echo $^ | tr ' ' '\n' > $@ @echo $^ | tr ' ' '\n' > $@
default += .git/info/exclude default += .git/info/exclude
@@ -76,6 +78,18 @@ article: ## Write an article
printf '%s\n\n' '---' >> $$path/$$filename.md ;\ printf '%s\n\n' '---' >> $$path/$$filename.md ;\
$(EDITOR) +5 "$$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 .PHONY: clean
clean: ## Remove all generated files clean: ## Remove all generated files
$(RM) $(default) $(RM) $(default)

View File

@@ -44,6 +44,8 @@ They should not assume the reader knows much beyond common terminal commands, an
People should be able to read an article from the beginning, then keep going until the end, and then stop. 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. 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 ## Be Opinionated
- Guides should not ask the reader to select options half-way through. - Guides should not ask the reader to select options half-way through.

View File

@@ -4,43 +4,43 @@ tags: [ "basics", "time" ]
--- ---
Install with: Install with:
```bash ```sh
sudo apt install at sudo apt install at
``` ```
Enable the daemon service with: Enable the daemon service with:
```bash ```sh
sudo systemctl enable --now atd sudo systemctl enable --now atd
``` ```
Then jobs can be specified with absolute time, such as: Then jobs can be specified with absolute time, such as:
```bash ```sh
at 16:20 at 16:20
``` ```
```bash ```sh
at noon at noon
``` ```
```bash ```sh
at midnight at midnight
``` ```
```bash ```sh
at teatime at teatime
``` ```
Type in your command, e.g.: Type in your command, e.g.:
```bash ```sh
touch /tmp/$FILE.txt touch /tmp/$FILE.txt
``` ```
The jobs can also be specified relative to the current time: The jobs can also be specified relative to the current time:
```bash ```sh
at now +15 minutes at now +15 minutes
``` ```
@@ -50,7 +50,7 @@ Finally, accept the jobs with ^D.
Display a list of commands to run with: Display a list of commands to run with:
```bash ```sh
atq atq
``` ```
@@ -58,7 +58,7 @@ atq
This will print all pending IDs. Remove a job by the ID with: This will print all pending IDs. Remove a job by the ID with:
```bash ```sh
atrm 2 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. Automatically add a job for later, by setting the date, then using echo for the command.
```bash ```sh
t="$(date -d "2 minutes" +%R)" t="$(date -d "2 minutes" +%R)"
echo "fortune > ~/$FILE" | at "$t" echo "fortune > ~/$FILE" | at "$t"
watch cat $FILE 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'): 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 pwd
``` ```
Have a look at what is here: Have a look at what is here:
```bash ```sh
ls 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: Have a look at **a**ll the files:
```bash ```sh
ls -a 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: Change directory (`cd`) down one level:
```bash ```sh
cd .. cd ..
``` ```
Look where you are again with `pwd`, then go back up. Use `ls`, and if you see `bob`, then: Look where you are again with `pwd`, then go back up. Use `ls`, and if you see `bob`, then:
```bash ```sh
cd bob cd bob
``` ```
Move around the directories. The place at the bottom is the 'root', and is known as `/`. Go to the root: Move around the directories. The place at the bottom is the 'root', and is known as `/`. Go to the root:
```bash ```sh
cd / cd /
``` ```
Do `ls` again and `cd` into `etc`. Look at how much space those folders are taking up: Do `ls` again and `cd` into `etc`. Look at how much space those folders are taking up:
```bash ```sh
du iptables du iptables
``` ```
That's the number of kilobytes the file is taking up. That's the number of kilobytes the file is taking up.
Do the same again, but in a human-readable format: Do the same again, but in a human-readable format:
```bash ```sh
du -h iptables du -h iptables
``` ```
The `du` program has `-h` for 'human', '-s' for 'short', and a bunch of other commands. 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: Have a look at the manual and try another command:
```bash ```sh
man du 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: Now you can try to gain super-powers and take over the system:
```bash ```sh
sudo -i 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. 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: Best to exit out of the root account:
```bash ```sh
exit exit
``` ```
Go find a file that isn't a directory. You can tell which is which with: Go find a file that isn't a directory. You can tell which is which with:
```bash ```sh
ls -l ls -l
``` ```
A directory starts with a 'd', like this: A directory starts with a 'd', like this:
```bash ```sh
drwxr-xr-x 79 root root 4096 Jan 3 05:15 /etc/ drwxr-xr-x 79 root root 4096 Jan 3 05:15 /etc/
``` ```
A standard file starts with '-', like this: A standard file starts with '-', like this:
```bash ```sh
`-rw-r--r-- 1 root root 8 Dec 11 17:26 hostname` `-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: Look inside the file /etc/hostname to find out your computer's name:
```bash ```sh
cat /etc/hostname cat /etc/hostname
``` ```
Print out the words "hello world": Print out the words "hello world":
```bash ```sh
echo "hello world" echo "hello world"
``` ```
Move back to your home directory: Move back to your home directory:
```bash ```sh
cd cd
``` ```
Take the words 'hello world', and put them in 'my_file': Take the words 'hello world', and put them in 'my_file':
```bash ```sh
echo 'hello world' > my_file echo 'hello world' > my_file
``` ```
Measure the disk usage of that file, then put the results at the bottom of the file: Measure the disk usage of that file, then put the results at the bottom of the file:
```bash ```sh
du $FILE >> $FILE du $FILE >> $FILE
``` ```
And check the results: And check the results:
```bash ```sh
cat $FILE 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: Look at your file's owner:
```bash ```sh
ls -l $FILE 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: Take your file and change the owner to root:
```bash ```sh
sudo chown root $FILE sudo chown root $FILE
``` ```
Change the same file so it's owned by the group 'audio': Change the same file so it's owned by the group 'audio':
```bash ```sh
sudo chown :audio $FILE sudo chown :audio $FILE
``` ```
Check you did that correctly: Check you did that correctly:
```bash ```sh
ls -l my_file 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: 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 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: Look at which groups you're in:
```bash ```sh
groups groups
``` ```
Change the file so that members of the audio group can write to the file: Change the file so that members of the audio group can write to the file:
```bash ```sh
sudo chmod g+w $FILE sudo chmod g+w $FILE
``` ```
Check you got it right with `ls -l`: Check you got it right with `ls -l`:
```bash ```sh
-rw-rw-r-- 1 root audio 0 Jan 3 19:20 my_file -rw-rw-r-- 1 root audio 0 Jan 3 19:20 my_file
``` ```
Try to delete the file again: Try to delete the file again:
```bash ```sh
rm my_file 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. 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: Use `-a` to **a**ppend, and `-G`, to say you're modifying groups:
```bash ```sh
sudo usermod -a -G audio [ your username here ] 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': Make a directory called 'new test':
```bash ```sh
mkdir 'new test' mkdir 'new test'
``` ```
Make two directories, called 'A', and 'Z': Make two directories, called 'A', and 'Z':
```bash ```sh
mkdir A Z mkdir A Z
``` ```
Make a single directory called 'A Z' Make a single directory called 'A Z'
```bash ```sh
mkdir 'A Z' 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': 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 du -sch * > A/'disk usage'.txt
``` ```
Look at your file: Look at your file:
```bash ```sh
cat A/'disk usage.txt' 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: 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 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: Start the manual:
```bash ```sh
man du 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': 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 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': Remove the directory 'Z':
```bash ```sh
rmdir Z rmdir Z
``` ```
Remove the directory 'Z': Remove the directory 'Z':
```bash ```sh
rmdir Z rmdir Z
``` ```
And then remove all the rest: And then remove all the rest:
```bash ```sh
rmdir * 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: 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 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 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: If unsure, ask where a program is:
```bash ```sh
whereis yum whereis yum
``` ```
```bash ```sh
whereis apt 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: Set a reminder of your package manager:
```bash ```sh
echo my package manager is yum | lolcat echo my package manager is yum | lolcat
``` ```
If that failed it's because you don't have `lolcat` installed. If that failed it's because you don't have `lolcat` installed.
Install lolcat: Install lolcat:
```bash ```sh
sudo apt install lolcat sudo apt install lolcat
``` ```
@@ -330,13 +330,13 @@ Try the same command again.
Search for things you want, like `libreoffice`, or `gimp`: Search for things you want, like `libreoffice`, or `gimp`:
```bash ```sh
apt search libreoffice apt search libreoffice
``` ```
... then install one of them with: ... then install one of them with:
```bash ```sh
apt install $PROGRAM apt install $PROGRAM
``` ```

View File

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

View File

@@ -5,32 +5,32 @@ tags: [ "basics", "format", "json" ]
Put output into column. Put output into column.
```bash ```sh
du -h /etc/* | column du -h /etc/* | column
``` ```
Reformat file with an explicit separator (`-s`): Reformat file with an explicit separator (`-s`):
```bash ```sh
column -ts: /etc/passwd column -ts: /etc/passwd
``` ```
Give columns names (`-N`), so you can hide some (`-H`): 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 column -ts: -N User,PW,UID,GID,Description,Home,shell -H PW,GID /etc/passwd
``` ```
Reorder with `-O` (unspecified items remain): 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 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`: 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 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 # While and Until
This prints from 1 until 9. This prints from 1 until 9.
```bash ```sh
COUNTER=1 COUNTER=1
while [ $COUNTER -lt 2 ]; do while [ $COUNTER -lt 2 ]; do
> ((COUNTER++)) > ((COUNTER++))
@@ -58,7 +58,7 @@ There's also 'until', which stops when something is true, rather than keeping go
# For # For
```bash ```sh
for i in $( ls ); do for i in $( ls ); do
> du -sh $i > du -sh $i
> done > done
@@ -70,19 +70,19 @@ The sequences tool counts up from X in jumps of Y to number Z.
Count from 1 to 10. Count from 1 to 10.
```bash ```sh
seq 10 seq 10
``` ```
Count from 4 to 11. Count from 4 to 11.
```bash ```sh
seq 4 11 seq 4 11
``` ```
Count from 1 to 100 in steps of 5. Count from 1 to 100 in steps of 5.
```bash ```sh
seq 1 5 100 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. Compose a statement for execution.
```bash ```sh
x='echo $y' x='echo $y'
echo $x echo $x
y=dragon y=dragon
@@ -14,7 +14,7 @@ eval "$x"
The results remain in the current shell, unlike sub-shells. The results remain in the current shell, unlike sub-shells.
```bash ```sh
b=basilisk b=basilisk
sh -c 'echo $b' sh -c 'echo $b'
eval "g=goblin" eval "g=goblin"

View File

@@ -11,20 +11,20 @@ This ID is called the 'inode'.
Create a file, and a hard link: Create a file, and a hard link:
```bash ```sh
fortune > $file_1 fortune > $file_1
mkdir -p x/y/z/ mkdir -p x/y/z/
ln $file_1 x/y/z/$file_2 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`: 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 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: 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 fortune | tee x/y/z/$file_2
cat $file_1 cat $file_1
cat x/y/z/$file_2 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 # Graphical Programs
```bash ```sh
xkill xkill
``` ```
@@ -17,7 +17,7 @@ Then click on the application which you want to kill.
To kill a program, find it with: To kill a program, find it with:
```bash ```sh
pgrep discord pgrep discord
``` ```
@@ -25,7 +25,7 @@ This will give you the UUID, e.g. `19643`.
Kill the program with: Kill the program with:
```bash ```sh
kill 19643 kill 19643
``` ```
@@ -33,7 +33,7 @@ kill 19643
To see an ordered list of termination signals: To see an ordered list of termination signals:
```bash ```sh
kill -l kill -l
``` ```
@@ -49,7 +49,7 @@ Higher numbers are roughly equivalent to insistence.
For example: For example:
```bash ```sh
kill -1 3498 kill -1 3498
``` ```
@@ -57,7 +57,7 @@ This roughly means 'maybe stop the program, if you can, maybe reload'.
Or the famous: Or the famous:
```bash ```sh
kill -9 3298 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: See a full list with:
```bash ```sh
cat /usr/share/i18n/SUPPORTED cat /usr/share/i18n/SUPPORTED
``` ```
Take the first portion to generate full locale information for a region: Take the first portion to generate full locale information for a region:
```bash ```sh
locale-gen ru_RU.UTF-8 locale-gen ru_RU.UTF-8
``` ```
Then use this for the current shell session with Then use this for the current shell session with
```bash ```sh
LANG=ru_RU.utf8 LANG=ru_RU.utf8
``` ```
Expand this to the entire system with: Expand this to the entire system with:
```bash ```sh
export LANG=ru_RU.utf8 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: Make it permanent for the entire system by editing:
```bash ```sh
sudo vim /etc/defaults/locale sudo vim /etc/defaults/locale
``` ```

View File

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

View File

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

View File

@@ -9,7 +9,7 @@ This & That
Refer to 'that last thing', and 'the first thing': Refer to 'that last thing', and 'the first thing':
```bash ```sh
fortune -l > file1 fortune -l > file1
cat !$ | tr -d u cat !$ | tr -d u
diff !^ !$ diff !^ !$
@@ -17,7 +17,7 @@ diff !^ !$
**NB:** this can go wrong: **NB:** this can go wrong:
```bash ```sh
ls -l file1 file2 ls -l file1 file2
cat !^ cat !^
``` ```
@@ -36,7 +36,7 @@ Input Run-Commands (`~/.inputrc`)
Alias Expansion Alias Expansion
--------------- ---------------
```bash ```sh
echo '"\C- ": shell-expand-line' >> ~/.inputrc echo '"\C- ": shell-expand-line' >> ~/.inputrc
exec bash exec bash
``` ```
@@ -47,7 +47,7 @@ Try just `ls`, then 'Control + Space'.
Glob Expansion (`*`) Glob Expansion (`*`)
-------------------- --------------------
```bash ```sh
echo '"\C-x": glob-expand-word' >> ~/.inputrc echo '"\C-x": glob-expand-word' >> ~/.inputrc
exec bash exec bash
ls *<C-x> ls *<C-x>
@@ -63,13 +63,13 @@ Arbitrary Commands
Use `\n` as a 'newline' character to automatically press `<Return>`. Use `\n` as a 'newline' character to automatically press `<Return>`.
```bash ```sh
echo 'Control-y: "| lolcat\n"' >> ~/.inputrc echo 'Control-y: "| lolcat\n"' >> ~/.inputrc
exec bash exec bash
ls<C-y> ls<C-y>
``` ```
```bash ```sh
Control-l: "\C-u clear -x && ls\n" Control-l: "\C-u clear -x && ls\n"
exec bash exec bash
cd /etc/<C-l> cd /etc/<C-l>
@@ -78,7 +78,7 @@ cd /etc/<C-l>
Readline as Vi Readline as Vi
-------------- --------------
```bash ```sh
echo 'set editing-mode vi' >> ~/.inputrc echo 'set editing-mode vi' >> ~/.inputrc
echo 'set keymap vi-insert' >> ~/.inputrc echo 'set keymap vi-insert' >> ~/.inputrc
exec bash 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. If you tried the previous commands then they will not work any more, because the `vi`-commands overwrite the other commands.
Remove them. Remove them.
```bash ```sh
sed '/ vi/d' ~/.inputrc sed '/ vi/d' ~/.inputrc
sed -i '/ 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. 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: But you can show the current mode in the prompt:
```bash ```sh
echo 'set show-mode-in-prompt on' >> ~/.inputrc echo 'set show-mode-in-prompt on' >> ~/.inputrc
exec bash exec bash
``` ```
Set new symbols for normal and insert mode: Set new symbols for normal and insert mode:
```bash ```sh
echo 'set vi-ins-mode-string " "' >> ~/.inputrc echo 'set vi-ins-mode-string " "' >> ~/.inputrc
echo 'set vi-cmd-mode-string " "' >> ~/.inputrc echo 'set vi-cmd-mode-string " "' >> ~/.inputrc
``` ```
@@ -148,33 +148,33 @@ Fuzzy Sort
Check your repos for `sk-im`, and install. Check your repos for `sk-im`, and install.
The program is called `sk`. The program is called `sk`.
```bash ```sh
FUZZY=sk FUZZY=sk
``` ```
If you don't have it, `fzy` or `fzf` should work the same way. If you don't have it, `fzy` or `fzf` should work the same way.
```bash ```sh
FUZZY=fzy FUZZY=fzy
``` ```
Find some 'read-config' files to check out: Find some 'read-config' files to check out:
```bash ```sh
find . -maxdepth 2 -name "*rc" find . -maxdepth 2 -name "*rc"
find . -maxdepth 2 -name "*rc" | $FUZZY find . -maxdepth 2 -name "*rc" | $FUZZY
``` ```
And read some: And read some:
```bash ```sh
PAGER='less -R' PAGER='less -R'
$PAGER "$(find . -maxdepth 2 -name "*rc" | $FUZZY)" $PAGER "$(find . -maxdepth 2 -name "*rc" | $FUZZY)"
``` ```
Make the change long-term: Make the change long-term:
```bash ```sh
alias rrc='$PAGER "$(find . -maxdepth 2 -name "*rc" | sk)"' alias rrc='$PAGER "$(find . -maxdepth 2 -name "*rc" | sk)"'
alias | grep rrc= >> ~/.bash_aliases 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: To make a soft link to a file in the current directory, linking is easy:
```bash ```sh
fortune > $file_1 fortune > $file_1
ln -s $file_1 $link_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: 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 cd dir_1
ln -s ../file_1 link_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: 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 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. Since it's just an address, you can delete the original file, then make another.
```bash ```sh
rm file_1 rm file_1
ls -l dir_1/ ls -l dir_1/
fortune > file_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): 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 ln -s -f ../dir_1/file_1 dir_2/link_2
cat 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: Set time to synchronize with an ntp server:
```bash ```sh
timedatectl set-ntp true 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: 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 sudo ln -sf /usr/share/zoneinfo/Europe/Belgrade /etc/localtime
``` ```
@@ -28,31 +28,31 @@ sudo ln -sf /usr/share/zoneinfo/Europe/Belgrade /etc/localtime
See local time, language and character settings with: See local time, language and character settings with:
```bash ```sh
locale locale
``` ```
List available locales with: List available locales with:
```bash ```sh
locale -a locale -a
``` ```
To see additional locales which are available (but not necessarily installed): To see additional locales which are available (but not necessarily installed):
```bash ```sh
cat /usr/share/i18n/SUPPORTED cat /usr/share/i18n/SUPPORTED
``` ```
Set a supported locale with: Set a supported locale with:
```bash ```sh
locale-gen pl_PL.UTF-8 locale-gen pl_PL.UTF-8
``` ```
Then set that language, with: Then set that language, with:
```bash ```sh
LANG=pl_PL.UTF-8 LANG=pl_PL.UTF-8
``` ```
@@ -62,7 +62,7 @@ LANG=pl_PL.UTF-8
Glimpse an overview with: Glimpse an overview with:
```bash ```sh
ntpq -p 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. If your clock drifts too far from the right time, it will not reset happily.
For it to reset like this: For it to reset like this:
```bash ```sh
sudo ntpd -q -g -x -n 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: 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 | \ tree -tf --dirsfirst --gitignore --noreport --charset ascii | \
sed -e 's/| \+/ /g' \ sed -e 's/| \+/ /g' \
-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. Let's get some entries with 'getent', e.g. passwd or group.
```bash ```sh
getent passwd getent passwd
``` ```
```bash ```sh
getent group getent group
``` ```
Obviously: Obviously:
```bash ```sh
getent shadow getent shadow
``` ```
## Examples ## Examples
```bash ```sh
sudo adduser maestro 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 This depends upon the settings in the /etc/default/useradd file and /etc/login.defs
```bash ```sh
sudo useradd -m pinkie sudo useradd -m pinkie
``` ```
add user 'pinkie' with a home directory add user 'pinkie' with a home directory
```bash ```sh
sudo adduser -m -e 2017-04-25 temp sudo adduser -m -e 2017-04-25 temp
``` ```
add expiry date to user add expiry date to user
```bash ```sh
userdel maestro userdel maestro
``` ```
delete maestro delete maestro
```bash ```sh
userdel -r maestro userdel -r maestro
``` ```
delete maestro and hir homefolder delete maestro and hir homefolder
```bash ```sh
groups groups
``` ```
find which group you are in find which group you are in
```bash ```sh
id id
``` ```
same same
```bash ```sh
id -Gn maestro id -Gn maestro
``` ```
Find which groups maestro is in Find which groups maestro is in
```bash ```sh
deluser --remove-home maestro deluser --remove-home maestro
``` ```
delete user maestro delete user maestro
```bash ```sh
usermod -aG sudo maestro usermod -aG sudo maestro
``` ```
Add user maestro to group sudo: Add user maestro to group sudo:
```bash ```sh
cat /etc/passwd cat /etc/passwd
``` ```
list users' passwords (and therefore users) list users' passwords (and therefore users)
```bash ```sh
groupadd awesome 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. There are user accounts for processes such as 'bin' and 'nobody' which are locked, so they're unusable.
```bash ```sh
passwd -l bin passwd -l bin
``` ```
Lock the user 'bin'. Lock the user 'bin'.
```bash ```sh
more /etc/passwd | grep games 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. 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' groupdel learners | delete the group 'learners'
``` ```
```bash ```sh
gpasswd -d pi games | remove user 'pi' from the group 'games' gpasswd -d pi games | remove user 'pi' from the group 'games'
``` ```
```bash ```sh
id games id games
``` ```
find the id number of group 'games' (60) find the id number of group 'games' (60)
```bash ```sh
usermod -aG sudo maestro usermod -aG sudo maestro
``` ```
@@ -156,7 +156,7 @@ Alternatively, change the shell in /etc/passwd.
Usermod also lets you change a user's username: Usermod also lets you change a user's username:
```bash ```sh
usermod -l henry mark usermod -l henry mark
``` ```
@@ -170,7 +170,7 @@ usermod -L henry
-G or -groups adds the user to other groups: -G or -groups adds the user to other groups:
```bash ```sh
usermod -G sudo henry 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: We can use groupmod, like like usermod, e.g. to change a name:
```bash ```sh
groupmod -n frontoffice backoffice groupmod -n frontoffice backoffice
``` ```
Delte a group: Delte a group:
```bash ```sh
groupdel frontoffice groupdel frontoffice
``` ```
@@ -200,37 +200,37 @@ groupdel frontoffice
See list of logged on users. See list of logged on users.
```bash ```sh
w w
``` ```
See last logons: See last logons:
```bash ```sh
last last
``` ```
or all logon attempts, including bad attempts: or all logon attempts, including bad attempts:
```bash ```sh
lastb lastb
``` ```
List recently accessed files: List recently accessed files:
```bash ```sh
last -d last -d
``` ```
See files opened by steve See files opened by steve
```bash ```sh
lsof -t -u steve lsof -t -u steve
``` ```
See files opened by anyone but steve See files opened by anyone but steve
```bash ```sh
lsof -u ^steve 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: Let's start with files executable by user:
```bash ```sh
sudo find / -type f -perm -g=s -ls sudo find / -type f -perm -g=s -ls
``` ```
And then those executable by the group: And then those executable by the group:
```bash ```sh
find / -type f -perm -g=s -ls find / -type f -perm -g=s -ls
``` ```
And finally, worrying files, executable by anyone as if sie were the owner: And finally, worrying files, executable by anyone as if sie were the owner:
```bash ```sh
find / -xdev \( -o -nogroup \) -print find / -xdev \( -o -nogroup \) -print
``` ```
@@ -260,7 +260,7 @@ Then have a look at resource usage per user.
# SGID # SGID
```bash ```sh
sudo chmod u+s process.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. 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 yes | $INSTALL_SCRIPT_FILE.sh
``` ```
This works best for disposable systems, like VMs or containers. 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. Try this on a live system, and you might find out that you should have read that message fully.
```bash ```sh
yes | yay 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

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

View File

@@ -1,6 +1,7 @@
--- ---
title: "git-lfs" title: "git-lfs"
tags: [ "data", "git" ] tags: [ "data", "git" ]
requires: [ "git" ]
--- ---
Git Large File Storage ('LFS') needs to change your `~/.gitconfig` to check out those binary files: 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: Check out the sample hooks:
```bash ```sh
cd $GIT_REPO cd $GIT_REPO
ls .git/hooks ls .git/hooks
head .git/hooks/pre-commit.sample 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: Add a hook to check the shell scripts in `$GIT_REPO` before making a commit:
```bash ```sh
echo '#!/bin/sh echo '#!/bin/sh
shellcheck *.sh' > .git/hooks/commit-msg shellcheck *.sh' > .git/hooks/commit-msg
chmod u+x .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. 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 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: Then go and create a new git somewhere else:
```bash ```sh
cd ..;mkdir sub-1;cd sub-1;git init --bare 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. Finally, you can clone this repo from your original.
```bash ```sh
git clone ../subtest git clone ../subtest
``` ```

View File

@@ -6,7 +6,7 @@ tags: [ "data", "GPG" ]
Generate keys: Generate keys:
```bash ```sh
gpg --full-generate-key gpg --full-generate-key
``` ```
@@ -14,7 +14,7 @@ Follow the guide.
# Encrypting a file # Encrypting a file
```bash ```sh
gpg -r malinfreeborn@posteo.net -e file gpg -r malinfreeborn@posteo.net -e file
``` ```
@@ -25,7 +25,7 @@ Check you have an encrypted version of your file.
# Changing Expiration Dates # Changing Expiration Dates
```bash ```sh
gpg --list-keys gpg --list-keys
# or... # or...
gpg -k gpg -k
@@ -37,13 +37,13 @@ gpg -k
Make a password with a password (cypher encryption). Make a password with a password (cypher encryption).
```bash ```sh
gpg -c --output passwords.txt gpg -c --output passwords.txt
``` ```
or or
```bash ```sh
gpg -c > passwords.txt gpg -c > passwords.txt
``` ```
@@ -53,7 +53,7 @@ Write message then stop with Ctrl+d.
Get the message back out the file with: Get the message back out the file with:
```bash ```sh
gpg -d passwords.txt gpg -d passwords.txt
``` ```
@@ -61,13 +61,13 @@ gpg -d passwords.txt
Search for a key at any key store: Search for a key at any key store:
```bash ```sh
gpg --search-keys nestorv gpg --search-keys nestorv
``` ```
Once you've made a decision about someone: Once you've made a decision about someone:
```bash ```sh
gpg --list-keys gpg --list-keys
``` ```
@@ -86,13 +86,13 @@ This is a fingerprint.
You can now decide the trust level (this stays on your computer). You can now decide the trust level (this stays on your computer).
```bash ```sh
gpg --edit-key CD30421FD825696BD95F1FF644C62C57B790D3CF gpg --edit-key CD30421FD825696BD95F1FF644C62C57B790D3CF
``` ```
Once you're in the interface, type `trust`. Once you're in the interface, type `trust`.
```bash ```sh
gpg --sign-key alice@posteo.net 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: Send those trusted keys up to a server, so people can see you have verified them:
```bash ```sh
gpg --send-keys 024C6B1C84449BD1CB4DF7A152295D2377F4D70F 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). 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 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: Your public key:
```bash ```sh
gpg --output me.gpg --armor --export gpg --output me.gpg --armor --export
``` ```
Alternatively: Alternatively:
```bash ```sh
gpg --export -a person@email.tld > my_key.pub 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. Create the configuration directory before you start, and add at least 1 URL.
```bash ```sh
mkdir ~/.config/newsboat mkdir ~/.config/newsboat
``` ```
```bash ```sh
echo 'https://voidlinux.org/atom.xml foss tech' >> ~/.config/newsboat/urls 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: To get the channel ID without hunting:
```bash ```sh
curl *'https://www.youtube.com/@1minfilms'* | grep -oE 'browseId":"U\w+"' | tail | cut -d'"' -f3 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 ## Script
```bash ```sh
pdftoppm -png *file*.pdf test pdftoppm -png *file*.pdf test
``` ```
```bash ```sh
for x in *png; do for x in *png; do
tesseract -l eng "$x" - >> out.txt tesseract -l eng "$x" - >> out.txt
done done

View File

@@ -23,6 +23,6 @@ Make a text file called 'pdfmark.txt'.
Then run: Then run:
```bash ```sh
gs -o output.pdf -sDEVICE=pdfwrite "$FILE".pdf pdfmark.txt 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: If the service comes already-started, stop it immediately:
```bash ```sh
sudo systemctl stop radicale 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`. `htpasswd` allows you to generate passwords for users, and place them in `/etc/radicale/users`.
```bash ```sh
PASS="$(xkcdpass)" PASS="$(xkcdpass)"
htpasswd -nb $USER "$PASS" | sudo tee -a /etc/radicale/users htpasswd -nb $USER "$PASS" | sudo tee -a /etc/radicale/users
echo "Your username is $USER" 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. Finally, replace the example `DOMAIN` with your actual domain name.
```bash ```sh
DOMAIN=whatever.com DOMAIN=whatever.com
sudo sed -i "s/DOMAIN/$DOMAIN/g" /etc/nginx/sites-available/radicale 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: Check nginx is happy:
```bash ```sh
sudo nginx -t sudo nginx -t
``` ```
You will almost certainly need a new SSL certificate for the site: You will almost certainly need a new SSL certificate for the site:
```bash ```sh
sudo certbod -d cal.$DOMAIN sudo certbod -d cal.$DOMAIN
``` ```
Start or restart both services: Start or restart both services:
```bash ```sh
sudo systemctl start radicale sudo systemctl start radicale
sudo systemctl restart nginx 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: Make a database for your boardgames, specifying only one field and value:
```bash ```sh
database=games.rec database=games.rec
n=Name n=Name
g=Vojvodina g=Vojvodina
@@ -18,21 +18,21 @@ recsel $database
Insert a few more, with the estimated playtime: Insert a few more, with the estimated playtime:
```bash ```sh
recins -f Name -v Saboter -f Playtime -v 30 $database recins -f Name -v Saboter -f Playtime -v 30 $database
recins -f Name -v Chess -f Playtime -v 30 $database recins -f Name -v Chess -f Playtime -v 30 $database
``` ```
View all games, or select one by number: View all games, or select one by number:
```bash ```sh
recsel $database recsel $database
recsel -n 0 $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`. 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 f=played
v=yes v=yes
recset -f $f -a $v $database 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: ...but the field is wrong, it should have a capital letter:
```bash ```sh
new_field=Played new_field=Played
recset -f $f --rename $new_field recset -f $f --rename $new_field
``` ```
@@ -49,19 +49,19 @@ recset -f $f --rename $new_field
Check how many records the database has: Check how many records the database has:
```bash ```sh
recinf $database recinf $database
``` ```
Look at just the games you've never played: Look at just the games you've never played:
```bash ```sh
recsel --expression="Played = 'no'" $database recsel --expression="Played = 'no'" $database
``` ```
Print how many, then just print the names: Print how many, then just print the names:
```bash ```sh
recsel -e "Played = 'no'" --count $database recsel -e "Played = 'no'" --count $database
recsel -e "Played = 'no'" --print=Name $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. 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 num=0
f=Played f=Played
value=yes 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`. 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 recset -e "Playtime = 40" -f Max_Players --set 50 games.rec
``` ```
This doesn't work, because that field does not exist. This doesn't work, because that field does not exist.
You can `--set-add` the field, to add it wherever it 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 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: Remove `Played` record from first game:
```bash ```sh
num=0 num=0
recset --number=$num -f Played --delete $database recset --number=$num -f Played --delete $database
``` ```
You can comment the line instead of deleting it: You can comment the line instead of deleting it:
```bash ```sh
num=1 num=1
recset --number=$num -f Played --delete $database recset --number=$num -f Played --delete $database
recsel $database recsel $database
@@ -111,7 +111,7 @@ cat $database
Delete an entire record: Delete an entire record:
```bash ```sh
num=2 num=2
recdel --number=$num $database recdel --number=$num $database
``` ```

View File

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

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. So if you want to search `/mnt` for videos, remove the word `/mnt` from the configuration file.
```bash ```sh
su root su root
cat /etc/updatedb.conf cat /etc/updatedb.conf
sed -i 's#/mnt/##' /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. 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 N=5
T=3 T=3
FILE=secret.txt FILE=secret.txt
@@ -17,7 +17,7 @@ Each shard is a line inside secret.txt.
Check it's working: Check it's working:
```bash ```sh
head -n $T $FILE | ssss-combine -t $T head -n $T $FILE | ssss-combine -t $T
tail -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: Restart the `soft-serve` service, then check it's working by cloning from localhost:
```bash ```sh
git clone http://localhost:23232/${some_repo}.git git clone http://localhost:23232/${some_repo}.git
``` ```

View File

@@ -5,7 +5,7 @@ tags: [ "data" ]
Work with a database: Work with a database:
```bash ```sh
sqlite3 "$FILE".sqlite3 sqlite3 "$FILE".sqlite3
``` ```
Compress the database: 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,6 +1,6 @@
--- ---
title: "task" title: "Taskwarrior"
tags: [ "organization" ] tags: [ "data", "organization" ]
--- ---
Set up the configuration file: Set up the configuration file:
@@ -9,6 +9,18 @@ Set up the configuration file:
task 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: Add a task:
```sh ```sh
@@ -44,18 +56,16 @@ task add project:house buy potted plant
task add proj:house.repair buy screwdriver task add proj:house.repair buy screwdriver
task add proj:house.repair buy shelf brackets task add proj:house.repair buy shelf brackets
task add pro:house.paint buy white paint task add pro:house.paint buy white paint
task add pro:house.paint buy red paint
task add pro:house.paint buy black paint for t in "buy red paint" "buy black paint" "buy brushes" ; do
task add pro:house.paint buy brushes task add pro:house.paint $t
done
``` ```
## Summary ## Summary
```sh ```sh
task pro:house sum task pro:house sum
```
```sh
task burndown.daily pro:house task burndown.daily pro:house
``` ```
@@ -63,44 +73,12 @@ The summaries will show how fast a project is being completed, and when you can
# Tags # Tags
```sh ```sh
task add +buy toothbrush task add +buy toothbrush
```
You can then see only tasks which involve buying something with:
```sh
task +buy task +buy
``` ```
# 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
```
# Review # Review
View list of tasks completed in the last week: View list of tasks completed in the last week:
@@ -111,21 +89,17 @@ task end.after:today-1wk completed
# User Defined Attributes # 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`.
```sh ```sh
task config uda.size.type string task config uda.size.type string
```
```sh
task config uda.size.label Size task config uda.size.label Size
``` ```
You can also ensure task tasks can only be `large`, `medium`, or `small`, then set a default.
```sh ```sh
task config uda.size.values large,medium,small task config uda.size.values large,medium,small
```
```sh
uda.size.default=medium uda.size.default=medium
``` ```

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

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

View File

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

View File

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

View File

@@ -13,7 +13,7 @@ Include = /etc/pacman.d/mirrorlist
And update: And update:
```bash ```sh
sudo pacman -Syu sudo pacman -Syu
``` ```
@@ -21,7 +21,7 @@ sudo pacman -Syu
Check your graphics card type: Check your graphics card type:
```bash ```sh
lspci | grep VGA lspci | grep VGA
``` ```
@@ -31,7 +31,7 @@ lspci | grep VGA
If you see `Nvidia`, then install the intel drivers: 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 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: 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 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`: If you see `AMD`, then check your card support `vulkan`:
```bash ```sh
yay -S gpu-viewer yay -S gpu-viewer
``` ```
```bash ```sh
vulkaninfo | grep 'VkPhysicalDeviceVulkanMemoryModelFeatures' -A 3 vulkaninfo | grep 'VkPhysicalDeviceVulkanMemoryModelFeatures' -A 3
``` ```
You should see 'true' here. 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 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/`: Clean the cache of old packages in `/var/cachepacman/pkg/`:
```bash ```sh
ls /var/cache/pacman/pkg/ | wc -l ls /var/cache/pacman/pkg/ | wc -l
sudo pacman -Sc sudo pacman -Sc
ls /var/cache/pacman/pkg/ | wc -l ls /var/cache/pacman/pkg/ | wc -l
``` ```
And the same for `yay` (with `-Yc` to remove old dependencies): And the same for `yay` (with `-Yc` to remove old dependencies):
```bash ```sh
ls ~/.cache/yay/ | wc -l ls ~/.cache/yay/ | wc -l
yay -Sc yay -Sc
yay -Yc 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. 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" sudo find /etc/ /var/ /usr/ -name "*.pacnew"
diff /etc/pacman.d/mirrorlist* diff /etc/pacman.d/mirrorlist*
``` ```
@@ -36,7 +36,7 @@ Either,
- Update the files manually, - Update the files manually,
```bash ```sh
sudo -e /etc/pacman.d/mirrorlist sudo -e /etc/pacman.d/mirrorlist
sudo rm /etc/pacman.d/mirrorlist.pacnew 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`. - 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 pacman -S pacman-contrib
sudo pacdiff sudo pacdiff
``` ```

View File

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

View File

@@ -5,7 +5,7 @@ tags: [ "void" ]
Make the autologin service: Make the autologin service:
```bash ```sh
cp -R /etc/sv/agetty-tty1 /etc/sv/agetty-autologin-tty1 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 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 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) 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 convert -resize 200% '256px-Void_Linux_logo.svg.png?20170131170632' void-logo.png
``` ```
Download a pretty wallpaper Download a pretty wallpaper
```bash ```sh
wget http://wallpapercave.com/wp/Wlm9Gv0.jpg wget http://wallpapercave.com/wp/Wlm9Gv0.jpg
``` ```
Put the void logo on all *jpg and *png images Put the void logo on all *jpg and *png images
```bash ```sh
for x in *.jpg for x in *.jpg
do do
composite -compose multiply -gravity Center void-logo.png "$x" "$x" composite -compose multiply -gravity Center void-logo.png "$x" "$x"

View File

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

View File

@@ -6,7 +6,7 @@ tags: [ "void" ]
Update all packages with Update all packages with
```bash ```sh
sudo xbps-install -Su 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. Void keeps *every* version of everything you install, so you can roll back to them.
Remove old packages with: Remove old packages with:
```bash ```sh
sudo xbps-remove -O sudo xbps-remove -O
``` ```
@@ -25,19 +25,19 @@ sudo xbps-remove -O
Old Void kernels are left on the boot partition. List them with: Old Void kernels are left on the boot partition. List them with:
```bash ```sh
vkpurge list vkpurge list
``` ```
Remove one with: Remove one with:
```bash ```sh
vkpurge 2.8.2_4 vkpurge 2.8.2_4
``` ```
Remove all but the latest with: Remove all but the latest with:
```bash ```sh
vkpurge rm all vkpurge rm all
``` ```
@@ -48,7 +48,7 @@ You can change this number to change the screen brightness.
For an easy utility, install `brightnessctl`. For an easy utility, install `brightnessctl`.
```bash ```sh
brightnessctl s 10%- brightnessctl s 10%-
brightnessctl s 10%+ brightnessctl s 10%+
``` ```
@@ -57,5 +57,5 @@ brightnessctl s 10%+
- [autologin](autologin.md) - [autologin](autologin.md)
- [services](sv.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: Look for cowsay in the repository:
```bash ```sh
xbps-query --repository --search cowsay xbps-query --repository --search cowsay
``` ```
Short version: Short version:
```bash ```sh
xbps-query -Rs cowsay xbps-query -Rs cowsay
``` ```
Search with regex: Search with regex:
```bash ```sh
xbps-query --regex -Rs 'cow(s)?\w' xbps-query --regex -Rs 'cow(s)?\w'
``` ```
List what's required for cowsay List what's required for cowsay
```bash ```sh
xbps-query -x cowsay xbps-query -x cowsay
``` ```
What packages are orphaned (i.e. installed as a dependency for another package, which has since been removed)? What packages are orphaned (i.e. installed as a dependency for another package, which has since been removed)?
```bash ```sh
xbps-query -O xbps-query -O
``` ```
Show cowsay's dependencies. Show cowsay's dependencies.
```bash ```sh
xbps-query -x cowsay xbps-query -x cowsay
``` ```
This shows `perl`. This shows `perl`.
To see what else depends on perl: To see what else depends on perl:
```bash ```sh
xbps-query -X perl xbps-query -X perl
``` ```
List all manually installed software. List all manually installed software.
```bash ```sh
xbps-query -m xbps-query -m
``` ```
@@ -57,14 +57,14 @@ xbps-query -m
Install cowsay Install cowsay
```bash ```sh
xbps-install cowsay xbps-install cowsay
``` ```
Upgrade current packages. Upgrade current packages.
`-R` looks at repositories, `-s` makes a sloppy search (for rough matches). `-R` looks at repositories, `-s` makes a sloppy search (for rough matches).
```bash ```sh
xbps-install -Suv xbps-install -Suv
``` ```
@@ -72,19 +72,19 @@ xbps-install -Suv
Remove cowsay Remove cowsay
```bash ```sh
xbps-remove cowsay xbps-remove cowsay
``` ```
...and all dependencies ...and all dependencies
```bash ```sh
xbps-remove -R cowsay xbps-remove -R cowsay
``` ```
Remove all orphaned dependencies. Remove all orphaned dependencies.
```bash ```sh
xbps-remove -o xbps-remove -o
``` ```
@@ -94,19 +94,19 @@ Show information about cowsay
Reinstall cowsay Reinstall cowsay
```bash ```sh
xbps-install -f cowsay xbps-install -f cowsay
``` ```
Look for broken packages. Look for broken packages.
```bash ```sh
sudo xbps-pkgdb -a sudo xbps-pkgdb -a
``` ```
And if you've found any, you might reconfigure all packages forcefully: And if you've found any, you might reconfigure all packages forcefully:
```bash ```sh
sudo xbps-reconfigure -af sudo xbps-reconfigure -af
``` ```

View File

@@ -5,7 +5,7 @@ requires: [ "ssh" ]
--- ---
# SSH Daemon Jail # SSH Daemon Jail
```bash ```sh
sudo cp /etc/fail2ban/jail.conf /etc/fail2ban/jail.d/ssh.local 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 sudo systemctl restart fail2ban
``` ```
```bash ```sh
sudo fail2ban-client status sudo fail2ban-client status
``` ```
```bash ```sh
sudo fail2ban-client status sshd sudo fail2ban-client status sshd
``` ```

View File

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

View File

@@ -8,7 +8,7 @@ This is a basic Linux firewall program.
Look at your firewalls: Look at your firewalls:
```bash ```sh
iptables -L 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: I don't need any forwarding, so I'm going to drop all forwarding:
```bash ```sh
iptables -P FORWARD DROP 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 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 iptables -A INPUT -s 192.168.0.23 -j DROP
``` ```
Or we can block all input from a particular port on the full Network. 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 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 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: To delete rule 2 from the INPUT chain:
```bash ```sh
iptables -D INPUT 3 iptables -D INPUT 3
``` ```
Alternatively, you can 'I'nsert a rule at the start, rather than 'A'ppending it. 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 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: Flush all existing rules with:
```bash ```sh
iptables -F iptables -F
``` ```

View File

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

View File

@@ -6,19 +6,19 @@ tags: [ "distros" ]
## Arch ## Arch
```bash ```sh
yay -S pi-hole-server yay -S pi-hole-server
``` ```
```bash ```sh
sudo systemctl enable --now pihole-FTL sudo systemctl enable --now pihole-FTL
``` ```
```bash ```sh
sudo systemctl disable --now systemd-resolved sudo systemctl disable --now systemd-resolved
``` ```
```bash ```sh
sudo rm -f /dev/shm/FTL-\* sudo rm -f /dev/shm/FTL-\*
``` ```
@@ -26,32 +26,32 @@ sudo rm -f /dev/shm/FTL-\*
Debian has a long, boring setup. Debian has a long, boring setup.
```bash ```sh
sudo apt-get install wget curl net-tools gamin lighttpd lighttpd-mod-deflate 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 curl -sSL https://install.pi-hole.net | PIHOLE_SKIP_OS_CHECK=true sudo -E bash
``` ```
# Setup # Setup
```bash ```sh
sudo usermod -aG pihole $USER sudo usermod -aG pihole $USER
``` ```
Remove that google dns server. Remove that google dns server.
```bash ```sh
pihole -a setdns 9.9.9.9 1.0.0.1 pihole -a setdns 9.9.9.9 1.0.0.1
``` ```
Disable pihole password by setting a blank password. Disable pihole password by setting a blank password.
```bash ```sh
pihole -a -p pihole -a -p
``` ```
Get a new list of blocked domains, then reload: Get a new list of blocked domains, then reload:
```bash ```sh
pihole -g -r 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: Observe the pihole's output while you ask it a question:
```bash ```sh
pihole -t pihole -t
``` ```
Then ask the question from another computer: Then ask the question from another computer:
```bash ```sh
dig @[ pihole ip ] archlinux.org 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: Generate a config file with:
```bash ```sh
rclone config rclone config
``` ```
Look at the contents of Google Drive: Look at the contents of Google Drive:
```bash ```sh
rclone ls gd:/ rclone ls gd:/
``` ```
If rclone loses authorization: If rclone loses authorization:
```bash ```sh
rclone authorization rclone authorization
``` ```
List only directories: List only directories:
```bash ```sh
rclone lsf -dirs-only google:/ rclone lsf -dirs-only google:/
``` ```
Mount the remote location on /tmp/google with: Mount the remote location on /tmp/google with:
```bash ```sh
rclone mount google /tmp/google rclone mount google /tmp/google
``` ```
Copy the contents of 'foo' to 'test'. Copy the contents of 'foo' to 'test'.
```bash ```sh
rclone copy foo/ google:test rclone copy foo/ google:test
``` ```
Sync contents of foo and test with a progress bar (will delete Google items): Sync contents of foo and test with a progress bar (will delete Google items):
```bash ```sh
rclone sync foo google:test -P rclone sync foo google:test -P
``` ```
Remove all duplicates Remove all duplicates
```bash ```sh
rclone dedupe google:test rclone dedupe google:test
``` ```
Delete contets of a remote file: Delete contets of a remote file:
```bash ```sh
rclone delete n:test rclone delete n:test
``` ```
Or delete the folder and contents as well: Or delete the folder and contents as well:
```bash ```sh
rclone purge n:test rclone purge n:test
``` ```
Copy to and from with: Copy to and from with:
```bash ```sh
rclone copyto google:test foo rclone copyto google:test foo
``` ```
or or
```bash ```sh
rclone copyto foo google:test rclone copyto foo google:test

View File

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

View File

@@ -4,25 +4,25 @@ tags: [ "scraping" ]
--- ---
Install `yt-dlp`. Install `yt-dlp`.
```bash ```sh
yt-dlp --write-auto-sub *<URL>* yt-dlp --write-auto-sub *<URL>*
``` ```
It will default to English, but you can specify another language with the flag --sub-lang: 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>* youtube-dl --sub-lang sv --write-auto-sub *<URL>*
``` ```
You can list all available subtitles with: You can list all available subtitles with:
```bash ```sh
yt-dlp --list-subs *<URL>* 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: 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>* 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. Query a host with the `host` command.
```bash ```sh
host $domain.$tld host $domain.$tld
``` ```
```bash ```sh
host $domain.$tld 9.9.9.9 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.): Request a specific record type (`CNAME`, `TXT`, et c.):
```bash ```sh
torsocks host -T -t $RECORD_TYPE $domain torsocks host -T -t $RECORD_TYPE $domain
``` ```

View File

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

View File

@@ -6,25 +6,25 @@ requires: [ "ssh" ]
Mount a remote filesystem locally with fuse-sshfs: Mount a remote filesystem locally with fuse-sshfs:
```bash ```sh
sshfs *user*@192.168.0.10:/home/*user* /tmp/mnt sshfs *user*@192.168.0.10:/home/*user* /tmp/mnt
``` ```
Unmount with: Unmount with:
```bash ```sh
fusermount -u /tmp/mnt fusermount -u /tmp/mnt
``` ```
Set it up on /etc/fstab with: 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 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. 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 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 # Get a Hostname
```bash ```sh
sudo vim /etc/tor/torrc sudo vim /etc/tor/torrc
``` ```

View File

@@ -22,29 +22,29 @@ Install it then start the service.
Arch Linux: Arch Linux:
```bash ```sh
sudo systemctl start transmission sudo systemctl start transmission
``` ```
Debian: Debian:
```bash ```sh
sudo systemctl start transmission-daemon sudo systemctl start transmission-daemon
``` ```
Add a torrent by the .torrent file, or a magnet link, like this: 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' 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 transmission-remote -a sita.torrent
``` ```
Now let's check that the torrent's been added successfully. Now let's check that the torrent's been added successfully.
```bash ```sh
transmission-remote -l 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. 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.: E.g.:
```bash ```sh
sudo usermod -aG transmission $USER 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: 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 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`: To both **r**emove **a**nd **d**elete a file, use `-rad`:
```bash ```sh
transmission-remote -t 4 -rad 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: 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 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. 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/ cd /var/lib/transmission/.config/transmission-daemon/
$EDITOR settings.json $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: Create a torrent of file or directory `Memes` with:
```bash ```sh
sudo chown -R :transmission Memes sudo chown -R :transmission Memes
transmission-create $(pwd)/Memes transmission-create $(pwd)/Memes
``` ```
Add a tracker to the torrent, to make sure others can find you easily: 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 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: Add your torrent and notes its number:
```bash ```sh
transmission-remote -a "$file".torrent transmission-remote -a "$file".torrent
transmission-remote -l transmission-remote -l
transmission-remote -t "$number" -i 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`. 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 transmission-remote -t "$number" -v
``` ```
If transmission cannot find it, then tell it where to find the torrent: If transmission cannot find it, then tell it where to find the torrent:
```bash ```sh
transmission-remote -t "$number" --find "$(pwd)" transmission-remote -t "$number" --find "$(pwd)"
``` ```
...and of course, make sure the permissions allow transmission to see the target. ...and of course, make sure the permissions allow transmission to see the target.
```bash ```sh
ls -ld "$file" 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: If not, try checking out what your local networking interfaces are, then check if they have been picked up:
```bash ```sh
dmesg | grep eth0 dmesg | grep eth0
``` ```
# Display Active Ports # Display Active Ports
```bash ```sh
netstat -l netstat -l
``` ```
...or maybe narrow it down to http: ...or maybe narrow it down to http:
```bash ```sh
netstat -l | grep http netstat -l | grep http
``` ```

View File

@@ -4,35 +4,35 @@ tags: [ "networking", "web" ]
--- ---
Install nginx: Install nginx:
```bash ```sh
sudo apt-get install nginx sudo apt-get install nginx
``` ```
```bash ```sh
sudo apt-get enable --now nginx sudo apt-get enable --now nginx
``` ```
Put a website somewhere: Put a website somewhere:
```bash ```sh
mkdir /var/www/html/mysite/ mkdir /var/www/html/mysite/
``` ```
Put an index file there: Put an index file there:
```bash ```sh
vim /var/www/html/mysite/index.html vim /var/www/html/mysite/index.html
``` ```
Make the owner `www-data` Make the owner `www-data`
```bash ```sh
chown -R www-data:www-data /var/www/html/mysite/ chown -R www-data:www-data /var/www/html/mysite/
``` ```
Make a configuration file for nginx: Make a configuration file for nginx:
```bash ```sh
vim /etc/nginx/sites-available/mysite.conf vim /etc/nginx/sites-available/mysite.conf
``` ```
@@ -54,13 +54,13 @@ server {
Make the site available: Make the site available:
```bash ```sh
ln -s /etc/nginx/sites-available/mysite.conf /etc/nginx/sites-enabled/ ln -s /etc/nginx/sites-available/mysite.conf /etc/nginx/sites-enabled/
``` ```
Test it's working: Test it's working:
```bash ```sh
nginx -t nginx -t
``` ```
@@ -82,17 +82,17 @@ Buy some DNS online, then check it's working.
*Once it's working*, use certbot: *Once it's working*, use certbot:
```bash ```sh
apt install certbot apt install certbot
``` ```
You may need to install an nginx python module: You may need to install an nginx python module:
```bash ```sh
apt install python3-certbot-nginx apt install python3-certbot-nginx
``` ```
```bash ```sh
domain=example.com domain=example.com
my_email=me@posteo.uk my_email=me@posteo.uk
certbot --nginx -d "$domain" --non-interactive --agree-tos -m "$my_email" 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. Stats on local net usage within domain.
```bash ```sh
iftop -p -n iftop -p -n
``` ```
```bash ```sh
whois domain.com whois domain.com
``` ```
Info on domain, whether it's taken, et c.: Info on domain, whether it's taken, et c.:
```bash ```sh
dig domain.com dig domain.com
``` ```
```bash ```sh
ifconfig ifconfig
``` ```
Versatile wifi tool: Versatile wifi tool:
```bash ```sh
nmcli nmcli
``` ```
@@ -35,7 +35,7 @@ nmcli
You want to connect to the internet. You want to connect to the internet.
```bash ```sh
sudo iwconfig 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:...... This tells you that your ESSID is 'Gandalf WajFaj', and the access point name is 10:05:......
```bash ```sh
nmcli radio 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. You're told that eth0 deals with your ethernet and `wlan0` deals with wifi.
`wlan0` is a file which represents your wifi device. `wlan0` is a file which represents your wifi device.
```bash ```sh
nmcli wlan0 wifi rescan nmcli wlan0 wifi rescan
``` ```
```bash ```sh
nmcli device wifi list nmcli device wifi list
``` ```
Now to connect. Now to connect.
```bash ```sh
nmcli device wifi connect [SSID] [your password] [wifi password] nmcli device wifi connect [SSID] [your password] [wifi password]
``` ```
Alternatively, you can use Alternatively, you can use
```bash ```sh
nmcli -ask device wifi connect [SSID] 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 # Volume Control
```bash ```sh
pactl set sink @DEFAULT_SINK@ +5% pactl set sink @DEFAULT_SINK@ +5%
``` ```
Find working outputs: Find working outputs:
```bash ```sh
aplay -l aplay -l
``` ```
@@ -30,7 +30,7 @@ amixer scontrols
# Change a Sound setting # Change a Sound setting
```bash ```sh
amixer set Master 5%- amixer set Master 5%-
``` ```
@@ -42,19 +42,19 @@ pulseaudio -k && sudo alsa force-reload
Toggle, mute, increase or decrase audio: Toggle, mute, increase or decrase audio:
```bash ```sh
amixer sset Master toggle amixer sset Master toggle
``` ```
```bash ```sh
amixer sset Master mute amixer sset Master mute
``` ```
```bash ```sh
amixer sset Master 5%+ amixer sset Master 5%+
``` ```
```bash ```sh
amixer sset Master 5%- amixer sset Master 5%-
``` ```
@@ -62,14 +62,14 @@ amixer sset Master 5%-
Start with: Start with:
```bash ```sh
alsamixer alsamixer
``` ```
Then press `F6` to see available Sound cards. 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: 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% 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. 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 sudo usermod -aG pulse-access mpd
``` ```
Working with mpd will be easier if you have access to its files, so maybe: Working with mpd will be easier if you have access to its files, so maybe:
```bash ```sh
sudo usermod -aG mpd $USER sudo usermod -aG mpd $USER
``` ```
@@ -56,7 +56,7 @@ sudo usermod -aG mpd $USER
Install `mpd-notification` and then start the service: Install `mpd-notification` and then start the service:
```bash ```sh
systemctl --user enable mpd-notification 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: Also, make sure the user mpd is part of the group pulse:
```bash ```sh
sudo adduser mpd pulse sudo adduser mpd pulse
``` ```

View File

@@ -8,31 +8,31 @@ tags: [ "system", "phone" ]
Install: Install:
```bash ```sh
yay -S simple-mtpfs yay -S simple-mtpfs
``` ```
List available phones: List available phones:
```bash ```sh
simple-mtpfs -l simple-mtpfs -l
``` ```
Make a mount point: Make a mount point:
```bash ```sh
mkdir phone mkdir phone
``` ```
Check your phone, and tell it to allow access to the USB. Check your phone, and tell it to allow access to the USB.
```bash ```sh
simple-mtpfs --device 1 phone simple-mtpfs --device 1 phone
``` ```
## Stop ## Stop
```bash ```sh
fusermount -u phone fusermount -u phone
rmdir 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: Return full contents of a string:
```bash ```sh
awk '{ print }' file awk '{ print }' file
``` ```
Print the first and second column: Print the first and second column:
```bash ```sh
awk '{print$1$2}' awk '{print$1$2}'
``` ```
Return every line with the word 'the' (like grep): Return every line with the word 'the' (like grep):
```bash ```sh
awk '/the/{print}' file awk '/the/{print}' file
``` ```
Print everything containing a lowercase letter: Print everything containing a lowercase letter:
```bash ```sh
awk '/[a-z]/{print}' file 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 # Conditionals
```bash ```sh
awk '{ if($1 ~ /123/) print }' file 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: Grep for 'hawk' in a story:
```bash ```sh
awk '/hawk/' story.txt awk '/hawk/' story.txt
``` ```
Return any line with one or more "&" sequences: Return any line with one or more "&" sequences:
```bash ```sh
awk '/&+/' script.sh awk '/&+/' script.sh
``` ```
The pipe is used for 'or', so 'Orcs or drums' would be: The pipe is used for 'or', so 'Orcs or drums' would be:
```bash ```sh
awk '/Orcs|Drums/' story.txt 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. 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: 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 cat list.txt | xargs rm
``` ```
@@ -81,13 +81,13 @@ x=$(( x*x ))
## Finding Duplicate Files ## Finding Duplicate Files
```bash ```sh
find . -type f -exec md5sum '{}' ';' | sort | uniq --all-repeated=separate -w 15 > all-files.txt find . -type f -exec md5sum '{}' ';' | sort | uniq --all-repeated=separate -w 15 > all-files.txt
``` ```
## Output random characters ## Output random characters
```bash ```sh
cat /dev/urandom | tr -cd [:alnum:] | dd bs=1 count=200 status=none && echo 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. Try something out in a random directory in `/tmp` so the files will be deleted when you next shut down.
```bash ```sh
mktemp -d mktemp -d
``` ```
That gives you a random directory to mess about in. That gives you a random directory to mess about in.
```bash ```sh
dir=$(mktemp -d) dir=$(mktemp -d)
for x in {A..Z}; do for x in {A..Z}; do
fortune > "$dir"/chimpan-$x 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): Ask if a directory has duplicates (`rdfind` will not delete anything):
```bash ```sh
rdfind $dir rdfind $dir
$EDITOR results.txt $EDITOR results.txt
``` ```
Replace the duplicated files with [hard links](../basics/hard_links.md). Replace the duplicated files with [hard links](../basics/hard_links.md).
```bash ```sh
rdfind -makehardlinks true $dir 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: Ask what type of application opens an mkv file:
```bash ```sh
xdg-mime query default video/mkv xdg-mime query default video/mkv
``` ```
Same with pdf: Same with pdf:
```bash ```sh
xdg-mime query default application/pdf xdg-mime query default application/pdf
``` ```
Ask what file-type `book.pdf` uses. Ask what file-type `book.pdf` uses.
```bash ```sh
xdg-mime query filetype *book.pdf* 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. Set the mime type of mp4 videos to mpv.
```bash ```sh
xdg-mime default mpv.desktop video/mp4 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. You can use an asterisk for everything in a category.
```bash ```sh
xdg-mime default org.gnome.font-viewer.desktop font/\* 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`. 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/ cp -r /usr/share/examples/lf ~/.config/
``` ```
Go straight to root with two keys. Go straight to root with two keys.
```bash ```sh
map g/ cd / map g/ cd /
``` ```
Have lf open a file with the default program when you press 'o', using the program `mimeo`. Have lf open a file with the default program when you press 'o', using the program `mimeo`.
```bash ```sh
map o &mimeo $f map o &mimeo $f
``` ```
Change that default text editor to look at the extension first. Change that default text editor to look at the extension first.
```bash ```sh
cmd open ${{ cmd open ${{
case $(file --mime-type $f -b) in case $(file --mime-type $f -b) in
application/x-sc) sc-im $fx;; 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. The standard renaming is bad, because you have to re-type the file extension.
Use this instead: Use this instead:
```bash ```sh
# rename current file without overwrite # 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 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> 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). First, install `ueberzug` (to show images).
Then clone the lfrun repo. Then clone the lfrun repo.
```bash ```sh
git clone https://github.com/cirala/lfimg.git git clone https://github.com/cirala/lfimg.git
cd lfimg cd lfimg

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`): 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
make -Bnd | make2graph make -Bnd | make2graph
make -Bnd | make2graph | graph-easy --boxart make -Bnd | make2graph | graph-easy --boxart

View File

@@ -1,4 +1,3 @@
--- ---
title: "Makefile Patterns" title: "Makefile Patterns"
tags: [ "system", "make" ] 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 sudo usermod --groups wheel,audio,$USER
``` ```
Add yourself to the `wheel` group: Add yourself to the `docker` group:
```sh ```sh
su root -c "usermod --append --groups wheel $USER" su root -c "usermod --append --groups docker $USER"
``` ```
Add yourself to the `network` group: Add yourself to the `network` group:
@@ -28,5 +28,11 @@ Add yourself to the `network` group:
sudo usermod -aG network $USER 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
```

View File

@@ -7,7 +7,7 @@ tags: [ "RAID", "disk" ]
You will need 4 disks and the `mdadm` package. You will need 4 disks and the `mdadm` package.
The total size will be equal to the disks x 3, because one will be used for redundancy. The total size will be equal to the disks x 3, because one will be used for redundancy.
```bash ```sh
sudo mdadm --create --verbose /dev/*md127* --level=5 --raid-devices=*4* */dev/sdb /dev/sdc /dev/sdd /dev/sde* sudo mdadm --create --verbose /dev/*md127* --level=5 --raid-devices=*4* */dev/sdb /dev/sdc /dev/sdd /dev/sde*
``` ```
@@ -19,7 +19,7 @@ Note the variable parts:
Now look at how the raid status: Now look at how the raid status:
```bash ```sh
cat /proc/mdstat cat /proc/mdstat
``` ```
@@ -27,7 +27,7 @@ This will increase until the entire thing is fine.
Check the health of your `mdadm` array: Check the health of your `mdadm` array:
```bash ```sh
sudo mdadm --detail /dev/md127 sudo mdadm --detail /dev/md127
``` ```
@@ -35,7 +35,7 @@ You should see `State : clean`. If you see it is `degraded`, then a disk has bro
## Replacing a Disk ## Replacing a Disk
```bash ```sh
sudo mdadm --add /dev/md127 /dev/sdb1 sudo mdadm --add /dev/md127 /dev/sdb1
``` ```

View File

@@ -5,26 +5,26 @@ tags: [ "system", "CPU", "memory" ]
Print the average CPU load over 1 minute, 5 minutes, and 15 minutes: Print the average CPU load over 1 minute, 5 minutes, and 15 minutes:
```bash ```sh
watch -d cat /proc/loadavg watch -d cat /proc/loadavg
stress="$(cat /proc/loadavg | awk '{print "Usage:" $2"%"}')" stress="$(cat /proc/loadavg | awk '{print "Usage:" $2"%"}')"
``` ```
Show memory usage in Gibitytes. Show memory usage in Gibitytes.
```bash ```sh
free -g free -g
``` ```
Show low and high gigibtye usage on a *l*ine, and repeat the measurement every 5 seconds: Show low and high gigibtye usage on a *l*ine, and repeat the measurement every 5 seconds:
```bash ```sh
REP=5 REP=5
free --lohi -g -s $REP | lolcat free --lohi -g -s $REP | lolcat
``` ```
Check the next thing cron will do: Check the next thing cron will do:
```bash ```sh
cronnext /var/spool/cron/$USER -l cronnext /var/spool/cron/$USER -l
``` ```

View File

@@ -6,38 +6,38 @@ tags: [ "systemd" ]
See a running log of all system messages: See a running log of all system messages:
```bash ```sh
journalctl -f journalctl -f
``` ```
Or just one user: Or just one user:
```bash ```sh
journalctl --user -f journalctl --user -f
``` ```
Or just one unit (`sshd`): Or just one unit (`sshd`):
```bash ```sh
journalctl -f -u sshd journalctl -f -u sshd
``` ```
Find errors since November Find errors since November
```bash ```sh
journalctl --since=2018-11-01 --grep="EXT4-fs error" journalctl --since=2018-11-01 --grep="EXT4-fs error"
``` ```
Limit size to 2G. Limit size to 2G.
```bash ```sh
journalctl --vacuum-size=2G journalctl --vacuum-size=2G
``` ```
Log the fact that you've installed your own `dnsmasq` on your system to `journalctl`, so that you can notice why your system's broken: Log the fact that you've installed your own `dnsmasq` on your system to `journalctl`, so that you can notice why your system's broken:
```bash ```sh
logger "Installed new dnsmasq" logger "Installed new dnsmasq"
sudo journalctl -f sudo journalctl -f
``` ```

View File

@@ -26,7 +26,7 @@ WantedBy=multi-user.target
After making the new service, systemd requires reloading: After making the new service, systemd requires reloading:
```bash ```sh
sudo systemctl daemon-reload sudo systemctl daemon-reload
``` ```

View File

@@ -2,33 +2,33 @@
title: "systemd" title: "systemd"
tags: [ "systemd" ] tags: [ "systemd" ]
--- ---
```bash ```sh
systemctl list-units systemctl list-units
``` ```
```bash ```sh
sudo systemctl status mpd sudo systemctl status mpd
``` ```
```bash ```sh
sudo systemctl daemon-reload sudo systemctl daemon-reload
``` ```
```bash ```sh
sudo systemctl taskd.service start sudo systemctl taskd.service start
``` ```
```bash ```sh
sudo systemctl status taskd.service sudo systemctl status taskd.service
``` ```
# Startup # Startup
```bash ```sh
sudo systemd-analyze sudo systemd-analyze
``` ```
```bash ```sh
sudo systemd-analyze blame sudo systemd-analyze blame
``` ```

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