Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 2 Dec 2013 19:34:15 +0000
From:      "Teske, Devin" <Devin.Teske@fisglobal.com>
To:        Colin Percival <cperciva@freebsd.org>
Cc:        Devin Teske <dteske@freebsd.org>, FreeBSD RC <freebsd-rc@FreeBSD.org>
Subject:   Re: RFC: support for re-sourcing /etc/rc.conf
Message-ID:  <06443C9D-9E4A-431E-934C-E0A19DBAA111@fisglobal.com>
In-Reply-To: <529CDF65.7000406@freebsd.org>
References:  <529BEDDB.8010003@freebsd.org> <20131202.214853.1540734630471865242.hrs@allbsd.org> <529CD535.5010903@freebsd.org> <9EF48D5E-2706-4628-BF7B-DBBD5D7E227F@fisglobal.com> <529CDF65.7000406@freebsd.org>

next in thread | previous in thread | raw e-mail | index | archive | help

On Dec 2, 2013, at 11:28 AM, Colin Percival wrote:

> On 12/02/13 11:17, Teske, Devin wrote:
>> On Dec 2, 2013, at 10:45 AM, Colin Percival wrote:
>>> No, the other way around -- a different script (part of ec2-scripts) up=
dates
>>> /etc/rc.conf based on metadata provided at VM launch time.  One use of =
this
>>> would be to set firstboot_pkgs_* variables to control the behaviour of =
the
>>> firstboot-pkgs port moments later in the boot process.
>>=20
>> sysrc(8) in 9.2+ base comes to mind.
>> NB: Available as a port for older releases 4.8+ (sysutils/sysrc)
>=20
> I should have been clearer, the VM launch user-data could specify any fil=
es to
> modify; it just happens that rc.conf is a problem because it's over-aggre=
ssively
> cached.
>=20

Thanks.


>>> 3. Early in the boot process, ec2-scripts reads that user-data, updates
>>>  /etc/rc.conf, and signals /etc/rc.
>>> 4. /etc/rc re-sources /etc/rc.conf.
>>=20
>> Cool. How's the signaling in #3 done to get #4?
>=20
> My (one line plus comments) patch teaches rc to re-source rc.conf if it r=
eceives
> a SIGALRM.
>=20

Nice.


>> I like the idea of firstboot_pkgs_*
>=20
> Great.  It's in the ports tree, sysutils/firstboot-pkgs.
>=20
>> I also like Hiroki's idea of stashing it all into rc.conf.d
>=20
> As I mentioned in reply to him, forcing people to use rc.conf.d instead of
> rc.conf seems like a usability challenge.
>=20

Yeah, I agree. rc.conf.d in your case raises an aspect of POLA.
--=20
Devin

_____________
The information contained in this message is proprietary and/or confidentia=
l. If you are not the intended recipient, please: (i) delete the message an=
d all copies; (ii) do not disclose, distribute or use the message in any ma=
nner; and (iii) notify the sender immediately. In addition, please be aware=
 that any message addressed to our domain is subject to archiving and revie=
w by persons other than the intended recipient. Thank you.



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?06443C9D-9E4A-431E-934C-E0A19DBAA111>