On Sat, 2003-07-26 at 13:50, bruce wrote: > Hey... > > It was never an issue understanding what an ISO is and it's role... > > What I was looking for... were the actual files themselves... for the most > part, the responses I got, were dealing with the ISOs... The actual RH9.0 > "installation files" can be found on the RH Ftp site ...I for get the actual > path now.. but i just found them!!!!! > > These are the apparent files the I'm looking for.. And nowhere in the > section of the RH installation manual could I find the actual location > listed... Or any indication as to where they reside, simply that you need > them! > > Now if I can figure out how to get the Remote Upgrade process down pat!! >
I don't understand. Everything you need is contained in the cds or isos. THe installer is downloaded during the process from the directory that contains all the files from the cd (what I refer to as the installation tree). the kernel and initrd needed to boot into the installation are contained in the images directory at the root of the first cd ( maybe all of them, I don't know) Used to be that you could gain access to the kernel and initrd my either creating a boot disk from the bootnet.img file or mounting it like so: The following is where I keep my 7.3 files [EMAIL PROTECTED] allfiles]$ pwd /install/redhat/7.3/allfiles [EMAIL PROTECTED] allfiles]$ ls -F autorun* README.ko RELEASE-NOTES-it.html boot.cat README.zh_CN RELEASE-NOTES.ja dosutils/ README.zh_TW RELEASE-NOTES-ja.html EULA RedHat/ RELEASE-NOTES.ko GPL RELEASE-NOTES RELEASE-NOTES-ko.html images/ RELEASE-NOTES.de RELEASE-NOTES.zh_CN README RELEASE-NOTES-de.html RELEASE-NOTES-zh_CN.html README-Accessibility RELEASE-NOTES.es RELEASE-NOTES.zh_TW README.de RELEASE-NOTES-es.html RELEASE-NOTES-zh_TW.html README.es RELEASE-NOTES.fr RPM-GPG-KEY README.fr RELEASE-NOTES-fr.html TRANS.TBL README.it RELEASE-NOTES.html README.ja RELEASE-NOTES.it [EMAIL PROTECTED] allfiles]$ cd images [EMAIL PROTECTED] images]$ ls boot.img drvblock.img fr oldcdrom.img pxeboot bootnet.img drvnet.img it pcmciadd.img README de es ja pcmcia.img TRANS.TBL [EMAIL PROTECTED] images]$ mkdir /mnt/instimg mkdir: cannot create directory `/mnt/instimg': Permission denied [EMAIL PROTECTED] images]$ sudo mkdir /mnt/instimg [EMAIL PROTECTED] images]$ mount bootnet.img -o loop /mnt/instimg/ mount: only root can do that [EMAIL PROTECTED] images]$ sudo mount bootnet.img -o loop /mnt/instimg/ [EMAIL PROTECTED] images]$ cd /mnt/instimg/ [EMAIL PROTECTED] instimg]$ ls boot.msg initrd.img param.msg snake.msg vmlinuz general.msg ldlinux.sys rescue.msg syslinux.cfg [EMAIL PROTECTED] instimg]$ the vmlinuz and initrd.img files are the ones that need to be put on the hard drive and booted into. try it on a test box until you get a feel for it. I typically attack problems like this by breaking complex stuff into simpler parts. In this case I see several parts that need to be completed: 1) Create network accessible installation tree. THe same old link I mentioned before test regular installation against it with floppy. Again creation of the floppy is in the docs. 2) boot install from harddrive copy the installation kernel and initrd to the harddrive and do the lilo thing until you can get the install to work manually from a remote machine Lilo will not have a ks.cfg append line in it for this step 3) build a kickstart config (ks.cfg) and do the lilo thing for it. the kickstart can be done from a floppy too if the harddrive thing gets in the way. It is quite a bit to get you head around at once so break it into pieces. Bret -- redhat-list mailing list unsubscribe mailto:[EMAIL PROTECTED] https://www.redhat.com/mailman/listinfo/redhat-list
