Since this is simply to read files, is it necessary to give the BFS filespace 
any space, or can it be enrolled with BLKS 0? 

Regards, 
Richard Schuh 

 

> -----Original Message-----
> From: The IBM z/VM Operating System 
> [mailto:[email protected]] On Behalf Of Richard Troth
> Sent: Thursday, October 15, 2009 9:39 AM
> To: [email protected]
> Subject: Re: Access Linux Files From CMS
> 
> Let me second what Dave Jones said: try the CMS NFS client.  
> If you're using CMS to manage Linux guests, it's a really 
> handy tool.  For example, consider that Linux is running NFS 
> to share a directory called "/export/stuff".  You could:
> 
>         openvm mount /../VMBFS:VMSYS:ROOT/ /
>         openvm run /bin/mkdir -m 555 -p /import/stuff
>         openvm mount /../NFS:linuxhostname/export/stuff /import/stuff
>         openvm getbfs /import/stuff/the.file the file a (olddate
> 
> Look into the TRANS|NOTRANS option for both 'mount' and 'getbfs'.
> Look into the LIST|NOLIST and other options for 'mount'.
> And of course the REPLACE option for 'getbfs', if needed.
> VM TCP/IP client tools disk required.
> 
> The CMS NFS client requires that you have a (non-NFS) byte 
> filesystem mounted as the root.  (You do not need the rest of 
> the shell and utilities functioning for this example, except 
> for the 'mkdir'
> command.  You do NOT need to launch a shell.)  The nature of 
> POSIX mounts is that there be an empty directory already at 
> the point where you want to mount.  (Thus the 'mkdir' command.)
> 
> -- Rick;   <><
> 
> 
> 
> 
> 
> On Thu, Oct 15, 2009 at 11:28, Schuh, Richard <[email protected]> wrote:
> > We have a need to be able to access files on a Linux system 
> from CMS 
> > in a different LPAR. Never having done this, the specifics 
> of how to 
> > do it are a mystery waiting to be solved. What are the 
> steps that need 
> > be done in order to accomplish this? Is there a procedure 
> for doing it 
> > documented somewhere, a Redbook perhaps? Any pointer to 
> speed us on our way will be appreciated.
> >
> > Regards,
> > Richard Schuh
> >
> >
> >
> 

Reply via email to