Date: Tue, 1 Nov 2005 14:45:54 -0800 From: Brooks Davis <brooks@one-eyed-alien.net> To: Maksim Yevmenkin <maksim.yevmenkin@savvis.net> Cc: freebsd-bluetooth@freebsd.org, freebsd-rc@freebsd.org Subject: Re: [RFC] rc.d integration for the bluetooth subsystem Message-ID: <20051101224554.GA20543@odin.ac.hmc.edu> In-Reply-To: <4367E346.4080106@savvis.net> References: <1129491219.1616.18.camel@localhost> <4353DBBC.2000508@savvis.net> <43541F79.6040008@ebs.gr> <43554BCE.7090309@savvis.net> <4355FD0C.2090702@ebs.gr> <4356D12F.7000006@savvis.net> <43576A9D.1050209@ebs.gr> <4357CEA5.1000308@savvis.net> <4357D9E2.6010701@ebs.gr> <4367E346.4080106@savvis.net>
next in thread | previous in thread | raw e-mail | index | archive | help
[-- Attachment #1 --] On Tue, Nov 01, 2005 at 01:51:02PM -0800, Maksim Yevmenkin wrote: > All, > > please find the first draft of bluetooth rc.d scripts located at > > http://people.freebsd.org/~emax/bluetooth-rc.diff.txt > > this patch adds > > 1) /etc/rc.d/bluetooth script that will be used to start and stop > bluetooth devices. it will be called by devd(8) in response to device > arrival and departure events. the script also supports _optional_ per > device configuration. per device configuration is stored in > /etc/rc.conf.d/bluetooth.$dev file, where $dev is the driver name of the > device, i.e. ubt0, sio4, btccc1 > > 2) /etc/rc.conf.d/bluetooth.device.sample script. this is just an > example. it should be copied to /etc/rc.conf.d/bluetooth.$dev and then > defaults can be adjusted. once again if there is no > /etc/rc.conf.d/bluetooth.$dev script then reasonable defaults will be used. > > 3) required changes to /etc/Makefile, /etc/mtree/BSD.root.dist, etc. to > hook up new scripts to the build. > > i'd appreciate any feedback you might have. > > this work is inspired by the patches from Panagiotis Astithas. This looks like a powerful framework, I may need to find some bluetooth devices to play with if you're going to make it relatively easy to configure them. :) I'm a bit dubious about the bluetooth.device.sample idea. What if you used an /etc/defaults/bluetooth.device that you pulled in to set the defaults instead? It could contain the current example code, but set all the variables do define the defaults. I think that would be more in keeping with current practice. Adding rc.conf.d to mtree is probably a good idea regardless though. -- Brooks -- 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 [-- Attachment #2 --] -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQFDZ/AhXY6L6fI4GtQRAu5rAKDeHNCbLUonvnH84o7AqdYJuNi8gACfd3uL 8+eW2ZVz/OA+3yXwl0h6oL8= =QWor -----END PGP SIGNATURE-----
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20051101224554.GA20543>