search for: additional_files

Gene, I'm lurking on this issue. Just in general it's fascinating because I basically use syslinux in a monkey-see-monkey do manner. Can you explain why you used the menu entries that way? What they actually do? You mentioned logging... How is the enabled/configured? Inquiring minds want to know and links to docs will do :) On 10/03/2017 03:30 AM, Gene Cumm via Syslinux wrote: >

On Wed, Oct 4, 2017 at 11:10 AM, Ady Ady via Syslinux <syslinux at zytor.com> wrote: > FWIW, the _need_ to use linux.c32 is becoming more common (in the sense > that other loading methods are not always capable of loading > newer/current kernels+initrams+additional_files, considering their > sizes). Unfortunately, only a minority of users seem to be aware of > Syslinux's syntax and modules, while the Syslinux-related packages are, > generally speaking and IMO, not reaching the level of > maintenance/support that common users seem to expect. It shou...

...n", or "menu", or "COM32", or "KERNEL-LIKE DIRECTIVES", or something. I sincerely hope it helps. FWIW, the _need_ to use linux.c32 is becoming more common (in the sense that other loading methods are not always capable of loading newer/current kernels+initrams+additional_files, considering their sizes). Unfortunately, only a minority of users seem to be aware of Syslinux's syntax and modules, while the Syslinux-related packages are, generally speaking and IMO, not reaching the level of maintenance/support that common users seem to expect. Regards, Ady.