9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: mveety@gmail.com
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] Can't "mk CONF=9pcdisk" --> gives error
Date: Mon, 23 Jul 2012 08:29:30 -0400	[thread overview]
Message-ID: <2452258.oMu2zgeCdk@as-laptop> (raw)
In-Reply-To: <0e3439c1-dcf2-49e8-bbd1-db0605edcc70@googlegroups.com>

On Monday 23 July 2012 08:32:12 Kyle Laracey wrote:
> On Thursday, July 19, 2012 1:48:06 PM UTC-4, John Floren
wrote:
> > On Thu, Jul 19, 2012 at 10:21 AM, erik quanstrom
> > &lt;quanstro@quanstro.net&gt; wrote: &gt;&gt; But as
Federico mentioned,
> > you might not want pcdisk--that&#39;s for &gt;&gt; running
with a kfs
> > root, which isn&#39;t officially supported any more. If
&gt;&gt; you were
> > looking at the 3e guide, that might explain it. These days,
&gt;&gt; for
> > a terminal, you probably want pcf (pc + fossil).
> > &gt;
> > &gt; for a terminal, ideally one would be booting off a file
server,
> > &gt; and have no local storage.
> > &gt;
> > &gt; but local storage can&#39;t be avoided,
> > &gt; as i see it, on a standalone terminal, simple, speedy,
safe
> > &gt; would trump fs features.  so kfs can&#39;t just be
excluded.
> > &gt;
> > &gt; your tradeoffs may vary.  :-)
> > &gt;
> > &gt; - erik
> > &gt;
> >
> > There&#39;s certainly reasons for using kfs, but for a new
user I&#39;d
> > probably recommend fossil simply because the documentation
and most
> > 9fans will assume you&#39;re using fossil.
> >
> > But yeah, *best* option is to netboot a 9pc kernel, it&#39;s
lovely to
> > just hit the power button when you&#39;re done working.
> >
> >
> > John
>
> Wow so do you guys actually netbook Plan9? Where's the central
> server? where you work / university or something? Or do you
just
> have it set up at your homes? Sounds pretty cool...

My fs/auth server is at my house, and I netboot 9vx off of it
when I need to get real work done. There used to be a server at
RIT that you could do the same thing at, but it doesn't seem to
be online anymore.

--
Veety



  parent reply	other threads:[~2012-07-23 12:29 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
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 [this message]
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=2452258.oMu2zgeCdk@as-laptop \
    --to=mveety@gmail.com \
    --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).