On Thu, May 31, 2012 at 08:32:42PM +0200, Martin Husemann wrote:
> On Thu, May 31, 2012 at 06:30:38PM +0100, David Laight wrote:
> > But you don't want /boot to try to load the module if the ffs code is
> > present in the kernel. Since /boot has no way of knowing what is in the
> > loaded kernel it is inappropriate for it to try to load the module file
> > and for the kernel to then try to load the module.
>
> I thought I agree with you - but now you confused me. If I create (with
> care) a kernel w/o internal ffs, I can easily edit /boot.cfg. Hard
> coding it in boot seems wrong. Isn't that what you said as well?
I think I misunderstood you...
David
--
David Laight: da...@l8s.co.uk
