docs(script): Expand on trivial and important packages distinction (#1)
This commit is contained in:
parent
45df9755f1
commit
a32a4df6a6
10
README.md
10
README.md
@ -44,6 +44,16 @@ zpool/root/archlinux
|
|||||||
```
|
```
|
||||||
If exactly one source returns that is the exact name of a ZFS dataset in an imported zpool we create a snapshot on it. If no source returns we silently exit. If more than one source returns we raise an error and halt the `pacman` transaction.
|
If exactly one source returns that is the exact name of a ZFS dataset in an imported zpool we create a snapshot on it. If no source returns we silently exit. If more than one source returns we raise an error and halt the `pacman` transaction.
|
||||||
|
|
||||||
|
We retain two different snapshot chains, one for `pacman` transactions that only affect what we are calling _trivial_ packages and a separate chain for _important_ packages. By default only the exact regular expression package name match `^(linux|systemd|zfs-(dkms|utils))$` is considered important so in plain English any one of:
|
||||||
|
|
||||||
|
- `linux`
|
||||||
|
- `systemd`
|
||||||
|
- `zfs-dkms`
|
||||||
|
- `zfs-utils`
|
||||||
|
|
||||||
|
Whenever an important package is affected by a transaction a snapshot goes into the corresponding chain. In all other cases - when an important package is not affected - snapshots go into the trivial chain.
|
||||||
|
|
||||||
|
The _trivial_ snapshot chain by default keeps 25 snapshots, the _important_ chain keeps 5. The thought process here is that you will likely not futz around with a kernel every day whereas you may very well install arbitrary packages multiple times a day. Snapshots should keep you safe for a couple of days hence the defaults of 5 and 15 snapshots, respectively.
|
||||||
|
|
||||||
Snapshots may look like so:
|
Snapshots may look like so:
|
||||||
```
|
```
|
||||||
|
Loading…
x
Reference in New Issue
Block a user