From: Ben Martin <monkeyiq@users.sourceforge.net>
To: Edward Shishkin <edward@namesys.com>
Cc: reiserfs-list@namesys.com
Subject: Re: Selecting unixfile plugin
Date: Mon, 05 Jun 2006 19:35:55 +1000 [thread overview]
Message-ID: <1149500156.3926.63.camel@sam> (raw)
In-Reply-To: <4483F791.7020608@namesys.com>
[-- Attachment #1: Type: text/plain, Size: 553 bytes --]
[snip]
>
> Yes, it is. Although this stuff should be qualified as experimental.
> If you have spare disk space and another box with serial connection,
> then we will send you the setup..
>
> Edward.
Cool. I'm looking forward to playing around with it. Hopefully I can
tailor the instructions to work with Xen or a filesystem mounted on
loopback (what I have at current) so the "spare machine" is somewhat
protected from the worst case.
I could generate the setup of scratch machine and serial connection if
this is required though.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
prev parent reply other threads:[~2006-06-05 9:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-05 7:06 Selecting unixfile plugin Ben Martin
2006-06-05 9:21 ` Edward Shishkin
2006-06-05 9:35 ` Ben Martin [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=1149500156.3926.63.camel@sam \
--to=monkeyiq@users.sourceforge.net \
--cc=edward@namesys.com \
--cc=reiserfs-list@namesys.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.