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

Bug#562847: closed by maximilian attems <maks@debian.org> (Bug#519800: fixed in initramfs-tools 0.94)



On Fri, Apr 09, 2010 at 03:42:57PM +0200, maximilian attems wrote:

> > suggest move backup out of /boot. This way we can have a number of
> > versions of initrd.
>
> no this is related to /boot space.

Wonderful! The hard logic. Yes, if You have too big /boot then You can
have lot of backup initrd there. But we want keep it small, isn't?.

> it was needed in the past and may still be helpful thus kept as option,
> but it will clutter much less.

It should not be option, it should be main functionality. And all
"clutter" should go out of /boot.

> > Not enough as soon as old image remain in place while new one
> > generated. Thus space needed is doubled in any way. It is good idea to
> > generate the new image out of /boot and then replace old image with new
> > one.
>
> this is admin error of too small /boot/.

How long You will repeat this absurdity? This will not "admin error" if
You will not use /boot for backup and temporary files. There are some
other places for this purposes, do You know?

> you context a change that was done for better reliability and
> you miss context of it, read
> https://wiki.ubuntu.com/HardyInitramfsErrorHandling

OK. I see, but there are nothing what I don't already know at least
related to this discussing. That is simple algorithm:

        1. You backup old intrd image
        2. You create new image as temporary file.
        3. You move new image in place of old one.
        4. If it fail due to low disk space You move back the old image
           into its' place.

And then You proudly say me "that was done for better reliability"! But
this is poor "reliability". This way You solve only one case, when
system become unbootable: when new image are already overridden by old
one, but there are not enough space for that and You have not neither
new nor old image. But there are other cases when system become
unbootable, for example due to contents of new image itself. This is
common case, when You can not boot with new image, but old one already
overridden, because image was generated few times before system boot.
Please, don't tell me, this is "admin error" again.

I don't understand, why You don't agree to move backup and temporary
files out of /boot? In this case Your idea of "reliability" remain in
place: when You can not replace old image with new one due to low disk
space, You will roll back to the old image as You do this now.

-- 

*********************************
****   Vladimir Stavrinov  ******
*******   vs@inist.ru   *********
*********************************




Reply to: