From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@9fans.net
Subject: Re: [9fans] Can't "mk CONF=9pcdisk" --> gives error
Date: Thu, 19 Jul 2012 13:21:04 -0400 [thread overview]
Message-ID: <c0f0187d210e309e5d11984e9982078a@ladd.quanstro.net> (raw)
In-Reply-To: <CAL4LZyhADVbrwhAE2c4xmhwLhZyng8VhbWUkZNAepL17G_u9GA@mail.gmail.c>
> 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
next prev parent reply other threads:[~2012-07-19 17:21 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-19 9:07 [9fans] Can't "mk CONF=9pcdisk" --> gives error "rc: #d/0: kalaracey
2012-07-19 9:16 ` Federico Benavento
2012-07-19 14:25 ` [9fans] Can't "mk CONF=9pcdisk" --> gives error Kyle Laracey
2012-07-19 9:17 ` [9fans] Can't "mk CONF=9pcdisk" --> gives error "rc: #d/0: Charles Forsyth
2012-07-19 14:25 ` [9fans] Can't "mk CONF=9pcdisk" --> gives error Kyle Laracey
2012-07-19 16:59 ` John Floren
[not found] ` <CAL4LZyhADVbrwhAE2c4xmhwLhZyng8VhbWUkZNAepL17G_u9GA@mail.gmail.c>
2012-07-19 17:21 ` erik quanstrom [this message]
2012-07-19 17:48 ` John Floren
2012-07-19 9:20 ` [9fans] Can't "mk CONF=9pcdisk" --> gives error "rc: #d/0: David du Colombier
2012-07-23 8:32 ` [9fans] Can't "mk CONF=9pcdisk" --> gives error Kyle Laracey
2012-07-23 11:14 ` hiro
2012-07-23 12:32 ` Matthew Veety
2012-07-23 12:29 ` mveety
2012-07-23 16:42 ` John Floren
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=c0f0187d210e309e5d11984e9982078a@ladd.quanstro.net \
--to=quanstro@quanstro.net \
--cc=9fans@9fans.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).