You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'll try to hack a plugin to autodetect crypted devices and another for LVM PVs.
Is there a cond I might use for "new device detected" so I could simply make both plugins try their luck?
Then order would not matter since both use a device but also create (at least one) new.
I was interested as well in finit because of its simplicity. However, in my understanding it's a “blackbox” that performs many steps on your behalf at boot (which isn't necessary a bad thing) but makes complex cases much harder to implement. This includes RAID, ZFS, LVM, LUKS or other things to perform before mounting /.
Either the solution would be to provide a way to customize the pre-boot process or to implement those things directly in finit (which to me is more error-prone). Or perhaps a initramfs performing its own steps before running finit?
Do you have some recommendations for that or ideas?
@markand For now I'd recommend a separate initramfs before running finit, definitely. That's how I set up my own RAID. There are some hand-over mechanisms defined by freedesktop/systemd (@ as first char in process name) that you can look into.
For a pure Finit approach, however, I'd very much like to see a native plugin for each separate task. The whole point of Finit is to be more integrated and use less scripts, otherwise you'd just end up with yet another SysV init or runit clone.
Activity
troglobit commentedon May 5, 2017
You're more than welcome to give it a try! 😃
DeX77 commentedon May 5, 2017
Used a VM with attached encrypted LVM PV and finit says (or to be precise: mount -na says) it could not find the special device.
Here is summary of what I did: https://wiki.archlinux.org/index.php/Dm-crypt/Encrypting_an_entire_system#LVM_on_LUKS
I'll try to hack a plugin to autodetect crypted devices and another for LVM PVs.
Is there a cond I might use for "new device detected" so I could simply make both plugins try their luck?
Then order would not matter since both use a device but also create (at least one) new.
troglobit commentedon May 8, 2017
Sorry for the late reply, but could mdev/udev be an alternative for this?
Currently implemented conditions are:
svc/<PATH>net/route/defaultnet/<IFNAME>/existnet/<IFNAME>/upDeX77 commentedon May 9, 2017
Had the same idea already. 😄
Will try to find some sufficient udev rules. Maybe borrowed from dracut.
troglobit commentedon May 9, 2017
troglobit commentedon Jul 3, 2017
@DeX77 did you ever resolve your issue? (Asking because bug triage prep for v3.0)
DeX77 commentedon Jul 4, 2017
@troglobit I actually didn't try further, sorry. Perhaps move it to a later milestone?
troglobit commentedon Jul 4, 2017
@DeX77 Sure thing! 👍
markand commentedon Mar 20, 2019
Hello,
I was interested as well in finit because of its simplicity. However, in my understanding it's a “blackbox” that performs many steps on your behalf at boot (which isn't necessary a bad thing) but makes complex cases much harder to implement. This includes RAID, ZFS, LVM, LUKS or other things to perform before mounting /.
Either the solution would be to provide a way to customize the pre-boot process or to implement those things directly in finit (which to me is more error-prone). Or perhaps a initramfs performing its own steps before running finit?
Do you have some recommendations for that or ideas?
troglobit commentedon Mar 20, 2019
@markand For now I'd recommend a separate initramfs before running finit, definitely. That's how I set up my own RAID. There are some hand-over mechanisms defined by freedesktop/systemd (@ as first char in process name) that you can look into.
For a pure Finit approach, however, I'd very much like to see a native plugin for each separate task. The whole point of Finit is to be more integrated and use less scripts, otherwise you'd just end up with yet another SysV init or runit clone.