From owner-freebsd-arch Mon Jan 22 20:36:23 2001 Delivered-To: freebsd-arch@freebsd.org Received: from mass.dis.org (mass.dis.org [216.240.45.41]) by hub.freebsd.org (Postfix) with ESMTP id 79E3237B401; Mon, 22 Jan 2001 20:36:06 -0800 (PST) Received: from mass.dis.org (localhost [127.0.0.1]) by mass.dis.org (8.11.1/8.11.1) with ESMTP id f0N4pSG01102; Mon, 22 Jan 2001 20:51:28 -0800 (PST) (envelope-from msmith@mass.dis.org) Message-Id: <200101230451.f0N4pSG01102@mass.dis.org> X-Mailer: exmh version 2.1.1 10/15/1999 To: "Brian F. Feldman" Cc: arch@FreeBSD.org Subject: Re: struct ucred is evil and must be contained In-reply-to: Your message of "Mon, 22 Jan 2001 23:28:11 EST." <200101230428.f0N4SBW01468@green.dyndns.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 22 Jan 2001 20:51:28 -0800 From: Mike Smith Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > The struct must be known as "ucred" in userspace to maintain > > compatibility with the old interfaces. > > But it isn't compatible, necessarily, so it probably really should be > changed. This is how it's done with e.g. xsocket, and the new proc > interface doesn't use plain "proc" either. Is there a good reason to not > change the name but still change the API? Only as far as I can tell because ucred is assumed to exist by software other than just the system, so whilst 'proc' and 'socket' were only ever exported for Bad and Evil reasons, ucred has been consumed because it's part of documented kernel interfaces. -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] V I C T O R Y N O T V E N G E A N C E To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message