From owner-freebsd-rc@FreeBSD.ORG Mon Dec 2 19:34:18 2013 Return-Path: Delivered-To: freebsd-rc@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 21C9C2FC; Mon, 2 Dec 2013 19:34:18 +0000 (UTC) Received: from mx1.fisglobal.com (mx1.fisglobal.com [199.200.24.190]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id D9D721F00; Mon, 2 Dec 2013 19:34:17 +0000 (UTC) Received: from smtp.fisglobal.com ([10.132.206.31]) by ltcfislmsgpa07.fnfis.com (8.14.5/8.14.5) with ESMTP id rB2JYGF5002572 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Mon, 2 Dec 2013 13:34:16 -0600 Received: from LTCFISWMSGMB21.FNFIS.com ([169.254.1.7]) by LTCFISWMSGHT03.FNFIS.com ([10.132.206.31]) with mapi id 14.03.0158.001; Mon, 2 Dec 2013 13:34:15 -0600 From: "Teske, Devin" To: Colin Percival Subject: Re: RFC: support for re-sourcing /etc/rc.conf Thread-Topic: RFC: support for re-sourcing /etc/rc.conf Thread-Index: AQHO75MygMZmDpdBLUKyR2AQoGR8qA== Date: Mon, 2 Dec 2013 19:34:15 +0000 Message-ID: <06443C9D-9E4A-431E-934C-E0A19DBAA111@fisglobal.com> 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> In-Reply-To: <529CDF65.7000406@freebsd.org> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.132.253.120] Content-Type: text/plain; charset="iso-8859-1" Content-ID: Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:5.11.72, 1.0.14, 0.0.0000 definitions=2013-12-02_03:2013-12-02,2013-12-02,1970-01-01 signatures=0 Cc: Devin Teske , FreeBSD RC X-BeenThere: freebsd-rc@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list Reply-To: Devin Teske List-Id: "Discussion related to /etc/rc.d design and implementation." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 02 Dec 2013 19:34:18 -0000 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.