On Sat, 23 Dec 2000, George Metz wrote:
> Random question here, which I figure maybe David, Charles, or one or two
> others might have thought of. Does anyone know if, in practice, there's a
> problem with using the same modules for different architectures?
>
> More specifically, is there going to be a module conflict if I use the
> same modules for the i486 kernel and the i486-NoFPU kernels? What about
> 486 and Pentium, or Pentium and 5x86? Thoughts on this? The majority of
> the compile time is taken up with recompiling the modules, so if there's
> no need to do so...
On a non-LRP system, there's a subsystem that checks versions:
CONFIG_MODVERSIONS:
Usually, modules have to be recompiled whenever you switch to a new
kernel. Saying Y here makes it possible, and safe, to use the
same modules even after compiling a new kernel; this requires the
program modprobe. All the software needed for module support is in
the modutils package (check the file Documentation/Changes for
location and latest version). NOTE: if you say Y here but don't
have the program genksyms (which is also contained in the above
mentioned modutils package), then the building of your kernel will
fail. If you are going to use modules that are generated from
non-kernel sources, you would benefit from this option. Otherwise
it's not that important. So, N ought to be a safe bet.
my EigerStein has no modprobe.
>
> As I recall, most 486 kernel tarballs include a standard kernel and a
> NoFPU kernel, so I'm assuming that this won't cause module conflicts. What
> about the rest though? Thoughts? Docs?
>
> On a related subject, I now have the kernel tarballs and 2.2.18 1680k
> image up on sourceforge, along with a small bit of HTML to make it nicer
> and not hide the full tarball name. I still can't scp to shell1, but I'm
> able to scp while logged into shell1, so that's good enough.
>
Is it just sitting there after you enter your password?
> --
> George Metz
> Commercial Routing Engineer
> [EMAIL PROTECTED]
>
>
>
> _______________________________________________
> Leaf-devel mailing list
> [EMAIL PROTECTED]
> http://lists.sourceforge.net/mailman/listinfo/leaf-devel
>
_______________________________________________
Leaf-devel mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/mailman/listinfo/leaf-devel
