From owner-freebsd-current Mon Jun 8 18:28:49 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA21892 for freebsd-current-outgoing; Mon, 8 Jun 1998 18:28:49 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp04.primenet.com (daemon@smtp04.primenet.com [206.165.6.134]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA21834 for ; Mon, 8 Jun 1998 18:28:31 -0700 (PDT) (envelope-from tlambert@usr07.primenet.com) Received: (from daemon@localhost) by smtp04.primenet.com (8.8.8/8.8.8) id SAA00169; Mon, 8 Jun 1998 18:28:31 -0700 (MST) Received: from usr07.primenet.com(206.165.6.207) via SMTP by smtp04.primenet.com, id smtpd000100; Mon Jun 8 18:28:24 1998 Received: (from tlambert@localhost) by usr07.primenet.com (8.8.5/8.8.5) id SAA24107; Mon, 8 Jun 1998 18:28:16 -0700 (MST) From: Terry Lambert Message-Id: <199806090128.SAA24107@usr07.primenet.com> Subject: Re: ___error changes break CDE and mwm To: jb@cimlogic.com.au (John Birrell) Date: Tue, 9 Jun 1998 01:28:15 +0000 (GMT) Cc: tlambert@primenet.com, jb@cimlogic.com.au, deischen@iworks.InterWorks.org, freebsd-current@FreeBSD.ORG In-Reply-To: <199806082147.HAA09002@cimlogic.com.au> from "John Birrell" at Jun 9, 98 07:47:35 am X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Why hasn't the ld.so patch been committed, as a workaround? > > John Polstra commented: "Ick! Hacks like that are practically > impossible to get rid of again, ever." > > With the transition to ELF well under way, I'd suggest that no hacks > are necessary. We should bump the aout shared library versions for the > release of 3.0. If 3.0 is released with ELF as the default, the > unsafe errno implementation of the past will be orphaned in aout (where > it belongs, IMO). > > Can we move on now? Sure. As long as a.out libraries aren't included in the 3.0 release OR they are included, but *no* other changes requiring a version number bump will occur before 3.0 is released. I don't think this can be guaranteed, if any 3.x library routines depend on 3.x only system calls (mount/omount, anyone?). Note that the hack only affects the 3.0-current ld.so, and could be removed when the version numbers are officially bumped for the release (ie: it goes away at the same time as the problem would have anyway). It is as clean as it can get, and it's self-deleting on release. Alternately, people could run 2.6R and quit complaining. 8-|. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message