From: Artem Bityutskiy <dedekind@infradead.org>
To: Jamie Lokier <jamie@shareable.org>
Cc: linux-mtd@lists.infradead.org, tommy <jiujin.hong@mid-fun.com>,
Corentin Chary <corentin.chary@gmail.com>
Subject: Re: about ubifs
Date: Mon, 08 Jun 2009 16:30:28 +0300 [thread overview]
Message-ID: <1244467828.5847.362.camel@localhost.localdomain> (raw)
In-Reply-To: <20090608122934.GG25684@shareable.org>
On Mon, 2009-06-08 at 13:29 +0100, Jamie Lokier wrote:
> Artem Bityutskiy wrote:
> > On Mon, 2009-06-08 at 13:01 +0100, Jamie Lokier wrote:
> > > I was thinking both sync-on-close and sync-on-close-after-truncate
> > > would be most useful as _generic_ mount options, in the same way that
> > > O_SYNC has generic filesystem support these days.
> >
> > May be. On the other hand this would kill any remote possibility of
> > having user-space fixed :-)
>
> My point was that "fixing" user-space by requiring every shell script
> to run a special (currently non-existing) fsync program after every
> thing it does which modifies a file (virtually every shell command)
> which has an ordered relationship with other files is stupid.
> It's fine for C programs to call fsync() (e.g. I'm good about doing
> that) even though it's sometimes breaks performance, but it's
> unhelpful to sprinkle every other line in every shell script with it,
> as it would defeat the point of shell scripts which is simplicity.
Not necessarily. Shell scripts may always just re-create their
files every time. Or re-create them if they are empty. Or for
large files use /bin/sync. Or even a /bin/fsync program can be
created.
But yes, I see what you mean, of course.
--
Best regards,
Artem Bityutskiy (Битюцкий Артём)
next prev parent reply other threads:[~2009-06-08 13:30 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-05 12:13 about ubifs tommy
2009-06-05 12:42 ` Corentin Chary
2009-06-05 13:03 ` tommy
2009-06-05 14:04 ` Corentin Chary
2009-06-08 1:35 ` Jamie Lokier
2009-06-08 1:52 ` tommy
2009-06-08 5:49 ` Artem Bityutskiy
2009-06-08 12:01 ` Jamie Lokier
2009-06-08 12:16 ` Artem Bityutskiy
2009-06-08 12:29 ` Jamie Lokier
2009-06-08 13:30 ` Artem Bityutskiy [this message]
2009-06-05 16:26 ` Artem Bityutskiy
-- strict thread matches above, loose matches on Subject: below --
2008-07-08 9:08 About UBIFS Qiang Wang
2008-07-08 9:08 ` Artem Bityutskiy
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=1244467828.5847.362.camel@localhost.localdomain \
--to=dedekind@infradead.org \
--cc=corentin.chary@gmail.com \
--cc=jamie@shareable.org \
--cc=jiujin.hong@mid-fun.com \
--cc=linux-mtd@lists.infradead.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