From: Christoph Hellwig <hch@infradead.org>
To: Erez Zadok <ezk@cs.sunysb.edu>
Cc: linux-fsdevel@vger.kernel.org
Subject: Re: single-file file system?
Date: Fri, 24 Sep 2004 21:44:25 +0100 [thread overview]
Message-ID: <20040924214425.A31697@infradead.org> (raw)
In-Reply-To: <200409242026.i8OKQDVE010037@agora.fsl.cs.sunysb.edu>; from ezk@cs.sunysb.edu on Fri, Sep 24, 2004 at 04:26:13PM -0400
On Fri, Sep 24, 2004 at 04:26:13PM -0400, Erez Zadok wrote:
> I have a need for a very simple f/s that supports only one file on a raw
> device, starting from the beginning of the device and growing until possibly
> its end. The reason for this simple f/s is to minimize the overhead for
> certain applications that don't need more than one large file, but cannot
> use a raw device directly (i.e., they expect a f/s interface). Do you know
> of any f/s that does that for Linux?
We actually have a filesystem that represents blockdevices as single big file
in fs/block_dev.c. It's just not mountable.
prev parent reply other threads:[~2004-09-24 20:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-24 20:26 single-file file system? Erez Zadok
2004-09-24 20:39 ` Andi Kleen
2004-09-24 20:44 ` Christoph Hellwig [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=20040924214425.A31697@infradead.org \
--to=hch@infradead.org \
--cc=ezk@cs.sunysb.edu \
--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).