Steve Lord schrieb:
>
> On Thu, 2002-04-25 at 10:59, Sean Neakums wrote:
> > commence Simon Matter quotation:
> >
> > > I guess you have also updated glibc. IIRC when updating glibc, the
> > > root fs can not be unmounted properly (remount readonly) on shutdown
> > > and therefore you'll notice recovery on the first boot after glibc
> > > upgrade. It has always been like this and was very annoying with
> > > big root fs on ext2 :) I'm sure it's not kernel related.
> >
> > I have never seen this happen after glibc upgrades on Debian systems,
> > and I can't think of a reason why it should happen at all. Steve's
> > suggestion that it's the readonly-remount-path bug sounds a lot more
> > plausible.
>
> It could be a case of dpkg being smarter than rpm here.
Okay, the problem I remembered has affected RedHat until recently. The
glibc RPM didn't 'telinit u' after upgrade so 'init' still used the old
glibc and / could not be unmounted properly.
http://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=17345
I think steve was right with the remount readonly bug. You can try 'rpm
-V xxx' on the upgraded packages to check integrity.
Simon
>
> Steve
>
> --
>
> Steve Lord voice: +1-651-683-3511
> Principal Engineer, Filesystem Software email: lord@xxxxxxx
|