Yes, with the RPM command. There is a parameter you can specify to RPM that tells it to install the contents relative to a particular directory, not relative to "/". That parameter is: --root <dir> Use the system rooted at <dir> for all operations. Note that this means the database will be read or modified under <dir> and any pre or post scripts are run after a chroot() to <dir>.
Which is just what you want/need. Mark Post -----Original Message----- From: James Melin [mailto:[EMAIL PROTECTED]] Sent: Friday, January 31, 2003 1:42 PM To: [EMAIL PROTECTED] Subject: Re: Assuming my IPL halt problem is because the kernal I installe d needs the 3390 mod 9 patch... Mark, thanks for the succinct point by point.... The problem that remains is that the kernal update on the maint disk are in RPM format. I am attempting to get the CD contents over to the new file system in order to attempt to run the yast2 utility. I have doubts this will work, nor do I think that I can get away with running RPM with my root file system mounted at /mnt instead of /. Is there any way to extract the needed bits from the RPM? |---------+----------------------------> | | "Post, Mark K" | | | <[EMAIL PROTECTED]| | | m> | | | Sent by: Linux on| | | 390 Port | | | <[EMAIL PROTECTED]| | | IST.EDU> | | | | | | | | | 01/29/2003 03:16 | | | PM | | | Please respond to| | | Linux on 390 Port| | | | |---------+----------------------------> >--------------------------------------------------------------------------- ---------------------------------------------------| | | | To: [EMAIL PROTECTED] | | cc: | | Subject: Re: Assuming my IPL halt problem is because the kernal I installe d needs the 3390 mod 9 patch... | >--------------------------------------------------------------------------- ---------------------------------------------------| James, What I would recommend doing is this: 1. IPL from the tape you created to start the install. 2. Start the install process again. When it gets to the point where the DASD volumes are mounted, stop. 3. Start another telnet/ssh session to the system. (If you try to break out of yast, I believe it unmounts the disks before it exits.) 4. FTP the updated kernel from your update CD to the boot directory on DASD. (See next item as to where that would be.) 5. chroot to the root file system. I believe the SuSE install mounts the volumes on /mnt, so you would do "chroot /mnt" 6. Re-run zipl with the new kernel. This is "applying the maintenance." 7. Exit from the chroot. 8. Unmount the DASD volumes 9. Re-IPL from DASD. Mark Post -----Original Message----- From: James Melin [mailto:[EMAIL PROTECTED]] Sent: Wednesday, January 29, 2003 10:27 AM To: [EMAIL PROTECTED] Subject: Assuming my IPL halt problem is because the kernal I installed needs the 3390 mod 9 patch... How do you update a system you cannot boot (SuSE 7.2 in this case)? The docs on the CD of maintenance I have say to 'run yast2 from the installed system' which is impossible, since I cannot get it to install. I have a ton of patches on the one maint CD I recieved. I was even able to use this to get an init ramdisk that could handle fdasd/dasdfmt properly, but I'm at a loss to figure out how to get the maint into a system that I cannot bring up. I am running in LPAR mode, as we have no VM (budget) available, so I can't even make 3390-3 images to use instead.
