From: Andrew Morton <akpm@osdl.org>
To: Tom Zanussi <zanussi@us.ibm.com>
Cc: linux-kernel@vger.kernel.org, karim@opersys.com
Subject: Re: [PATCH 4/4] relayfs: Documentation for exported relay fileops
Date: Wed, 9 Nov 2005 14:03:36 -0800 [thread overview]
Message-ID: <20051109140336.2d584067.akpm@osdl.org> (raw)
In-Reply-To: <17266.28537.722390.913812@tut.ibm.com>
Tom Zanussi <zanussi@us.ibm.com> wrote:
>
> +By default of course, relay_open() creates relay files in the relayfs
> +filesystem. Because relay_file_operations is exported, however, it's
> +also possible to create and use relay files in other pseudo-filesytems
> +such as debugfs.
Why would anyone wish to place relayfs files within other filesystems?
If users wish relayfs files to appear in other places, is it not sufficient
to do this with mount tricks?
next prev parent reply other threads:[~2005-11-09 22:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-09 21:51 Tom Zanussi
2005-11-09 22:03 ` Andrew Morton [this message]
2005-11-09 22:37 ` Tom Zanussi
2005-11-09 22:46 ` Greg KH
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=20051109140336.2d584067.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=karim@opersys.com \
--cc=linux-kernel@vger.kernel.org \
--cc=zanussi@us.ibm.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®