Alan Stern wrote:
> On Sat, 25 Apr 2009, Jamie Lokier wrote:
>
> > I'm thinking this broader use:
> >
> > - My boot _script_ is waiting for a disk which identifies as
> > UUID=392852908752345749857 to appear before it can mount it on
> > /data. If there's no such disk, it proceeds without it. It's a
> > USB disk, behind a USB hub.
> >
> > - My boot script is looking to see if I'm holding down 'z' on the
> > keyboard, to do something different. But how does it know if
> > there's a USB keyboard plugged in (behind two USB hubs) that
> > hasn't finished being detected?
> >
> > It just seemed to fit comfortably into what's being discussed.
>
> Are you suggesting this new interface be exported to userspace somehow?
Not directly. Only in the same way that open("/dev/console") delays
until there's a console, so reading the keyboard can delay until we
know if we had a keyboard plugged in at boot, and looking for a disk
called UUID=392852908752345749857 can wait until we know if there was
one plugged in at boot time.
The latter issue with UUID is done in userspace now by reading all
disks, but I'm under the impression changes are planned in that
department because reading every disk from userspace to locate
specific ones is too slow on big systems.
-- Jamie
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
