Exposing the mouse battery status through HAL
sergey.udaltsov at gmail.com
Wed Dec 1 02:49:45 PST 2004
OK. You nearly convinced me. So I will introduce the "addons" property
as you advised - but still will use internally my own
"command_interface" to detect the devices to maintain.
On Wed, 1 Dec 2004 05:45:12 -0500, Behdad Esfahbod
<behdad at cs.toronto.edu> wrote:
> On Wed, 1 Dec 2004, Sergey Udaltsov wrote:
> > > Then you need an oracle to tell you that you need mousebatd
> > > daemon. The idea was to be able to find out what daemons are
> > > needed.
> > Why oracle??? Just put the binary into drivers.d - that's it! Isn't
> > that what drivers.d was introduced for? Or do you want to be able to
> > execute arbitrary binary anywhere in the filesystem?
> *My* understanding is that it's not the best practice to put all
> possible daemons there and run all of them so they can decide if
> there's something interesting for them or not. Think of too many
> of them. And think of when the needed daemon is not installed.
> We want to be able to notify the user that for best results (s)he
> needs to install a daemon providing this functionality. In a
> shiny world, that may be automated by installing the RPM
> providing that name on a Fedora system for example, using yum of
> > Sergey
hal mailing list
hal at freedesktop.org
More information about the Hal