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

Compare commits

base: quico-os-setup:10093d7dd8c8452768f1c0c99ba7466e38c8155e
Branches Tags
quico-os-setup:main
..
compare: quico-os-setup:262c0a6b5a4da1475b987b06d0706bfce237ee75
Branches Tags
quico-os-setup:main

3 Commits
10093d7dd8 ... 262c0a6b5a

Author SHA1 Message Date
hygienic-books
262c0a6b5a docs(meta): It's root-on-ZFS 2023-10-27 01:20:09 +02:00
hygienic-books
477dbfbb90 docs(meta): Explain Conventional Commits scopes 2023-10-27 00:50:53 +02:00
hygienic-books
d4c357f334 docs(meta): syslinux is a dependency, without it this hook is useless 2023-10-27 00:50:26 +02:00
1 changed files with 4 additions and 2 deletions
Expand all files Collapse all files

6
README.md
View File

@@ -4,6 +4,8 @@ Arch Linux pacman hook to automatically recreate syslinux and MBR after updates
# Setup
> Not explicitly listed here as a step but still relevant: This `pacman` hook only makes sense if you're using Syslinux as your boot loader and have the homonymous `syslinux` package installed.
Get started like so:
1. Install dependencies `jq` and `rsync`
@@ -39,7 +41,7 @@ If this returns zero or more than one mounted drive we bail, print an error mess
# Assumptions
This hook is intended to work with [quico.space/quico-os-setup/arch-zbm](https://quico.space/quico-os-setup/arch-zbm), a root on ZFS installation script that uses ZFSBootMenu as its boot loader; it's specifically intended for use on `arch-zbm` machines that use legacy BIOS. Before using this hook for any other purpose please closely review what it does and adapt to your use case as needed.
This hook is intended to work with [quico.space/quico-os-setup/arch-zbm](https://quico.space/quico-os-setup/arch-zbm), a root-on-ZFS installation script that uses ZFSBootMenu as its boot loader; it's specifically intended for use on `arch-zbm` machines that use legacy BIOS. Before using this hook for any other purpose please closely review what it does and adapt to your use case as needed.
We do not care about `pacman` events other than a `syslinux` package update. Specifically if ZFSBootMenu gets an update `syslinux` and our Master Boot Record remain unaffected. Kernel update? Same, no change needed since no kernel or module change directly influence the simple and decoupled structure of `syslinux`.
@@ -62,6 +64,6 @@ Commit _types_ besides `fix` and `feat` are:
The following _scopes_ are known for this project. A Conventional Commits commit message may optionally use one of the following scopes or none:
- `script`: Any other script work that doesn't specifically fall into the above scopes
- `script`: Work related to the commands triggered by `pacman`
- `hook`: Configuring the hook(s)
- `meta`: Affects the project's repo layout, readme content, file names etc.