Re: Automatic deletion of loopback device upon umount?

On Tue, Mar 7, 2017 at 6:12 PM, Mirko Vogt wrote: >> "foo" is a cramfs filesystem file which might help illustrate the issue >> >> 1) loopback mount "foo" to mount /bar >> 2) umount /bar >> 3) append new files and re-generate the "foo" cramfs image >> 4) loopback mount "foo" to

Re: [PATCH] dd: call fsync() only once before exiting if conv=fsync is specified

Hi! On 03/14/2017 06:44 PM, Rostislav Skudnov wrote: Signed-off-by: Rostislav Skudnov It would probably be useful to tell why this change was made: it makes the behavior consistent with coreutils dd and fixes performance problems caused by calling fsync() over and

[PATCH] dd: call fsync() only once before exiting if conv=fsync is specified

Signed-off-by: Rostislav Skudnov --- coreutils/dd.c | 10 +- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/coreutils/dd.c b/coreutils/dd.c index 5e68087..d89c0ae 100644 --- a/coreutils/dd.c +++ b/coreutils/dd.c @@ -532,17 +532,17 @@ int dd_main(int

Re: [PATCH] add paste implementation

On Mon, Mar 13, 2017 at 09:30:56AM -0400, Jody Lee Bruchon wrote: > Given that BusyBox is intended to be as small as possible since it is > targeted at embedded platforms, I'd say that declaring variables inside of a > code block which are used only within a code block is better. Not only does

Re: Problem with cat

On 2017-03-14, Lauri Kasanen wrote: > On Mon, 13 Mar 2017 19:24:17 + (UTC) > Grant Edwards wrote: > >> That paragraph is wrong (or at least misleading). I've checked the >> source code, and 2.6.33 does not update the output file postition (at >> least

Re: Problem with cat

On Mon, 13 Mar 2017 19:24:17 + (UTC) Grant Edwards wrote: > That paragraph is wrong (or at least misleading). I've checked the > source code, and 2.6.33 does not update the output file postition (at > least not the version I downloaded from kernels.org nor the