From Mageia wiki
Jump to: navigation, search

Summary

The installer currently runs on top of a cut down init. It should be converted to systemd which will allow for more complete service administration during install.

Owner

  • Name: Colin Guthrie
  • Email: colin@mageia.org

Resources

QA to ensure installer works.

Current status

  • Targeted release: Mageia 3
  • Last updated: 2013/03/20
  • Percentage of completion: 0%

Note: I didn't have enough time to work on this feature for Mageia 3. I will attempt again for Mageia 4!

Detailed Description

Currently, the service management code in drakx supports three different mechanism of managing services. 1) sysvinit via chkconfig, 2) systemd via systemctl and 3) systemd via filesystem proding+chkconfig. The third mode in particular use used only in the installer where a running systemd instance is not available for full service introspection. If the installer ran systemd itself, we could run systemd-nspawn (a sort of substitute for chroot) which will allow us to have a more unified codebase for service management.

Why it would be good for Mageia to include it

It reduces the "customised" nature of the installer and rescue systems to use more standard constructs for which more people will ultimately have knowledge.

Test case

Just make sure the installer works.

Software / Packages Dependencies

  • drakx: Support needs to be written for a systemd boot and service management code should be consolidated.

What could disrupt development of this new feature

Nothing external.

Planning

Research into how stage1 and stage2 work and planning of how best to move from stage1 to stage2 (systemd targets?) should allow for a detailed plan of how to implement systemd for the installer.

Contingency

If things don't work we still with what we've got.

Release Notes

Documentation