From owner-freebsd-current@FreeBSD.ORG Tue Jun 22 00:43:02 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A726916A4CE for ; Tue, 22 Jun 2004 00:43:02 +0000 (GMT) Received: from smtp3.server.rpi.edu (smtp3.server.rpi.edu [128.113.2.3]) by mx1.FreeBSD.org (Postfix) with ESMTP id 52F3E43D45 for ; Tue, 22 Jun 2004 00:43:02 +0000 (GMT) (envelope-from drosih@rpi.edu) Received: from [128.113.24.47] (gilead.netel.rpi.edu [128.113.24.47]) by smtp3.server.rpi.edu (8.12.8/8.12.8) with ESMTP id i5M0h1F4014176; Mon, 21 Jun 2004 20:43:01 -0400 Mime-Version: 1.0 X-Sender: drosih@mail.rpi.edu Message-Id: In-Reply-To: <200406220157.02776.max@love2party.net> References: <20040620134437.P94503@fw.reifenberger.com> <200406211639.22243.max@love2party.net> <20040621164657.GA2544@dragon.nuxi.com> <200406220157.02776.max@love2party.net> Date: Mon, 21 Jun 2004 20:43:00 -0400 To: Max Laier From: Garance A Drosihn Content-Type: text/plain; charset="us-ascii" ; format="flowed" X-Scanned-By: CanIt (www . canit . ca) cc: freebsd-current@freebsd.org Subject: Re: _ users [Was: startup error for pflogd] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 22 Jun 2004 00:43:02 -0000 At 1:56 AM +0200 6/22/04, Max Laier wrote: >On Monday 21 June 2004 18:46, David O'Brien wrote: > > On Mon, Jun 21, 2004 at 04:39:10PM +0200, Max Laier wrote: > > > > > > If there is no resistance against "yet another user", I will > > > add _pflogd. > > > > I would prefer just 'pflogd' until it is discussed if we want to > > follow the _ way. > >Okay, let's talk about this then: Any strong optionions one way >or the other? > >There is no technical argument (to my knowledge) that suggests >either. My vote is for "_" to keep the diff down, but >that is not an argument of course. Others have said that it: > - helps to recognize system processes > - helps to see "bad things" happening (1000 _pflogd is not a > good sign) > - resolves possible namespace problems I like _pflogd I think it can be _pflogd even if we do not explicitly decide to use _ for usernames added by other services. To claim otherwise is like saying you can't end the username in 'd' unless we decide that 'd' should be the last letter for userids added for all future service names. "_" is legal as the first letter in a userid. You should not need to get permission to use any legal letter in a userid that you want the system to add. Whether we DO decide to use _ for future services is perhaps worth debating. It sounds like a good idea to me, if for no other reason than to avoid namespace problems. However I do not think we should require it. The wish to "keep the diff down" would be just as valid when importing some other package as it is here for adding _pflogd. -- Garance Alistair Drosehn = gad@gilead.netel.rpi.edu Senior Systems Programmer or gad@freebsd.org Rensselaer Polytechnic Institute or drosih@rpi.edu