Re: s6-linux-init: Actions after unmounting filesystems

2019-08-17 Thread Casper Ti. Vector
On Sat, Aug 17, 2019 at 11:01:35PM +, Laurent Bercot wrote: > The asymmetry of mounting and unmounting filesystems is really a pain > in the ass for the design of an init/shutdown sequence. I wanted to > keep the shutdown as quick, minimal, and reliable as possible, but it > seems there's no

Re: s6-linux-init: Actions after unmounting filesystems

2019-08-17 Thread Laurent Bercot
There are certain setups that require doing something after filesystems are unmounted. Two examples are LVM logical volumes and LUKS encrypted volumes, but I suppose there must be more cases. In any such setup, the shutdown sequence would include a 'vgchange -a n' command or 'cryptsetup close'

s6-linux-init: Actions after unmounting filesystems

2019-08-17 Thread Guillermo
For the 0.4.x.x series of s6-linux-init, the shutdown sequence model was that s6-svscan replaced itself with a 'stage3 init' that ran as process 1 until the machine halted, powered off, or rebooted. The stage3 init was an execline script. s6-linux-init-1.0.0.0 and later, among other things, has