From owner-freebsd-arch Mon Mar 11 1:48:25 2002 Delivered-To: freebsd-arch@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.86.163]) by hub.freebsd.org (Postfix) with ESMTP id 6266B37B402 for ; Mon, 11 Mar 2002 01:48:22 -0800 (PST) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.12.2/8.12.2) with ESMTP id g2B9lwnp017498; Mon, 11 Mar 2002 10:47:58 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: Harti Brandt Cc: Garance A Drosihn , arch@FreeBSD.ORG Subject: Re: Increasing the size of dev_t and ino_t In-Reply-To: Your message of "Mon, 11 Mar 2002 10:34:55 +0100." <20020311102511.M516-100000@beagle.fokus.gmd.de> Date: Mon, 11 Mar 2002 10:47:58 +0100 Message-ID: <17497.1015840078@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In message <20020311102511.M516-100000@beagle.fokus.gmd.de>, Harti Brandt write s: >There is an explicit requirement in POSIX: it requires a given >st_ino/st_dev pair to uniqely identify a file. I take this to mean: if two >files have the same st_ino/st_dev pair, they are the same file. If I mount >the same volume in different places in the tree any file on that volume >must have the same st_ino/st_dev pair in both mount points. As worded by >POSIX the st_ino/st_dev pairs are not required to be persistant through >reboots. It can, however, be hard to implement persistant file handles for >NFS based on non-persistant st_info/st_dev pairs. (Sorry, I confused st_dev and st_rdev earlier). Ok, I think we are on the same page now. I don't think any of the stuff headed for -current would give you trouble in this respect. Just because we _can_ assign a random st_dev doesn't mean we will shoot ourselves in the foot by doing so :-) And still, I see no pressure to increase the size of (u)dev_t on any platforms. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message