[systemd-devel] Breaking ordering cycles... a suggestion.
Lennart Poettering
lennart at poettering.net
Mon May 21 08:55:42 PDT 2012
On Thu, 17.05.12 16:00, Colin Guthrie (gmane at colin.guthr.ie) wrote:
> >> Or do you think it's not even worth it (medium
> >> term goal is probably to disable support for non-native units at compile
> >> time anyway I guess...)
> >
> > I think we will keep that for a long time. We plan though, to rip out
> > all sysv code and provide the functionality with generators running at
> > bootup. This would read all the sysv init scripts and create .service
> > files in /run for them.
>
> Ahh yes, I can see that being a cleaner system right enough. It would
> still be nice to know that a given unit is actually sysv, lsb or native
> tho' (and actually generating files in /run would kind of blur the "is
> native" question a bit) for the purposes of this prioritisation, but I
> guess just knowing if the unit was from lib, run or etc might be enough
> in this case.
I have now added an item to the todo list so that we priorize what to
drop by its location in /run vs. /usr and so on.
Lennart
--
Lennart Poettering - Red Hat, Inc.
More information about the systemd-devel
mailing list