From mboxrd@z Thu Jan  1 00:00:00 1970
From: erik quanstrom <quanstro@quanstro.net>
Date: Sat, 18 Aug 2012 10:57:45 -0400
To: 9fans@9fans.net
Message-ID: <0d222a32d99cd6e44274c7ca2367d08d@brasstown.quanstro.net>
In-Reply-To: <5FF01BA4-294A-4EEA-AED9-BBECF6A67642@ar.aichi-u.ac.jp>
References: <CD4608E2-13AB-4532-8A99-83862C4A20BE@ar.aichi-u.ac.jp>
	<37d8ce422508d964daf7dbff83dd3b82@brasstown.quanstro.net>
	<CAL4LZyimqPZVQGmTDXzKBJsJNUaLsCEQBZz4qY8YSCb7pMkypA@mail.gmail.com>
	<5FF01BA4-294A-4EEA-AED9-BBECF6A67642@ar.aichi-u.ac.jp>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Subject: Re: [9fans] fossil option -m
Topicbox-Message-UUID: abb72fba-ead7-11e9-9d60-3106f5b1d025

> I have looked contents in /boot/bootfs.paq of 9front.
> I like the booting process: flexible, elegant and probably powerful.

it's another stage of bootloading which requires a number of things to be built-in
to the kernel.  in this sense, it's like initrd.

if we were to instead make the local file servers (fossil+venti, kfs, cwfs, etc.)
idiomatic enough in their arguments, it should be easy enough to drive them
with the same boot code, that needn't bloat the kernel, or require fancy
memory reclaim.

also,

> let's make it "fsmb".  that way we need not enumerate file servers.
> i've always found listing things in mb is easier to work out.

i take it back.  $fsname^mb is idiomatic enough to automate.
sorry for the noise.

- erik