On Sun, 27 Apr 2003, Robert Denton wrote: >First I decided to ftp get the ks file from the windows ftp server and edit >it in vi and re-upload it. This did not work. Either vi preserves the CRLF line endings, or the Windows FTP server / linux client, ascii vs binary download gets it wrong. >Next I decided to create an all new ks file on my RH9 box in vi, and >never open it or touch it with a windows editor, and upload it to the >windows based FTP server from which I was doing my remote installs. I >was certain this would work. Oddly it did not. You uploaded it ascii mode and downloaded in binary perhaps? >So then I decided to make my RH9 box a webserver (on a private IP) upload >the base and RPMS dirs to it and recreate a brand new ks.cfg in vi and >placed it in the webroot of the RH box. Finally this worked. As you'd expect :) >The secret, as it appears to this Linux newbie, is to never let it >touch a windows machine in any way. Create the kickstart file in Linux >and keep it in Linux. You might get away with a Windows FTP server if you make sure the file on disk has Unix line endings. To identify the type of file in linux, use either "cat -v filename" and look for ^M characters, or use "file filename" and look for "filename: ASCII text, with CRLF line terminators". In Windows, open the file in Notepad; CRLF will look "right", single LF endings will run together into one enormous line. (Wordpad always displays properly, so don't use that to check.) To convert between line endings, the utilities dos2unix and unix2dos are useful. There's also mac2unix for those CR line endings. Cheers, Phil
