According to Jeremy Wiebe: While burning my CPU.
>
> Hi Richard.
>
> What do you mean by my theory about 2.0 and 2.2? When I installed linux the
> rc.sysinit had the mtag line using 2.0.* I didn't put that in there so to
> get it to recognize 2.2 kernels I changed it to 2.* In my opinion this
> will work fine for years to come unless we hit the 3.x kernels soon. I
> don't mean to flame you here...I'm just pretty sure that the solution that I
> presented was clear and well founded.
>
> If it isn't could you point out where it isn't?
I pointed out that the asterisk a "*" sign, is the issue here, the asterisk
is used as a wild card, therefor recocnising "all" directorys, be it 2.0 2.1
3.x they will still be seen, if of course they are in /lib/modules, thats
why i said try my script, its part of Redhat-5.2's rc.sysint script,
obviously you did not take heed of what i said.
>
> Oh, one more thing. The .rhkmvtag is not a script but a text file that
> contains the ouput of `cat /proc/version`.
Then if thats the case there MUST be sommat else missing when one makes a
new kernel.
I will do my best and try to install Redhat this week, this sort of thing
gets my mojo going.
>
> ------------------------------------------------------
> Another message from Jer Wiebe
>
> Find me at...
> email: [EMAIL PROTECTED]
> ICQ: 4945359
> ---- snip ----
>
> >
> > No thats not nessacary, it does not matter what the version number is, you
> > can see the effects of any script by making your own small script like the
> > one that follows, you can then see what they do.
> >
> > #!/bin/sh
> >
> > ktag="`cat /proc/version`"
> > grep -l "$ktag" /lib/modules/*
> >
> > You will see that it will return "all" the subdirs from /lib/modules so
> your
> > theory about 2.0 or 2.2 is unfounded.
> >
> > The magic is done by the ".rhkmvtag" script and possably another one, the
> > one i mentioned in my last mail.
> >
> > >
> > > --------excerpt from rc.sysinit------------------
> > >
> > > # Set up kernel version-dependent symlinks.
> > > rm -f /lib/modules/preferred
> > > if [ -n $USEMODULES ]; then
> > > ktag="`cat /proc/version`"
> > > mtag=`grep -l "$ktag" /lib/modules/2.*/.rhkmvtag`
> > > ^^^^^
> > > If I remember correctly, on a 5.2 system the above line is:
> > > mtag=`grep -l "$ktag" /lib/modules/2.0.*/.rhkmvtag`
> >
> > Not according to a copy i have..
> >
> > mtag=`grep -l "$ktag" /lib/modules/*/.rhkmvtag` 2> /dev/null
> >
> > There is no need to have /2.0 as the asterisk (*) is a wildcard and will
> > show ALL dirs.
> >
> > I shall be reinstalling the most popular distro's again soon, so i will
> then
> > be able to check what i say before sending mail, at the moment i only have
> a
> > working Slackware here, so once again we will have to wait untill a more
> > experianced Redhat users comments about this.
> >
> >
> > >
> > > Hope that helps.
> > >
> > > ------------------------------------------------------
> > > Another message from Jer Wiebe
> > >
> > > Find me at...
> > > email: [EMAIL PROTECTED]
> > > ICQ: 4945359
> > >
> > > >
> > > > Redhat removes the symbolic link in /boot called preferred at
> boottime,
> > > take
> > > > a look at /etc/rc.d/rc.sysinit.
> > > > As far as i can tell the next few lines looks for the kernel version
> > > number
> > > > with 'cat /proc/version' the next part is magic, i rather think it
> looks
> > > for
> > > > an extention like 2.2.7-1 it uses a script called "rhkmvtag"
> > > > RedHatKernelMakeVersionTag so i think maybe the thing to do is rename
> the
> > > > image in /boot as follows.
> > > >
> > >
> > > P.S. My experience was that you don't need an extension on the kernel
> > > version. But I download kernels from ftp.kernel.org and don't bother
> with
> > > the rpm'ed kernels.
> > >
> >
> >
> > --
> > Regards Richard.
> > [EMAIL PROTECTED]
> >
>
--
Regards Richard.
[EMAIL PROTECTED]
