## 1. 66boot-* utilities
-In the boot-66serv package there are three sh scripts that try to make configurations for 66 on voidlinux as easy as possible.
-In many cases these will be the only configuration a user needs to get the stage 1 scripts configured correctly.
+In the boot-66serv package there are three small posix shell scripts that try to make configurations for 66 on voidlinux as easy as possible.
+In many cases, running these will be the only step a user needs to get the stage 1 scripts configured correctly.
These are:
+
1. 66boot-initial-setup
2. 66boot-rcdotconf
3. 66boot-storage-autoconf
### 2.1 66boot-initial-setup
`66boot-initial-setup` is the first script written.
-It created basic `trees` (boot, default and runit) and enables:
+It can be used to create basic `trees` (boot, default and runit) and enable:
- the `boot@system` module service in the *boot* tree,
- the `switch-initutils` service in the *default* tree and the
- `runit` service in the *runit* tree.
After running `66boot-initial-setup` a user is expected to configure their system, either by editing directly /etc/66rc.conf or by using `66-env`.
The boot@ service gives the user a lot of power in order to configure the boot process and that is awesome and... dangerous.
Some basic configuration keys correspond to the configurations keys in /etc/rc.conf and these settings can be safely transferred to the new configuration format. That is exactly what `66boot-rc.conf` does. And in many cases it will be enough to run it in order to configure the system.
-A user can then either continue using rc.conf and re-run the script on configuration changes or gradually learn the new configuration.
+A user can then either continue using rc.conf and re-run the script on configuration changes or gradually learn and take advantag of the new configuration format.
### 2.3 66boot-storage-autoconf
+When an option in the `boot@` module service configuration is disabled,the corresponding service script will not run at all. That is a very nice feature that lets a user finetune the boot process and avoid execution of what they do not need.
+It can also lead to severe problems in boot if a needed options are disabled. `66boot-rcdotconf` will check for the validity of some configuration keys when applying configurationf from `/etc/rc.conf`, but there was another area with potential issues.
+
+`boot@` has seperate services for the support of lvm, mdraid, dmraid, luks, zfs, btrfs. In the original implementation enabling one of these if the necessary utilities were not present in the system or even if there were but no storage device of the type was detected, the boot will fail.
+This was... correct, but also fragile. `66boot-storage-autoconf` was created to make this area of configuration easier for the user and the boot proccess more robust.
+
+This is accomplised by using `blkid` from `util-linux` to discover the TYPE of storage volumes in the system and `66-which` to determine if the corresponding utilities exisist. After that, the configuration is written with `66-env` in the environment/configuration file of the boot@system service and any iregularities are pointed out.
+
+## 3. Upstream contributions based on the scripts
+
+These three scripts are in some ways voidlinux-specific:
+
+- `66boot-initial-setup` is implementing policy that is based on the current official voidlinux policy. It does not have much that will help beyond the distribution.
+- `66boot-rcdotconf` is tranlating the voidlinux `/etc/rc.conf`, and while they are other distributions with similar configurations it is not certain that translated to exactly the same or compatible implementation.
+- `66boot-storage-autoconf` is probably the most distribution-independent of the three. But it still has some aspects - such as package names- that are voidlinux-specific. These are clearly documented in the script comments.
+
OSDN Git Service
