First off, thanks to all of you who replied to my prior message. I was amazed by the speed of your replies. I fixed my problems with %post scripting and that is working fine now. I decided to create a 1st run startup script && rank dos2unix on the file. Works like a charm. This leaves me with my current problem of having to manually enter the IP Address every time I kickstart. It seems like KS is ignoring my network line. At one point it would try to use DHCP but failed; I thought (from other posts in this mailing list) that it was the combination of the gigabit ethernet card and our catalyst. Treespanning is turned on, but portfast is turned on (the reccomended fix) for that node. If that was the problem, one would assume that the portfast would have solved it. Thus, I must assume that it has something to do with fat fingers or blurry eyes. I've included snippet of my ks.cfg(s) file below. From what I understand the syntax is correct -- if someone could point out what I'm doing wrong I'd much appreciate. The theories I am currently investigating are: 1. Being that network module is currently on a drivers disk, I may have to create my own custom install disks. 2. provide ip as an option at bootprompt. 3. train an army of monkeys to enter the ip information. .::SNIP::. # Kickstart file automatically generated by anaconda. # ks.cfg install lang en_US langsupport --default en_US.iso885915 en_US.iso885915 keyboard us mouse msintellips/2 --device psaux network --bootproto dhcp --device eth0 nfs --server 192.168.210.12 --dir /u2/install/7.3.wget
