On 17-Sep-99 Richard Adams wrote:
> I'm quite syure you will see where the lines are not correctly
> wrapped, however -n mver -a -f "/boot/module-info-$mver" returns
> the whole output of cat version, so how could it possably link the
> things together, or have i taken one pill to many this time.??
are you sure you don't mean pils? (in which case I would recommend that you
increase the dosage significantly).
>
> In all cases i never get symlinks made at boottime, and like i siad
> the ones crated with make install are not even deleted.
>
> One thing is certain, it all seems to boot ok and i never seem to
> get any unresolved symbols from different modules versions.
If I understand what you mean correctly, Redhat does some script magic at
boot time which causes it to determine which kernel image you are running and
then symlinking /lib/modules/current to the correct set of modules. Kerneld
and its friends use that for preference, before looking in any of the other
"usual" places.
It doesn't re-symlink any of the kernel images (I believe) because they work
on the basis that if you select anything other than the default, then you
probably will want to run _that_ kernel and its modules, it also then allows
the bit of magic with the modules.
>
> Dirk, maybe you have an explanation on that for me, and possably
> others who might even have noticed the same problem.
>
Hope this helps, as I said earlier, for me - it just works.
groetjes..
Dirk G1TLH
--
Dirk-Jan Koopman, Tobit Computer Co Ltd
At the source of every error which is blamed on the computer you will find
at least two human errors, including the error of blaming it on the computer.
