Package: klibc-utils
Version: 1.4.34-1
Trying to run nfsmount, I get the following errors:
nfsmount -o ro,nolock server:/foo /mnt
socket: Protocol not supported
socket: Protocol not supported
NFS over TCP not available from server
Using strace, I see the following:
execve("nfsmount", ["nfsmount", "-o", "ro,nolock", "server:/foo", "/mnt"], [/*
13 vars */]) = 0
svr4_syscall() = 4078
svr4_syscall() = -1 ERRNO_4210 (Unknown error 4210)
stat64(0x7ff0fee7, 0x7ff0fd08) = 0
socket(PF_INET, SOCK_DGRAM, IPPROTO_TCP) = -1 EPROTONOSUPPORT (Protocol not
supported)
write(2, "socket: Protocol not supported\n", 31) = 31
socket(PF_INET, SOCK_STREAM, IPPROTO_UDP) = -1 EPROTONOSUPPORT (Protocol not
supported)
write(2, "socket: Protocol not supported\n", 31) = 31
write(2, "NFS over TCP not available from "..., 41) = 41
exit(1) = ?
These two calls got my attention:
socket(PF_INET, SOCK_DGRAM, IPPROTO_TCP)
socket(PF_INET, SOCK_STREAM, IPPROTO_UDP)
/usr/include on a mipsel box shows the following:
/usr/include/asm/socket.h: * @SOCK_DGRAM - datagram (conn.less) socket
/usr/include/asm/socket.h: SOCK_DGRAM = 1,
/usr/include/linux/net.h: * @SOCK_DGRAM: datagram (conn.less) socket
/usr/include/linux/net.h: SOCK_DGRAM = 2,
/usr/include/linux/irda.h:/* Protocol types to be used for SOCK_DGRAM */
/usr/include/bits/socket.h: SOCK_DGRAM = 1, /* Connectionless,
unreliable datagrams
/usr/include/bits/socket.h:#define SOCK_DGRAM SOCK_DGRAM
the klibc source package also defines SOCK_DGRAM as 2 in
usr/include/sys/socket.h
I am using unmodified packages from etch.
I'm not sure what's wrong, it looks like linux-kernel-headers on
mipsel has inconsistent definitions for the socket types, but somehow
this does not seem to affect non-klibc-based applications... Probably
the issue is that klibc's usr/include/sys/socket.h needs to present
different values on mipsel (i.e. SOCK_DGRAM = 1 in that case).
--
Michel "Walken" Lespinasse
"Bill Gates is a monocle and a Persian cat away from being the villain
in a James Bond movie." -- Dennis Miller
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
