Selon Gilles Espinasse
>
> From: mcoolive
> > while [ ! -f /proc/bus/usb/devices ]; do sleep 2; done
> >
> > But what will happen if support for « /proc/bus/usb » is not compile ?
> > Can we verify that ?
> >
> > mcoolive.
> >
> >
> You have too other cases of failure :
> - usb disabled in bios
> - no usbcore
> - no usb-{u,o,e}hci
> - devfs not mounted
>
> I almost feel happy without hot-plug
kernel hotplug launch userspace hotplug only if the material is detected
by the the kernel.
> You have too other cases of failure :
> - usb disabled in bios
> - no usbcore
> - no usb-{u,o,e}hci
So it is not a problem.
"No devfs" or "No usbfs" are problems because programs upcalled
by the kernel suppose their existance.
"devfs" and "usbfs" are not drivers, they are abstractions of material
for programs running in userspace.
I think there two solutions :
- kernel module wait to upcall userspace hotplug if devfs or usbfs
(or all other abstractions) is suppported but is not ready.
- userpace module can know if devfs and usbfs (and ...) are supported,
and wait them if needed.
We can implement the second only (hotplug is not our work).
But can we know if "support for devfs" and "support for usbfs" are compiled ?
If we can't, there is an error in architecture of hotplug.
mcoolive.
