From: <vmendez@inf.uc3m.es>
To: linux-fsdevel@vger.kernel.org
Subject: FiST & unionfs
Date: Thu, 6 Feb 2003 13:27:56 +0100 (CET) [thread overview]
Message-ID: <7793518467vmendez@inf.uc3m.es> (raw)
Hello everybody,
let me introduce myself, I'm new on this mailing list and I am involved
in a parallel file system based on NFS development, calls eXpand:
http://arcos.inf.uc3m.es/~xpn/
in the framework of my MD research at the "Universidad Carlos III de
Madrid", Spain.
My target is to get the eXpand client library into the kernel, mainly to
increase performances reagarding with the kernell proccess runtime.
Due to the lack of portabilty issues I have been studing FiST for
stacking the eXpand, and I am interested in the prototype unionfs for
linux. Erez told me that the unionfs wasn't stable enoug to release,
anyway I would like to know full sintax and semantic of fan-out with
FiST, and I don't mind to much if after I have to work with the fist
compile code in C.
¿My anyone help me in someway?
Many thanks.
Regards.
-
To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
reply other threads:[~2003-02-06 12:27 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=7793518467vmendez@inf.uc3m.es \
--to=vmendez@inf.uc3m.es \
--cc=linux-fsdevel@vger.kernel.org \
/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).