From owner-freebsd-current Wed Dec 2 12:30:49 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA01033 for freebsd-current-outgoing; Wed, 2 Dec 1998 12:30:49 -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 MAA00999; Wed, 2 Dec 1998 12:30:42 -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 MAA08556; Wed, 2 Dec 1998 12:32:10 -0800 (PST) To: Garrett Wollman cc: current@FreeBSD.ORG, dillon@FreeBSD.ORG Subject: Re: Uh oh... In-reply-to: Your message of "Wed, 02 Dec 1998 10:44:24 EST." <199812021544.KAA20290@khavrinen.lcs.mit.edu> Date: Wed, 02 Dec 1998 12:32:10 -0800 Message-ID: <8552.912630730@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > It has never in the past handled creating new users or groups. > Witness the `network' group, the `xten' user, the `uucp' user, the `man' > group, and the `dialer' group. I think xten, uucp, user and dialer have been around for long enough that we didn't have much trouble with them. The `network' group was another one I fielded a lot of questions over. I think all this shows is that we've been here before and it sucked then too (I also guess that some core folk are avoiding our user base since it seems that some of you have formed a rather rose-colored impression of past events! :-). It's a bootstrapping issue which I'm even more solidly convinced should have *some* kind of safety belt installed, even if it just tells you "please go off and create user foo with uid 30 and gid 33" and cops out. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message