[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: sysvinit 2.88dsf-26 still not safe to upgrade



Hi!

On Fri, 8 Jun 2012 00:46:16 +0200, Pino Toscano <pino@debian.org> wrote:
> Alle martedì 31 gennaio 2012, Pino Toscano ha scritto:
> > Alle martedì 31 gennaio 2012, Svante Signell ha scritto:
> > > Be careful not to upgrade to initscripts  2.88dsf-21 or  2.88dsf-22
> > > is you want to play safe.
> > 
> > In particular, any version of sysvinit >= 2.88dsf-19 during the
> > migration from /dev/initctl to /run/initclt causes a SIGUSR1 to be
> > sent to the process with PID 1, which for us is /hurd/init.
> > (This uncover an old gotha with kill(), which allows base system
> > processes to be killed.)
> > The affected packages are all the ones of the sysvinit source, i.e.:
> >   sysvinit sysvinit-utils sysv-rc initscripts bootlogd
> > 
> > A solution for this is already being investigated with Roger Leigh.
> 
> The problem above of sysvinit killing PID 1 has been fixed with 
> 2.88dsf-26, landed in unstable syeterday... although this version (in 
> particular, sysv-rc) does not configure correctly -- #676463
> 
> Until that is solved, the advice is to not upgrade 
>   sysvinit sysvinit-utils sysv-rc initscripts bootlogd

Seems that we're fine again:

    Preparing to replace sysvinit 2.88dsf-13.13 (using .../sysvinit_2.88dsf-28_hurd-i386.deb) ...
    Unpacking replacement sysvinit ...
    Processing triggers for man-db ...
    Setting up sysvinit (2.88dsf-28) ...
    sysvinit: creating /run/initctl
    Not restarting sysvinit: init not running

And:

    Preparing to replace sysv-rc 2.88dsf-13.13 (using .../sysv-rc_2.88dsf-28_all.deb) ...
    Unpacking replacement sysv-rc ...
    Processing triggers for man-db ...
    Setting up sysv-rc (2.88dsf-28) ...


Grüße,
 Thomas

Attachment: pgpBqXJclDEaI.pgp
Description: PGP signature


Reply to: