Re: m68k boot-floppies
> > That sounds scary. What would be the reason for this?
>
> i guess the i386 folk thought loop would always be installed modular.
Right, they are a bit tight with LILO constraints and the like.
> should be possible to test if the kernel as loop support or not (try mounting
> something on the loop device, and testing the error messages, or something
> such).
If it's all about a biased assumption 'everybody has loop as module',
rather test if loop is builting (grep loop /proc/devices) and skip loading
the module.
> > Nope, depmod probably requires read access to the kernel symbol table
> > which is installed with the kernel.
>
> What do you need depmod for ? you could brutally insmod the needed module, and
> depmod stuff later.
And blow up if someone decided to use a different kernel? I think you can
do that already.
It's more about automatically loading 8390.o when somebody wants
ariadne.o. The whole boot floppies install procedure is for dummies (well,
almost) and the concept of module dependencies might escape them.
> Also, you could add the symbol table with the drivers tarball instead.
Sure enough. OTOH modules can be built that work for different builds of a
kernel (I never use symbol versioning for example). The symbol table of
the kernel is all that matters.
Michael
Reply to: