From owner-freebsd-current Tue Jun 18 00:06:35 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id AAA05408 for current-outgoing; Tue, 18 Jun 1996 00:06:35 -0700 (PDT) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id AAA05403 for ; Tue, 18 Jun 1996 00:06:30 -0700 (PDT) Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.12/8.6.9) id QAA13025; Tue, 18 Jun 1996 16:58:09 +1000 Date: Tue, 18 Jun 1996 16:58:09 +1000 From: Bruce Evans Message-Id: <199606180658.QAA13025@godzilla.zeta.org.au> To: freebsd-current@freebsd.org, tony@fit.qut.edu.au Subject: Re: Bug in NFS Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > Hi there, I think I have found a bug in the 2.2-current nfs code. I am > exporting the /dev directory to a client but it seem that the minor > number of the devices are changed across the nfs mount. > On the server: > brw-r----- 1 root operator 0, 0x00010002 Jun 19 00:32 /dev/wd0 > On the client: > brw-r----- 1 root operator 0, 2 Jun 19 00:32 /dev/wd0 NFS only supports 16-bit device numbers so it can't possibly preserve 32-bit device numbers if the high bits are actually used. This is the problem here. More fundamentally, device numbers aren't portable across OS's, so they shouldn't be exported. Bruce