The following message is a courtesy copy of an article
that has been posted to gmane.linux.debian.devel.kernel as well.
On 26 Mar 2006, Jonas Smedegaard wrote:
> On Sun, 26 Mar 2006 15:56:15 +0200
> maximilian attems <[EMAIL PROTECTED]> wrote:
>
>>> The init ram fs was not created using initramfs-tools, and yet it
>>> tries to recreate the initramfs on upgrade, without asking the
>>> admin, which is an problem in its own right: Why is automated
>>> regeneration of the initramfs being done? If I want to, I should
>>> be able to refresh the initrd when I wish it should be updated.
>>
>> ok so an upgrade of initramfs-tools tried to alter an yaird
>> generated initramfs. i'm sorry but i can't reproduce that:
>
> Perhaps the ramdisk is actually (auto-)created by initramfs-tools
> without Manoj noticing, due to the (since fixed, I believe) bug in
> initramfs-tools of forcing regeneration (disregarding the
> checksums)?
No, I manually created that initrd.
> Manoj: Could you please double-check that the ramdisk is in fact not
> generated by initramfs-tools? If you believe it to be built using
> yaird instead, then simply looking at the size of the file is
> probably enough...
Yes, it is indeed created by yaird. I had tried an initramfs
tools created ramdisk, but that failed with cryptsetup, so I went
back and ued yaird to recreate q woeking ramdisk.
manoj
--
I used to think I was indecisive, but now I'm not so sure.
Manoj Srivastava <[EMAIL PROTECTED]> <http://www.golden-gryphon.com/>
1024D/BF24424C print 4966 F272 D093 B493 410B 924B 21BA DABB BF24 424C
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
