From owner-freebsd-current@FreeBSD.ORG Mon Apr 28 11:28:18 2003 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 80A1937B401; Mon, 28 Apr 2003 11:28:18 -0700 (PDT) Received: from MX4.estpak.ee (ld1.estpak.ee [194.126.101.98]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9C95443F3F; Mon, 28 Apr 2003 11:28:17 -0700 (PDT) (envelope-from kalts@estpak.ee) Received: from kevad.internal (80-235-38-44-dsl.mus.estpak.ee [80.235.38.44]) by MX4.estpak.ee (Postfix) with ESMTP id 20F211D0010; Mon, 28 Apr 2003 21:28:16 +0300 (EEST) Received: (from vallo@localhost) by kevad.internal (8.12.9/8.12.9/Submit) id h3SISFT5001237; Mon, 28 Apr 2003 21:28:15 +0300 (EEST) (envelope-from vallo) Date: Mon, 28 Apr 2003 21:28:15 +0300 From: Vallo Kallaste To: "Jacques A. Vidrine" , Lowell Gilbert , freebsd-current@FreeBSD.org Message-ID: <20030428182815.GA1188@kevad.internal> References: <20030428190209.A21656@dilbert.robbins.dropbear.id.au> <20030428075916.GA53857@myhakas.internal> <20030428080505.GA1474@chihiro.leafy.idv.tw> <20030428075916.GA53857@myhakas.internal> <20030428105521.GB2676@madman.celabo.org> <20030428111859.GA2923@madman.celabo.org> <44n0iallyq.fsf@be-well.ilk.org> <20030428144846.GA29465@madman.celabo.org> <20030428180901.GA1009@kevad.internal> <20030428181102.GA39754@madman.celabo.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20030428181102.GA39754@madman.celabo.org> User-Agent: Mutt/1.5.4i-ja.1 Subject: Re: Somethings still up with new NSS? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: kalts@estpak.ee List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 28 Apr 2003 18:28:18 -0000 On Mon, Apr 28, 2003 at 01:11:02PM -0500, "Jacques A. Vidrine" wrote: > On Mon, Apr 28, 2003 at 09:09:01PM +0300, Vallo Kallaste wrote: > > I'm beating the dead horse now, but what has happened to idea of > > tracking such events in the UPDATING file? I did remember the NSS > > update when I updated my system and specifically looked into > > UPDATING to get some clues beforehand, but found nothing. This has > > two sides, of course, it had probably saved my ass but the bug > > remained. > > What is it you are suggesting to put in UPDATING? Hmph, now that's a question. You posted the answer yourself some emails ago on this topic, but I deleted all of them after the problem got resolved. It was something along the lines of using pwd_mkdb or vipw after updating the system but before doing anything else, so all the records will be forced to new format. This isn't necessary, now that you found and fixed the bug. -- Vallo Kallaste