Re: VFS integration with kernel mounts
- From: Alexander Larsson <alexl redhat com>
- To: David Zeuthen <david fubar dk>
- Cc: "gnome-vfs-list gnome org" <gnome-vfs-list gnome org>, "gtk-devel-list gnome org" <gtk-devel-list gnome org>, Jerry Haltom <wasabi larvalstage net>
- Subject: Re: VFS integration with kernel mounts
- Date: Mon, 07 May 2007 09:07:52 +0200
On Fri, 2007-05-04 at 11:48 -0400, David Zeuthen wrote:
> On Fri, 2007-05-04 at 09:00 -0500, Jerry Haltom wrote:
> > Why doesn't HAL use UUIDs?
>
> Doesn't exactly make sense. Maybe you mean: "Why does my mount points
> not use UUID?". Understand that HAL [1] is only a source of information
> + mechanism to allow g-v-m, KDE, gnome-mount, whatever to mount file
> systems from removable drives at a given location.
>
> It's obviously policy what mount point (and mount options) to use; so
> that needs to come from the desktop session. So gnome-mount stores this
> in gconf (see the gnome-mount man page) and if there is no settings
> stored for a given volume we use reasonable and tasteful defaults. And
> it's not reasonable to prefer
>
> /media/12345-83294230-4230423-323232
>
> over
>
> /media/EOS_DIGITAL
>
> In addition some file systems don't have UUID's and some instances of a
> file systems leaves it unset (my EOS 5D leaves the UUID blank when
> formatting the CF card with FAT16). So you need to use the fs label
> which is not always unique... (again, my EOS 5D always chooses
> EOS_DIGITAL).
So, UUID file identifiers look horrible, etc. I agree. But why are we
then arguing for using them in gvfs? The same arguments apply there.
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Alexander Larsson Red Hat, Inc
alexl redhat com alla lysator liu se
He's a gun-slinging umbrella-wielding paramedic in a wheelchair. She's a
scantily clad red-headed femme fatale with her own daytime radio talk show.
They fight crime!
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]