Re: [Etherboot-developers] Etherboot.zdsk suggestions...

[<ke...@et...>]

>Ok, if needed I can do it.... but the simplest and fastest way is
>building the etherboot.zdsk image, make the floppy, and try it on a PC
>without network card (so it will probe everything....): the main target
>is having no driver probing infinite times the same network card (so no
>ESC will be required...); the second target is having coherent and
>limited output from each driver probing...

Please take a few moments to document the behaviour and post to this
list.

>Is it influenced by the order of the object files passed to the
>compiler?

By the order the object files are specified to the linker.

>No problem... the big problem was WHERE to put my hand to prevent this
>file to be included in etherboot.zdsk; at the end I changed genrules.pl,
>but I'm not really sure it is the right place...

It's already commented out in the 5.2.1 I believe.

>I think we should provide a simple way to build custom "50 driver in a
>single image" image: ie, providing a file with the driver list somone
>want to include...
>This file could be auto generated during the build process, and the user
>can comment/uncomment the drivers he want to include in the final
>image...

If you would like to look at this and send in some software that would
be good. However a multidriver image is only a medium priority item
because it would be useful only as a probe floppy, it would be slow as a
production floppy.