From owner-freebsd-arch Tue Sep 4 10: 3:55 2001 Delivered-To: freebsd-arch@freebsd.org Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by hub.freebsd.org (Postfix) with ESMTP id 3535837B401 for ; Tue, 4 Sep 2001 10:03:50 -0700 (PDT) Received: from fledge.watson.org (robert@fledge.pr.watson.org [192.0.2.3]) by fledge.watson.org (8.11.5/8.11.5) with SMTP id f84H3hP56149 for ; Tue, 4 Sep 2001 13:03:43 -0400 (EDT) (envelope-from robert@fledge.watson.org) Date: Tue, 4 Sep 2001 13:03:43 -0400 (EDT) From: Robert Watson X-Sender: robert@fledge.watson.org To: arch@FreeBSD.org Subject: ucred -> cred, cr_[ug]id Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII 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 Earlier this year, I merged the 'pcred' and 'ucred' structures into a single 'ucred' structure, recognizing that in practice our use of pcred and ucred was such that the costs of the change were low, but the clarity associated with the change was relatively high. This simplified things from a variety of perspective, including reference counting and synchronization. This is a change also performed on a number of other UNIX platforms, including Solaris and IRIX. However, on those platforms, the single structure is called 'cred' and not 'ucred'. As such, I'd like to propose that we do the following: o Replace all references to struct ucred with struct cred o Repo-copy src/sys/ucred.h to src/sys/cred.h I don't feel all that strongly about this change, but do think it would make sense given the use of the structure, and the evolution of other platforms making similar classes of changes. On a similar note, when I merged ucred and pcred, I maintained cr_uid as the effective uid: other platforms typically stick an 'e' in front to get cr_euid, making it consistent with other variables in the structure. If I were to make the 'cred' change, I'd also improve consistency by adding the 'e' to the effective uid and gid structures. Any strong reasons not to do this? Robert N M Watson FreeBSD Core Team, TrustedBSD Project robert@fledge.watson.org NAI Labs, Safeport Network Services To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message