From: Richard Miller <9fans@hamnavoe.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Plan 9 not recognizing Xen extended disk image
Date: Mon, 28 May 2007 20:15:06 +0100 [thread overview]
Message-ID: <d539dcfb3a928823adc5aaea37ef3ac4@hamnavoe.com> (raw)
In-Reply-To: <228a56b60705280912j4a51ccbcwe0b37f57d17a1ebe@mail.gmail.com>
> I do not want to reinstall Plan 9 and reconfigure it if possible, as
> it is hard for me to find a full free day to do that.
The fossil fs is not designed to be resized dynamically.
If you don't want to backup and reinstall, and you have enough
physical disk space to hold (temporarily) two disk images, you
could create a new disk image and restart plan 9 with both old
and new image attached, format the new fossil, and copy your
files from the old fossil to the new.
Are you using venti as well as fossil? In that case, it would be
the data in venti that you need to copy from old new new image,
and then you can just initialise the fossil with the venti score.
prev parent reply other threads:[~2007-05-28 19:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-28 0:34 Eric Boston
2007-05-28 9:17 ` Richard Miller
2007-05-28 16:12 ` Eric Boston
2007-05-28 19:15 ` Richard Miller [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=d539dcfb3a928823adc5aaea37ef3ac4@hamnavoe.com \
--to=9fans@hamnavoe.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).