Closed WavyEbuilder closed 1 month ago
Thanks, I appreciate the quick response. As for it doesn't seem that any of refpolicy's distros support this
, that seems to be correct from what I have seen, yes. I'll bear it doesn't seem that any of refpolicy's distros support this.
in mind to try and minimize the changes outside of the base interfaces in the init policy module for example.
Thanks again
Hi!
I'm looking to add support for the dinit init system and service manager to the refpolicy. I had a few questions along the way, so I thought I would create an issue to track them here.
1) Would upstream be interested in this? 2) Regarding unit files, the current policy seems very much designed around the concept that only systemd has unit files, and all other init systems have init scripts. In the case of dinit this is wrong; dinit has unit files. For example, the init_unit_files interface has the following policy:
This quite clearly is designed around systemd here. A possible design idea I had for this was to make use of the already existing systemd build option, allowing for something like this:
Would this be a desirable approach to upstream? My approach going into this is to ensure that no significant changes (ideally none) are needed outside of the base system init policy, keeping interface APIs the same.
3) Are there any caveats/stumble-blocks I should be careful with along the way that should be noted?
Thanks