Mageia: systemdMageia: systemd

Colin GuthrieMageia ContributorColin GuthrieMageia Contributor

A little about...A little about...

...Me!!!...Me!!!

What is Mageia: BackgroundWhat is Mageia: Background

● Mandriva

● Good, strong user community

● Commercial problems

● Mageia

● Community focused, non-commercial

● Most of the original community

● Encourage commercial usage

● Mandriva

● Good, strong user community

● Commercial problems

● Mageia

● Community focused, non-commercial

● Most of the original community

● Encourage commercial usage

How Things WorkHow Things Work

● Council

● Various groups

● Regular meetings

● Try to be inclusive in terms of packages, but mindful of resources

● Ultimately... it’s a “Meritocracy”– Those who do, decide

● Council

● Various groups

● Regular meetings

● Try to be inclusive in terms of packages, but mindful of resources

● Ultimately... it’s a “Meritocracy”– Those who do, decide

Pushing ChangesPushing Changes

● Each cycle we propose changes

● General review + vote

● Then the fun begins!– Usually the week before freeze!

● Each cycle we propose changes

● General review + vote

● Then the fun begins!– Usually the week before freeze!

Boot + InitBoot + Init

● Previously used sysvinit

● Various experiments and toe-dipping to speed up boot performance

● More parallelisation

● Start X11 early to improve perceived boot time

● Early systemd packaged as an option

● Previously used sysvinit

● Various experiments and toe-dipping to speed up boot performance

● More parallelisation

● Start X11 early to improve perceived boot time

● Early systemd packaged as an option

Why systemd?Why systemd?

● See other talks!!

● Sysadmin

● Clear up the mess of sysvinit/inittab/boiler-plate

● Stateful tracking of services

● Automatic restart on failure

● Better tracking of service processes (cgroups)

● Socket activation

● See other talks!!

● Sysadmin

● Clear up the mess of sysvinit/inittab/boiler-plate

● Stateful tracking of services

● Automatic restart on failure

● Better tracking of service processes (cgroups)

● Socket activation

Mageia 2: systemd by default?Mageia 2: systemd by default?

● Proposal to use systemd as default init

● Proposal accepted \o/

● systemd (v44) is the default init in Mageia 2

● sysvinit still supported as an option

● Proposal to use systemd as default init

● Proposal accepted \o/

● systemd (v44) is the default init in Mageia 2

● sysvinit still supported as an option

Issues EncounteredIssues Encountered

● Various technical issues encountered– Packaging helpers

– Migrating service state on upgrade

– Forcing conversion to systemd on upgrade

– Ordering cycles and LSB headers

– Nothing too troubling!

● Various technical issues encountered– Packaging helpers

– Migrating service state on upgrade

– Forcing conversion to systemd on upgrade

– Ordering cycles and LSB headers

– Nothing too troubling!

More Issues EncounteredMore Issues Encountered

● GUI Utilities and Installer– Mageia (and Mandriva before) offer a “services”

GUI application during install and for administrators post install

– Had to be converted to systemd but also support sysvinit

– Combination of “systemctl list-units”, “systemctl list-unit-files” and “chkconfig --list”

● GUI Utilities and Installer– Mageia (and Mandriva before) offer a “services”

GUI application during install and for administrators post install

– Had to be converted to systemd but also support sysvinit

– Combination of “systemctl list-units”, “systemctl list-unit-files” and “chkconfig --list”

Knock on DependenciesKnock on Dependencies

● LVM + Device Enumeration– udev metadata more important

– mkinitrd does not use udev /o\

– Solution? Use dracut \o/

– Mageia 2 only supported systemd+dracut

– mkinitrd+sysvinit still officially supported

● LVM + Device Enumeration– udev metadata more important

– mkinitrd does not use udev /o\

– Solution? Use dracut \o/

– Mageia 2 only supported systemd+dracut

– mkinitrd+sysvinit still officially supported

Non-Technical Issues?Non-Technical Issues?

● Some minor FUD, but nothing significant

● Overall, due to our QA team there were very few post-release complaints or problems

● Hard to judge accurately but ~90%+ users use systemd

● Some minor FUD, but nothing significant

● Overall, due to our QA team there were very few post-release complaints or problems

● Hard to judge accurately but ~90%+ users use systemd

Upstream + X-Distro EngagementUpstream + X-Distro Engagement

● Good relationship upstream

● Several fixes pushed upstream

● Helped upstream QA

● Very encouraging relationships with other distros

● Nice to see small differences disappearing

● Good relationship upstream

● Several fixes pushed upstream

● Helped upstream QA

● Very encouraging relationships with other distros

● Nice to see small differences disappearing

What’s Next for Mageia?What’s Next for Mageia?

● Mageia 3– Drop support for sysvinit + mkinitrd

– Implement the /usr move

– More disciplined packaging● No udev rules in /etc● No tmpfiles configs in /etc

● Mageia 3– Drop support for sysvinit + mkinitrd

– Implement the /usr move

– More disciplined packaging● No udev rules in /etc● No tmpfiles configs in /etc

What’s Next for Mageia?What’s Next for Mageia?

● Mageia 4– Tidy up packaging rules

● No referencing of /bin, /sbin and /lib[64] in packaged files

– Switch to Predictable Network Interface Names

– Attempt to reduce packaging variations● Enabling/Restarting package on install/upgrade● Adopt Package Presets

– Change how X (or $DISPLAYSERVER) starts

● Mageia 4– Tidy up packaging rules

● No referencing of /bin, /sbin and /lib[64] in packaged files

– Switch to Predictable Network Interface Names

– Attempt to reduce packaging variations● Enabling/Restarting package on install/upgrade● Adopt Package Presets

– Change how X (or $DISPLAYSERVER) starts

What’s Next For Distributions?What’s Next For Distributions?

????????