Date: Wed, 7 Apr 2004 17:09:28 -0500
From: Andy Isaacson <adi@hexapodia.org>
To: bug-coreutils@gnu.org, linux-kernel@vger.kernel.org
Subject: Re: dd PATCH: add conv=direct
Message-ID: <20040407220928.GI2814@hexapodia.org>
References: <20040406220358.GE4828@hexapodia.org> <20040407220224.GA26850@sgi.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20040407220224.GA26850@sgi.com>
User-Agent: Mutt/1.4.1i
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1005
Lines: 26

On Wed, Apr 07, 2004 at 05:02:24PM -0500, Nathan Straz wrote:
> On Tue, Apr 06, 2004 at 05:03:58PM -0500, Andy Isaacson wrote:
> > Linux-kernel:  is this patch horribly wrong?
> ...
> > to force O_DIRECT.  The enclosed patch adds a "conv=direct" flag to
> > enable this usage.
> 
> Adding the functionality to conv= doesn't seem right to me.  conv= is
> for converting the data in some way.  This is just changing the way data
> is written.  Right?

There's already conv=notrunc which means "open without O_TRUNC".  I
agree that it's a nonintuitive interface, but then, the entire dd(1)
command line is.

> Have you looked at lmdd?  It supports O_DIRECT and many other things not
> in the standard dd.

Wasn't aware of that one.  Thanks for the pointer.

-andy
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/