On Tue, 2018-04-17 at 05:46 +0000, Petr Pisar wrote: > On 2018-04-17, Zbigniew Jędrzejewski-Szmek <zbyszek@xxxxxxxxx> wrote: > > I'm a bit surprised that there's no reply to this fairly explosive > > idea. Maybe Nikos' text is too long, so let me summarize: > > > > tl;dr: the proposal is to start services immediately during > > installation (in %post), iff they are enabled in presets and the > > system is live (not a chroot or such). > > > > Maybe nobody knows how to determine a system is live. This determination is on systemd and if anyone should know that, it should be a init, isn't it? >From the comment #30 in bug #1545027, there is a reference to snapd spec file, that is already doing this (using systemd). I would not say this is a problem today, we would not be able to tell if we can or can not start a service. systemd is powerful and can simplify these things for us. The problem is that it does not matter for most of the technical people to run one more command "systemctl start foo" after "dnf install". But it really does for non-technical ones. They usually have to reboot to make things work (hello M$). This is also the reason why the snapd has this post script -- it is much more (likely) to be used by non- technical people than the smart cards daemon and less likely to be installed out of the box. If we want to make it simpler to use for *any* user, we should go this way and allow starting enabled services after installation, either by explicit post scriptlet or automatically inside of existing systemd scriptlets. [1] https://bugzilla.redhat.com/show_bug.cgi?id=1545027#30 Jakub Jelen Software Engineer Security Technologies Red Hat, Inc. _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
