From owner-freebsd-current Tue Jun 18 15:54:29 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id PAA06333 for current-outgoing; Tue, 18 Jun 1996 15:54:29 -0700 (PDT) Received: from palmer.demon.co.uk (palmer.demon.co.uk [158.152.50.150]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id PAA06310 for ; Tue, 18 Jun 1996 15:54:24 -0700 (PDT) Received: from palmer.demon.co.uk (localhost [127.0.0.1]) by palmer.demon.co.uk (sendmail/PALMER-1) with ESMTP id XAA01177; Tue, 18 Jun 1996 23:53:12 +0100 (BST) To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) cc: freebsd-current@FreeBSD.ORG (FreeBSD-current users) From: "Gary Palmer" Subject: Re: Bug in NFS In-reply-to: Your message of "Tue, 18 Jun 1996 23:48:39 +0200." <199606182148.XAA10060@uriah.heep.sax.de> Date: Tue, 18 Jun 1996 23:53:11 +0100 Message-ID: <1175.835138391@palmer.demon.co.uk> Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk J Wunsch wrote in message ID <199606182148.XAA10060@uriah.heep.sax.de>: > As Gary Palmer wrote: > > This is probably because NFS can't handle ``large'' major/minor > > numbers (my guess is that they are truncated down to 8 bits for > > encoding into the structure passed back and forth). Just like you > > can't do 4.4BSD ``flags'' (see chflags(1)) over NFS. > NFSv3 uses 32 bits for the major and minor number, NFSv3 uses 2x32 > bits. I take it one of those is meant to be NFSv2? :-) > (Gee, am i the only one reading the specs before posting? ;-) I read the include file for NFSv2 before posting. Doesn't that count? :-) Gary -- Gary Palmer FreeBSD Core Team Member FreeBSD: Turning PC's into workstations. See http://www.FreeBSD.ORG/ for info