Preston, I had the same problems with the same things. I found that you need to give the entire path to the executable, /bin or /sbin for the /mnt commands. Also, for the fstab file, I echo'd the entries that I wanted in the fstab file using redirection, and then ran the mount -a command right after. That seemed to work. Its also very important to understand what's going on in the chrooted environment. Drew ----- Original Message ----- From: "Preston Wade" <Preston_Wade@xxxxxxxxxx> To: <kickstart-list@xxxxxxxxxx> Sent: Monday, February 17, 2003 2:18 PM Subject: %post script > Hello All, > > I have noticed some interesting things with kickstart lately. I have just > really started playing with it. One of the major things I have noticed and > haven't really seen an answer to is the following. > > When I use a post install script in my ks.cfg file the following things > don't happen. > /mnt/cdrom - doesn't get created > /mnt/floppy - doesn't get created > their corresponding entries in /etc/fstab don't get created. > > these entries normally get installed with the filesystem rpm which I am > installing. > > If I use the same ks.cfg file with the post section commented out the above > items get created. > > I can't really think of an explanation for this except that I am stomping on > an existing post install script. > > I could just add these things to my post section but, then I am not sure > what else is not getting created correctly. > > Thanks, > Preston > > > > _______________________________________________ > Kickstart-list mailing list > Kickstart-list@xxxxxxxxxx > https://listman.redhat.com/mailman/listinfo/kickstart-list > >
