9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Heiko Dudzus <heiko.dudzus@gmx.de>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Fossil on devfs
Date: Sat, 26 Nov 2005 14:30:57 +0100	[thread overview]
Message-ID: <ece7638b742808bc3f9d62060761d2a7@voidness.de> (raw)
In-Reply-To: <14ec7b180511221137r6a477866pe2dcf7adfcddc83@mail.gmail.com>

Andrey Mirtchovski wrote:
> here's what i have:
> 
> plan9.ini:
> fsconfig=/dev/sdC0/fscfg
> bootargs=local!#S/sdC0/fossil

Ok. That was it. Thanks.

> fscfg:
> # cat /dev/sdC0/fscfg
> fsdev:
> mirror fossil /dev/sdC0/fossil /dev/sdD0/fossil
> mirror isect /dev/sdC0/isect /dev/sdD0/isect
> mirror arenas /dev/sdC0/arenas /dev/sdD0/arenas
> mirror nvram /dev/sdC0/nvram /dev/sdD0/nvram

What's the point of having /dev/fs/nvram?  To be more specific: I do
see the point of having to copies of the nvram partition.  But out of
curiosity: where do you reference /dev/fs/nvram when using the system?

Isn't /dev/sdC0/9fat worth to be mirrored with devfs?

Heiko



  reply	other threads:[~2005-11-26 13:30 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-22 19:27 Heiko Dudzus
2005-11-22 19:37 ` Christoph Lohmann
2005-11-22 20:23   ` Russ Cox
2005-11-22 19:37 ` andrey mirtchovski
2005-11-26 13:30   ` Heiko Dudzus [this message]
2005-11-26 13:55     ` andrey mirtchovski
2005-11-26 14:34       ` Christoph Lohmann
2005-11-26 14:42         ` andrey mirtchovski
2005-11-26 17:55       ` Heiko Dudzus
2005-11-27  0:54         ` Russ Cox
2005-11-27  0:55           ` Russ Cox
2006-02-02 20:51 ` Tharaneedharan Vilwanathan
2006-02-02 23:20   ` Steve Simon
2006-02-03  0:18     ` Micah Stetson
2006-02-03  9:10       ` Tharaneedharan Vilwanathan
2006-02-03 18:21         ` Heiko Dudzus
2006-02-04 15:28           ` Tharaneedharan Vilwanathan
2006-02-04 12:25         ` Steve Simon

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=ece7638b742808bc3f9d62060761d2a7@voidness.de \
    --to=heiko.dudzus@gmx.de \
    --cc=9fans@cse.psu.edu \
    /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).