Pending issues with RELENG_5
Jeremy Chadwick
freebsd at jdc.parodius.com
Mon Sep 27 10:45:11 PDT 2004
Oops, forgot one:
* No /etc/defaults/make.conf -- has this methodology been changed since
RELENG_4? If not, I assume this will be rectified prior to 5.3
going to -RELEASE? Most of us have been going off of 4.x boxes which
have /etc/defaults/make.conf, but the tweaks may not be the same
between 4.x and 5.x (some deprecated, new additions, changes, etc.).
--
| 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. |
On Mon, Sep 27, 2004 at 10:03:21AM -0700, Jeremy Chadwick wrote:
> 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. |
>
> _______________________________________________
> freebsd-current at freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-current
> To unsubscribe, send any mail to "freebsd-current-unsubscribe at freebsd.org"
More information about the freebsd-current
mailing list