9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Skip Tavakkolian <9nut@9netics.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] repartitioning
Date: Sat, 30 Jun 2007 00:35:30 -0700	[thread overview]
Message-ID: <02fdc19c6c35e4c5ecfd99f7b4e92a08@9netics.com> (raw)
In-Reply-To: <615a97c12583e1c44977db4886362d8d@csplan9.rit.edu>

> When I wanted cfs, I just added another virtual hard drive (about 200
> megabytes) and formatted that from within Plan 9. Works just fine!
> Perhaps there is a specific reason you want to use the same disk,
> but I think my method will save some hassle.

that's a better idea.  thanks.  that thought had occurred to me, but it
came in a fleeting moment of clarity between my cat's interruptions
and the call to dinner; i promptly forgot it :)



      reply	other threads:[~2007-06-30  7:35 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-30  3:55 Skip Tavakkolian
2007-06-29 22:11 ` john
2007-06-30  7:35   ` Skip Tavakkolian [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=02fdc19c6c35e4c5ecfd99f7b4e92a08@9netics.com \
    --to=9nut@9netics.com \
    --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).