At 10:50 AM -0600 1/10/02, der Mouse wrote:
>Option 3 requires something like a devfs, which has been discussed
>before; I recommend that nobody post about its pros or cons without
>having read the past discussion on the subject.

Why not just write a daemon that queries the kernel about the currently
present drivers, then adds/deletes according to a certain user-defined
policy? The most that would need to be added to the kernel is a query
function to list the active devices, and perhaps a blocking poll function.

You could even have the daemon remember the permissions of the dev files
when it deletes them, depending on the type of device.


Cheers - Tony 'Nicoya' Mantler :)


--
Tony "Nicoya" Mantler - Renaissance Nerd Extraordinaire - nicoya@apia.dhs.org
Winnipeg, Manitoba, Canada           --           http://nicoya.feline.pp.se/