Re: s6/66 integration (previously boot-66serv )

[mobinmob <mobinmob@users.noreply.github.com>]

[-- Attachment #1: Type: text/plain, Size: 1302 bytes --]

New comment by mobinmob on void-packages repository

https://github.com/void-linux/void-packages/pull/45578#issuecomment-1950238891

Comment:
> Oh good to know. Am I assuming correct that the values in the `[]` of each line in the [configuration file](https://git.obarun.org/obmods/boot-66serv/-/blob/master/configure?ref_type=heads) are showing the default value for the argument? If so, could we remove the `KEYMAP` argument in the template? Are the `TTY` and `TZ` arguments necessary for the building process?

The configuration file for the boot@ service contains by default all possible keys. 
That may change in the future but the upstream logic is to be explicit in configuration. In order to prevent anything missing that may result in weird behaviour, I have created a way to test the configuration ([see here](https://git.obarun.org/obmods/boot-66serv/-/merge_requests/1)) and missing keys is an error.  
The configure arguments in the template are just the default values that the void configuration has, nothing more. They are there only to ensure that the default configuration mathes the voidlinux default one.
`66boot-rc.conf` can populate the configuration with the values from the void `/etc/rc.conf` file and `66boot-starage-autoconf` finds the correct values for ZFS,BTRFS etc.