Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S263587AbUCUB2R (ORCPT ); Sat, 20 Mar 2004 20:28:17 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S263588AbUCUB2R (ORCPT ); Sat, 20 Mar 2004 20:28:17 -0500 Received: from gockel.physik3.uni-rostock.de ([139.30.44.16]:1935 "EHLO gockel.physik3.uni-rostock.de") by vger.kernel.org with ESMTP id S263587AbUCUB2Q (ORCPT ); Sat, 20 Mar 2004 20:28:16 -0500 Date: Sun, 21 Mar 2004 02:28:01 +0100 (CET) From: Tim Schmielau To: Robin Holt cc: Ragnar =?iso-8859-1?Q?Kj=F8rstad?= , lkml , Arthur Corliss , Albert Cahalan Subject: Re: [patch,rfc] BSD accounting format rework In-Reply-To: <20040319211457.GA19662@lnx-holt> Message-ID: References: <20040319191916.GQ1066@vestdata.no> <20040319211457.GA19662@lnx-holt> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 912 Lines: 20 On Fri, 19 Mar 2004, Robin Holt wrote: > How about breaking the ac_version structure down as two nibbles? One > half being the major version and the other half being a minor version. > The major version, when changed, means the structure is no longer compatible. > The minor version can be changed when existing fields are not modified > in either form or function. Yes, I also thought about it. But now that we've used up all available padding there is no way of binary compatible changes. And if we allow variable size accounting file entries, we have to store their size anyways. Which would then make an even better version indicator, as Ragnar suggested. Tim - 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/