From owner-freebsd-current@FreeBSD.ORG Tue Jun 22 23:17:15 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 673DB16A4CE for ; Tue, 22 Jun 2004 23:17:15 +0000 (GMT) Received: from moutng.kundenserver.de (moutng.kundenserver.de [212.227.126.173]) by mx1.FreeBSD.org (Postfix) with ESMTP id 292ED43D55 for ; Tue, 22 Jun 2004 23:17:15 +0000 (GMT) (envelope-from max@love2party.net) Received: from [212.227.126.205] (helo=mrelayng.kundenserver.de) by moutng.kundenserver.de with esmtp (Exim 3.35 #1) id 1BcuVh-0001zh-00; Wed, 23 Jun 2004 01:17:01 +0200 Received: from [84.128.133.182] (helo=donor.laier.local) by mrelayng.kundenserver.de with asmtp (TLSv1:RC4-MD5:128) (Exim 3.35 #1) id 1BcuVg-0004vC-00; Wed, 23 Jun 2004 01:17:01 +0200 From: Max Laier To: freebsd-current@freebsd.org Date: Wed, 23 Jun 2004 01:14:18 +0200 User-Agent: KMail/1.6.2 References: <20040620134437.P94503@fw.reifenberger.com> <20040622155106.C79584@carver.gumbysoft.com> In-Reply-To: <20040622155106.C79584@carver.gumbysoft.com> MIME-Version: 1.0 Content-Type: multipart/signed; protocol="application/pgp-signature"; micalg=pgp-sha1; boundary="Boundary-02=_L1L2Ad/LigueH7x"; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200406230114.19277.max@love2party.net> X-Provags-ID: kundenserver.de abuse@kundenserver.de auth:e28873fbe4dbe612ce62ab869898ff08 cc: Garance A Drosihn 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 23:17:15 -0000 --Boundary-02=_L1L2Ad/LigueH7x Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Wednesday 23 June 2004 00:56, Doug White wrote: > On Mon, 21 Jun 2004, Garance A Drosihn wrote: > > I like _pflogd > > I like the idea too, but I think its missed the train to get in on 5.x. > This breaks a lot of distributed user management since the system users > will become desync'd from prior releases, particularly 4.x. Adoption of 5 > is a bit slack and I expect to see mixed 4/5 environments for quite a > while still. 4 to 5 is going to be a bad enough migration as is; lets not > make it worse :) > > I think its quite doable for 6.x; this gives ports a chance to get on > board without having a huge rush before 5.3 hits the street. I completely agree with you here. My question is, what should I do with=20 pflogd? I don't see much point in creating user pflogd now, patching pflogd= =20 to use it and revert everything back for 6-current. So will it be much of a= =20 problem to add _pflogd now eventhough the rest of the daemons is not yet=20 converted? =2D-=20 Best regards, | mlaier@freebsd.org Max Laier | ICQ #67774661 http://pf4freebsd.love2party.net/ | mlaier@EFnet --Boundary-02=_L1L2Ad/LigueH7x Content-Type: application/pgp-signature Content-Description: signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (FreeBSD) iD8DBQBA2L1LXyyEoT62BG0RAnn/AJwJqDnHo7AWd0C+7VHjRSjbgiMcSgCfYkBu U+91GFFpX42+p0126GnS8VE= =lkhc -----END PGP SIGNATURE----- --Boundary-02=_L1L2Ad/LigueH7x--