Bug 113787
Summary: | Automounting Olympus Cameras (others too) on Gnome | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Alexandre Strube <surak> |
Component: | hotplug | Assignee: | Bill Nottingham <notting> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 1 | CC: | exodus, ihok, johnp, mitr, redhat.bugzilla, rvokal, yqu |
Target Milestone: | --- | Keywords: | FutureFeature |
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Enhancement | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2004-11-14 14:28:06 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Alexandre Strube
2004-01-18 01:59:51 UTC
Under the section of this bugzilla report where you copy certain modules.usbmap to usb.usermap, it is not necessary if the following is done (specifically with the Lexar Jumpdrive, but should affect ALL usb-storage devices): Edit the /etc/hotplug/hotplug.functions do the following: Move the following script lines up: if echo "$MODULE" | grep -q "usb-storage" > /dev/null 2>&1 ; then [ -x /usr/sbin/updfstab ] && /usr/sbin/updfstab fi Move them right above this section: if [ -x $HOTPLUG_DIR/$TYPE/$MODULE ]; then debug_mesg Module setup $MODULE for $DESCRIPTION $HOTPLUG_DIR/$TYPE/$MODULE LOADED=true fi The $HOTPLUG_DIR/$TYPE/$MODULE translates to the /etc/hotplug/usb/usb- storage script. It executes mount as indicated in bugzilla #113787, but nothing mounts because no entry is made in /etc/fstab. The reason that the usb.usermap workaround works is because the usb.agent script calls load_drivers () again for the contents of usb.usermap, and since the entry has been made, the mount succeeds. As for the root problem, I am trying to figure out how the /dev/fd0 device becomes owned by the current user. If I can figure this out then the rest should be history. Device nodes such as /dev/fd0 get their permissions changed when a user logs in, by a pam module the name of which I forget at the moment... but the settings for it are contained in /etc/security/console.perms Hope that helps... will this feature be included in fc2 ?? There haven't been any changes made locally in this area. This is about usability, something which differentiates all Redhat's distributions from the rest. Why not make this change then? If I understand correctly, this feature assumes that you unmount the camera *after* it's been unplugged. How, then, is the kernel supposed to flush the cache to the drive? I.e. this calls for data corruption, doesn't it? What difference does it make? The filesystem is mounted as root, so it's read only... I'm adding J5 to the CC of this bug as I suspect it has probably already been partially solved with the new drop of HAL/D-BUS/fstab-sync coming in rawhide. Once gnome-volume-manager is in this should be for the most part solved. Only thing left is to make a libgphoto VFS module so that cameras that are not exported as mass storage can also be used with ease. Just upgraded from Fedora 1 to fedora 2. The Olympus is still not part of updfstab.conf , altough sony has been added. Is there any issue with olympus that we are not aware of? The usb-storage still needs to be created. Well, not quite a progress. Just booted a open version of Xandros and all of this went up automatically (including the printer installation assistant when I plugged it in). Come on, this is not sooo damn complicated to be in bugzilla for more than one release of fedora. Check out rawhide. If your Olympus is mass storage it will add it to /etc/fstab. As my comment says above, once g-v-m is in , which should be sometime this week, it will also be automounted. All this takes a huge amount of work to do correctly, please be patient. g-v-m fixes this in Fedora Core 3. It does not automount. It appears at "MY Computer", which is quite different. You still have to mount it manually, or clicking its icon twice. It should pop up with an import photo dialog. It should also automount it as long as you have gnome-volume-manager installed. Is this problem solved? A customer encountered the same problem and didn't know how to solve it. The OS release is RHEL5.0. (In reply to comment #13) > It does not automount. It appears at "MY Computer", which is quite > different. You still have to mount it manually, or clicking its icon > twice. |