On 06/16/2011 02:04 PM, Will Stephenson wrote:
On Friday 10 Jun 2011 19:04:14 Frederic Crozat wrote:
For discussing / helping with systemd integration for Factory, please use opensuse-factory mailing list or go to #opensuse-factory IRC channel on Freenode.
We need your help to make sure openSUSE 12.1 will use systemd at 200% ;)
Ok, I took the time to read and re-read all of the systemd blogs, some man pages, and our wiki articles, so here are my 2 cents on the matter:
To systemd maintainers, and maintainers of our init scripts: 1) Our sysvinit scripts are configured by sourcing variables from /etc/sysconfig. This allows us to keep common init scripts over several distribution versions and releases, and allows YaST to modify the way services are run by modifying /etc/sysconfig files only.
systemd service files support environment variable substitution for some keys, eg ExecStart, and the values are obtained from single config files specified by absolute paths in EnvironmentFile keys. Is this sufficient to maintain the same configurability as we use now in init scripts?
To systemd maintainers: 2) While I agree with systemd's performance goals and recognise the persuasive narrative for the socket activated design in the LP blog series, I hear that it additionally replaces other parts of userland. Massive uncertainty rules in my head about what those are and the wider effects of those changes.
As an example, http://lwn.net/Articles/441328/ mentions that there are plans to remove ConsoleKit and merge its functionality into a systemd helper daemon. What changes of this type to the runtime platform are implied by systemd that would affect eg a KDE session (other than https://bugzilla.novell.com/show_bug.cgi?id=655141) , and who is planning to do the work to adapt to those?
To systemd maintainers, and everyone else, since I suspect the systemd guys are not omniscient: 3) What are the big gaps that it doesn't currently do, compared to sysvinit? I hear of things like encrypted LVM volumes not working being dismissed as unimportant.
tested (/boot simple partition) and full rest encrypted volume group with several logical volume. (/ /var swap /home) Works, has to be finished to not fsck each volume at each restart.
I'll start you off with "password agents to do interactive things during service startup, eg openvpn passwords" (bnc675406): http://www.freedesktop.org/wiki/Software/systemd/PasswordAgents
4) Are non-NetworkManager network configurations supported? was working on a 11.4 + systemd + normal network + Gnome3
Will
But yes several systemd native service are not ready/fully apache2 (who try the different worker?) postgresql (which is a complicated one to get it upstream) rpm based have on pg version, debian like have several version supported. Oh Will there's a trend actually to kill a vast majority of the /etc/sysconfig contain :-) -- Bruno Friedmann Ioda-Net Sàrl www.ioda-net.ch openSUSE Member & Ambassador GPG KEY : D5C9B751C4653227 irc: tigerfoot -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org