From: John Floren <john@jfloren.net>
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 09:42:46 -0700 [thread overview]
Message-ID: <CAL4LZygF82O10bwj-1KYquno9NmNni4tOBJ7xS+jqikZs=-e7Q@mail.gmail.com> (raw)
In-Reply-To: <0e3439c1-dcf2-49e8-bbd1-db0605edcc70@googlegroups.com>
On Mon, Jul 23, 2012 at 1:32 AM, Kyle Laracey <kalaracey@gmail.com> 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 <quanstro@quanstro.net> wrote:
>> >> 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
>> >
>>
>> There's certainly reasons for using kfs, but for a new user I'd
>> probably recommend fossil simply because the documentation and most
>> 9fans will assume you're using fossil.
>>
>> But yeah, *best* option is to netboot a 9pc kernel, it's lovely to
>> just hit the power button when you'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...
>
Here at work, we've got a cpu/auth/file server running fossil and
venti off a Coraid storage appliance, sitting in the machine room. We
netboot some terminals and a 32-core test server from it.
At home, I've got a cpu/auth/file server running on an old Thinkpad,
but I generally just drawterm in since 1. it's a hassle to plug
yourself into the wired network and 2. I rarely have a netbootable
terminal at home.
Netbooting is great, though. You can also cheat and install Plan 9 on
the disk, but then specify that root is from a remote server, meaning
your kernel will boot from the hard drive but after bootup it's
basically idle.
John
prev parent reply other threads:[~2012-07-23 16:42 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
2012-07-23 16:42 ` John Floren [this message]
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='CAL4LZygF82O10bwj-1KYquno9NmNni4tOBJ7xS+jqikZs=-e7Q@mail.gmail.com' \
--to=john@jfloren.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).