On 11 July 2011 15:09, Andreas Jaeger <aj@suse.com> wrote:
We're not talking about the sysadmin in the proposal (at least not directly)!
The proposal is for distributors how they will configure the system - to define which services are run by default and which not.
The sysadmin will configure the system starting from the preconfiguration with systemctl. No need for the admin to learn about all this magic ;)
Fine but why complicate things, does someone really want to write a file parser? If you just have Disable as default policy, and then have flag set by distro to make "enable" a global default, that's it done. It DOES matter to the sysadmin, because if it's : service-default-install-policy enabled disabled Once at a large installation, will going to want to change the policy most likely; for example if the admin have 2 distro's they'll want the SAME defaults! So the simpler you make it the better alround. What can be more efficient than 0 byte files for a flag in 2 directories? A runninug system does indeed have systctl etc, but I thought the was Distro policy, package polocy with some over-ride. It may seem different, to the running system, but it'd be likely quite easy to write scripts to do the systemctl to match the site policy, when one desired, if you define it nicely. Filesystem state has advantages, because there's good tools to replicate it. Regards Rob -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org