It seems that quite a bit of stuff built up very quickly after the 2.07
release:
Changes from 2.07 to 2.08-pre6:
* Add new configuration command "ontimeout" to allow timeout
to have a different action than just pressing Enter.
* Add new configuration command "onerror" to allow a custom
command to be executed in case the kernel image is not found.
* Fix bugs in the COMBOOT/COM32 command-line parsing. APPEND
now works with COMBOOT/COM32 images.
* PXELINUX: Poll for ARP requests while sitting at the
prompt. This makes some boot servers a lot less unhappy.
* PXELINUX: Actually free sockets when we get a failure
(including file not found.) This bug would cause us to run
out of sockets and thus "go deaf" after a while.
* MEMDISK: Add an API to query for the existence of MEMDISK.
* SYSLINUX: Fix loading boot sectors (.bs/.bss) from floppy
disk.
* .c32 is now one of the extensions searched for
automatically.
I have gotten one feature request to have PXELINUX support some kind of
server+path syntax (i.e. something like 192.0.2.69:/path/file); I'm not
sure if it's better to move -pre6 to release candidate status and hold
off on that one (it's a reasonably major change of the internals) or if
I should implement it and expect a few more prereleases before final 2.08.
Also, anything else for 2.08 (unfixed bugs or wanted features) please
speak up now...
-hpa
Hi, "H. Peter Anvin" <hpa at zytor.com> schrieb am 01.12.03 08:34:14:> Also, anything else for 2.08 (unfixed bugs or wanted features) please > speak up now...I've asked some while ago for some method to not allow additional parameters on the syslinux command line. Especially in pxelinux this would be useful in connection with the 'implicit' command, to only allow the labels & parameters defined in the pxelinux config file. So if someone enters 'linux init=/bin/sh' the 'linux' label and its parameters would be used, and the 'init=/bin/sh' isn't appended to the command line. 'implicit 2' would be some parameter to implement this. Maybe this is useful for syslinux & isolinux also, but there's not much possibility to change the config file on a read-only cd-rom ... Regards, Josef ______________________________________________________________________________ Horoskop, Comics, VIPs, Wetter, Sport und Lotto im WEB.DE Screensaver1.2 Kostenlos downloaden: http://screensaver.web.de/?mc=021110
"H. Peter Anvin" <hpa at zytor.com> schrieb am 01.12.03 08:34:14:>> Also, anything else for 2.08 (unfixed bugs or wanted features) please >> speak up now... > >I have a project in the background with a computer using a Matrix Orbital LCD/Keypad interface. Since the keypad does not generate normal function key input one would need a KBDMAP that applies to serial input to map the characters to function keys. I've looked at the code for SYSLINUX to make this change (and discussed where/how to best implement it with HPA) but the issue has not risen to the top of my To Do list yet. That's my only wanted feature (and one that I will eventually get around to implementing if some generous soul does not do it before me). g.
Another possibly useful feature for memdisk (though not for ver 2.08): Accept one more argument, say initrd2 or something like that and "mount" that image under B: or X: or whatever. This will allow us to cross the size limit of 2.88MB floppies. Ofcourse when I say "mount" I dont expect memdisk to mount it, just that set things up so that DOS mounts it there. Of course, one may say that if we need more than 2.88MB worth of info, then one should give a hard disk image to memdisk. But, if I am right (I might be wrong here) in such a case, the image will become C:\ (in DOS) and the regular hard disk will become D:. Then if one tries to install Windows, then the windows drive will be called D: in the final installation. This may lead to certain undesirable things. For eg, there are still windows software (new ones at that) out there which always install to "C:\Program Files" without even checking if windows has been installed in C: or D:. Right now my usage is only 87% of the 2.88MB floppy, so I hope I am not forced into the hard disk image route in the near future. BTW, if I give memdisk a hard disk image, can one make sure that DOS recognizes it not as C: but some thing later, i.e. make DOS assign drive letters to the regular hard disks first and then assign one to the memdisk image? If I remember correctly, some topic like this did come up some time ago. - Murali H. Peter Anvin wrote:> It seems that quite a bit of stuff built up very quickly after the 2.07 > release: > > Changes from 2.07 to 2.08-pre6: > * Add new configuration command "ontimeout" to allow timeout > to have a different action than just pressing Enter. > * Add new configuration command "onerror" to allow a custom > command to be executed in case the kernel image is not found. > * Fix bugs in the COMBOOT/COM32 command-line parsing. APPEND > now works with COMBOOT/COM32 images. > * PXELINUX: Poll for ARP requests while sitting at the > prompt. This makes some boot servers a lot less unhappy. > * PXELINUX: Actually free sockets when we get a failure > (including file not found.) This bug would cause us to run > out of sockets and thus "go deaf" after a while. > * MEMDISK: Add an API to query for the existence of MEMDISK. > * SYSLINUX: Fix loading boot sectors (.bs/.bss) from floppy > disk. > * .c32 is now one of the extensions searched for > automatically. > > I have gotten one feature request to have PXELINUX support some kind of > server+path syntax (i.e. something like 192.0.2.69:/path/file); I'm not > sure if it's better to move -pre6 to release candidate status and hold > off on that one (it's a reasonably major change of the internals) or if > I should implement it and expect a few more prereleases before final 2.08. > > Also, anything else for 2.08 (unfixed bugs or wanted features) please > speak up now... > > -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:> > Right now my usage is only 87% of the 2.88MB floppy, so I hope I am not > forced into the hard disk image route in the near future. >You can create floppy images much larger than 2.88MB -- you just have to specify the geometry explictly.> BTW, if I give memdisk a hard disk image, can one make sure that DOS > recognizes it not as C: but some thing later, i.e. make DOS assign drive > letters to the regular hard disks first and then assign one to the > memdisk image?That might not be too hard to do. There are a few caveats, however: a) MEMDISK must be a BIOS drive, so if there are non-BIOS drives in the system (device drivers, in other words), they will always come after the MEMDISK. b) MEMDISK must be adjacent to all the real drives, i.e. if the BIOS has real drives C: (80h) and D: (81h) MEMDISK could be C:, D: or E:, but not, for example, F: or Q:. -hpa
I dont know if adding that feature (making memdisk force BIOS to choose the last possible drive letter), would help in any situation except the situation I described. Right now, having a 10MB floppy image is more than enough for me. BTW, Thanks to the new MEMDISK interrupt, I have one DOS image which does a whole lot of things depending on the arguments it gets. I have implemented an an rc.d style autoexec.bat and that makes things really useful. The key is a program which parses the boot time arguments and sets appropriate environment variables (a simple modification of the sample program which comes with syslinux). This is also available for download (http://people.cs.uchicago.edu/~gmurali/gui), in case anyone is interested. This feature has reduced the number of DOS images in my CD and hence maintaining them is a lot easier. - Murali H. Peter Anvin wrote:>>BTW, if I give memdisk a hard disk image, can one make sure that DOS >>recognizes it not as C: but some thing later, i.e. make DOS assign drive >>letters to the regular hard disks first and then assign one to the >>memdisk image? >> >> > >That might not be too hard to do. There are a few caveats, however: > >a) MEMDISK must be a BIOS drive, so if there are non-BIOS drives in the >system (device drivers, in other words), they will always come after the >MEMDISK. > >b) MEMDISK must be adjacent to all the real drives, i.e. if the BIOS has >real drives C: (80h) and D: (81h) MEMDISK could be C:, D: or E:, but >not, for example, F: or Q:. > >
Hi, that's a really impressive page for your multiboot-cd/dvd. the dos program for scanning memdisk parameters may force me to learn how to compile :) do you know about PEbuilder? * http://www.nu2.nu/pebuilder/ * http://www.911cd.net/forums/index.php? I'm appreciating Isolinux and MKISOFS more and more. DVD is already at 2.5GB .. (Knoppix, WinPE, Win2000, ReactOS, FreeDOS, and applications+drivers) and now I'll not post too much garbage on the list. after all, it's a developer's list Bernd Blaauw
It is possible to network boot an ISO9660 image?
"Blaauw,Bernd B."
<B.Blaauw at student To: <syslinux at
zytor.com>
.fontys.nl> cc:
Sent by: Subject: RE: [syslinux] Planning
a 2.08 release
syslinux-bounces@
zytor.com
12/04/2003 12:37
PM
Hi,
that's a really impressive page for your multiboot-cd/dvd.
the dos program for scanning memdisk parameters may force me to learn how
to compile :)
do you know about PEbuilder?
* http://www.nu2.nu/pebuilder/
* http://www.911cd.net/forums/index.php?
I'm appreciating Isolinux and MKISOFS more and more.
DVD is already at 2.5GB ..
(Knoppix, WinPE, Win2000, ReactOS, FreeDOS, and applications+drivers)
and now I'll not post too much garbage on the list. after all, it's a
developer's list
Bernd Blaauw
_______________________________________________
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.
Murali Krishnan Ganapathy wrote:> > I dont know if adding that feature (making memdisk force BIOS to choose > the last possible drive letter), would help in any situation except the > situation I described. Right now, having a 10MB floppy image is more > than enough for me. >As I said... unfortunately at least DOS can only boot from either the first fd or the first hd.> BTW, Thanks to the new MEMDISK interrupt, I have one DOS image which > does a whole lot of things depending on the arguments it gets. I have > implemented an an rc.d style autoexec.bat and that makes things really > useful. The key is a program which parses the boot time arguments and > sets appropriate environment variables (a simple modification of the > sample program which comes with syslinux). This is also available for > download (http://people.cs.uchicago.edu/~gmurali/gui), in case anyone is > interested. > > This feature has reduced the number of DOS images in my CD and hence > maintaining them is a lot easier.:) -hpa