RE: gvfs not support PCI-Express card reader auto-mount

["Yin, Yan" <yan yin intel com>]

Hi David, 
Thanks for your comments, please see my reply below.

Regards,
Yin, Yan


> -----Original Message-----
> From: David Zeuthen [mailto:zeuthen gmail com]
> Sent: Thursday, September 16, 2010 8:12 PM
> To: Yin, Yan
> Cc: gvfs-list gnome org
> Subject: Re: gvfs not support PCI-Express card reader auto-mount
> 
> Hi,
> 
> On Thu, Sep 16, 2010 at 1:55 AM, Yin, Yan <yan yin intel com> wrote:
> > Hi folks,
> > We have a bug that PCI express card reader automount failure in MeeGo,
> according to the comments in ggduvolume.c, only interfaces "USB", "Firewire",
> "sdio" and "optical discs" are allowed for automount.
> > To fix the bug, "scsi" is needed to add as one more interface (see the
> attachments), is this workaround acceptable for upstream?
> 
> No, it is absolutely not acceptable to do this - the whitelist is
> there exactly because if we just mount any random device we run into
> problems if people use GNOME on a machine that is connected to a SAN
> with say 1000 disks. I have personally dealt with bugs like that for
> enterprise customers and that's why it's so restrictive. Bitter
> experience, stuff like that :-)
> 
> > if not and there is a better solution, please kindly let me know, thanks!
> >
> > see http://bugs.meego.com/show_bug.cgi?id=3084
> 
> The problem is how the device is classified. GVfs gets this
> information from udisks. So please file a udisks bug attach the usual
> stuff normally requested, see
> 
>  http://freedesktop.org/wiki/Software/udisks
> 
> at https://bugs.freedesktop.org/enter_bug.cgi?product=udisks and we
> can take it from there.
If the device needs to be re-classified in udisks, which interface (out of the 4) should it belong to? 
Is it seems more like a workaround other than a solution, as the device report the interface as scsi and we intentionally changed it to another one?
> 
>      David