On Mon, Sep 07, 2009 at 10:46:34AM +0200, Bastian Blank wrote:
> > I really can't explain you why the behaviour is still the same.
>
> The mentioned bug shows a different problem.
I suspect that the referenced bug report was made with "/" being ext2,
while nowadays ext3 is the default. If I'm ri
W dniu 2009-09-07 10:46, Bastian Blank pisze:
[...]
>> 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".
>
> That is expected as there
On Mon, Sep 07, 2009 at 12:36:08AM +0200, Piotr Kaczuba wrote:
> 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
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 th
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 dealloca
Package: libc6
Version: 2.9-26
Severity: normal
The postinst script must run "telinit u" so that init re-executes itself.
Otherwise, on reboot, the old libc won't be properly deleted. See also
bug #25444.
"Telinit u" was there but with 2.9-23, it was removed from the postinst
script for unknown r
6 matches
Mail list logo
