On 25 Jun, Phil Watkinson shaped the bitstream to say:
> At 09:49 25/06/98 +0000, [EMAIL PROTECTED] wrote:
>>
>> [snip....] Thus when you install the
>>kernel rpm it goes along fine until it tries to remove the 32 modules
>>and then it errors out. What I ended up with was a partial install of
>>an RPM... (Whoa!).
>
> I was all set up to upgrade my RH 5.0 to the 2.0.34 kernel, but now I'm
> worried. (BTW, I have kernel 2.0.31 - not 32).
>
> Would a workround be to remove the existing modules package first -
> ( kernel-modules-2.0.31-7 on my machine) then upgrade the rest from a
> temporary directory as described ??
>
> Anyone successfully upgraded to 2.0.34 on a RH 5.0 system without having
> to do a full re-compile afterwards??
>
> Waiting anxiously,
> Phil Watkinson,
> Boston, UK.
>
>
I forgot something off of that last post. My environment is SCSI and I
run the SCSI driver as a module so I have to mkinitrd. That's why I
had the big hassle with modules in the first place 'cause the modules
for the new kernel didn't contain loop.o or /dev/loop0. I don't know
why it happened this way but since it happened to me twice I've gotta
believe it's happening to everyone with the same environment. The real
pisser is that when I ran make xconfig I made the appropriate
module selections but the loopback device just flat wasn't there 40
minutes later when I was running mkinitrd! My solution? I hadn't
deleted the 2.0.32 modules yet and there was a file in the modules
directory called (drum roll please <g>) "loop.o". So I cp'd it into the
new modules directory for 2.0.34 and voila... everything worked!
--
Chuck Mead
[EMAIL PROTECTED]
http://www.moongroup.com/unix/
HOST SYSTEM NOT RESPONDING, PROBABLY DOWN. DO YOU WANT TO WAIT? (Y/N)
This message sent with TkRat v1.1
--
PLEASE read the Red Hat FAQ, Tips, Errata and the MAILING LIST ARCHIVES!
http://www.redhat.com/RedHat-FAQ /RedHat-Errata /RedHat-Tips /mailing-lists
To unsubscribe: mail [EMAIL PROTECTED] with
"unsubscribe" as the Subject.
