udev rules files
kay.sievers at vrfy.org
Fri May 1 17:48:51 PDT 2009
On Sat, May 2, 2009 at 02:33, Patrice Dumas <pertusus at free.fr> wrote:
> On Sun, Apr 26, 2009 at 04:22:46PM +0200, Kay Sievers wrote:
>> interface. At that point, the block stuff will be disabled in HAL.
>> power/battery/UPS handling from HAL. At this point, the part of HAL
>> will be disabled.
> Why do you want to disable stuff in hal? Just don't use it?
HAL will go away entirely in the longer term, not next month, but as
soon as all the important stuff is replaced with a proper solution.
> may be other software using hal and needing a working hal. I am thinking
> about halevt I developped, it works fine, and I'd prefer not to have to
> rewrite it too soon
Sure, it's an extension to hal, and people who use hal can continue
using it as long as hal exists.
> especially if the design of the whole stack
> changes every 2 years or so.
And it's longer than two years, and also not every two years, it's the
first time since the is a "stack" at all. And nobody can be sure, in a
few years there might be another time. Stuff around us changes, and
stuff needs to adapt to changes. In this case, the adaption happens by
a full replacement, not by extending it, because it did not make
>> Device Access Control Lists, the stuff that grants access to devices
>> like the cdrom, the webcam, the camera, ... will likely be part of
>> udev-extras integrating with ConsoleKit. It is not implemented at all
>> at the moment.
> Wouldn't it be better if this was taken into account in the design
> before the whole stack gets phased out?
Nothing will go away before the stuff is properly replaced. It's all
taken care of. It's just that nobody worked on that as of now, because
it's just work but not a harder problem to solve, like the other stuff
we are currently working on.
More information about the devkit-devel