[syslinux] [PATCH] ifmemdsk.c32: Allow boot options based on presence of MEMDISK

Shao Miller Shao.Miller at yrdsb.edu.on.ca
Mon Aug 8 10:33:17 PDT 2011


On 8/8/2011 13:15, Bernd Blaauw wrote:
> Op 8-8-2011 15:32, Miller, Shao schreef:
>> http://git.zytor.com/?p=users/sha0/syslinux.git;a=shortlog;h=refs/heads/
>> ifmemdsk
>>
>> Review welcome!
>
> How's the 'particular MEMDISK is sought by the options' part working?

Good day, Bernd.  Sorry I haven't gotten to your other e-mails, yet.  
Detection of a particular MEMDISK seems like a nice feature to discuss. :)

> without --mbfts  the module doesn't do/show anything anyway.

I don't follow.  For the 'memdisk iso' scenario, INT 0x13, AH==0x08 
MEMDISK probe isn't going to work, as only the AH==0x4X functions 
work...  So I would agree that one or both of '--mbfts' and 
'--safe-hooks' must be used in order to detect the MEMDISK.  Nothing 
will "show" without '--info'.

> I was initially under the impression decisions could be taken if some 
> keyword was found on memdisk's append line (for example 'iso')

So how about a '--find' option?:

   --find [<item>]

As in:

LABEL loadiso
   KERNEL memdisk
   INITRD some.iso
   APPEND test1 test2=foo raw

...Later that same day, in the chained-to ISOLINUX' config-file...

LABEL test1
   COM32 ifmemdsk.c32
   APPEND --mbfts --find test1 echo.c32 Found test1 -- echo.c32 No test1
LABEL test2
   COM32 ifmemdsk.c32
   APPEND --mbfts --find test2=foo echo.c32 Found test2=foo -- echo.c32 
No test2=foo

Does that seem sensible?  I'll probably wait for some hpa-approval of 
the current, basic incarnation before attempting a '--find' feature.

- Shao Miller




More information about the Syslinux mailing list