public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: art@usfltd.com
Cc: linux-kernel@vger.kernel.org, torvalds@osdl.org
Subject: Re: usb-scanner-cameras kernel-2.6.22 and udev-095 problem
Date: Thu, 17 May 2007 11:14:27 -0700	[thread overview]
Message-ID: <20070517181427.GB5735@kroah.com> (raw)
In-Reply-To: <20070517120544.d2hnzayns4o8scks@67.106.77.50>

On Thu, May 17, 2007 at 12:05:44PM -0500, art@usfltd.com wrote:
>  greg
> 
> >> You didn't answer my, "what distro are you using" question.  Also, what
>  package created the udev rule that creates the above symlink?
> 
>  distro fc6
>  Linux xxx.xxx 2.6.22-rc1-200705170855cfq6-g0479ea0e #134 SMP PREEMPT Thu May 
>  17 09:13:26 CDT 2007 x86_64 x86_64 x86_64 GNU/Linux

You answered the first question above, not the second :(

>  2.6.20
> 
>  $ udevtest /class/usb_device/usbdev2.10
>  main: looking at device '/class/usb_device/usbdev2.10' from subsystem 
>  'usb_device'
>  run_program: '/bin/sh -c 'K=usbdev2.10; K=${K#usbdev}; printf 
>  bus/usb/%03i/%03i ${K%%.*} ${K#*.}''
>  run_program: '/bin/sh' (stdout) 'bus/usb/002/010'
>  run_program: '/bin/sh' returned with status 0
>  udev_rules_get_name: rule applied, 'usbdev2.10' becomes 'bus/usb/002/010'
>  udev_rules_get_name: add symlink 'scanner-usbdev2.10'
>  udev_device_event: device '/class/usb_device/usbdev2.10' already in 
>  database, validate currently present symlinks
>  udev_node_add: creating device node '/dev/bus/usb/002/010', major = '189', 
>  minor = '137', mode = '0644', uid = '0', gid = '0'
>  udev_node_add: creating symlink '/dev/scanner-usbdev2.10' to 
>  'bus/usb/002/010'
>  main: run: 'socket:/org/kernel/udev/monitor'
>  main: run: '/lib/udev/udev_run_devd'
>  main: run: 'socket:/org/freedesktop/hal/udev_event'
>  main: run: '/sbin/pam_console_apply /dev/bus/usb/002/010 
>  /dev/scanner-usbdev2.10'

And if you run that 'udevtest' command on 2.6.21 what happens?

Again, you have not shown me the udev rule that adds that symlink, is it
something you added by hand, or something that Fedora added to the rules
file?

thanks,

greg k-h

  reply	other threads:[~2007-05-17 18:17 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-17 17:05 usb-scanner-cameras kernel-2.6.22 and udev-095 problem art
2007-05-17 18:14 ` Greg KH [this message]
  -- strict thread matches above, loose matches on Subject: below --
2007-06-07  3:11 art
2007-06-07  3:37 ` Greg KH
2007-06-07  2:26 art
2007-06-06  0:20 art
2007-06-06  5:34 ` Greg KH
2007-05-18  0:00 art
2007-05-24 17:53 ` Greg KH
     [not found]   ` <6bffcb0e0706050518l53628a55k7b91ce38e272289d@mail.gmail.com>
2007-06-05 21:46     ` Greg KH
2007-05-16 19:58 art
2007-05-17  5:14 ` Greg KH
2007-05-15 17:42 art
2007-05-15 18:02 ` Linus Torvalds
2007-05-15 22:51 ` Greg KH

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20070517181427.GB5735@kroah.com \
    --to=greg@kroah.com \
    --cc=art@usfltd.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@osdl.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox