From: cristi <cuciferus@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] gtkam+non-rootuser
Date: Fri, 23 Jun 2006 22:40:46 +0000 [thread overview]
Message-ID: <20060623224046.66b44305@cuci> (raw)
In-Reply-To: <449C19CB.9090108@gmail.com>
On Fri, 23 Jun 2006 18:41:47 +0200
Ralph Slooten <axllent@gmail.com> wrote:
>
> When you plug in your camera into your USB, what does `lsusb` show?
Bus 001 Device 001: ID 0000:0000
Bus 002 Device 010: ID 03f0:6e02 Hewlett-Packard
Bus 002 Device 001: ID 0000:0000
> Then, looking in /proc/bus/usb/[Bus-id_of_your_camera]
:) nothing.... there is nothing in /proc/bus/usb, found it though
in /dev/bus/usb/002/010 but
crw-r--r-- 1 root root 189, 137 Jun 23 22:26 010 so I would still be
able to download the pictures but that does not happen
> You see, the new device created here is the root:plugged one. What
> does yours show? The thing you need to keep in mind here is that you
> have to have rw permissions to that new device file, else you get
> that error. If yours is roor:root or something, do a chown of it and
> then try as user... the chances are it'll work (until you next plug
> your camera is of course).
Searching the net also found this:
"Like most, my camera identifies itself as an external hard disk
connected over the USB bus, using the SCSI transport. To access my
photos, I mount the drive and copy the image files onto my hard disk.
Not all cameras work in this way: some of them use a non-storage
protocol such as cameras supported by gphoto2. In the gphoto case, you
do not want to be writing rules for your device, as is it controlled
purely through userspace (rather than a specific kernel driver). "
here :http://www.reactivated.net/writing_udev_rules.html
> Doing a grep for plugdev in /etc returns /etc/hotplug/usb/usbcam ...
> seems that file is responsible for the permissions, but what happens
> then is a mystery to me ;-)
Followed the instructions there but i got lost quickly as there were
unclear to me so i did not got the script to do something useful
> As for that line being mandatory, no I don't believe so, but about 1
> year ago I had the same issues, got talking with some usb-gurus and
> they said to add that. At that time it did the trick, and since then
> I've kept it ;-)
I should also buy them a beer for a good advice here
Thanks!
--
gentoo-user@gentoo.org mailing list
prev parent reply other threads:[~2006-06-23 22:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-23 11:55 [gentoo-user] gtkam+non-rootuser cristi
2006-06-23 13:42 ` Ralph Slooten
2006-06-23 15:22 ` cristi
2006-06-23 16:41 ` Ralph Slooten
2006-06-23 22:40 ` cristi [this message]
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=20060623224046.66b44305@cuci \
--to=cuciferus@gmail.com \
--cc=gentoo-user@lists.gentoo.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