Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S262410AbTE0A13 (ORCPT ); Mon, 26 May 2003 20:27:29 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S262412AbTE0A13 (ORCPT ); Mon, 26 May 2003 20:27:29 -0400 Received: from pc2-cwma1-4-cust86.swan.cable.ntl.com ([213.105.254.86]:6860 "EHLO lxorguk.ukuu.org.uk") by vger.kernel.org with ESMTP id S262410AbTE0A12 (ORCPT ); Mon, 26 May 2003 20:27:28 -0400 Subject: Re: [patch?] truncate and timestamps From: Alan Cox To: viro@parcelfarce.linux.theplanet.co.uk Cc: Linus Torvalds , Andries.Brouwer@cwi.nl, akpm@digeo.com, Linux Kernel Mailing List In-Reply-To: <20030523011751.GC14406@parcelfarce.linux.theplanet.co.uk> References: <20030523011751.GC14406@parcelfarce.linux.theplanet.co.uk> Content-Type: text/plain Content-Transfer-Encoding: 7bit Organization: Message-Id: <1053992553.17151.18.camel@dhcp22.swansea.linux.org.uk> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.2.2 (1.2.2-5) Date: 27 May 2003 00:42:35 +0100 Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 944 Lines: 21 On Gwe, 2003-05-23 at 02:17, viro@parcelfarce.linux.theplanet.co.uk wrote: > Andries had shown that there is _no_ consensus. Ergo, POSIX can take > a hike and we should go with the behaviour convenient for us. It's that > simple... Skipping the update on a truncate not changing size is a performance win although not a very useful one. I don't think we can ignore the standard however. For one it simply means all the vendors have to fix it so they can sell to Government etc. Now we can certainly put the fix in -every- vendor tree on the planet and not base, I'm just not sure for something so trivial it isnt better just to fix it to the spec *or* beat the spec authors up to fix the spec. - 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/