quico-os-setup/zfs-pacman-hook
1
0
Fork 0
Code Issues 3 Pull Requests Packages Projects Releases Wiki Activity

Compare commits

base: quico-os-setup:3516f56580dc19abafd028f7f0ebf395d007e934
Branches Tags
quico-os-setup:main quico-os-setup:1-get-base-version-going
...
compare: quico-os-setup:d606ae9688c08536320fecd664ec1f933b59e5df
Branches Tags
quico-os-setup:1-get-base-version-going quico-os-setup:main

2 Commits
3516f56580 ... d606ae9688

Author SHA1 Message Date
hygienic-books
d606ae9688 refactor(docs): Layout (#1) 2023-12-26 06:15:01 +01:00
hygienic-books
2246823d06 refactor(docs): Typo (#1) 2023-12-26 06:14:04 +01:00
1 changed files with 2 additions and 2 deletions
Expand all files Collapse all files

4
README.md
View File

@@ -126,7 +126,7 @@ With these settings it is possible to cause ZFS snapshot name collisions (meanin
- They cover the same type of operation (_Install_, _Remove_ or _Upgrade_) - They cover the same type of operation (_Install_, _Remove_ or _Upgrade_)
- They cover the same list of packages - They cover the same list of packages
The script safeguards against naming collisions by adding a monotoniccally incrementing counter after the timestamp string. The script safeguards against naming collisions by adding a monotonically incrementing counter after the timestamp string.
For example by running `pacman -S tmux` three times within the same minute (once for an _Install_ operation and two more times for two identical _Upgrade_ operations) your system may generate the following example snapshots: For example by running `pacman -S tmux` three times within the same minute (once for an _Install_ operation and two more times for two identical _Upgrade_ operations) your system may generate the following example snapshots:
``` ```
@@ -138,7 +138,7 @@ zpool/root/archlinux@pacman_2023-03-07-0116_2_op:upgr_sev:trv_pkgs:tmux
Notice that lines 2 and 3 would collide since their dataset names are virtually identical other than the counter suffix which was incremented by 1 to avoid a collision. Notice that lines 2 and 3 would collide since their dataset names are virtually identical other than the counter suffix which was incremented by 1 to avoid a collision.
> This facilitates a hands-off approach to using this script on a daily driver system without risking missing snapshots or employing other more involved approaches to avoid naming collisions. This facilitates a hands-off approach to using this script on a daily driver system without risking missing snapshots or employing other more involved approaches to avoid naming collisions.
# Rollback # Rollback