lws@comm.WANG.COM (Lyle Seaman) (02/22/90)
I have an Sun running SunOS 3.4 and several SCO Unix V/386 boxes. I have no problem exporting filesystems from any of these machines and mounting them on any other machine, but if I try to export only a subirectory (a child of a filesystem root) I have no success. For example: when my exports file contains /usr And I do a showmount -e thathost from another machine I see /usr is exported. I can mount /usr on another machine as well. But if my exports file contains: /usr/src Which is not a filesystem itself (Note that /usr/src is the only thing in the exports file), when I do a showmount -e thathost nothing appears to be exported. Sun support wasn't much help - they said it "works on a 4.0 machine configured as a server". Please e-mail. Thanks, Lyle. comm.wang.com!lws@uunet.uu.net
dce@smsc.sony.com (David Elliott) (02/23/90)
In article <1990Feb22.152003.22717@comm.WANG.COM> lws@comm.WANG.COM (Lyle Seaman) writes: >I have an Sun running SunOS 3.4 and several SCO Unix V/386 boxes. >I have no problem exporting filesystems from any of these machines and >mounting them on any other machine, but if I try to export only a >subirectory (a child of a filesystem root) I have no success. This appears to be a general NFS version 3 problem. The behavior is similar on Sony NEWS/OS, which uses this version of NFS. Given the fact that SunOS 3.4 probably came out as NFS version 4 was being finished up, it's unlikely that there's a version 3 fix for it. (Note that I'm speculating on the timing -- I wasn't there.) The only thing I can think of (besides upgrading your system) to help would be to set the permissions on the upper levels of the filesystem so that it isn't useable from an NFS mount. This will have ramifications on your local machine. >Sun support wasn't much help - they said it "works on a 4.0 machine >configured as a server". What do you expect? SunOS 4.* has been out for over a year now. My experience shows that it isn't reasonable for a company to support that many versions of an OS (you're asking them to support 2 major and 4 minor versions from 3.4->4.0.3). As far as I'm concerned, part of the support "understanding" (if not the actual agreement) is that the customer agrees to upgrade to the latest version for continued support, and the vendor agrees to keep the amount of work required to upgrade to a minimum. One question: Do you believe that the support folks even tried to research the problem, looking it up in back reports or talking to technical folks? Sun support has a very good reputation (I guess with that many DOA units, you have to have good support). -- David Elliott dce@smsc.sony.com | ...!{uunet,mips}!sonyusa!dce (408)944-4073 "...it becomes natural, like a third sense." -- Homer Simpson
harrys@tons61.UUCP (Harry Skelton) (03/01/90)
In article <1990Feb22.152003.22717@comm.WANG.COM> lws@comm.WANG.COM (Lyle Seaman) writes: > >Sun support wasn't much help - they said it "works on a 4.0 machine >configured as a server". > >Please e-mail. >Thanks, >Lyle. >comm.wang.com!lws@uunet.uu.net According to the NFS we have, it is "illegal" to export a child of a exported file system/directory. Much the same way you are trying to do. I personally think this problem. Unix file permissions should handle any problems with file I/O etc... I have a problem where PC-NFS does not support multible groups when the Unix host does not run YellowPages. (we have no need to...we are happy with /etc/passwd and /etc/group). Seems that we can't mount drives because of this! Real bummer. I think we'll have to make alternate id's for PC and others for the PC users due to mount areas and Unix file permissions. Sun has not been a big help on this issue. Just for the count: this is/will be affecting 200 workstations! -- Harry Skelton - Senior Systems Administrator - U.S. Dept. of Transportation ..!attctc!tons61!harrys ..!obdient!tons61!harrys ..!tfd!tons61!harrys [ Views expressed by Harry Skelton are not those of the US Gov. or CBSI ]