Yes, I know the files are in ASCII - I did that intentionally because all of the Linux install documentation says to use a Windows or Linux FTP server (or SMB server) , but I wanted to try to install from my z/OS file server.
I don't _know_ what Yast does under the covers to read the installation files, I just thought it would assume an ASCII system. And there's no documentation which says "these files need to be text, these binary", or at least I haven't found it on the CDs (Google is next). Of course, converting them to EBCDIC might also bring up line-ending issues. As for using the CMS FTP client - no, I can't use it because I'm a z/OS shop! The TSO client works though. I created /sles9xroot and in the dialog on the HMC with the install system I gave it that directory. It is also the home directory of the user I gave the dialog. The FTP log shows it retrieving /sles9xroot/content in ASCII /sles9xroot/boot/root in binary /sles9xroot/content _again_ in binary this time /sles9xroot/media.1/info.txt in binary /sles9xroot/control.xml in binary before (I think) the failure message occurs. Tim Hare Senior Systems Programmer Florida Department of Transportation (850) 414-4209 ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
