From mboxrd@z Thu Jan  1 00:00:00 1970
References: <4638ff903fe76813f3aaa6f6502bb2ef@hamnavoe.com>
	<055019189f9c99ade0a2884377823d8c@brasstown.quanstro.net>
	<20120819110400.1eec7f20@zinc.9fans.fr>
	<0e628d91647d479baf567e8cccd11f49@brasstown.quanstro.net>
In-Reply-To: <0e628d91647d479baf567e8cccd11f49@brasstown.quanstro.net>
Mime-Version: 1.0 (1.0)
Content-Type: text/plain;
	charset=us-ascii
Message-Id: <53A5515B-A4F0-4006-A8F5-70990D854D59@bitblocks.com>
Content-Transfer-Encoding: 7bit
From: Bakul Shah <bakul@bitblocks.com>
Date: Sun, 19 Aug 2012 09:06:13 -0700
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] fossil option -m
Topicbox-Message-UUID: ac73c864-ead7-11e9-9d60-3106f5b1d025

On Aug 19, 2012, at 8:04 AM, erik quanstrom <quanstro@quanstro.net> wrote:

> On Sun Aug 19 05:06:03 EDT 2012, 0intro@gmail.com wrote:
>>> let's make it "fsmb".  that way we need not enumerate file servers.
>>
>> Just wondering. How do you distinguish between Fossil
>> and Venti, when they are running on the same machine?
>> They have very different memory requirement.
>
> i retracted this suggestion yesterday.  not only for the reason you
> point out, but also because if we generalize the kfs, fossil code
> to bootlocalfses, $($fsname)mb seems the obvious choice.

What's mb? Milli bits?