From: Moshe Yudkowsky <msha5_17@bl.com>
To: linux-hotplug@vger.kernel.org
Subject: libgphoto2 calls hotplug script with wrong variables
Date: Mon, 05 Dec 2005 23:31:51 +0000 [thread overview]
Message-ID: <4394CDE7.1070008@bl.com> (raw)
I can fix this myself, but I'm curious to know if anyone else has fixed
it, if it needs a bug report, or if something is very wrong with the way
my system works.
My udev directory has a file called "libgphoto2.rules" -- I didn't put
it there, but I don't know which package did (from the changelog, I
suspect it was libgphoto2 package using a utility called
"print-udev-rules").
In any case, when I plug in a USB camera, the file will use manufacturer
and product code to find RUN+="/etc/hotplug/usb/libgphoto2".
Here's some problems:
(1a) I keep on reading on this list that /etc/hotplug is supposed to be
deprecated, and yet here's /etc/hotplug that looks pretty official.
(1b) I also keep reading about HAL, but it isn't installed on my machine
accoring to dpkg. Should it be? If it is supposed to be, why isn't in
installed -- which script should have installed it?
(2) The script libgphoto2 doesn't work. The goal of libgphoto2 is to set
the device created by hotplug (later udev) so that anyone in group
$CAMERA can use it, but that doesn't happen, and here's why.
The script uses the environment variable $DEVICE. Now, that's
interesting, because the udev man page doesn't mention this variable in
the ENVIRONMENT section of the page at all, and it makes me wonder just
what variables are available to anything I run as a RUN+= script. Not
documented?
Problem:
The $DEVICE isn't equivalent to $DEVPATH. For example,
DEVICE is "/proc/bus/usb/002/010"
while
DEVPATH is "/devices/pci0000:00/0000:00:10.1/usb2/2-1/2-1:1.0".
Neither of these is any good when I want to configure the port that's
been created; what I need is the USB bus device path so I can set group
permissions. E.g., what I need is
/dev/bus/usb/002/010
No dobut I will find the correct magic combination, but if anyone has
already solved this problem, please let me know.
--
Moshe Yudkowsky
work: http://www.Disaggregate.com
book: http://www.PebbleAndAvalanche.com
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_idv37&alloc_id\x16865&op=click
_______________________________________________
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 reply other threads:[~2005-12-05 23:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-05 23:31 Moshe Yudkowsky [this message]
2005-12-06 0:06 ` libgphoto2 calls hotplug script with wrong variables Marco d'Itri
2005-12-06 4:30 ` Moshe Yudkowsky
2005-12-06 8:18 ` Marco d'Itri
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=4394CDE7.1070008@bl.com \
--to=msha5_17@bl.com \
--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).