> >>My kickstart file correctly >>builds the new machine and makes the authorized_keys, but when >>I try to mount the nfs (located in 192.168.14.1:/tftpboot) and >>copy a file to the new system kickstart fails. > > Fails how? If it's the mount that's failing (or taking a very long > time), you probably need the "-o nolock" option. > >>Also where does kickstart send the error output? > > To the other VTs (use Alt+F2, Alt+F3 etc to see them). > It seems that I was not making it through the nfs mount. The "-o nolock" worked great. I could not see any error message in the Alt+F3 or Alt+F5 screens that mentioned nfs. The server logs were also quite useless. However, it works now. Thanks again. -JH
