Re: Init starting twice again
Loic Prylli <Loic.Prylli@ens-lyon.fr> writes:
> Jason Gunthorpe writes:
> >
> > On Tue, 3 Nov 1998, Loic Prylli wrote:
> >
> > > There is a new sysvinit alpha deb in master Incoming. It seems to
> > > accept well the telinit u. Hopefully you can upgrade safely from old
> > > ones to this one.
> >
> > Assuming the 'u' thingy works, can you upgrade the package and have it
> > NO trash the file system or will one more reboot be needed?
>
> I would say now, that you can upgrade from an install done with an old
> init (from the 980705 install set for instance), to the newer one
> without any reboot (and with no trash).
>
> You have to be very careful to upgrade the sysvinit package before the
> libc, (and libc before dpkg).
>
> The bug was encoutered after the re-exec is done. That means even
> while upgrading from a buggy init, as long as the new one is OK, the
> upgrade should go smoothly. That happened to me, but by security, you
> may want to have an experimental confirmation from someone starting
> with the same init version than you.
The question is whether the install scripts check the version of the
init RUNNING or the version of the init INSTALLED. If the latter is
the case, installing a new init twice, or a new and an even newer
version without rebooting would summon the bug. So I would rather
reboot after installing a working init.
BTW, is there already a compiled fixed version available for Alpha?
Falk
Reply to: