Date: Tue, 18 Jun 1996 23:13:17 +0200 (MET DST) From: J Wunsch <j@uriah.heep.sax.de> To: freebsd-current@FreeBSD.org (FreeBSD-current users) Subject: Re: Bug in NFS Message-ID: <199606182113.XAA09482@uriah.heep.sax.de> In-Reply-To: <Pine.HPP.3.92.960618175110.29374I-100000@ice.fit.qut.edu.au> from Tony Jago at "Jun 18, 96 05:56:30 pm"
next in thread | previous in thread | raw e-mail | index | archive | help
As Tony Jago wrote:
> > (The NFS spec seems to use a 32-bit integer to pass the `rdev' field,
> > so it's IMHO not strictly necessary to limit the information.)
> I am using NFSv3 in fact after a bit of testing that seems to be the
> problem!!! If I use NFSv2 then it works fine. I smell a bug....
Oooops. In NFS v3, both the major and the minor number are allowed to
be 32 bits. I assume something has been over-eager in stripping them
down.
specdata3
struct specdata3 {
uint32 specdata1;
uint32 specdata2;
};
The interpretation of the two words depends on the type of file system
object. For a block special (NF3BLK) or character special (NF3CHR)
specdata1 and specdata2 are the major and minor device numbers,
repectively. (This is obviously a UNIX-specific interpretation.) For
all other file types, these two words should either be set to 0 or the
values should be agreed upon by the client and server.
--
cheers, J"org
joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE
Never trust an operating system you don't have sources for. ;-)
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199606182113.XAA09482>