From: David Woodhouse <dwmw2@infradead.org>
To: Eli Carter <eli.carter@inet.com>
Cc: linux-fsdevel@vger.kernel.org
Subject: Re: File perforation.
Date: Wed, 08 Jan 2003 22:34:44 +0000 [thread overview]
Message-ID: <22288.1042065284@passion.cambridge.redhat.com> (raw)
In-Reply-To: <3E1CA628.7000002@inet.com>
eli.carter@inet.com said:
> Could you elaborate on the difference between what you want to do and
> sparse files?
No difference. Given a non-sparse file, I want a way to make it sparse.
Well, I _have_ a way to make it sparse; all I have to do is write out a
single log entry. What I am lacking is a way for the user to tell me to do
so :)
I'm aware that you can do this by deleting the file and writing out a new
copy. But this is flash and it has a limited number of write cycles; I don't
want to do that.
--
dwmw2
next prev parent reply other threads:[~2003-01-08 22:34 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-08 22:06 File perforation David Woodhouse
2003-01-08 22:28 ` Eli Carter
2003-01-08 22:34 ` David Woodhouse [this message]
2003-01-08 22:56 ` Eli Carter
2003-01-08 23:14 ` David Woodhouse
2003-01-09 1:22 ` Andrew Morton
2003-01-09 3:23 ` Andreas Dilger
2003-01-08 23:17 ` Steven Whitehouse
2003-01-08 23:16 ` David Woodhouse
2003-01-08 23:36 ` Steven Whitehouse
2003-01-08 23:25 ` David Woodhouse
2003-01-10 1:39 ` Bryan Henderson
2003-01-08 22:45 ` Dave Kleikamp
2003-01-08 22:55 ` Matthew Wilcox
2003-01-08 23:02 ` David Woodhouse
2003-01-11 9:47 ` Christoph Hellwig
2003-01-10 1:34 ` Bryan Henderson
-- strict thread matches above, loose matches on Subject: below --
2003-01-10 22:24 Steven French
2003-01-11 1:46 ` Bryan Henderson
2003-01-13 3:52 Steven French
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=22288.1042065284@passion.cambridge.redhat.com \
--to=dwmw2@infradead.org \
--cc=eli.carter@inet.com \
--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