nina

it does work as expected: https://github.com/void-linux/void-mklive/blob/master/mklive.sh.in#L377 see how it's appended to `PACKAGE_LIST` i use this feature and it works

hm, not quite sure it shouldn't even let you proceed this far since the script expects a kernel package in format `linux`

oh, i see why - it's because the check uses `*` so it technically matches as long as there is `linux` in the name in your case, it doesn't work...

`ro` is a default kernel cmdline flag for majority of setups though, it mounts the root read-only and *then* it's the target system's job to remount it as rw.

I have a concept of "targets" in my system, which are basically like systemd targets or sysvinit runlevels, specifying different points in the boot process to which enabled services can...

relatedly to this, i've also been thinking whether we could have some way to have "providers" for services, as targets can still be pretty inflexible for this; e.g. a service...

`before` is more useful in general, because it allows you to ensure that services will guarantee having attempted to start at a specific point `after` doesn't provide any such guarantee...

the problems with this approach are basically 1) you need to use `dinitctl enable`, which only works when the service manager is running and its socket is present; therefore, people...

if this was implemented, i was thinking i could in general drop a lot of the target stuff, and instead set up the service relationships in a simpler and more...

> The problems are mainly around: > > * handling the case where the named "before" service isn't (yet) loaded, but gets loaded later (still potentially before either has started)...