On Mon, 2007-03-19 at 13:53 -0500, Michael E Brown wrote: > On Mon, Mar 19, 2007 at 02:06:13PM -0400, Jeremy Katz wrote: > > On Mon, 2007-03-19 at 10:09 -0700, Florin Andrei wrote: > > > Rahul Sundaram wrote: > > > > > > > > It would do that everytime on bootup though. Right? Can we make it > > > > disable itself if the support is not there on first run? > > > > > > What would be nice is have a program that goes through all init scripts > > > after the installer is done and disables those services for whom there's > > > no capability in the hardware. > > > Sounds like something that firstboot could do. > > > > Except that the hardware that's attached to your system changes. Maybe > > you don't have bluetooth built-in on your machine, but you plug in a > > bluetooth USB dongle at some point. > > Or, if you are on a recent Dell laptop with libsmbios installed and run > "dellWirelessCtl --boot --bt 1" to enable bluetooth at runtime. (assuming you > have that module installed.) Or if you're on a thinkpad and you hit "Fn-F5". All variations of "hardware that's attached to your system changes." :) josh -- fedora-devel-list mailing list fedora-devel-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-devel-list
