Contents
Summary
We should aim to not package/ship any SystemV initscripts in Mageia.
Owner
- Name: Colin Guthrie
- Email: colin@mageia.org
Resources
systemd maintainer, Colin Guthrie
Current status
- Targeted release: Mageia 4
- Last updated: 2013-01-21
- Percentage of completion: 0%
Detailed Description
We should aim to not package/ship any SystemV initscripts in Mageia. These should be replaced by native systemd units providing the same, but native capabilities. An exception to this rule might be the "initscripts" package which may be more hassle than it's worth to migrate (specifically the network initscript)
Why it would be good for Mageia to include it
Mageia 3 dropped support for sysvinit and only supports systemd. By utilising native systemd units everywhere we can provide a first class distribution with clear documentation for administrators on how to administer their system. There would be less caveats in said documentation if we do not have to explain (in detail) about sysvinit scripts and how they operate and how support is provided for these "legacy" systems in systemd.
Test case
Simply testing daemons which are run as system services.
Software / Packages Dependencies
None specifically, although obviously several packages will be affected.
What could disrupt development of this new feature
Not a lot. We already use systemd only. It's just a matter of translating sysvinit scripts into native systemd units.
Planning
We should co-operate with both other distros (e.g. Fedora, Suse and Arch specifically) whose existing efforts in writing and upstreaming systemd units can be leveraged. When there is not an active upstream plan we should aim to contact upstream and ask them to include the systemd support in their next release.
Contingency
If we do not complete this task, we will still support sysvinit anyway, and thus there is little impact in not completing this feature.