I've been working on bootscripts. Basically, I'm rewriting them to get a better understanding. I may end up throwing them out completely but I want to discuss the issue of error handling.
There are three bootscript files that use the read ENTER construct: checkfs, udev, and functions. In the case of functions, the construct is used in print_error_msg that is only called from the rc script. It is not a fatal function. In checkfs, the construct is called in three different places. In two places it is followed immediately by a halt and one place a reboot. In udev, the construct is called in two places. In both cases, it is followed by a halt. The question is how to handle these errors in a headless or keyboardless system. The problems identified are pretty serious and it's doubtful anything could be written to the disk. I'm thinking about moving the messages/halt/reboot to the functions script so they all can be handled in one place. If we then have the functions script do: [ -e /etc/sysconfig/init_params ] && . /etc/sysconfig/init_params then when we want to optionally stop for the user to read something: # Wait for the user by default [ "${HEADLESS=0}" = "0" ] && read ENTER To disable the need for a keyboard entry, the /etc/sysconfig/init_params file would define the following: HEADLESS=1 -------- The above would only apply to LFS bootscripts. I can't think of anything from BLFS or a third party that would need to stop the boot sequence to wait for the user to read a message. Should we integrate this into the LFS bootscripts? -- Bruce -- http://linuxfromscratch.org/mailman/listinfo/lfs-dev FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page