From: Joshua Wood <josh@utopian.net>
To: 9fans@cse.psu.edu
Subject: RE: [9fans] Venti config for booting from fs(3)
Date: Thu, 15 Nov 2007 17:10:46 -0800 [thread overview]
Message-ID: <0C23F343-DE66-4749-B798-4AD966035999@utopian.net> (raw)
> • The venti would be used for the fossil boot partition, so needs to
> be there at startup. fs(3) suggests sticking the config on a floppy
> (!). This seems like not the most reliable option. Where are others
> sticking their fs(3) configs for boot?
The wiki page for mirroring under venti and fossil:
http://plan9.bell-labs.com/wiki/plan9/
Mirroring_with_Fossil_and_Venti/index.html
Suggests storing the fs config in an 'fscfg' parition on the local
(hard) disk, similar to the conf headers for venti or fossil themselves.
> • Once there's an fsconfig var, how does the rest of the
> startup go?
> I don't see it pulling that in anywhere. This needs to be well before
> cpurc, right? Will this require a custom boot?
And then one can set 'fsonfig=' in plan9.ini to the partition created
above to start devfs with it at boot.
The rest of your questions I'm experimenting with myself & am very
interested in the experience of others and yours; I do know Russ Cox
has some informative comments about venti and fossil caching (in
memory) at the end of the venti-rescue paper. The big hint for a
single-machine fossil+venti, I thought, is that fossil caches venti
blocks, too.
--
Josh
next reply other threads:[~2007-11-16 1:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-16 1:10 Joshua Wood [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-11-16 0:38 Anthony Sorace
2007-11-16 1:11 ` erik quanstrom
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=0C23F343-DE66-4749-B798-4AD966035999@utopian.net \
--to=josh@utopian.net \
--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).