tech-misc archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]

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




To: der Mouse <mouse%Rodents.Montreal.QC.CA@localhost>

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

From: matthew green <mrg%eterna.com.au@localhost>

Date: Sun, 24 Feb 2008 10:22:08 +1100


   
   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.


Follow-Ups:

Re: why not have rcvars for all rc.d scripts? -- and downinterfaces and bootconf.sh not complete rc.d scripts
From: der Mouse


References:

Re: why not have rcvars for all rc.d scripts? -- and downinterfaces and bootconf.sh not complete rc.d scripts
From: der Mouse




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

Next by Date: Re: core dump in column(1) with 33 columns

Previous by Thread: Re: why not have rcvars for all rc.d scripts? -- and downinterfaces and bootconf.sh not complete rc.d scripts

Next by Thread: Re: why not have rcvars for all rc.d scripts? -- and downinterfaces and bootconf.sh not complete rc.d scripts

Indexes:

reverse Date

reverse Thread

Old Index



Home | Main Index | Thread Index | Old Index