From mboxrd@z Thu Jan 1 00:00:00 1970 MIME-Version: 1.0 In-Reply-To: <6fe792a6937e8e23ab679036748b5cd7@brasstown.quanstro.net> References: <3c03af7d31e57a9359d2aade038dd88b@vitanuova.com> <6382a3fce81dc84bf423fa25fca25da9@ladd.quanstro.net> <6fe792a6937e8e23ab679036748b5cd7@brasstown.quanstro.net> Date: Tue, 16 Nov 2010 12:12:19 +0000 Message-ID: From: roger peppe To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Subject: Re: [9fans] 9p vs http Topicbox-Message-UUID: 82901a80-ead6-11e9-9d60-3106f5b1d025 On 16 November 2010 01:18, erik quanstrom wrote: >> > i claim that a fs with this behavior would be broken. =C2=A0intro(5) >> > seems to agree with this claim, unless i'm misreading. >> >> you're right - fossil is broken in this respect, as is exportfs >> {cd /mnt/term/dev; ls -lq | sort} for a quick demo. > > so what's fossil's excuse? i'd say it's a bug. fossil could easily reserve some number of bits of the qid (say 20 bits) to make the files in the dump unique while still allowing space for a sufficient number of live files. that doesn't invalidate my original point though.