From owner-freebsd-current Wed Dec 2 02:39:51 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA04526 for freebsd-current-outgoing; Wed, 2 Dec 1998 02:39:51 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA04521 for ; Wed, 2 Dec 1998 02:39:50 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by zippy.cdrom.com (8.9.1/8.9.1) with ESMTP id CAA06866; Wed, 2 Dec 1998 02:41:29 -0800 (PST) To: Matthew Dillon cc: current@FreeBSD.ORG Subject: Re: Uh oh... In-reply-to: Your message of "Wed, 02 Dec 1998 02:31:13 PST." <199812021031.CAA13477@apollo.backplane.com> Date: Wed, 02 Dec 1998 02:41:28 -0800 Message-ID: <6862.912595288@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Uh oh. Hmmm. Can we specify a uid in the BSD.root.dist rather then > a user name ? It wouldn't really solve the problem since then you'd just have the 2nd-order bug reports of "why are all my files owned by this funny number?" coming in - there's really just no substitute for getting the new entries into the password file. Fortunately, the pw(8) command makes this pretty easy to do. You can check to see if the user/uid is already there by doing something like: if pw usershow bind > /dev/null 2>&1; then pw useradd bind ..other args.. fi In /usr/src/Makefile.inc1's buildworld rule (I'd stick it before the hierarchy stuff, for obvious reasons). - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message