I like it too... No code anywhere than needed. After all, if /etc/rc
doesn't exist, everything's messed up anyway, so you mideswell make it more
dependent upon that script.
-----Original Message-----
From: Chas <cpinck...@dynasty.net>
To: p...@originative.co.uk <p...@originative.co.uk>
Cc: r...@dataplex.net <r...@dataplex.net>; curr...@freebsd.org
<curr...@freebsd.org>
Date: Monday, March 22, 1999 5:12 PM
Subject: Re: /etc/rc.conf, take 46!
>Now that sounz like a simple solution.:)) Paul...
>> >
>> > An alternate, and perhaps cleaner approach would be to always suck in
>> > /etc/defaults/rc.conf and /etc/rc.conf. Then suck in those
>> > files specified
>> > in ${additional_rc_conf_files}.
>>
>> I still think we're chasing our tails with all this configuration stuff.
>>
>> Why can't /etc/rc load /etc/defaults/rc.conf followed by /etc/rc.conf (if
>> present). Don't have anything in /etc/defaults.rc.conf except default
>> variable settings.
>>
>> The local admin can do what the hell they want in /etc/rc.conf, including
>> putting in a bit of script to load /etc/rc.conf.local
>> /etc/rc.conf.flavour_of_month etc.
To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-current" in the body of the message
