From owner-freebsd-arch Thu Nov 22 12: 6:56 2001 Delivered-To: freebsd-arch@freebsd.org Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.208.78.105]) by hub.freebsd.org (Postfix) with ESMTP id 5EBEF37B405; Thu, 22 Nov 2001 12:06:52 -0800 (PST) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.11.4/8.11.4) id fAMK6p795695; Thu, 22 Nov 2001 12:06:51 -0800 (PST) (envelope-from sgk) Date: Thu, 22 Nov 2001 12:06:51 -0800 From: Steve Kargl To: "Andrew R. Reiter" Cc: Julian Elischer , arch@FreeBSD.org Subject: Re: wine namespace pollution (was Re: Kernel Thread scheduler) Message-ID: <20011122120651.B95507@troutmask.apl.washington.edu> References: <20011121212416.A88350@troutmask.apl.washington.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from arr@FreeBSD.org on Thu, Nov 22, 2001 at 02:42:56PM -0500 Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Thu, Nov 22, 2001 at 02:42:56PM -0500, Andrew R. Reiter wrote: > On Wed, 21 Nov 2001, Steve Kargl wrote: > > : > :[1] Our struct thread in conflicts with the > :struct thread in wine. Fortunately, we can currently work > :around this conflict. > : > > I thought "issue" came up a couple weeks ago and that wine really did not > need to include sys/user.h and therefore the person removed the #include > line and all was well. Is this still the same problem? > Wine fixed this problem a couple days ago. But, if Julian is starting the next round of KSE work, it would be nice to protect kernel internal structures if we can. As pointed out by jhb, struct proc includes struct thread, so consumers (e.g., gdb, ps, ...) of struct proc need be updated. I'm going to play around today to see what needs to be done. -- Steve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message