On Monday 09 Jun 2008 06:05:45 you wrote: > I take from this that you are using Splashy from initramfs but init-top is > not "early" enough for your installation of LUKS? > > Why don't you move the Splashy script where it make sense for your system > and redo your initramfs? > > Splashy (or any other applications) won't be "panacea". Meaning, there is > no perfect solution for all systems world-wide. Different people have > different needs.
I think the problem is different. splashy works good to some extent with LUKS. The problem is that it doesn't give the user a prompt to decrypt the device (on which the root-filesystem is installed). So because of this problem, I've disabled splashy in initramfs through /etc/default/splashy. # Set to "1" to allow Splashy to be put inside initramfs # Remember to run "update-initramfs" and read the README file carefully # default "1" ENABLE_INITRAMFS=0 This allows me to have splashy NOT start from initramfs and thus I get a proper password prompt to decrypt my root device. When not using splashy from initramfs, as a user, my expectation is that it should start as soon as real root is available and init is started. But in the boot process I see it starting too late. That is the bug I suspect, for which this bug report is filed. I'm using dependency boot init. If I look into /etc/rc2.d/, I don't see any listing of splashy there. In a non-initramfs scenario, shouldn't splashy be starting as soon as root dev is available? Same is the case during shutdown. splashy starts almost halfway. Ritesh -- Ritesh Raj Sarraf RESEARCHUT - http://www.researchut.com "Necessity is the mother of invention."
signature.asc
Description: This is a digitally signed message part.
