Hi, thanks...but a couple more questions: >Depends on what one defines the purpose of kickstart to be. If it's to >automate the Q+As in the install and allow for custom scripting, then >that still works. So if this still works....then why would I need to worry about the anaconda assumptions? If it is still available then it sould work? >You could: > >- Rebuilt bootdisk.img to include the modules you need (not tested, >might break some anaconda assumptions about where modules are located). >- Customise and burn the provided boot.iso to CD, and install solely >from that. Where is the documentation for this please? I've been pouring over RH9 docs for two weeks and have not found it. The 9 docs are quite obscure. The LDP howtos were quite helpful in providing the information I needed to get this going correctly. But the 9 docs are not too helpful. >- Use a "PXE floppy" or the hardware of the PC to kick off a PXE >install, where the network drivers can be transferred over the network >:). For security purposes of our network...and some of our contract requirements, I need to keep it to a CD/FLoppy. That's why this ks solution was so appealing to me to begin with. > >Hope this helps, Maybe...if you could point me in the exact dir for documentation that would tremendously help. -C > > >_______________________________________________ >Kickstart-list mailing list >Kickstart-list@xxxxxxxxxx >https://listman.redhat.com/mailman/listinfo/kickstart-list F. Charlene Watson Systems Analyst LAboratory of Information Technologies University of Tennessee, Knoxville 865-974-9187
