Subject: Re: rc.conf vs interface aliases
To: <>
From: Ignatios Souvatzis <>
List: tech-net
Date: 01/19/2006 07:05:49
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Wed, Jan 18, 2006 at 05:01:03PM -0500, der Mouse wrote:
> >> I'm currently leaning towards a local script in rc.d, with
> >> REQUIRE:root and BEFORE:network, which rewrites /etc/ifconfig.* and
> >> /etc/pf.conf based on /etc/ifnames (or whatever).  But that seems
> >> pretty gross,
> > Why?
> It's rewriting config files on every boot.
> > The good thing about rc.d is that you can do that cleanly.
> Sure, the rc.d side of it is relatively clean, as such things go.  It's
> the other side of it - rewriting /etc/ifconfig.* and /etc/pf.conf (and
> possibly others, though I know of no others yet) - that I find gross.

Hm, yes... on the other hand, it _is_ a configuration change... other=20
people use a monster like cfengine to make those co-ordinated. Just=20
view it as a mini cfengine ;-)

seal your e-mail:

Content-Type: application/pgp-signature
Content-Disposition: inline

Version: GnuPG v1.4.1 (NetBSD)