From owner-cvs-all Tue Feb 20 17:21: 2 2001 Delivered-To: cvs-all@freebsd.org Received: from mailman.zeta.org.au (mailman.zeta.org.au [203.26.10.16]) by hub.freebsd.org (Postfix) with ESMTP id B668D37B491; Tue, 20 Feb 2001 17:20:49 -0800 (PST) (envelope-from bde@zeta.org.au) Received: from bde.zeta.org.au (bde.zeta.org.au [203.2.228.102]) by mailman.zeta.org.au (8.9.3/8.8.7) with ESMTP id MAA09178; Wed, 21 Feb 2001 12:20:46 +1100 Date: Wed, 21 Feb 2001 12:20:13 +1100 (EST) From: Bruce Evans X-Sender: bde@besplex.bde.org To: John Baldwin Cc: Poul-Henning Kamp , cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org, "Pierre Y. Dampure" Subject: Re: cvs commit: src/sys/sys user.h In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-cvs-all@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 20 Feb 2001, John Baldwin wrote: > On 20-Feb-01 Bruce Evans wrote: > > Things in the middle must not change. They must be initialized with whatever > > the used to be, or with dummy values if that is harmless. There would have > > been no problems if this rule were followed for the priority fields. struct > > priority can't be used in struct rusage anyway, since it is a kernel struct. > > Well, it gets more tricky. I've been playing with bumping MAXCOMLEN to 19 (so > it uses a total of 20 rather than 17 chars, which is 32-bit aligned) which > results in expanding teh size of a structure in the middle of kinfo_proc, which > the current kinfo_proc scheme cannot handle. This would also break binary compatibility of ktrace recrords (struct ktr_header). Almost everything that is defined in has some binary compatibility issues. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message