From owner-freebsd-current Sat Jul 14 21:41: 8 2001 Delivered-To: freebsd-current@freebsd.org Received: from mail.rpi.edu (mail.rpi.edu [128.113.22.40]) by hub.freebsd.org (Postfix) with ESMTP id 0AAEC37B403 for ; Sat, 14 Jul 2001 21:41:05 -0700 (PDT) (envelope-from drosih@rpi.edu) Received: from [128.113.24.47] (gilead.acs.rpi.edu [128.113.24.47]) by mail.rpi.edu (8.11.3/8.11.3) with ESMTP id f6F4f3V126924; Sun, 15 Jul 2001 00:41:03 -0400 Mime-Version: 1.0 X-Sender: drosih@mail.rpi.edu Message-Id: In-Reply-To: <200103151610.LAA46410@khavrinen.lcs.mit.edu> References: <200103151610.LAA46410@khavrinen.lcs.mit.edu> Date: Sun, 15 Jul 2001 00:40:59 -0400 To: Garrett Wollman , freebsd-standards@bostonradio.org From: Garance A Drosihn Subject: Re: Latest version of mega header file POSIX update Cc: current@FreeBSD.org Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Back on March 15/2001, Garrett Wollman wrote: >I have finally produced another version of the big header file patch >for people to look at. I'm still running an older (January) kernel >and world based on these changes. I have verified that these still >build on i386-architecture systems. I'm looking for some people to >do the following: > >1) Look at the changes to machine-dependent i386 headers and make > analogous changes, or verify the changes I've made, in the Alpha > and IA64 code. > >2) Test it. I'm interested not only in whether it runs -- I'm fairly > confident of that -- but also in what external software it breaks, > if any. > >I'm expecting to make a third pass over the header files once Austin >Group draft 6 is issued. (Draft 7 is expected to be the final text.) >However, I really, really want to get this checked in so that we can >all have a framework on which to work. > >The patch has now gotten too large for some e-mail systems, so I'm >making it available via the Web at > . As I'm sitting here picking off the occasional compile-time warnings in lpr&friends, I'm wondering about the status & timeline of this big posix-push patch. (one of the warnings I'm getting would be solved by the changes to in this patch). Is the goal to have this patch in current for "5.0-release" later this year? If so, what milestones should we be shooting for? Is this going to show up in 4-stable too, or is it too widespread a change to try and MFC it? (I am not suggesting it SHOULD be MFC'ed, I'm just wondering). [also, it seems to me there was a more recent message about this patch, but it seems I didn't save that one] I've got this idea of trying to build an alternate /usr/include on my -current machine, and then see how it works by switching between the current /usr/include and an alternate version which included the latest version of this patch. On the other hand, I do a lot more day-to-day living on a -stable system, so I'm not sure how much of a test I'd give these changes on my -current system. -- Garance Alistair Drosehn = gad@eclipse.acs.rpi.edu Senior Systems Programmer or gad@freebsd.org Rensselaer Polytechnic Institute or drosih@rpi.edu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message