From owner-cvs-all Wed Nov 29 13:38:15 2000 Delivered-To: cvs-all@freebsd.org Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193]) by hub.freebsd.org (Postfix) with ESMTP id C8DB337B401; Wed, 29 Nov 2000 13:38:10 -0800 (PST) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.9.3/8.9.3) id QAA19599; Wed, 29 Nov 2000 16:38:08 -0500 (EST) (envelope-from wollman) Date: Wed, 29 Nov 2000 16:38:08 -0500 (EST) From: Garrett Wollman Message-Id: <200011292138.QAA19599@khavrinen.lcs.mit.edu> To: Garance A Drosihn Cc: cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org Subject: Re: cvs commit: src/usr.sbin/inetd builtins.c In-Reply-To: References: <200011270434.eAR4Y7D45315@mobile.wemm.org> <200011271520.KAA94212@khavrinen.lcs.mit.edu> <3A22C835.2D84B426@newsguy.com> <200011272057.PAA96878@khavrinen.lcs.mit.edu> Sender: owner-cvs-all@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG < said: > Given that there are already distributed file systems which CANNOT > give a unique device+inode pair for a given file (due to the limited > range of the device and inode variables), how can we stick to the > POSIX definition? You have to invent values. I haven't looked recently at the actual requirement; it's possible that a 64-bit hash would work. (I'm not sure if the actual requirement is `distinct files implies distinct numbers' or `same files implies same numbers', and that would make a difference. > Claiming that such a filesystem is "broken" misses the point. Protocol != implementation. -GAWollman To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message