isolinux at pouhovitch.com
2004-Jun-29 23:52 UTC
[syslinux] timeout timer gets reset after bad kernel image
Since this is my first post on the mailing list I got to get all the praising out of the way. I have played around with isolinux for a couple of days now, and it is really great. Thank you Peter. Now regarding the timeout. The timeout gets interrupted when one presses any key on the keyboard, however if I enter an invalid kernel image to boot the timeout is restarted after isolinux fails to locate the kernel. I am not sure if this is a bug or it was planned to behave that way. At any rate, I find this behavior a little bit unexpected. Norris
ganapathy murali krishnan
2004-Jun-30 17:56 UTC
[syslinux] timeout timer gets reset after bad kernel image
You should interpret timeout as the amount of time isolinux will wait at the boot prompt for you to press the first key without doing anything. If you press a key within the timeout interval (just one key) then come back after an hour (without completely typing the name of a kernel image and hitting return), you will still see isolinux waiting for your keystroke. So, every time isolinux gets back to the prompt, it starts the clock ticking then. I am sure this is intentional. Even though it is possible to get what ever behavious your want, it is not worth the effort to implement that, considering that isolinux's basic functionality is to provide you with an interface by which you select the kernel image to boot into. Anything more than that is just for the look and feel. - Murali isolinux at pouhovitch.com wrote:>Since this is my first post on the mailing list I got to get all the praising out of the way. I have played around with isolinux for a couple of days now, and it is really great. Thank you Peter. > >Now regarding the timeout. > >The timeout gets interrupted when one presses any key on the keyboard, however if I enter an invalid kernel image to boot the timeout is restarted after isolinux fails to locate the kernel. I am not sure if this is a bug or it was planned to behave that way. At any rate, I find this behavior a little bit unexpected. > >Norris > >_______________________________________________ >SYSLINUX mailing list >Submissions to SYSLINUX at zytor.com >Unsubscribe or set options at: >http://www.zytor.com/mailman/listinfo/syslinux >Please do not send private replies to mailing list traffic. > > > >