From mboxrd@z Thu Jan  1 00:00:00 1970
From: erik quanstrom <quanstro@quanstro.net>
Date: Thu, 19 Jul 2012 13:21:04 -0400
To: 9fans@9fans.net
Message-ID: <c0f0187d210e309e5d11984e9982078a@ladd.quanstro.net>
In-Reply-To: <CAL4LZyhADVbrwhAE2c4xmhwLhZyng8VhbWUkZNAepL17G_u9GA@mail.gmail.c>
References: <1f5637de-024f-48d6-97c7-aba6cf870a7c@googlegroups.com>
	<CAOw7k5iN+fPqfuq0Hg2GzMb2NvtTig92_B_KGrRsO4jvm9oCYA@mail.gmail.com>
	<96703eac-fc2e-4bee-8c0f-a7c5a3ff03d8@googlegroups.com>
	<CAL4LZyhADVbrwhAE2c4xmhwLhZyng8VhbWUkZNAepL17G_u9GA@mail.gmail.c>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Subject: Re: [9fans] Can't "mk CONF=9pcdisk" --> gives error
Topicbox-Message-UUID: a473cdc6-ead7-11e9-9d60-3106f5b1d025

> But as Federico mentioned, you might not want pcdisk--that's for
> running with a kfs root, which isn't officially supported any more. If
> you were looking at the 3e guide, that might explain it. These days,
> for a terminal, you probably want pcf (pc + fossil).

for a terminal, ideally one would be booting off a file server,
and have no local storage.

but local storage can't be avoided,
as i see it, on a standalone terminal, simple, speedy, safe
would trump fs features.  so kfs can't just be excluded.

your tradeoffs may vary.  :-)

- erik