Mailinglist Archive: opensuse-packaging (118 mails)

< Previous Next >
Re: [opensuse-packaging] systemd presets vs. package install order

Hello,

On Jun 16 09:25 Ludwig Nussel wrote (excerpt):
If apparmor was previously installed but not enabled you cannot
know whether the admin intentionally left it in that state.

I think the actual issue is not what the old state was versus
what the new default state will be but that one cannot know
if our default is what the admin intentionally wants.

If our distribution default for the previously installed package
is known but the actual setings of the previously installed
package differs, the admin must have intentionally changed it
and the update of the package is not allowed to "simply change"
the admin's intentional settings.

Now one might think that when the actual settings of the previously
installed package is our distribution default, the update of the
package is allowed to change it to the distribution default of
the new package.

Example:

When the service in the old package is disabled by default and
its actual state is disabled, and the new default is enabled,
then the update would be allowed to enable the service.

But this is not true because the old package default
could be what the admin intentionally wants.


The following question might be off-topic but is still related:

Is there a generic method in the running system to reset the
systemd configuration of a service back to "factory defaults"?

My usecase:
For testing I run several "systemctl start/stop/enable/disable"
commands and afterwards I would like to go back to the pristine
state after a new system installation from scratch.


Kind Regards
Johannes Meixner
--
SUSE LINUX GmbH - GF: Felix Imendoerffer, Jane Smithard,
Dilip Upmanyu, Graham Norton - HRB 21284 (AG Nuernberg)

--
To unsubscribe, e-mail: opensuse-packaging+unsubscribe@xxxxxxxxxxxx
To contact the owner, e-mail: opensuse-packaging+owner@xxxxxxxxxxxx

< Previous Next >