Ok. Then it's as expected. In this usbdb, usb/disk is built into usbd. That means that usbd will spawn a driver for disk as soon as it sees a disk plugged in. If you run usb/disk on your own, there will be no unhandled disks left for it and it should say that there are no disks and exit.
Regarding the mount, yes, the fs from usbd is to be mounted also at /dev for usbfat and others to use. You might add an entry to your namespace file if it's not mounted by default. On Mon, Jul 19, 2010 at 3:48 PM, Jeff Sickel <[email protected]> wrote: > > On Jul 19, 2010, at 3:33 AM, Francisco J Ballesteros wrote: > >>> >>> If I do: >>> >>> usb/disk >>> >>> I get "no device found". But if instead the command is: >>> >>> usb/usbfat: >>> >>> I get /dev/sdU0.0 and /dev/sdU0.1 with plausible trees (ctl data raw). The >>> sdU0.0 corresponds to a usb/probe that returns: >>> >> >> Are you running usbd with embedded disks? In that case the disks are owned by >> the usb/disk linked into usbd, and the one you start by hand should >> see no disks, as it happens. >> I'd like to confirm this, just to know if it's a bug. > > That question made me go back to the man page and dig through the sources > again. It's the default/most recent configuration from yesterday's live CD. > > cpu% cat usbdb > # only kb, disk, and ether are prepared for embedding. > # others are not yet converted to sit in the usbd device driver library > embed > kb csp=0x010103 csp=0x020103 args= > disk class=storage args= > ether class=255 csp=0x00ffff args= > serial class=255 csp=0xffffff vid=0x9e88 did=0x9e8f args= > # wifi class=0 csp=0 vid=0x0bda did=0x8192 args= > # wifi class=0 csp=0 vid=0x148f did=0x2870 args= > > > Another side note: I had to explicitly do the following for anything to show > up: > > cat% mount /srv/usb /n/usb > > > >
