From owner-cvs-all Tue Feb 20 1:40: 3 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 41AFD37B401; Tue, 20 Feb 2001 01:39:51 -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 UAA08524; Tue, 20 Feb 2001 20:39:47 +1100 Date: Tue, 20 Feb 2001 20:39:15 +1100 (EST) From: Bruce Evans X-Sender: bde@besplex.bde.org To: John Baldwin Cc: "Pierre Y. Dampure" , cvs-all@FreeBSD.org, cvs-committers@FreeBSD.org, Poul-Henning Kamp 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 Mon, 19 Feb 2001, John Baldwin wrote: > about if needed. The current kinfo_proc is now actually worse than before, > because if something changes in teh middle, then all the programs such as > ps(1), top(1) etc. just misparse the information instead of telling you that > proc chagned as they did in the past. Of course, a better way of doing this 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. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message