Mark Hedges schreef:
1) When I installed splashy with apt-get I was running my
custom kernel. When I removed splashy I was running the
stock kernel, but it rebuilt initramfs for the custom
kernel. So it did not by default only rebuild the
initramfs of the current kernel.
You're right. It
As I said, there is the possibility to configure
initramfs-tools to rebuild all initramfses on removal, why
isn't that a solution for your use case?
Oh I see, I didn't get that. That would work.
Maybe a debconf option for Splashy that lets the user choose
to configure it that way
Op Wed, 3 Sep 2008 11:03:18 -0700 (PDT)
schreef Mark Hedges [EMAIL PROTECTED]:
As I said, there is the possibility to configure
initramfs-tools to rebuild all initramfses on removal, why
isn't that a solution for your use case?
Oh I see, I didn't get that. That would work.
Maybe a
tags 497313 +wontfix
thanks
Mark Hedges schreef:
I was going to write that this was an update-initramfs
problem, but I just found in the manpage that one can call
update-initramfs -u -k all to update initramfs for all
kernel versions. I guess splashy should do this?
Yeah I saw that too
On Tue, 2 Sep 2008, Tim Dijkstra wrote:
Well, this is what splashy used to do, but there were complains about
this. Some people want to keep old initramfses around which are known to
work. Also updating all initramfses could potentially take a very long
time. It is now agreed, that all
5 matches
Mail list logo