Ubuntu
devicekit-disks package

karmic: USB drives have funny names in /media

Bug #416470 reported by Bernhard
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
devicekit-disks (Ubuntu)
New
Low
Unassigned

Bug Description

Binary package hint: gvfs

In Karmic, my USB flash drive here is called:

/media/2d8de29a-f8a2-4b5f-979a-fb96fa818c53

while in jaunty it was simply

/media/disk

I liked the old name better. :) Much easier and I had it in many bash scripts, so I would prefer if we could go back to the old names.

Revision history for this message
Chris Coulson (chrisccoulson) wrote :

Is that just the mount-point name or the actual presentable name (as displayed in Nautilus)? What is the output of "gvfs-mount -li"?

Anyway, what you've shown there is just the mount-point, which I think is set by devicekit-disks anyway. The name is the UUID of the volume by the way.

affects: gvfs (Ubuntu) → devicekit-disks (Ubuntu)
Revision history for this message
Bernhard (b.a.koenig) wrote :

The UUID (2d8de29a-....) is also the path name in nautilus. That's the problem. Output of "gvfs-mount -li" is

> gvfs-mount -li
Drive(0): SanDisk Cruzer
  Type: GProxyDrive (GProxyVolumeMonitorGdu)
  ids:
   unix-device: '/dev/sdc'
  themed icons: [drive-removable-media-usb] [drive-removable-media] [drive-removable] [drive]
  is_media_removable=1
  has_media=1
  is_media_check_automatic=1
  can_poll_for_media=1
  can_eject=1
  can_start=0
  can_stop=0
  start_stop_type=shutdown
  Volume(0): 4.1 GB Filesystem
    Type: GProxyVolume (GProxyVolumeMonitorGdu)
    ids:
     uuid: '2d8de29a-f8a2-4b5f-979a-fb96fa818c53'
     unix-device: '/dev/sdc1'
    themed icons: [drive-removable-media-usb] [drive-removable-media] [drive-removable] [drive]
    can_mount=1
    can_eject=1
    should_automount=1
    Mount(0): 4.1 GB Filesystem -> file:///media/2d8de29a-f8a2-4b5f-979a-fb96fa818c53
      Type: GProxyMount (GProxyVolumeMonitorGdu)
      themed icons: [drive-removable-media-usb] [drive-removable-media] [drive-removable] [drive]
      can_unmount=1
      can_eject=1
      is_shadowed=0

Revision history for this message
Chris Coulson (chrisccoulson) wrote :

Hmmm, I think that using the UUID (or label, if one exists) as the mount point is more of a design decision than a bug. UUID's and labels are more persistent than having "/media/disk", "/media/disk2" etc, which get allocated depending on the order that you insert the disks. UUID's and labels are more descriptive too.

Changed in devicekit-disks (Ubuntu):
importance: Undecided → Low
Revision history for this message
Chris Coulson (chrisccoulson) wrote :

This is actually already reported as bug 390304

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.