From owner-freebsd-current@FreeBSD.ORG Mon Sep 27 17:03:22 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 242D616A4CF for ; Mon, 27 Sep 2004 17:03:22 +0000 (GMT) Received: from mail.parodius.com (mail.parodius.com [64.62.145.229]) by mx1.FreeBSD.org (Postfix) with ESMTP id E313843D48 for ; Mon, 27 Sep 2004 17:03:21 +0000 (GMT) (envelope-from jdc@pentarou.parodius.com) Received: from pentarou.parodius.com (jdc@localhost [127.0.0.1]) by mail.parodius.com (8.13.1/8.13.1) with ESMTP id i8RH3Lup033896 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Mon, 27 Sep 2004 10:03:21 -0700 (PDT) (envelope-from jdc@pentarou.parodius.com) Received: (from jdc@localhost) by pentarou.parodius.com (8.13.1/8.13.1/Submit) id i8RH3LU7033895 for freebsd-current@freebsd.org; Mon, 27 Sep 2004 10:03:21 -0700 (PDT) (envelope-from jdc) Date: Mon, 27 Sep 2004 10:03:21 -0700 From: Jeremy Chadwick To: freebsd-current@freebsd.org Message-ID: <20040927170321.GA31501@parodius.com> Mail-Followup-To: freebsd-current@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.6i Subject: Pending issues with RELENG_5 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: Mon, 27 Sep 2004 17:03:22 -0000 Here's a list of things that still concern me so far with RELENG_5, particularly with BETA6 (and even more recent than that). Hopefully the appropriate parties can chime in here... * No /etc/mergemaster.rc or /etc/defaults/mergemaster.rc Possibly creating this out-of-the-box during install, or keep a template in /etc/defaults/mergemaster.rc ? * /etc/rc.d/named does not set up chroot environment properly For example, in the chroot_autoupdate() function, lines 37 and 41 call pax blindly, referring to ${named_chrootdir}/dev even if it hasn't been created. The same goes for ${named_chrootdir}/etc/namedb/rndc.key, and the entire ${named_chrootdir}/etc tree (etc/localtime, etc/namedb, and so on). Could we get appropriate if [ -d ...]; then mkdir/chown/chmod; fi statements for creating this structure? I personally have no idea who the appropriate directories should be owned by, or perm'd to. * bind9 chroot tips Possibly some details on how to configure named.conf inside the default named.conf? We hint at it already... * Leftovers from bind8-->bind9 upgrade We now have two versions of nslookup; /usr/bin/nslookup and /usr/sbin/nslookup (deprecated), but we've also /usr/lib/libisc.* I assume this can be deleted and ldconfig -R re-run? There's also the old dnsquery and dnskeygen binaries, extraneous manpages, etc.. [This entry could spawn off quite a long thread about how exactly we plan on handling 'outdated' files. None of this will matter when actually installing 5.3-STABLE (when released) on a new box, but for all bazillion of us who cvsup+world, it's a long-standing issue.] I was in a hurry this morning to get this out, meaning my actual "full list" is probably quite a bit longer... just need the time to sit down and type it all in. :-) -- | Jeremy Chadwick jdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. |