#39: Fedora 14: spin-kickstarts adjustments for dconf and systemd ------------------------------+--------------------------------------------- Reporter: adamwill | Owner: Type: defect | Status: new Priority: blocker | Milestone: Fedora 12 Alpha Component: fedora-live-base | Keywords: ------------------------------+--------------------------------------------- This ticket is to track changes that should be made to spin-kickstarts for Fedora 14 to accommodate systemd and potentially gconf -> gsettings/dconf migration.

the livesys service created in fedora-live-base / fedora-live-mini uses chkconfig multiple times to disable certain services during live boot. We should probably either add 'systemctl' commands here or replace the 'chkconfig' commands with 'systemctl' commands (not sure if we want to keep the chkconfig calls for building pre-F14 live images, or what). There's a plan to make chkconfig compatible with systemd, but even so it's probably best to use the 'native' tool where we can.

The command change is pretty simple, for e.g., 'chkconfig --level 345 yum- updatesd off 2>/dev/null' should become 'systemctl disable yum- updatesd.service 2>/dev/null' . However, we may need to make further adjustments, because systemd is not a serial init system: unless the relationship is specified somehow, we can't assume that the livesys service will be run before the services it's meant to disable. Possibly the easiest way to do this would be to make the livesys service a native systemd service and specify Before= relationships for all the services it's intended to disable. (If we're going to do that it might be nice to split the two services up a bit further into systemd service files (and add additional files for the customizations each spin makes to the services), make a target out of the group of them, and ship it in an RPM package that only live spins include, instead of the current slightly hacky method of writing it out in %post of fedora-live-base and fedora- live-mini).

Note that systemd is currently actually not capable of doing this (having one service disable subsequent services during the same boot sequence) at all, even if everything is configured correctly; I have a bug open against systemd for that, and Lennart will be looking at it. https://bugs.freedesktop.org/show_bug.cgi?id=29535

Secondly, the livesys service runs a bunch of gconftool-2 commands to disable NetworkManager update notification during the live system. We may need to adjust these tools for dconf/gsettings, if NetworkManager is migrated. I'll try to get more info on that from the desktop team.