After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 155636 - mounts too much on session start
mounts too much on session start
Status: RESOLVED FIXED
Product: gnome-volume-manager
Classification: Deprecated
Component: general
unspecified
Other Linux
: Normal normal
: ---
Assigned To: Robert Love
Robert Love
Depends on:
Blocks:
 
 
Reported: 2004-10-17 12:46 UTC by Sjoerd Simons
Modified: 2005-08-03 19:01 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
Adds option to not mount fixed disks on startup and honor automount options (7.51 KB, patch)
2004-10-17 12:50 UTC, Sjoerd Simons
none Details | Review
patch to g-v-m so that it will honour volume.policy.should_mount (519 bytes, patch)
2004-12-05 02:23 UTC, Scott McKenzie
none Details | Review

Description Sjoerd Simons 2004-10-17 12:46:11 UTC
I got some complaints from debian users that gvm mounts too much on startup.
After some research it seems that g-v-m just mounts everything on startup
even if ``mount removable drives/media'' is turned off.

More ``problematic'' is that some people don't seem to like it that their
static disks are mounted on startup. For example some stray windows or os X 
partition
Comment 1 Sjoerd Simons 2004-10-17 12:50:00 UTC
Created attachment 32690 [details] [review]
Adds option to not mount fixed disks on startup and honor automount options

The patch adds an option to not mount fixed disks add g-v-m start. And doesn't
let g-v-m mount media/volumes that wouldn't have been mounted while g-v-m was
running
Comment 2 Scott McKenzie 2004-12-05 02:15:50 UTC
Shouldn't g-v-m honour HAL's policies?  The default storage-policy.fdi specifies
that volumes on non-hotpluggable and non-removable storage devices should not be
mounted.  Unfortunately it does not have a rule to enforce this policy on the
actual volumes.  Adding the following to the default policy (or a user policy)
will propagate that policy to the volumes on the device:
<device>
  <match key="block.is_volume" bool="true">
    <match key="volume.fsusage" string="filesystem">
      <match key="@block.storage_device:storage.policy.should_mount" bool="false">
        <merge key="volume.policy.should_mount" type="bool">false</merge>
      </match>
    </match>
  </match>
</device>

g-v-m can then be patched to not mount volumes where volume.policy.should_mount
is false.
Comment 3 Scott McKenzie 2004-12-05 02:23:39 UTC
Created attachment 34494 [details] [review]
patch to g-v-m so that it will honour volume.policy.should_mount
Comment 4 Jeffrey Stedfast 2005-08-03 19:01:37 UTC
HAL's policys are going away shortly, so this fix is at best short-term.

that said, I believe this problem to be fixed in CVS already anyway via other means.

		if (libhal_device_property_exists (ctx, drive, "storage.hotpluggable", NULL)
		    && libhal_device_get_property_bool (ctx, drive, "storage.hotpluggable", NULL))
			mount = config.automount_drives;
		else if (libhal_device_property_exists (ctx, drive, "storage.removable", NULL)
			 && libhal_device_get_property_bool (ctx, drive, "storage.removable", NULL))
			mount = config.automount_media;
		else
			mount = TRUE;
		libhal_free_string (drive);
		
		if (!mount)
			continue;