Eyal Lebedinsky wrote:
> Problem is that one gets tons of errors due to the use of the wrong
> kernel.
> The exact way for doing it right is actually:
> depmod -ae $(KERNELRELEASE) -F $(LS)/System.map
Yep, but one must define KERNELRELEASE for 2.0 kernels. As I said, I will
fix this for next release.
> > Loop-AES build instructions _require_ you to disable the loop driver in the
> > kernel. If you have two loop.o drivers, you skipped some build instructions.
>
> It is not in the kernel, it is in my /lib/modules as it was built
> originally.
> I want to keep it there while I play with the new module, and not lose
> the
> original. Naturally, just my preference, not everybodies.
I meant that loop must be completely disabled, as it says in the README:
CONFIG_BLK_DEV_LOOP=n
Regards,
Jari Ruusu <jari.ruusu@pp.inet.fi>
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Fri Sep 07 2001 - 21:00:27 EST