Re: upgrades must not change the installed init system [was: Re: Cinnamon environment now available in testing]
Marcin Kulisz wrote:
> On 2014-09-09 18:23:58, Josh Triplett wrote:
> > Michael Biebl wrote:
> > > Together with the /lib/sysvinit/init fallback binary in sysvinit and
> > > (and optionally my patch getting merged for grub [1]), this should
> > > provide for a hopefully seamless upgrade experience.
> >
> > Agreed, this seems like the best plan: avoid prompting in the common
> > case, prompt in cases that might cause problems, and provide an easy
> > fallback.
> >
> > In particular, given that /etc/init.d/* scripts are typically conffiles,
> > we could easily detect if they've been directly changed, and if so, warn
> > about edits (with a list of edited files) and point to information on
> > applying those changes to the corresponding systemd services.
>
> What about cases when init scripts doesn't come from any package but are
> crafted by hand?
Those init scripts will continue to work fine under systemd, as init
scripts, until the sysadmin gets around to rewriting them as systemd
services or similar. The case that prompted my comment involved edited
init scripts overridden by (unedited) .service files, which we can
address by scanning for modified init scripts that have overriding
services, and prompting in that case. However, that doesn't apply to
custom local init scripts.
- Josh Triplett
Reply to: