From owner-freebsd-current Wed Dec 2 23:18:22 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA10787 for freebsd-current-outgoing; Wed, 2 Dec 1998 23:18:22 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from fw.bby.com.au (ns.bby.com.au [192.83.119.129]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA10766 for ; Wed, 2 Dec 1998 23:18:18 -0800 (PST) (envelope-from gnb@bby.com.au) Received: (from daemon@localhost) by fw.bby.com.au (8.8.8/8.6.9) id SAA08410 for ; Thu, 3 Dec 1998 18:18:04 +1100 (EST) Received: from melba.bby.com.au(192.43.186.1) via SMTP by fw.bby.com.au, id smtpd008408; Thu Dec 3 07:18:02 1998 Received: from lightning (lightning.bby.com.au [192.43.186.20]) by melba.bby.com.au (8.8.2/8.8.2) with ESMTP id SAA29220 for ; Thu, 3 Dec 1998 18:18:08 +1100 (EST) Message-Id: <199812030718.SAA29220@melba.bby.com.au> X-Mailer: exmh version 2.0.1 12/23/97 X-Mailer: exmh version 2.0.1 12/23/97 From: Gregory Bond To: current@FreeBSD.ORG Subject: How to catch all the /etc/pam.conf type mistakes Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 03 Dec 1998 18:17:59 +1100 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've just cvsup'd from the 3.0 CDs and been bit by the pam.conf thang (that was handily explained by John Polk's message in the mailing list archives - I'm new to -current and not long on this list, despite having run Stable and followed the -stable list since 2.2.6). 2 Questions: - How can I easily tell what time my sources were cvsup'd to [apart from redirecting stderr and using the error file as a timestamp?] - How can I find a list of all the things (such as pam.conf) that I need to fix that installworld doesn't notice? Is there some equivalent of the ERRATA file for tracking -current? I caught this one because missing pam.conf causes vocal and common error messages, and I found the email because I searched for pam.conf. What I am a little worried about is there may be other similar things I need to manually fix but I just haven't noticed them yet... Greg. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message