[syslinux] config_cwd can be killed?

Ady Ady ady-sf at hotmail.com
Mon Mar 6 00:02:29 PST 2017


> > > What about if the CONFIG (LDLINUX)  and MENU.c32 (and gfxboot.c32?)
> > > modules looked for arguments like "cwd=path/to/dir" (cwd relative and
> > > possibly including .. to drop parent directories?) or
> > > "cwd=/abs/path/to/dir" to change directories at that point in the
> > > parsing of the config files.  (Similar to the way initrd=filename is
> > > special for KERNEL types)  Then we wouldn't need this config_cwd
> > > private buffer and we could delete it and save some bytes of memory
> > > and simplify code.
> 
> Yes please, kill config_cwd
> 
> 
> Groeten
> Geert Stappers
 
 
@Phil,

I'd like to request a "translation" for common (non-developers) users. 
What would this "killing" mean in terms of users' usage of the CONFIG 
directive?

For example, would it mean that the second argument of the CONFIG 
directive be ignored (i.e. not usable anymore)?

Thank you,
Ady.



More information about the Syslinux mailing list