Hi Bruce,
Bruce:
read -t "${itime}" -n 1 interactive 2>&1 > /dev/null
$interactive is not set until the read command completes.
It shouldn't need to be set in the script.
Alex:
This is kind of a chicken and egg situation.
If for some reason (say, unknown to us mortals as yet) the 'read'
does NOT read the keyboard, then the "interactive" remains unset,
as I noticed in real life. Thus, my artificially "forcing" a value
to "interactive" on the third line.
The "reason" is then reinforced by the later unresponsiveness
that can be witnessed at the "(Yes/no/continue)" point.
My guess was that at the "S" level (as confirmed by the display line,
runlevel: S
)
the USB keyboard (and mouse) had not been recognized by my system.
This is why I'm not sure that, based on the latest LFS boot
configuration maybe some sort of Udev (or other phenomenon) can actually
detect the USB input devices for people more up-to-date on it.
Cheers,
-- Alex
--
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page
