Subject: Re: YUP issues
From: Tony Yazbeck (tyazbeck@bigfoot.com)
Date: Mon Nov 06 2000 - 15:13:01 MST
The way I updated to the 2.2.17 kernel was simply by downloading the 2.2.17
kernel rpm as well as the new recompiled 'vmlinux' files from your ftp site.
I installed the kernel using rpm -I, and then when I restarted simply
selected the new vmlinux file from Bootx.
Is there something wrong with how I did this. The message I get simply tells
me that I already have the kernel, but when it does that, yup just stops
without updating the rest of the things that need updating.
Thanks for your help,
Tony
> From: Bryan Stillwell <bstill@terraplex.com>
> Reply-To: yellowdog-general@lists.yellowdoglinux.com
> Date: Mon, 6 Nov 2000 14:59:52 -0700
> To: yellowdog-general@lists.yellowdoglinux.com
> Subject: Re: YUP issues
>
> On Mon, Nov 06, 2000 at 01:27:07PM -0500, Tony Yazbeck wrote:
>> I successfully updated to kernel 2.2.17 and all works great. However, I
>> updated to 2.2.17 WITHOUT using yup update. The problem is that now, when I
>> choose to do yup update in order to bring up to date all other outdated
>> components that I may have, yup stops whenever it encounters the 2.2.17
>> kernel, saying that it already has it. Doesn't yup check against what you
>> already have to update around it?
>
> How did you update to the 2.2.17 kernel? If you used rpm from the
> command line /without/ using --nodeps or --force, yup should still be
> working...
>
> What is the error that yup displays when it reaches the kernel package?
>
> Bryan
>
> --
> Terra Soft Solutions, Inc. | Software Engineer
> http://www.terrasoftsolutions.com/ | bstill@terraplex.com
> GPG fingerprint: 3608 4610 8C08 B8EB 0970 9686 8A93 386C 6116 EFE2
>
This archive was generated by hypermail 2a24 : Mon Nov 06 2000 - 15:12:57 MST