Re: hotplug, udev and usbkey question

[Tony Godshall <togo@of.net>]

According to Bob Alexander,
> John L Fjellstad wrote:
> >Bob Alexander <bob@ngi.it> writes:
> >
> >
> >>But I still have a problem. The /dev/usbkey device is still not created.
> >>
> >>Reading your very good explanation I also believe it should already
> >>have since I also had the following (0644 root.root):
> >>
> >>bob@t40:/etc/udev/rules.d$ cat 10-local.rules
> >>BUS="usb", KERNEL="sd?1", SYSFS{serial}="0206430D0A001CBC", NAME="usbkey"
> >>
> >>syslog only shows the creation of the sda* devices from
> >>/etc/udev/rules.d/z_hal-plugdev.rules
> >>
> >>Any other things to look at ?
> >
> >
> >Could post your syslog entries for udev when inserting the usb key.  One
> >thing I would look at is removing "KERNEL=sd?1".  At my place, the usb
> >key is uba1. I wonder if the rule is too specific.
> >  
> 
> There you go John,
> here is what goes into syslog when I insert the usbkey.
> 
> Have a nice weekend,
> Bob
> 
> Mar 19 09:33:17 localhost kernel: usb 4-3: new high speed USB device 
> using ehci_hcd and address 3
> Mar 19 09:33:18 localhost kernel: SCSI subsystem initialized
> Mar 19 09:33:18 localhost kernel: Initializing USB Mass Storage driver...
> Mar 19 09:33:18 localhost kernel: scsi0 : SCSI emulation for USB Mass 
> Storage devices
> Mar 19 09:33:18 localhost kernel: usbcore: registered new driver usb-storage
> Mar 19 09:33:18 localhost kernel: USB Mass Storage support registered.
> Mar 19 09:33:18 localhost usb.agent[6457]:      usb-storage: loaded 
> successfullyMar 19 09:33:18 localhost kernel: usb-storage: device found at 3
> Mar 19 09:33:18 localhost kernel: usb-storage: waiting for device to 
> settle before scanning
> Mar 19 09:33:23 localhost kernel:   Vendor:           Model: USB Flash 
> Memory  Rev: 1.00
> Mar 19 09:33:23 localhost kernel:   Type:   Direct-Access 
>        ANSI SCSI revision: 00
> Mar 19 09:33:23 localhost kernel: usb-storage: device scan complete
> Mar 19 09:33:23 localhost scsi.agent[6575]: disk at 
> /devices/pci0000:00/0000:00:1d.7/usb4/4-3/4-3:1.0/host0/target0:0:0/0:0:0:0
> Mar 19 09:33:24 localhost kernel: SCSI device sda: 246272 512-byte hdwr 
> sectors
> (126 MB)
> Mar 19 09:33:24 localhost kernel: sda: assuming Write Enabled
> Mar 19 09:33:24 localhost kernel: sda: assuming drive cache: write through
> Mar 19 09:33:24 localhost kernel: SCSI device sda: 246272 512-byte hdwr 
> sectors
> (126 MB)
> Mar 19 09:33:24 localhost kernel: sda: assuming Write Enabled
> Mar 19 09:33:24 localhost kernel: sda: assuming drive cache: write through
> Mar 19 09:33:24 localhost kernel:  sda: sda1
> Mar 19 09:33:24 localhost kernel: Attached scsi removable disk sda at 
> scsi0, channel 0, id 0, lun 0
> Mar 19 09:33:24 localhost udev[6606]: configured rule in 
> '/etc/udev/rules.d/z_hal-plugdev.rules[2]' applied, 'sda' becomes '%k'
> Mar 19 09:33:24 localhost udev[6606]: creating device node '/dev/sda'
> Mar 19 09:33:24 localhost udev[6624]: configured rule in 
> '/etc/udev/rules.d/z_hal-plugdev.rules[2]' applied, 'sda1' becomes '%k'
> Mar 19 09:33:24 localhost udev[6624]: creating device node '/dev/sda1'

Hi.

Did you try changing NAME= to SYMLINK=?  That way the real
device will still go where the kernel would have put it (which 
is handy since some utils don't look for customized names), at 
/dev/sda1, and you should have a handy symlink to it that
you can use for almost any purpose you would have used real
node for.

Tony