best way to determine devices with drivers

Andrew Luecke at
Wed Jun 23 19:38:56 PDT 2004

Actually, turns out i was worried about nothing.. phew. for a very
short time i was starting to think that some software, like digital
cameras didn't use a kernel module.. luckily, i'm wrong. I found out
stuff like digital cameras use the Mass storage module in the kernel,
so, luckily, it will work like I want it to (when the linux.driver
works again) ;)

So, looks like I'll be going the way of HAL/DBUS (no more weird usage
of sysfs for me).

Thanks for the help all.

By the way, has anyone here thought of extending HAL to work over
network, like recording the networked devices.. It's always handy to
know what capabilities your toaster has when you plug it into the
network ;)

On Thu, 24 Jun 2004 00:44:29 +0200, David Zeuthen <david at> wrote:
> On Mon, 2004-06-21 at 13:58 +1000, andrew luecke wrote:
> > Maybe I'll also need to develop a database that can record userspace progs
> > and drivers for devices or something.. guess it just got more complex.
> >
> This sounds a bit backwards to me; wouldn't it be smarter to record what
> kernel module or userspace library is needed per device rather than
> tracking what devices/libraries applications use? The .fdi files in HAL
> might help with this.
> Let's see if I understand correctly; For example, if I insert a
> removable harddisk and there is a NTFS partition, your software will
> download the NTFS kernel module, install it and insmod it? If so, how do
> you plan to tell the desktop this (I assume it will take some time to
> download etc.)? D-BUS?
> Cheers,
> David

hal mailing list
hal at

More information about the Hal mailing list