From owner-freebsd-rc@FreeBSD.ORG Mon Nov 7 20:01:01 2005 Return-Path: X-Original-To: freebsd-rc@freebsd.org Delivered-To: freebsd-rc@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 51DF716A420; Mon, 7 Nov 2005 20:01:01 +0000 (GMT) (envelope-from brdavis@odin.ac.hmc.edu) Received: from odin.ac.hmc.edu (Odin.AC.HMC.Edu [134.173.32.75]) by mx1.FreeBSD.org (Postfix) with ESMTP id A7A1C43D5F; Mon, 7 Nov 2005 20:00:57 +0000 (GMT) (envelope-from brdavis@odin.ac.hmc.edu) Received: from odin.ac.hmc.edu (localhost.localdomain [127.0.0.1]) by odin.ac.hmc.edu (8.13.0/8.13.0) with ESMTP id jA7K0eHF007832; Mon, 7 Nov 2005 12:00:40 -0800 Received: (from brdavis@localhost) by odin.ac.hmc.edu (8.13.0/8.13.0/Submit) id jA7K0eqB007831; Mon, 7 Nov 2005 12:00:40 -0800 Date: Mon, 7 Nov 2005 12:00:40 -0800 From: Brooks Davis To: Maksim Yevmenkin Message-ID: <20051107200040.GB29473@odin.ac.hmc.edu> References: <4357CEA5.1000308@savvis.net> <4357D9E2.6010701@ebs.gr> <4367E346.4080106@savvis.net> <20051102111709.GD2465@comp.chem.msu.su> <20051102161311.GA8499@odin.ac.hmc.edu> <43690365.60909@savvis.net> <20051102190655.GA3961@odin.ac.hmc.edu> <436A6649.7000602@savvis.net> <20051103203217.GA30685@odin.ac.hmc.edu> <436BE02D.2020404@savvis.net> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="DBIVS5p969aUjpLe" Content-Disposition: inline In-Reply-To: <436BE02D.2020404@savvis.net> User-Agent: Mutt/1.4.1i X-Virus-Scanned: by amavisd-new X-Spam-Status: No, hits=0.0 required=8.0 tests=none autolearn=no version=2.63 X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on odin.ac.hmc.edu Cc: freebsd-bluetooth@freebsd.org, freebsd-rc@freebsd.org, Panagiotis Astithas Subject: Re: [RFC] rc.d integration for the bluetooth subsystem X-BeenThere: freebsd-rc@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list 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, 07 Nov 2005 20:01:01 -0000 --DBIVS5p969aUjpLe Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Nov 04, 2005 at 02:26:53PM -0800, Maksim Yevmenkin wrote: > All, >=20 > please find next revision of bluetooth-rc stuff at >=20 > http://people.freebsd.org/~emax/bluetooth-rc-1.diff.txt >=20 > in this revision i have moved all bluetooth configuration files under=20 > /etc/bluetooth. bluetooth.device.sample is now called 'default.conf' and= =20 > file that contain device specific overrides called '$dev.conf' (i.e.=20 > 'ubt0.conf'). >=20 > so, '/etc/rc.d/bluetooth start $dev' does the following >=20 > 1) sets hardwired defaults (for backward compatibility) >=20 > 2) reads up /etc/bluetooth/default.conf (if any) I think /etc/defaults/bluetooth.device.conf might be better since we do have a defined location of default files and this will discourge people from messing with them. > 3) reads up /etc/bluetooth/$dev.conf (if any) > > 4) starts the stack >=20 > even though /etc/bluetooth/{default,$dev}.conf are not exactly shell=20 > scripts they are still kinda like shell scripts :) these files should=20 > follow sh(1) syntax to set the variable, comments etc. >=20 > the parser in bluetooth_read_conf() is very simple and value of a=20 > variable is still used in sh(1) eval. so one must be careful when=20 > editing these files. >=20 > is this looks like something? i also could write=20 > bluetooth.device.conf(5) man page that describes the parameters as well= =20 > as the syntax of the files. A bluetooth.device.conf(5) man page would be a good idea, though the example file is quite good. -- Brooks --=20 Any statement of the form "X is the one, true Y" is FALSE. PGP fingerprint 655D 519C 26A7 82E7 2529 9BF0 5D8E 8BE9 F238 1AD4 --DBIVS5p969aUjpLe Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQFDb7JnXY6L6fI4GtQRAuApAKC6XhPvWzU55oJk66DRUCx9qP7IfwCeNkkg qYfoTNfhx895GnVTkdp5aGY= =4m9P -----END PGP SIGNATURE----- --DBIVS5p969aUjpLe--