Bug#497313: [Splashy-devel] Bug#497313: Bug#497313: splashy: deb hooks don't rebuild initramfs for all installed kernels
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 is not updating the initramfs of the current kernel (the one you are running), but it is updating the initramfs of a kernel which is sorted as highest by some algorithm I do not remember the details of. What is most important is that it will always be the same kernel, whatever one you are running at the moment. I think the sorting is such that under normal circumstances (as in: you just track the debian kernels) it will update the newest kernel. 2) What happens if I rebuilt the initramfs of kernel A to include splashy, but then I boot kernel B and remove the splashy package, then reboot to kernel A? Won't the kernel load the boot screen that was included? But I've removed it so what will happen after switching root? If you boot an initramfs with splashy included while it is removed from the root system, splashy will be started from initramfs as usual. The process will probably just survive the root-switching. There will however not be a splashy-update command on the root file system, so the progress bar will not be updated. Splashy will however timeout at some point. You will also still be able to kill splashy manually. So nothing dramatic will happen. You can also change the kernel command-line from grub and add nosplash to supress splashy. I think there should be a splashy update that wraps update-initramfs (or yaird or whatever you have selected) and keeps track of which kernels have splashy installed. That sounds much to fragile. Then `splashy_config -s theme` can call that automatically. (That was something that took me a while to figure out that I needed to do BTW.) [ this is not relevant for the current discussion, but it is probably a good idea to let splashy_config rebuild the initramfs as if it were a package update] As I explained before it was agreed under all maintainers supplying initramfs additions that rebuilding more than one initramfs on upgrades/removals is not going to happen by default. This is what was the concensus. Also `normal' users will find their system working as usual. It will only give (minor) problems if you start installing custom kernels. 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? Tim -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#497313: [Splashy-devel] Bug#497313: Bug#497313: splashy: deb hooks don't rebuild initramfs for all installed kernels
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 (non-default) would be a good thing for average desktop users who would want splashy on for all kernels but who don't want to mess with initramfs-tools config files or don't know how. Thanks! -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#497313: [Splashy-devel] Bug#497313: Bug#497313: splashy: deb hooks don't rebuild initramfs for all installed kernels
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 debconf option for Splashy that lets the user choose to configure it that way (non-default) would be a good thing for average desktop users who would want splashy on for all kernels but who don't want to mess with initramfs-tools config files or don't know how. Well, because it is an option of initramfs-tools it should be a debconf-option for that package. But yes, that would be an idea. I even implemented it already;), only the initramfs-tools maintainer chose not to use the patch. grts Tim -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#497313: [Splashy-devel] Bug#497313: Bug#497313: splashy: deb hooks don't rebuild initramfs for all installed kernels
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 after I filed. Makes sense to me. If I installed splashy, then I want boot splash screens, right? 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 packages that want to alter an initamfs are now supposed to call the same command which by default only rebuilds the initramfs of the current kernel. If you do want to rebuild all initramfses on an updte you can configure update-initramfs-tools to do that. I do not know the configuration file by hard but you can probably find it easily under /etc/. grts Tim -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#497313: [Splashy-devel] Bug#497313: Bug#497313: splashy: deb hooks don't rebuild initramfs for all installed kernels
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 packages that want to alter an initamfs are now supposed to call the same command which by default only rebuilds the initramfs of the current kernel. If you do want to rebuild all initramfses on an updte you can configure update-initramfs-tools to do that. I do not know the configuration file by hard but you can probably find it easily under /etc/. OK, well, 1, that's not what it did, and 2, that may break. 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. 2) What happens if I rebuilt the initramfs of kernel A to include splashy, but then I boot kernel B and remove the splashy package, then reboot to kernel A? Won't the kernel load the boot screen that was included? But I've removed it so what will happen after switching root? I think there should be a splashy update that wraps update-initramfs (or yaird or whatever you have selected) and keeps track of which kernels have splashy installed. Then `splashy_config -s theme` can call that automatically. (That was something that took me a while to figure out that I needed to do BTW.) And when you uninstall it should look up the kernels into which you've installed splashy, and rebuild only those. Mark -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
