When there's an error at boot time that requires user input (ctrl-D or root password), silent fbsplash should automatically switch to verbose mode, or else it looks like it just froze on bootup.
What kind of errors are we talking here about? (specific examples and initscripts, please) This feature is generally already implemented in the splash scripts, but it requires some sort of cooperation from the initscripts -- ie. when an initscript wants to get some data from the user, it has to call a proper function.
I have a USB disk that I had accidentally set to automount on boot. When it wasn't plugged in, of course it failed to mount. At that point the system stopped booting and asked me to enter the root password for maintenance, or press ctrl-D to continue. Only, I wasn't in verbose mode, so I didn't actually see it ask me. It just looked like the system was frozen until I manually switched it to verbose. Is that the information you were looking for?
I take it it was the 'localmount' script that failed, right? If that was indeed the case, then something must be broken in the splash scripts. I'll have a look at it. And one more question: are you running the latest splashutils (1.1.9.10)?
Sorry, I had to rebuild my whole system last week because of a bad hard disk. I haven't had time to set up Gensplash since then. However, I can tell you that I was definitely running whatever was stable on x86 within two days of 1/15/06. I run a stable system and I update about every two days.
Also for me... for a long time... It used to work. Configuration: media-gfx/splashutils-1.1.9.10-r1 sys-apps/baselayout-1.12.0-r1 media-gfx/splash-themes-livecd-2006.0 sys-kernel/suspend2-sources-2.6.16-r7 /etc/conf.d/rc: RC_PARALLEL_STARTUP="yes" /etc/conf.d/splash: SPLASH_TTYS="1 2 3 4 5 6" SPLASH_VERBOSE_ON_ERRORS="yes" /sbin/splash-functions.sh does not get the error from baselayout?
Any news regarding this issue?
I'll set up gensplash again this weekend and see if anything has changed. Perhaps I hadn't set the SPLASH_VERBOSE_ON_ERRORS="yes" value properly.
My configuration is valid :) And it still does not work.
Alon: Which initscripts fail to start during boot in your case?
(In reply to comment #9) > Alon: Which initscripts fail to start during boot in your case? Hi! I am gladly can say it works now! Since my last comment all I did is upgrade to 2.6.17. I don't see how it is related... But I don't remember any baselayout or splashutils upgrade. So I don't really know what happened, but I am glad it works now :) Thanks!
OK, I'm assuming the issue is fixed now. If it isn't -- let me know, and I'll reopen the bug.
