>>>>> "michael" == michael <[EMAIL PROTECTED]> writes:
michael> On Friday 11 May 2001 11:39 am, Blue Lizard uttered:
>> Denis Artru wrote:
>> > On Fri, 11 May 2001, michael wrote:
>> >> I am using 2.4.3-20mdk and want to upgrade to 2.4.3-27mdk.
>> >> I am afraid because of all I have read about "can't boot into mdk after
>> >> kernel upgrade... no initrd made " etc.
>> >> What do I need to do to successfully upgrade my kernel using rpm?
>> >
>> > Go to directory /boot
>> > make the link vmlinuz and System.map to your new kernel.
>> > #ln -fs vmlinuz-2.4.3-27mdk vmlinuz
>> > #ln -fs System.map-2.4.3-27mdk System.map
>> >
>> > And to finish use lilo
>> > #lilo
michael> I am upgrading initscripts from cooker 5.83-6
michael> source, headers,doc and 2.4.3-27 all in same directory
michael> rpm -ivh *.rpm ...doesn't work spews dependencies everywhere
michael> rpm -Uvh *.rpm ....well, it seems to be working all packages installed
michael> of and red colored letters in config and System.map
michael> A config-2.4.3-27mdk is there as well as a System.map 2.4.3-27.The vmlinuz
michael> 2.4.3-27 is there too.
Hi
That links are created by kheader and are supposed to point to
the running kernel. I.e. if you boot in a different kernel,
you should get the right links again.
On the other hand, I think that we should have a _strong_
dependency in the running kernel (aka not able to -i it, only
upgrades). That will make life much more easy for everybody
users and developers (/me thinking on changing that :)
Later, Juan.
--
In theory, practice and theory are the same, but in practice they
are different -- Larry McVoy
