On Tue, Jun 10, 2008 at 10:55 AM, Ritesh Raj Sarraf <[EMAIL PROTECTED]> wrote:
> Hi Luis and others.. > > Thank you for the wonderful and informative wiki that you guys have > maintained > for splashy. > > On Monday 09 Jun 2008 20:09:52 Ritesh Raj Sarraf wrote: > > 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. > > > > So I also tried your suggestion and moved splashy from init-top to > local-bottom. While that serves the purpose (I get the password prompt > properly), splashy for some reason keeps dying. Is the splashy log logged > somewhere. > > > 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 > > For the delayed startup/shutdown problem, it is an interesting case. > splashy has: > ### BEGIN INIT INFO > # Provides: splashy > # Required-Start: mountkernfs > # Required-Stop: $all > # Default-Start: S > # Default-Stop: 0 6 > # Short-Description: A script to calculate the progress percentage for init > scripts > # Description: This calculates the progress percentage > # for the scripts in /etc/rcS.d and > # /etc/rc$CURRENT_RUNLEVEL.d. > ### END INIT INFO > > But still it gets listed under /etc/rcS.d/ at S22splashy. That is too late. > > If I change that to S02splashy, I get exactly what I expect. I don't know > why > it is getting S22 given that it already has "Required-Start: mountkernfs". > I also tried using "X-Start-Before" but that too didn't help. > > So I think maybe the problem is with insserv. I'd suggest that you dpkg -P splashy and reinstall. This is what the postinst script does: update-rc.d splashy start 03 S . stop 01 6 0 . >/dev/null So, Splashy should be /etc/rcS.d/S03splashy. This script does nothing if Splashy is running from initramfs. -- ----)(----- Luis Mondesi Maestro Debiano ----- START ENCRYPTED BLOCK (Triple-ROT13) ------ Gur Hohagh [Yvahk] qvfgevohgvba oevatf gur fcvevg bs Hohagh gb gur fbsgjner jbeyq. ----- END ENCRYPTED BLOCK (Triple-ROT13) ------
