W dniu 06.09.2009 13:25, Bastian Blank pisze:
On Sat, Sep 05, 2009 at 04:20:55PM +0200, Piotr Kaczuba wrote:
The postinst script must run "telinit u" so that init re-executes itself.
Otherwise, on reboot, the old libc won't be properly deleted.
Please show your test results. This would mean that the kernel is not
able to properly deallocate inodes in use by init.
See also
bug #25444.
This bug is over 10 years and many, many kernel and glibc releases old.
Please explain why the behaviour is still the same.
[...]
No sophisticated test results are needed, really. Just do an upgrade of
libc and see what happens on reboot. Init is still using the old libc
and the read-only remount of / fails with "mount: / is busy". And it's
not the inodes used by init that the kernel can't deallocate but the
ones of the old libc because init is still using it.
I really can't explain you why the behaviour is still the same. You
should be asking this question on the kernel mailing list if you feel
that it should be different. Anyway, before removing "telinit u" from
the postinst script, you should have checked yourself that it's not
needed any more.
Regards,
Piotr
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
