thakur@zerkalo.harvard.edu (Manavendra K. Thakur) (07/18/90)
There is a bug in the 4.1 mount command that prevents the machine from
mounting NFS filesystems from non-Sun machines. The relevant Bug IDs are
1040275 and 1036952.
Sun has fixed this bug in SunOS 4.1.1. For those who need the patch now,
however, it is available from Sun support (refer to the two bug id numbers
listed above). Or, you can ftp the patch from my machine,
zerkalo.harvard.edu [128.103.40.201], in the file /pub/mount.4.1.patch.Z.
Here is the README file that comes with the patch:
=== Cut here ===
Kewords: mount
Synopsis: sun client cannot mount a filesystem from a non-Sun system under 4.1
SunOS release: 4.1
BugID's fixed with this patch: 1040275, 1036952
Architectures for which this patch is available: sun3, sun3x, sun4, sun4c
Obsoleted by: 4.1.1
Problem Description:
A Sun machine running SunOS 4.1 cannot mount a file system exported from
a non-Sun machine. The error message is something like:
mount: non-Sun:/filename server not responding
RPC program not registered
But, on the same local net the Sun machines running SunOS 4.0.3 are
still able to mount the same non-Sun remote file system without any
problem.
=== End here ===
Note that the "fix" Sun implemented simply consists of backing off to a
slightly previous version of mount.c:
zeraklo% strings /usr/etc/mount.4.1 | grep '@(#)'
@(#)mount.c 2.93 90/01/08 Copyr 1985, 1989 Sun Micro
@(#)mountxdr.c 1.19 89/06/20 Copyr 1984 Sun Micro
zerkalo% strings /usr/etc/mount | grep '@(#)' # The patched version
@(#)mount.c 2.91 89/10/05 Copyr 1985, 1989 Sun Micro
@(#)mountxdr.c 1.19 89/06/20 Copyr 1984 Sun Micro
Hope this helps somebody out there.
Manavendra K. Thakur Internet: thakur@zerkalo.harvard.edu
System Manager, High Energy Division BITNET: thakur@cfa.BITNET
Harvard-Smithsonian Center for DECNET: CFA::thakur
Astrophysics UUCP: ...!uunet!mit-eddie!thakurlaukee@relay.eu.net (David Lau-Kee) (07/23/90)
thakur@zerkalo.harvard.edu (Manavendra K. Thakur) writes: >There is a bug in the 4.1 mount command that prevents the machine from >mounting NFS filesystems from non-Sun machines. The relevant Bug IDs are >1040275 and 1036952. Does anyone have more information on this bug? Exactly what is failing? I appear to be able to mount my NeXT partitions on Suns running 4.1. David Lau-Kee NRS: laukee@uk.co.canon, INET: laukee%canon@nsfnet-relay.ac.uk UUCP: laukee@canon.uucp, PATH: ..!mcsun!ukc!uos-ee!canon!laukee
brent@terra.eng.sun.com (Brent Callaghan) (07/24/90)
In article <10148@brazos.Rice.edu>, canon!laukee@relay.eu.net (David Lau-Kee) writes: > thakur@zerkalo.harvard.edu (Manavendra K. Thakur) writes: > > >There is a bug in the 4.1 mount command that prevents the machine from > >mounting NFS filesystems from non-Sun machines. The relevant Bug IDs are > >1040275 and 1036952. > > Does anyone have more information on this bug? Exactly what is failing? > I appear to be able to mount my NeXT partitions on Suns running 4.1. SunOS 4.1 adds a new version of the MOUNT protocol (version 2) that includes a procedure to provide POSIX pathconf support. The SunOS 4.1 mount command was modified to try a bind to version 2 followed by a fallback to version 1 if version 2 is not supported. The patch description is NOT correct. The new mount logic works correctly for almost all non-Sun implementations of NFS except for Silicon Graphics and Prime. Made in New Zealand --> Brent Callaghan @ Sun Microsystems uucp: sun!bcallaghan phone: (415) 336 1051