From: Ric Wheeler <rwheeler@redhat.com>
To: Olaf van der Spek <olafvdspek@gmail.com>
Cc: "Ted Ts'o" <tytso@mit.edu>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>,
linux-ext4@vger.kernel.org
Subject: Re: Atomic file data replace API
Date: Tue, 28 Dec 2010 17:36:19 -0500 [thread overview]
Message-ID: <4D1A6663.8000307@redhat.com> (raw)
In-Reply-To: <AANLkTimKy7+cYfPKKywS3FvaJMt2OYApYY8dR81uGHTN@mail.gmail.com>
On 12/28/2010 05:25 PM, Olaf van der Spek wrote:
> On Tue, Dec 28, 2010 at 8:06 PM, Ric Wheeler<rwheeler@redhat.com> wrote:
>> I really think that you have missed the point of this list.
>>
>> This list is for either developers (those who have downloaded the free code
>> and work on it) or others who want to move things forward concretely.
> Maybe.
>
>> Perfectly fine to contribute ideas, but if you are not a coder or do not
>> have the time or inclination to work on things yourself, you have to be
>> *really* convincing.
>>
>> We continually get bombarded with ideas, wish list items, etc so we are not
>> lacking in work to do.
> I understand.
>
>> If you cannot explain the use case, you will not get any buy in...
> I assumed that preserving file owner would be a normal feature and
> would not require additional explanation.
> One use case would be updating a file in a save way when you have
> write access to that file but not to anything else.
>
> Also, according to Ted, a lot of app devs get saving a file in a safe
> way wrong. So I'm asking what the recommended way to do it is. Is that
> strange?
>
> Olaf
I think that various developers have answered this for you several times.
As a suggestion, if you are not a kernel developer, show us specifically a bit
of application code that demonstrates something that you want to have work
differently.
Test it with power failure (buy an external e-sata or USB disk and pull power
while running your app).
Ric
next prev parent reply other threads:[~2010-12-28 22:36 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-27 11:51 Atomic file data replace API Olaf van der Spek
2010-12-27 13:20 ` Amir Goldstein
2010-12-27 15:53 ` Olaf van der Spek
2010-12-27 17:20 ` Amir Goldstein
2010-12-27 18:34 ` Olaf van der Spek
2010-12-28 2:59 ` Ted Ts'o
2010-12-28 17:27 ` Olaf van der Spek
2010-12-28 19:06 ` Ric Wheeler
2010-12-28 22:25 ` Olaf van der Spek
2010-12-28 22:36 ` Ric Wheeler [this message]
2010-12-28 22:58 ` Olaf van der Spek
2010-12-29 9:20 ` Amir Goldstein
2010-12-29 12:42 ` Olaf van der Spek
2010-12-29 15:30 ` Christian Stroetmann
2010-12-29 15:35 ` Olaf van der Spek
2010-12-29 16:30 ` Christian Stroetmann
2010-12-29 17:12 ` Olaf van der Spek
2010-12-29 17:15 ` Greg Freemyer
2010-12-29 19:30 ` Christian Stroetmann
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=4D1A6663.8000307@redhat.com \
--to=rwheeler@redhat.com \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=olafvdspek@gmail.com \
--cc=tytso@mit.edu \
/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).