Working on fixing lower-priority bugs that I didn't want to risk
destabilizing the 2.07 release for:
Changes in 2.08:
* Add "timeoutcmd" to allow timeout to have a different
action
than just pressing Enter.
* Fix bugs in the COMBOOT/COM32 command-line parsing. APPEND
now works with COMBOOT/COM32 images.
ftp://ftp.kernel.org/pub/linux/utils/boot/syslinux/Testing/
-hpa
I tried 2.08-pre1 and timeout command does not seem to be working. This
is exactly what I see.
1. At the prompt I just hit Enter and the default kernel boots fine.
2. At the prompt I type in "defimg" and it boots fine (including the
append option for COM32 images).
3. The appropriate part of my isolinux.cfg is
timeout readker.c32 prep
label defimg
kernel readker.c32
append prep
After the timeout, the machine seems to hang and pressing Alt-Ctrl-Del
has not effect. Only solution is to hit the reset button on the machine.
Is the timeoutcmd supposed to handle COM32 images as well?
- Murali
H. Peter Anvin wrote:> Working on fixing lower-priority bugs that I didn't want to risk
> destabilizing the 2.07 release for:
>
> Changes in 2.08:
> * Add "timeoutcmd" to allow timeout to have a different
action
> than just pressing Enter.
> * Fix bugs in the COMBOOT/COM32 command-line parsing. APPEND
> now works with COMBOOT/COM32 images.
>
> ftp://ftp.kernel.org/pub/linux/utils/boot/syslinux/Testing/
>
> -hpa
>
> _______________________________________________
> 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.
>
>
ganapathy murali krishnan wrote:> > I tried 2.08-pre1 and timeout command does not seem to be working. This > is exactly what I see. > > 1. At the prompt I just hit Enter and the default kernel boots fine. > 2. At the prompt I type in "defimg" and it boots fine (including the > append option for COM32 images). > 3. The appropriate part of my isolinux.cfg is > > timeout readker.c32 prep^^^^^^^ error...> > label defimg > kernel readker.c32 > append prep > > After the timeout, the machine seems to hang and pressing Alt-Ctrl-Del > has not effect. Only solution is to hit the reset button on the machine. > > Is the timeoutcmd supposed to handle COM32 images as well? >Yes, but the command is "timeoutcmd" -- "timeout" is a different command which sets the timeout interval. -hpa
I wrote (what I think is) a useful piece of comboot code, to autoboot into various images. Here is a small explanation of what it does -------------- INTRO TO AUTOBOOTING ----------- The comboot code, reads a "stack" of labels pops one off the "stack", and uses the comboot API to boot into the specified label. In case the "stack" is empty or the stack has not been setup, it boots into the label specified by its command line argument. Another utility, creates such a "stack" by writing the "stack" to an unused portion of the hard disk. A typical use is as follows ---- contents of file "bootorder" ----- # Comment line # First install windows winstall # Windows needs a few reboots off the local hard disk to # finish the installation. local local local local # Now we can start with the debian installation linstall firewall=yes image=debian local ----- end of file "bootorder" ----- $ writeker /dev/hda < bootorder after writeker has been called, every succesive boot using the comboot code will result in the execution of the images in the specified order. The writeker utility is a binary which executes under linux, the corresponding readker.c32 is the comboot code. ----------------------- END OF INTRODUCTION ----------------- Would people like to see code like this packaged with syslinux? Hopefully more people will start to use COMBOOT to do some non-trivial things. - Murali
I would love to see more comboot examples, some sort of menu system woule be especially helpful. Where is the code that you mention below. -Aaron On Mon, 24 Nov 2003, ganapathy murali krishnan wrote:> I wrote (what I think is) a useful piece of comboot code, to autoboot > into various images. Here is a small explanation of what it does > > -------------- INTRO TO AUTOBOOTING ----------- > > The comboot code, reads a "stack" of labels pops one off the "stack", > and uses the comboot API to boot into the specified label. In case the > "stack" is empty or the stack has not been setup, it boots into the > label specified by its command line argument. > > Another utility, creates such a "stack" by writing the "stack" to an > unused portion of the hard disk. > > A typical use is as follows > > ---- contents of file "bootorder" ----- > # Comment line > # First install windows > winstall > # Windows needs a few reboots off the local hard disk to > # finish the installation. > local > local > local > local > # Now we can start with the debian installation > linstall firewall=yes image=debian > local > ----- end of file "bootorder" ----- > > $ writeker /dev/hda < bootorder > > after writeker has been called, every succesive boot using the comboot > code will result in the execution of the images in the specified order. > > The writeker utility is a binary which executes under linux, the > corresponding readker.c32 is the comboot code. > > ----------------------- END OF INTRODUCTION ----------------- > > Would people like to see code like this packaged with syslinux? > Hopefully more people will start to use COMBOOT to do some non-trivial > things. > > - Murali > > _______________________________________________ > 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. > >
The autobooting code can be downloaded from http://people.cs.uchicago.edu/~gmurali/gui/autoboot.html. Look for the download links at the bottom of the page. - Murali Aaron McSorley wrote:> I would love to see more comboot examples, some sort of menu system > woule be especially helpful. Where is the code that you mention below. > > -Aaron >