From: Kay Sievers <kay.sievers@vrfy.org>
To: linux-hotplug@vger.kernel.org
Subject: Re: Problem getting udev to see Kodak camera?
Date: Tue, 23 Nov 2004 23:45:20 +0000 [thread overview]
Message-ID: <1101253520.3327.8.camel@localhost.localdomain> (raw)
In-Reply-To: <41A2C9EA.6040906@cox.net>
On Tue, 2004-11-23 at 00:26 -0500, Christian Convey wrote:
Is this camera a generic storage device? If not, you will not get a
device node for. Try libgphoto2:
http://www.gphoto.org/proj/libgphoto2/support.php
> I've got a Kodak EasyShare DX6490, hooked up to my Toshiba P25-S507
> laptop. I'm running Debian Sarge with their 2.6.8-1 kernel and I've
> installed Sarge's udev package (version 046).
>
> I can't get my udev rules to show my camera in the /dev filesystem, and
> I'm concerned about the results of a test I ran. Anyone mind commenting? ...
> pascal:/sys/bus/usb/devices# udevinfo -p
> /sys/devices/pci0000:00/0000:00:1d.1/usb3/3-1/3-1.2/3-1.2:1.0 -a
udev does not care about /sys/devices/* devices. There will never be a
device node! The "dev" files are only for class and block devices.
Good luck,
Kay
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://productguide.itmanagersjournal.com/
_______________________________________________
Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
next prev parent reply other threads:[~2004-11-23 23:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-23 5:26 Problem getting udev to see Kodak camera? Christian Convey
2004-11-23 23:45 ` Kay Sievers [this message]
2004-11-24 1:29 ` Christian Convey
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=1101253520.3327.8.camel@localhost.localdomain \
--to=kay.sievers@vrfy.org \
--cc=linux-hotplug@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).