udev, hal, and usb mass storage.

[Behdad Esfahbod]

On Mon, 19 Apr 2004, Anthony Metcalf wrote:

> On Mon, 19 Apr 2004 07:44:40 -0400
> Behdad Esfahbod <behdad at cs.toronto.edu> wrote:
>
> > Hi,
> >
> > I think you should look for it under gnome-volume-manager.  IMHO
> > it should take care of the link, and it should be easy to do
> > there.
> >
> > behdad
>
> That was my first thought, but Gnome-volume-manager needs the info
> before it can do anything with it. It is hal's job to provide that info.
> At this moment in time, hal does not know about the link, therefore gvm
> *cannot* know about the link.

Are you sure?  I'm not.  hal sends a notice about /dev/sda1 has
been added, then g-v-m on reading /etc/fstab notices that
/dev/keyfob is a symlink to /dev/sda1, so it mounts it.  What's
wrong with this scenario?  On the other hand, hal cannot provide
the symlink name, as there may be a lot of them.  Which one
should it select?

And about making /dev/sda1 a symlink, it *can* have sideeffects.
Maybe not in your scenario, but in other cases.  At least
/dev/sda1 is not detected as a block device anymore.  But well,
you can tell udev to create both /dev/sda1 and /dev/keyfob as
block devices with the same major-minor.

--behdad
  behdad.org

_______________________________________________
hal mailing list
hal at freedesktop.org
http://freedesktop.org/mailman/listinfo/hal