I was planning on using FTP rather than NFS (since I don't have NFS set up). I probably will end up with ASCII / EBCDIC issues, I imagine, unless everything is done in binary by the installer (which, if it assumes ASCII systems, it could do). Since I'm not running the actual script - I don't believe USS has a "loopback" mount option either - I'm trying the following:
1. Burn the iso images to CD 2. Create an HFS dataset for each CD 3. Create a /u/sles9root directory, and the other directories that mksles9root creates 4. Create appropriate mounts (cribbing from mksles9root) 5. using PuTTY's pscp command copy the CDs to the z/OS-USS directories What I am ending up with is all of the files, in ASCII, in their appropriate place. The main question is whether the FTP install starts in 'binary' or 'text' mode, 'text' would cause the z/OS FTP server to invoke translation under the assumption that the files were EBCDIC which is an incorrect assumption in this case. iconv is indeed the conversion utility. Also, while using BROWSE within Unix Systems Services, the DISPLAY UTF8 makes an ASCII file more-or-less readable - x'0A' isn't handled properly so there are no line endings, but you can view what it says. I'll let you know how it works (or how it blows up). Tim Hare Senior Systems Programmer Florida Department of Transportation (850) 414-4209 Michael MacIsaac <[EMAIL PROTECTED]> Sent by: Linux on 390 Port <[email protected]> 03/14/2006 11:27 AM Please respond to Linux on 390 Port <[email protected]> To [email protected] cc Subject Re: mksles9root.sh question Tim, > is the "-e" meaningful on a Linux system I believe that is recommended in the SuSE documentation. On Linux the -e flag is used to enable interpretation of the backslash-escaped characters. And there does not appear to be any more backslashed characters in the script, so you can probably safely delete the flag. However, the bigger question is "Will this work?" I haven't heard of anyone using z/OS USS to do serve the install tree. The issue of ASCII <=> EBCDIC will almost certainly come into play. The install tree will have both binary and text files. I'm assuming you were planning to export the directory in NFS as binary, so text files should come across as ASCII (though you will probably not be able to read them in USS). The order and instorder files, however, might be a problem - I assume the script will create them as EBCDIC. While you're hacking out the -e flag, you may want to hack in an EBCDIC => ASCII command - what is it iconv? Just some thoughts. I may be missing some assumptions. Let us know how it goes. "Mike MacIsaac" <[EMAIL PROTECTED]> (845) 433-7061 ---------------------------------------------------------------------- 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 ---------------------------------------------------------------------- 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
