On Wed, Jun 22, 2005 at 03:49:39PM -0500, Rene Rivera wrote:
>
> bash-3.00# mount_nfs -2 192.168.0.3:/export /mnt/export.3
> mount_nfs: /mnt/export.3: Protocol not supported
> bash-3.00# mount_nfs -2 -T 192.168.0.3:/export /mnt/export.3
> mount_nfs: /mnt/export.3: Protocol not supported
> bash-3.00# mount_nfs -2 -U 192.168.0.3:/export /mnt/export.3
> mount_nfs: /mnt/export.3: Protocol not supported
i checked /usr/src/sbin/mount{,_nfs} and /usr/src/sys/nfs
to see what part of the code is making the 'Protocol not supported',
but didn't find it. :( doing a global search in /usr/src
( granted, if somewhere in the code it is like '%s not supported'
or crosses a terminal line, i would've missed it ):
----
[/usr/src] $ find . -type f | xargs grep "Protocol not supported"
./gnu/lib/libiberty/src/strerror.c: ENTRY(EPROTONOSUPPORT, "EPROTONOSUPPORT",
"Protocol not supported"),
./gnu/usr.bin/cvs/lib/strerror.c: ENTRY(EPROTONOSUPPORT, "EPROTONOSUPPORT",
"Protocol not supported"),
./gnu/usr.bin/cvs/os2/porttcp.c: case SOCEPROTONOSUPPORT: return
"Protocol not supported";
./gnu/usr.bin/cvs/windows-NT/sockerror.c: /* EPROTONOSUPPORT */ "Protocol
not supported",
./gnu/usr.bin/perl/pod/perlfaq.pod:Why doesn't my sockets program work under
System V (Solaris)? What does the error message "Protocol not supported" mean?
./gnu/usr.bin/perl/pod/perlfaq8.pod:=head2 Why doesn't my sockets program work
under System V (Solaris)? What does the error message "Protocol not supported"
mean?
./gnu/usr.bin/perl/pod/perltoc.pod:does the error message "Protocol not
supported" mean?
./lib/libc/gen/errlist.c: "Protocol not supported", /* 43 -
EPROTONOSUPPORT */
./lib/libc/nls/C.msg:43 Protocol not supported
./lib/libc/sys/intro.2:.It Er 43 EPROTONOSUPPORT Em "Protocol not supported" .
./libexec/ftp-proxy/ftp-proxy.c: "522 Protocol not
supported, use (1)\r\n");
./libexec/ftp-proxy/ftp-proxy.c: "501 Protocol not
supported\r\n");
./libexec/ftpd/ftpd.c: epsv_protounsupp("Protocol not supported");
./libexec/ftpd/ftpd.c: * 522 Protocol not supported (proto,...)
./sys/sys/errno.h:#define EPROTONOSUPPORT 43 /* Protocol not
supported */
./usr.sbin/route6d/route6d.c: /* Protocol not supported */
./usr.sbin/route6d/route6d.c: /* Protocol not supported */
----
so that is looking like nothing that has in specific to
to with NFS... <shrug>
on a whim, i tried mounting a remote nfs partition onto
a local dir with a '.' in it, but that worked ok for v2/v3.
> thought should be done. And just in case this is the exports on the
> Linux machine:
>
> /export 192.168.0.2(rw,no_wdelay,no_subtree_check,sync)
this probably doesn't matter, but what if you just change the
options to be a simple (rw) or (ro)? perhaps those options
only apply on the server side and are therefore not communicated
over to the 192.168.0.3 client, but .. ?
any chance of making the linux allow nfs v3 and trying that,
if only to see if you get the same error?
jared
-
[ openbsd 3.7 GENERIC ( jun 10 ) // i386 ]
