It may work better to create the NFS export space and mount it RW from an ASCII client workstation - then build the install tree from the ASCII client.
On 3/14/06, Michael MacIsaac <[EMAIL PROTECTED]> wrote: > > 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 > -- Jay Brenneman ---------------------------------------------------------------------- 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
