re: why not have rcvars for all rc.d scripts? -- and downinterfaces and bootconf.sh not complete rc.

   
   Many of the ones you list have other controls that are
functionally
   equivalent; for example, a missing sysctl.conf
effectively disables
   sysctl.  (I am not defending the current paradigm, just
trying to
   describe it; in fact, I rather dislike the way it pushes
configuration
   information out into a bunch of little files instead of
keeping it in
   rc.conf - the aspect of that that bothers me most,
personally, is
   network interface configuration.)


you can put a lot of network config (at least what i use) in
rc.conf.
eg, i either have dhclient=YES or
ifconfig_<int>="..." and
defaultroute=a.b.c.d.  that works mostly for me.


.mrg.

>> [...], I rather dislike the way it pushes
configuration information
>> out into a bunch of little files instead of keeping
it in rc.conf -
>> the aspect of that that bothers me most,
personally, is network
>> interface configuration.)
> you can put a lot of network config (at least what i
use) in rc.conf.

Yes, but not if you have more than two addresses on an
interface.  I
added code to 3.1's rc.d/network to handle ifalias_xxN_1,
ifalias_xxN_2, etc; if anyone wants it I'll be happy to
share, but the
comment

        # Note that $ifaliases_xxN works only with certain
configurations and
        # considered not recommended.  Use /etc/ifconfig.xxN
if possible.

leads me to think NetBSD does not want it, so I haven't gone
through
yet another round of trying to fix something only to be
unequivocally
told it's not broken.

/~ The ASCII				der Mouse
 / Ribbon Campaign
 X  Against HTML	       mouserodents.montreal.qc.ca
/  Email!	     7D C8 61 52 5D E7 2D 39  4E F1 31 3E E8 B3
27 4B

On Sun, 24 Feb 2008, der Mouse wrote:

>>> [...], I rather dislike the way it pushes
configuration information
>>> out into a bunch of little files instead of
keeping it in rc.conf -
>>> the aspect of that that bothers me most,
personally, is network
>>> interface configuration.)
>> you can put a lot of network config (at least what
i use) in rc.conf.
>
> Yes, but not if you have more than two addresses on an
interface.  I
> added code to 3.1's rc.d/network to handle
ifalias_xxN_1,
> ifalias_xxN_2, etc; if anyone wants it I'll be happy to
share, but the
> comment

 	You can specify multiple aliases on the same
ifaliase_<if>, var:

 	    ifconfig_fxp0=192.168.3.2
 	    ifaliases_fxp0="192.168.3.11 - 192.168.3.12 -
192.168.3.13 -"
 	    defaultroute=192.168.3.1

 	That would have worked in 3.x, and I believe in 2.x
also...

-- 
 		David/absolute       -- www.NetBSD.org: No hype required
--

>> Yes, but not if you have more than two addresses on
an interface.  I
>> added code to 3.1's rc.d/network to handle
ifalias_xxN_1,
>> ifalias_xxN_2, etc; if anyone wants it I'll be
happy to share, but
>> the comment
> You can specify multiple aliases on the same
ifaliase_<if>, var:

Oh, that's right, I tend to forget about that because it's
not
sufficient for my purposes, because you can't specify
anything but
simple IPv4-with-netmask, and I'm interested in commands
like "inet6
2610:.... prefixlen 96".  (I also added rcvars to
specify pre- and
post-config commands for an interface, but that's got
nothing to do
with aliases.)

/~ The ASCII				der Mouse
 / Ribbon Campaign
 X  Against HTML	       mouserodents.montreal.qc.ca
/  Email!	     7D C8 61 52 5D E7 2D 39  4E F1 31 3E E8 B3
27 4B