On Tue, Jun 10, 2008 at 10:55 AM, Ritesh Raj Sarraf <<a href="mailto:rrs@researchut.com">rrs@researchut.com</a>> wrote:<br><div class="gmail_quote"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Hi Luis and others..<br>
<br>
Thank you for the wonderful and informative wiki that you guys have maintained<br>
for splashy.<br>
<div class="Ih2E3d"><br>
On Monday 09 Jun 2008 20:09:52 Ritesh Raj Sarraf wrote:<br>
> On Monday 09 Jun 2008 06:05:45 you wrote:<br>
> > I take from this that you are using Splashy from initramfs but init-top<br>
> > is not "early" enough for your installation of LUKS?<br>
> ><br>
> > Why don't you move the Splashy script where it make sense for your system<br>
> > and redo your initramfs?<br>
> ><br>
> > Splashy (or any other applications) won't be "panacea". Meaning, there is<br>
> > no perfect solution for all systems world-wide. Different people have<br>
> > different needs.<br>
><br>
> I think the problem is different.<br>
><br>
> splashy works good to some extent with LUKS. The problem is that it doesn't<br>
> give the user a prompt to decrypt the device (on which the root-filesystem<br>
> is installed). So because of this problem, I've disabled splashy in<br>
> initramfs through /etc/default/splashy.<br>
><br>
> # Set to "1" to allow Splashy to be put inside initramfs<br>
> # Remember to run "update-initramfs" and read the README file carefully<br>
> # default "1"<br>
> ENABLE_INITRAMFS=0<br>
><br>
><br>
> This allows me to have splashy NOT start from initramfs and thus I get a<br>
> proper password prompt to decrypt my root device.<br>
><br>
<br>
</div>So I also tried your suggestion and moved splashy from init-top to<br>
local-bottom. While that serves the purpose (I get the password prompt<br>
properly), splashy for some reason keeps dying. Is the splashy log logged<br>
somewhere.<br>
<div class="Ih2E3d"><br>
> When not using splashy from initramfs, as a user, my expectation is that it<br>
> should start as soon as real root is available and init is started. But in<br>
> the boot process I see it starting too late. That is the bug I suspect, for<br>
> which this bug report is filed.<br>
><br>
> I'm using dependency boot init. If I look into /etc/rc2.d/, I don't see any<br>
> listing of splashy there.<br>
><br>
> In a non-initramfs scenario, shouldn't splashy be starting as soon as root<br>
> dev is available?<br>
><br>
> Same is the case during shutdown. splashy starts almost halfway.<br>
><br>
> Ritesh<br>
<br>
</div>For the delayed startup/shutdown problem, it is an interesting case.<br>
splashy has:<br>
### BEGIN INIT INFO<br>
# Provides: splashy<br>
# Required-Start: mountkernfs<br>
# Required-Stop: $all<br>
# Default-Start: S<br>
# Default-Stop: 0 6<br>
# Short-Description: A script to calculate the progress percentage for init<br>
scripts<br>
# Description: This calculates the progress percentage<br>
# for the scripts in /etc/rcS.d and<br>
# /etc/rc$CURRENT_RUNLEVEL.d.<br>
### END INIT INFO<br>
<br>
But still it gets listed under /etc/rcS.d/ at S22splashy. That is too late.<br>
<br>
If I change that to S02splashy, I get exactly what I expect. I don't know why<br>
it is getting S22 given that it already has "Required-Start: mountkernfs".<br>
I also tried using "X-Start-Before" but that too didn't help.<br>
<br>
So I think maybe the problem is with insserv.</blockquote><div><br>I'd suggest that you dpkg -P splashy and reinstall. This is what the postinst script does:<br><br>update-rc.d splashy start 03 S . stop 01 6 0 . >/dev/null<br>
<br>So, Splashy should be /etc/rcS.d/S03splashy. <br></div></div><br>This script does nothing if Splashy is running from initramfs.<br><br>-- <br>----)(----- <br>Luis Mondesi<br>Maestro Debiano<br><br>----- START ENCRYPTED BLOCK (Triple-ROT13) ------<br>
Gur Hohagh [Yvahk] qvfgevohgvba oevatf gur fcvevg bs Hohagh gb gur fbsgjner jbeyq.<br>----- END ENCRYPTED BLOCK (Triple-ROT13) ------