9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Gregory Pavelcak <g.pavelcak@comcast.net>
To: 9fans@cse.psu.edu
Subject: [9fans] Interleaved Fossil Install
Date: Tue, 11 Oct 2005 06:22:30 -0400	[thread overview]
Message-ID: <75c6c1561b499a639f93ec8ee5ea227a@comcast.net> (raw)

I have three small scsi drives and two 100G IDE drives.
I was thinking about doing a fresh install onto a single
machine making an interleaved fossil on the scsi drives
and using the ide for venti. Does this make sense? If it does,
what is the proper order of operations? Do I partdisk, prepdisk,
then interleave the fossils generated in prep? Or do I create
the interleaved filesystem first and prep that?

I've been trying to sort this out from a combination of
installation instructions and the using mirrors with fossil
wiki, but I'm still not sure how to incorporate fs(3) into
the installation.

Thanks.

Greg


                 reply	other threads:[~2005-10-11 10:22 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=75c6c1561b499a639f93ec8ee5ea227a@comcast.net \
    --to=g.pavelcak@comcast.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).