OS updates install via KS!

[Wehner, Robert]

Asim,

I think someone mentioned that you're running the rpm command in a nochroot
environment in the %post section, so you're essentially installing the
updates into the boot environment, not onto the OS you're installing on the
disk. You can run all of this without the "--nochroot" and it should work
(removing the $CHROOT variable since it won't be needed). If you need the
nochroot environment for some reason, you can run both a "%post --nochroot"
and then a "%post" version for the rpm install. If you must leave the %post
section as nochroot, you could also try the --root option to rpm. Something
like rpm -Fvh --root ${CHROOT} ${CHROOT}${KICKMNT}/OSupdates/* may work
although I have not tried that myself in a kickstart environment.

Robert

>Date: Wed, 07 Apr 2004 13:42:44 -0400
>From: "R. Drew Davis" <drew at anbauenterprises.com>
>Subject: Re: OS updates install via KS!
>To: Asim Zuberi <asim.zuberi.1993 at njit.edu>
>Cc: linux-poweredge at dell.com

>On Tue, 2004-04-06 at 09:46, Asim Zuberi wrote:
>  
>> Hi there --
>>  
>> Here's the situation. I have the following code configured to perform
>> the OS updates during the
>> kickstart process. For some reason the updates didn't get installed
>> during the process. However
>> if I execute the same command (rpm -Fvh <dir>) after the OS install
>> and mounting the filesystem
>> (local/RedHat) via NFS  then it runs fine. What am I missing here?
>>  
>> OS: RedHat 9.0 (open source); HW: Dell PowerEdge 650
>>  
>> /etc/exports 
>> =========
>> /local/RedHat *(ro,root_squash)
>>  
>>  
>> ks.cfg
>> =====
>>  
>> %post --nochroot
>> #!/bin/sh
>> CHROOT=/mnt/sysimage
>> KICKMNT=/ks
>>  
>> test -d "${CHROOT}${KICKMNT}" || mkdir -- "${CHROOT}${KICKMNT}"
>>  
>> # Setup NFS mounts
>> echo "****** Mounting from bladetest2 Server....******"
>> mount -t nfs 135.1.45.11:/local/RedHat "${CHROOT}${KICKMNT}"
>>  
>> echo "****** Applying package updates...******"
>> rpm -Fvh "${CHROOT}${KICKMNT}"/OSupdates/*
>> 
>> thanks!
>> --Asim;
>
>No messages anywhere?   My first blind guess is that the $PATH isn't set
>right so the commands aren't running at all.   You might be able to
>discern this by how quickly does the processing complete?   If it
>finishes too quickly, maybe it isn't really running at all.

>My second blind guess is that the run *is* completing, but somehow not
>to the file system that you expect it to install to.   I'd rather run
>the first guess to ground before trying to figure out an explanation
>that fits the framework of this 2nd guess.
>
>Drew
>  
>