On Fri, 17 Sep 1999, Dirk Koopman wrote:
> On 17-Sep-99 Richard Adams wrote:
> > It will copy vmlinuz to /vmlinuz period, unless
> > /usr/src/linux/Makefile is edited around line 69 and the hash
> > removed, then /boot will be the default install path.
>
> What it actually does is copy (b)zImage (say version 2.2.12) to
>
> /boot/vmlinuz-2.2.12
Well its been a log time since i tryed any of that, so i'll have to
eat my words and appolagise.
> then
>
> cp /boot/vmlinuz /boot/vmlinuz.old
> rm /boot/vmlinuz
> ln -s /boot/vmlinuz-2.2.12 /boot/vmlinuz
>
> It does not remove any /boot/vmlinuz-* files, therefore you can alter your
> lilo.conf to look something like this:-
Agreed, my lio.conf has 25 entires.
>
>
> You don't lose anything of what has gone before unless you get rid of it, it
> sets your System.map up correctly (which most people forget to do). Here is
> an ls -l of my /boot directory:-
>
[snip]
>
> What could be more flexible than that? Why would you (unless you are a kernel
> developer) want to do anything else?
I try anything once, this to my suprise has been added behind my back
so to speak, foor the last 2 years i have had qrl again after 8 years
of doing nothing else than following linux development.
As a matter of fact i have been lying in bed now for 6 weeks due to
back problems, all explaned at http://212.92.66.77 or
http://pa3gcu.ampr.org the ampr.or route should be working again
tommorrow, a friend is comming to repair my set, it only works when
it feels like it. The web-page has a web cam online so you can see
what i am doing in bed ;-)
> >
> > After reading ./arch/i386/boot/Makefile i would certanly not use make
> > install on my system, i define a EXTRAVERSION in the Top dir Makefile
> > and it seems that make install and install.sh in the same directory
> > dont use the extraversion number, simply .old, now that would render
> > my system useable with 2 kernels only as modules would be the
> > biggest problem. Or am i missing something which is before my eys
> > here so close i cant see it.??.
Well i sure did miss something which is right before my eys, lets put
it down to "keep taking the pils".
However on another note, the symlinks which are created with make
install are not changed at boottime when another kernel is choosen.
Looking at /etc/rc.d/rc.sysinit they should be removed and relinked
to the to be booted kernel, however it does not happen like it should.
I have taken the relavant part of te script and called it something
else, now when it is run funny things happen.
It all works up untill the following lines,
[ -n "$mver" -a -f "/boot/module-info-$mver" ] && ln -sf /boot/module-info-$
mver /boot/module-info
[ -n "$mver" -a -f "/boot/System.map-$mver" ] && ln -sf /boot/System.map-$mv
er /boot/System.map
action "Finding module dependencies" depmod -a
fi
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.??
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.
Dirk, maybe you have an explanation on that for me, and possably
others who might even have noticed the same problem.
Just in case i have not mentioned it, i have Redhat 6.0
On the otherhand the cause and answer could be contained in your
signature.
Thanks for a speedy and polite reply.
>
> Dirk G1TLH (perplexed of Dereham)
> ---
> 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.
--
Regards Richard
[EMAIL PROTECTED]
