|
On Oct 19, 2018, at 10:04 PM, Scott Klement <midrange-l@xxxxxxxxxxxxxxxx> wrote:
Jon,
Mounting NFS from the Mac should be as simple as:
mount your-ibmi.com:/path/to/nfs/share/on/server /path/to/mount/on
-SK
On 10/16/2018 11:56 AM, Jon Paris wrote:
None of it Rob - but since I need to issue the mount on the Mac the nice pretty IBM i command doesn't help a lot. It has to be "translated" - I finally found an example on the web that actually identified which part was the server name. Tried it - still can't get it to work.
I've wasted way too much time on this so for now I'm just giving up.
Thanks to all for the help.
Jon Paris
www.partner400.com
www.SystemiDeveloper.com
On Oct 16, 2018, at 7:54 AM, Rob Berendt <rob@xxxxxxxxx> wrote:
On part two: How to tell the system to mount to...
What part of this example was hard to figure out?
MOUNT TYPE(*NFS) MFS('gdihq:/tmp') ...
The name of the system I am mounting against was GDIHQ
Rob Berendt
--
IBM Certified System Administrator - IBM i 6.1
Group Dekko
Dept 1600
Mail to: 2505 Dekko Drive
Garrett, IN 46738
Ship to: Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com
From: "Jon Paris" <jon.paris@xxxxxxxxxxxxxx>
To: "Midrange-L Midrange-l" <midrange-l@xxxxxxxxxxxx>
Date: 10/15/2018 04:22 PM
Subject: Re: Mapping Shared IFS folders to Mac
Sent by: "MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxx>
I'm only interested in the Mac "consuming" the exported folders Rob.
I agree about using the native mount (i.e. native to Mac) but how the beep
do you tell it what server to connect to? - the man pages go on forever
and (like most Linux docs) use a lot of words to say nothing terribly
useful. And of course there is no help ,,,
Jon Paris
www.partner400.com
www.SystemiDeveloper.com
On Oct 15, 2018, at 4:00 PM, Rob Berendt <rob@xxxxxxxxx> wrote:For
CHGNFSEXP is the IBM i naming version for EXPORTS, not for MOUNT.
And EXPORTFS is the bastardization of the industry export because of
binder language already using EXPORT.
EXPORT* = serve
MOUNT = consume
For commands that are common to rest of the open systems world (like
mount, ping) I tend to use their naming instead of the IBM i version.
example I would use MOUNT instead of ADDMFS(which I had to search tofind
that name) and I would use PING instead of VFYTCPCMN.Jon
The IBM i version may often make more sense but if you work in multiple
worlds then I stick to the standards.
Rob Berendt
--
IBM Certified System Administrator - IBM i 6.1
Group Dekko
Dept 1600
Mail to: 2505 Dekko Drive
Garrett, IN 46738
Ship to: Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com
From: "Jim Oberholtzer" <midrangel@xxxxxxxxxxxxxxxxx>
To: "'Midrange Systems Technical Discussion'"
<midrange-l@xxxxxxxxxxxx>
Date: 10/15/2018 03:29 PM
Subject: RE: Mapping Shared IFS folders to Mac
Sent by: "MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxx>
Have you tried NFS mounts? Aside from bypassing the crap SMB/SBM2 does
to
you it's faster.
On IBM i .
Strnfssvr *all
CHGNFSEXP OPTIONS('-I -O RO') DIR('/whateverdirectory/subdir/etc/etc')
On Unix/MAC:
Mount command.
I'll assume you have authority to the directories and such.
--
Jim Oberholtzer
Agile Technology Architects
-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of
Parisfor
Sent: Monday, October 15, 2018 12:08 PM
To: Midrange-L <midrange-l@xxxxxxxxxxxx>
Subject: Mapping Shared IFS folders to Mac
Anyone had any experience with doing this?
I'm getting an error that URLs of type smb: are not supported.
All documentation I can find relates to Windows. I have no trouble
connecting to other servers (and for that matter connection to the i by
other means).
OS is at 7.3.
I know it will be something idiotic but I haven't used a mapped drive
about 15 years and my ancient brain has forgotten everything I ever knewI
guess..
And yes I have checked that the NetSvr is started.
Jon Paris
www.partner400.com
www.SystemiDeveloper.com
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe,
unsubscribe,
or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a
moment to review the archives at https://archive.midrange.com/midrange-l
Please contact support@xxxxxxxxxxxx for any subscription relatedlist
questions.
Help support midrange.com by shopping at amazon.com with our affiliate
link:
http://amzn.to/2dEadiD
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.
Please contact support@xxxxxxxxxxxx for any subscription related
questions.
Help support midrange.com by shopping at amazon.com with our affiliate
link: http://amzn.to/2dEadiD
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
To post a message email: MIDRANGE-L@xxxxxxxxxxxxquestions.
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.
Please contact support@xxxxxxxxxxxx for any subscription related
Help support midrange.com by shopping at amazon.com with our affiliatelink: http://amzn.to/2dEadiD
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.
Please contact support@xxxxxxxxxxxx for any subscription related
questions.
Help support midrange.com by shopping at amazon.com with our affiliate
link: http://amzn.to/2dEadiD
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.
Please contact support@xxxxxxxxxxxx for any subscription related questions.
Help support midrange.com by shopping at amazon.com with our affiliate link: http://amzn.to/2dEadiD
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.
Please contact support@xxxxxxxxxxxx for any subscription related questions.
Help support midrange.com by shopping at amazon.com with our affiliate link: http://amzn.to/2dEadiD
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.