Oh dear... now we are both confused? > Yes, I am trying to build a one pack RAMDISK/RPM volume.
I only recalled your hobby after the first reply. > You lost me on these two replies. > Seems like they accomplish the same thing? The quick start disk is just to IPL the ramdisk system, and then load the stuff via FTP or so. The second is to have a disk with rpm packages and boot that. > I'm not sure why you sent the second one?? I think it is a neat idea and should be tried, and I expect it is a lot of work ;-) > How is it different than the first?? I remembered your need for CMS RESERVEd format, and right now the bug in zipl does not allow to boot from that type. But if you create an OS compatible volume (or LDL layout) you have trouble shipping the data. I am getting on thin ice since I did not try this yet myself, but I expect the RedHat install 'from hard disk' will require a particular layout of that partition that might give trouble with the /boot there too. So I suggested two partitions that you might be able to copy with OS utilities (not tried). > If I go with the second suggestion, > what would the syntax of the zipl be ??? With your fully working RedHat system, you get the new disk in it too. Say your new disk would be /dev/dasdc with two partitions. Mount the /dev/dasdc1 over /boot and fill it with the boot kernel, initrd, parmfile and the bootsector fragments that live in your /boot now. cd /boot zipl -t . -i kernel.img -r initrd_oco.img -p parmfile Also build a filesystem on /dev/dasdc2 and store the proper RedHat/.. directory structure there. Now when you IPL that disk you should be able to get to that 2nd partition and use that as your install medium. As said, nerver tried. Rob
