[Bug 10191] dd with conv=fsync after dba0dc1999bb1e8bfe64607e2a9385cda361fcb7 no longer works as expected

bugzilla at busybox.net bugzilla at busybox.net
Wed Aug 9 11:24:03 UTC 2017


--- Comment #4 from Denys Vlasenko <vda.linux at googlemail.com> ---
(In reply to Neil MacLeod from comment #3)
> If necessary we'll just continue to revert this change, although I'd argue that changing the behaviour of dd like this (and at this stage for what seems like a marginal benefit) may not be the best idea

I respectfully disagree. In the long term, importance of not fragmenting Linux
world into many slightly incompatible niches is more important than having one
or the other incompatible feature which happens to suit some particular need
better than "standard" behavior. (I use "standard" loosely here. Basically, for
bbox, "standard" is usually what the same-named tool in popular Linux distros
is doing).

You can petition coreutils to change "fsync", or add a new flag
("fsync_block"?). Then bbox copies that feature.

You can find another way to achieve what you want, with other tools/options.
For example, maybe running "fsync FILE" (we have this as applet) or "sync" in
another process forces writes out, so you can reliably see file size?

You are receiving this mail because:
You are on the CC list for the bug.

More information about the busybox-cvs mailing list