Date: Wed, 29 Nov 2000 16:38:08 -0500 (EST) From: Garrett Wollman <wollman@khavrinen.lcs.mit.edu> To: Garance A Drosihn <drosih@rpi.edu> Cc: cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org Subject: Re: cvs commit: src/usr.sbin/inetd builtins.c Message-ID: <200011292138.QAA19599@khavrinen.lcs.mit.edu> In-Reply-To: <p04330101b64a34131126@[128.113.24.47]> References: <200011270434.eAR4Y7D45315@mobile.wemm.org> <Pine.NEB.3.96L.1001127004343.36087A-100000@fledge.watson.org> <200011271520.KAA94212@khavrinen.lcs.mit.edu> <3A22C835.2D84B426@newsguy.com> <200011272057.PAA96878@khavrinen.lcs.mit.edu> <p04330101b64a34131126@[128.113.24.47]>
next in thread | previous in thread | raw e-mail | index | archive | help
<<On Tue, 28 Nov 2000 23:28:52 -0500, Garance A Drosihn <drosih@rpi.edu> 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200011292138.QAA19599>