El dom, 19-10-2008 a las 14:54 +0000, Rogério Brito escribió:
> Hi, I am upstream for usbmount. Please, see bug #229883.
>
> Do you have HAL running? Any gnome or kde thing automounting devices?
Yes, i've HAL running. No GNOME or KDE installed.
> If not, could you please use the following command to see what udev
> would do with your device:
>
> udevadm test --action=add /sys/class/block/sda1 (or whatever)
>
> It generates *a lot* of output. Many screens, depending on the device.
root@sbg-ajuntament:~# udevadm test --action=add /sys/class/block/sdc1
This program is for debugging only, it does not run any program,
specified by a RUN key. It may show incorrect results, because
some values may be different, or not available at a simulation run.
parse_file: reading '/etc/udev/rules.d/05-options.rules' as rules file
parse_file: reading '/etc/udev/rules.d/05-udev-early.rules' as rules
file
parse_file: reading '/etc/udev/rules.d/20-names.rules' as rules file
parse_file: reading '/etc/udev/rules.d/30-cdrom_id.rules' as rules file
parse_file: reading '/etc/udev/rules.d/40-basic-permissions.rules' as
rules file
parse_file: reading '/etc/udev/rules.d/40-permissions.rules' as rules
file
parse_file: reading '/etc/udev/rules.d/45-fuse.rules' as rules file
parse_file: reading '/etc/udev/rules.d/60-persistent-input.rules' as
rules file
parse_file: reading '/etc/udev/rules.d/60-persistent-storage-tape.rules'
as rules file
parse_file: reading '/etc/udev/rules.d/60-persistent-storage.rules' as
rules file
parse_file: reading '/etc/udev/rules.d/60-symlinks.rules' as rules file
parse_file: reading '/etc/udev/rules.d/61-persistent-storage-edd.rules'
as rules file
parse_file: reading '/etc/udev/rules.d/65-mdadm.vol_id.rules' as rules
file
parse_file: reading '/etc/udev/rules.d/70-persistent-cd.rules' as rules
file
parse_file: reading '/etc/udev/rules.d/70-persistent-net.rules' as rules
file
parse_file: reading '/etc/udev/rules.d/75-cd-aliases-generator.rules' as
rules file
parse_file: reading
'/etc/udev/rules.d/75-persistent-net-generator.rules' as rules file
parse_file: reading '/etc/udev/rules.d/80-programs.rules' as rules file
parse_file: reading '/etc/udev/rules.d/85-alsa.rules' as rules file
parse_file: reading '/etc/udev/rules.d/85-hdparm.rules' as rules file
parse_file: reading '/etc/udev/rules.d/85-hwclock.rules' as rules file
parse_file: reading '/etc/udev/rules.d/85-ifupdown.rules' as rules file
parse_file: reading '/etc/udev/rules.d/85-mdadm.rules' as rules file
parse_file: reading '/etc/udev/rules.d/85-pcmcia.rules' as rules file
parse_file: reading '/etc/udev/rules.d/90-modprobe.rules' as rules file
parse_file: reading '/etc/udev/rules.d/95-hal.rules' as rules file
parse_file: reading '/etc/udev/rules.d/95-udev-late.rules' as rules file
parse_file: reading '/etc/udev/rules.d/z60_usbmount.rules' as rules file
unable to open device '/class/block/sdc1'
> Another good diagnostic tool would be the following:
>
> udevinfo -a -p $(udevinfo -q path -n /dev/sda1) (idem)
root@sbg-ajuntament:~# udevinfo -a -p $(udevinfo -q path -n /dev/sdc1)
Udevinfo starts with the device specified by the devpath and then
walks up the chain of parent devices. It prints for every device
found, all possible attributes in the udev rules key format.
A rule to match, can be composed by the attributes of the device
and the attributes from one single parent device.
looking at parent device '/devices/pci0000:00':
KERNELS=="pci0000:00"
SUBSYSTEMS==""
DRIVERS==""
It seems all data is ok, no ?
BTW mount command don't show the device:
root@sbg-ajuntament:~# mount
/dev/md0 on / type ext3 (rw,errors=remount-ro)
proc on /proc type proc (rw,noexec,nosuid,nodev)
/sys on /sys type sysfs (rw,noexec,nosuid,nodev)
varrun on /var/run type tmpfs (rw,noexec,nosuid,nodev,mode=0755)
varlock on /var/lock type tmpfs (rw,noexec,nosuid,nodev,mode=1777)
udev on /dev type tmpfs (rw,mode=0755)
devshm on /dev/shm type tmpfs (rw)
devpts on /dev/pts type devpts (rw,gid=5,mode=620)
/dev/md1 on /home type xfs (rw)
securityfs on /sys/kernel/security type securityfs (rw)
rpc_pipefs on /var/lib/nfs/rpc_pipefs type rpc_pipefs (rw)
But it is mounted on:
/var/run/usbmount/ST350083_0AS_1/
Thaks.
--
"Si has construido un castillo en el aire, no has perdido el tiempo, es
allí donde debería estar. Ahora debes construir los cimientos debajo de
él." - George Bernard Shaw, escritor irlandés
Marc Montañés * mail: <email address hidden> * telf: 622216489
El dom, 19-10-2008 a las 14:54 +0000, Rogério Brito escribió:
> Hi, I am upstream for usbmount. Please, see bug #229883.
>
> Do you have HAL running? Any gnome or kde thing automounting devices?
Yes, i've HAL running. No GNOME or KDE installed.
> If not, could you please use the following command to see what udev block/sda1 (or whatever)
> would do with your device:
>
> udevadm test --action=add /sys/class/
>
> It generates *a lot* of output. Many screens, depending on the device.
root@sbg- ajuntament: ~# udevadm test --action=add /sys/class/ block/sdc1
This program is for debugging only, it does not run any program,
specified by a RUN key. It may show incorrect results, because
some values may be different, or not available at a simulation run.
parse_file: reading '/etc/udev/ rules.d/ 05-options. rules' as rules file rules.d/ 05-udev- early.rules' as rules rules.d/ 20-names. rules' as rules file rules.d/ 30-cdrom_ id.rules' as rules file rules.d/ 40-basic- permissions. rules' as rules.d/ 40-permissions. rules' as rules rules.d/ 45-fuse. rules' as rules file rules.d/ 60-persistent- input.rules' as rules.d/ 60-persistent- storage- tape.rules' rules.d/ 60-persistent- storage. rules' as rules.d/ 60-symlinks. rules' as rules file rules.d/ 61-persistent- storage- edd.rules' rules.d/ 65-mdadm. vol_id. rules' as rules rules.d/ 70-persistent- cd.rules' as rules rules.d/ 70-persistent- net.rules' as rules rules.d/ 75-cd-aliases- generator. rules' as rules.d/ 75-persistent- net-generator. rules' as rules file rules.d/ 80-programs. rules' as rules file rules.d/ 85-alsa. rules' as rules file rules.d/ 85-hdparm. rules' as rules file rules.d/ 85-hwclock. rules' as rules file rules.d/ 85-ifupdown. rules' as rules file rules.d/ 85-mdadm. rules' as rules file rules.d/ 85-pcmcia. rules' as rules file rules.d/ 90-modprobe. rules' as rules file rules.d/ 95-hal. rules' as rules file rules.d/ 95-udev- late.rules' as rules file rules.d/ z60_usbmount. rules' as rules file
parse_file: reading '/etc/udev/
file
parse_file: reading '/etc/udev/
parse_file: reading '/etc/udev/
parse_file: reading '/etc/udev/
rules file
parse_file: reading '/etc/udev/
file
parse_file: reading '/etc/udev/
parse_file: reading '/etc/udev/
rules file
parse_file: reading '/etc/udev/
as rules file
parse_file: reading '/etc/udev/
rules file
parse_file: reading '/etc/udev/
parse_file: reading '/etc/udev/
as rules file
parse_file: reading '/etc/udev/
file
parse_file: reading '/etc/udev/
file
parse_file: reading '/etc/udev/
file
parse_file: reading '/etc/udev/
rules file
parse_file: reading
'/etc/udev/
parse_file: reading '/etc/udev/
parse_file: reading '/etc/udev/
parse_file: reading '/etc/udev/
parse_file: reading '/etc/udev/
parse_file: reading '/etc/udev/
parse_file: reading '/etc/udev/
parse_file: reading '/etc/udev/
parse_file: reading '/etc/udev/
parse_file: reading '/etc/udev/
parse_file: reading '/etc/udev/
parse_file: reading '/etc/udev/
unable to open device '/class/block/sdc1'
> Another good diagnostic tool would be the following:
>
> udevinfo -a -p $(udevinfo -q path -n /dev/sda1) (idem)
root@sbg- ajuntament: ~# udevinfo -a -p $(udevinfo -q path -n /dev/sdc1)
Udevinfo starts with the device specified by the devpath and then
walks up the chain of parent devices. It prints for every device
found, all possible attributes in the udev rules key format.
A rule to match, can be composed by the attributes of the device
and the attributes from one single parent device.
looking at device '/block/sdc/sdc1': ="block" dev}==" 8:33" start}= ="63" size}== "976768002" stat}== "18090600 403056096 91848243 734783800"
KERNEL=="sdc1"
SUBSYSTEM=
DRIVER==""
ATTR{
ATTR{
ATTR{
ATTR{
looking at parent device '/block/sdc': ="block" dev}==" 8:32" range}= ="16" removable} =="0" size}== "976773168" stat}== "16512534 1578225 403057816 155993970 30539872 capability} =="12"
KERNELS=="sdc"
SUBSYSTEMS=
DRIVERS==""
ATTRS{
ATTRS{
ATTRS{
ATTRS{
ATTRS{
61307870 734786456 847550580 0 128924260 1003549200"
ATTRS{
looking at parent device pci0000: 00/0000: 00:1d.7/ usb5/5- 4/5-4:1. 0/host4/ target4: 0:0/4:0: 0:0': ="4:0:0: 0" ="scsi" device_ blocked} =="0" type}== "0" scsi_level} =="3" vendor} =="ST350083" model}= ="0AS " state}= ="running" timeout} =="30" iocounterbits} =="32" iorequest_ cnt}==" 0x2cdf67d" iodone_ cnt}==" 0x2cdf67d" ioerr_cnt} =="0x0" modalias} =="scsi: t-0x00" evt_media_ change} =="0" queue_depth} =="1" queue_type} =="none" max_sectors} =="240"
'/devices/
KERNELS=
SUBSYSTEMS=
DRIVERS=="sd"
ATTRS{
ATTRS{
ATTRS{
ATTRS{
ATTRS{
ATTRS{rev}==" "
ATTRS{
ATTRS{
ATTRS{
ATTRS{
ATTRS{
ATTRS{
ATTRS{
ATTRS{
ATTRS{
ATTRS{
ATTRS{
looking at parent device pci0000: 00/0000: 00:1d.7/ usb5/5- 4/5-4:1. 0/host4/ target4: 0:0': ="target4: 0:0"
'/devices/
KERNELS=
SUBSYSTEMS==""
DRIVERS==""
looking at parent device pci0000: 00/0000: 00:1d.7/ usb5/5- 4/5-4:1. 0/host4' : ="host4"
'/devices/
KERNELS=
SUBSYSTEMS==""
DRIVERS==""
looking at parent device pci0000: 00/0000: 00:1d.7/ usb5/5- 4/5-4:1. 0': ="5-4:1. 0" ="usb" ="usb-storage" bInterfaceNumbe r}=="00" bAlternateSetti ng}==" 0" bNumEndpoints} =="02" bInterfaceClass }=="08" bInterfaceSubCl ass}==" 06" bInterfaceProto col}==" 50" modalias} =="usb: v059Fp1010dC683 dc00dsc00dp00ic 08isc06ip50" interface} =="Bulk Only Interface"
'/devices/
KERNELS=
SUBSYSTEMS=
DRIVERS=
ATTRS{
ATTRS{
ATTRS{
ATTRS{
ATTRS{
ATTRS{
ATTRS{
ATTRS{
looking at parent device '/devices/ pci0000: 00/0000: 00:1d.7/ usb5/5- 4': ="usb" dev}==" 189:514" configuration} =="Bulk Only Configuration" bNumInterfaces} ==" 1" bConfigurationV alue}== "1" bmAttributes} =="c0" bMaxPower} ==" 2mA" urbnum} =="227760827" idVendor} =="059f" idProduct} =="1010" bcdDevice} =="c683" bDeviceClass} =="00" bDeviceSubClass }=="00" bDeviceProtocol }=="00" bNumConfigurati ons}==" 1" bMaxPacketSize0 }=="64" speed}= ="480" busnum} =="5" devnum} =="3" version} ==" 2.00" maxchild} =="0" quirks} =="0x0" authorized} =="1" manufacturer} =="LaCie" product} =="LaCie Desktop Hard Drive" serial} =="ST3500830A 9QG617ZE"
KERNELS=="5-4"
SUBSYSTEMS=
DRIVERS=="usb"
ATTRS{
ATTRS{
ATTRS{
ATTRS{
ATTRS{
ATTRS{
ATTRS{
ATTRS{
ATTRS{
ATTRS{
ATTRS{
ATTRS{
ATTRS{
ATTRS{
ATTRS{
ATTRS{
ATTRS{
ATTRS{
ATTRS{
ATTRS{
ATTRS{
ATTRS{
ATTRS{
ATTRS{
ATTRS{
looking at parent device '/devices/ pci0000: 00/0000: 00:1d.7/ usb5': ="usb" dev}==" 189:512" configuration} =="" bNumInterfaces} ==" 1" bConfigurationV alue}== "1" bmAttributes} =="e0" bMaxPower} ==" 0mA" urbnum} =="53" idVendor} =="0000" idProduct} =="0000" bcdDevice} =="0206" bDeviceClass} =="09" bDeviceSubClass }=="00" bDeviceProtocol }=="01" bNumConfigurati ons}==" 1" bMaxPacketSize0 }=="64" speed}= ="480" busnum} =="5" devnum} =="1" version} ==" 2.00" maxchild} =="8" quirks} =="0x0" authorized} =="1" manufacturer} =="Linux 2.6.24-21-server ehci_hcd" product} =="EHCI Host Controller" serial} =="0000: 00:1d.7" authorized_ default} =="1"
KERNELS=="usb5"
SUBSYSTEMS=
DRIVERS=="usb"
ATTRS{
ATTRS{
ATTRS{
ATTRS{
ATTRS{
ATTRS{
ATTRS{
ATTRS{
ATTRS{
ATTRS{
ATTRS{
ATTRS{
ATTRS{
ATTRS{
ATTRS{
ATTRS{
ATTRS{
ATTRS{
ATTRS{
ATTRS{
ATTRS{
ATTRS{
ATTRS{
ATTRS{
ATTRS{
ATTRS{
looking at parent device '/devices/ pci0000: 00/0000: 00:1d.7' : ="0000: 00:1d.7" ="pci" ="ehci_ hcd" vendor} =="0x8086" device} =="0x268c" subsystem_ vendor} =="0x1025" subsystem_ device} =="0x268c" class}= ="0x0c0320" irq}==" 17" local_cpus} =="00000000, 00000000"
KERNELS=
SUBSYSTEMS=
DRIVERS=
ATTRS{
ATTRS{
ATTRS{
ATTRS{
ATTRS{
ATTRS{
ATTRS{
ATTRS{modalias} =="pci: v00008086d00002 68Csv00001025sd 0000268Cbc0Csc0 3i20" numa_node} =="-1" enable} =="1" broken_ parity_ status} =="0" msi_bus} ==""
ATTRS{
ATTRS{
ATTRS{
ATTRS{
looking at parent device '/devices/ pci0000: 00': ="pci0000: 00"
KERNELS=
SUBSYSTEMS==""
DRIVERS==""
It seems all data is ok, no ?
BTW mount command don't show the device:
root@sbg- ajuntament: ~# mount remount- ro) nosuid, nodev) nosuid, nodev) nosuid, nodev,mode= 0755) nosuid, nodev,mode= 1777) security type securityfs (rw) nfs/rpc_ pipefs type rpc_pipefs (rw)
/dev/md0 on / type ext3 (rw,errors=
proc on /proc type proc (rw,noexec,
/sys on /sys type sysfs (rw,noexec,
varrun on /var/run type tmpfs (rw,noexec,
varlock on /var/lock type tmpfs (rw,noexec,
udev on /dev type tmpfs (rw,mode=0755)
devshm on /dev/shm type tmpfs (rw)
devpts on /dev/pts type devpts (rw,gid=5,mode=620)
/dev/md1 on /home type xfs (rw)
securityfs on /sys/kernel/
rpc_pipefs on /var/lib/
But it is mounted on:
/var/run/ usbmount/ ST350083_ 0AS_1/
Thaks.
--
"Si has construido un castillo en el aire, no has perdido el tiempo, es
allí donde debería estar. Ahora debes construir los cimientos debajo de
él." - George Bernard Shaw, escritor irlandés
Marc Montañés * mail: <email address hidden> * telf: 622216489