On Thu, Oct 30, 2008 at 10:09:14AM +0100, Christian Jaeger wrote:[color=blue]
> Yves-Alexis Perez wrote:[color=green]
>> do you still reproduce this?[/color]
> Well I haven't had the time to try again yet, but if nothing has
> changed, I'd expect it still be the case.[/color]
Well, except in the following you say you dont :)[color=blue]
>> I never saw something like this, so it's
>> kind of weird.
>> Can your provide complete log for update-initramfs -u -v ?[/color]
> I've now compiled 220.127.116.11, and run
> update-initramfs -c -v -k 18.104.22.168 => output_create.txt
> and after that,
> update-initramfs -u -v -k 22.214.171.124 => see output_update.diff for the
> difference from the above.
> I'm in the midst of pressing work, so I don't want to reboot now.
> Instead I've taken a look at the generated initrd file. But, to my
> amazement, the cryptroot file is back there now??:[/color]
If you manage to reproduce it (with 2.6.26 for example) please provide
the log from update-initramfs. You don't build your kernel with
make-kpkg (which, at install time, will generate the initrd itself)?
To UNSUBSCRIBE, email to [email]debian-bugs-dist-REQUEST@lists.debian.org[/email]
with a subject of "unsubscribe". Trouble? Contact [email]email@example.com[/email]