Comment 9 for bug 10999

Revision history for this message
In , Mike Mestnik (cheako) wrote : Re: Bug#284492: devfs.rules: Don't change NAME into a port(host?/bus?) specific target, for gvm.

--- Sjoerd Simons <email address hidden> wrote:

> On Mon, Dec 06, 2004 at 08:11:54PM +0100, Marco d'Itri wrote:
> > reassign 284492 gnome-volume-manager
> > thanks
> >
> > On Dec 06, "M Mestnik) (Shared Account" <email address hidden>
> wrote:
> >
> > > Gnome-volume-manager mounts my cds with the REAL device "NAME=".
> It's good
> > > to see that it's not being set to "hdc" but it's still being set to
> a
> > > port(host?/bus?) specific name. I subjest that the NAME="%c{2}"
> since this
> > > will allways be easy to see as a cdrom. Then SYMLINK="%k %c{1}".
> >
> > There is no reason to change the default configuration of udev.
> > I'm reassigning this bug to g-v-m, in the possibility that its
> > maintainer has something to add.
>
> Are you just guess that it will behave that way, or does it really
> behave that
> way? The current unstable hal and g-v-m shouldn't (They check
> volume.policy.desired_mount_point).
>
The name changed after I started using udev's devfs.rules. These rules
for whatever reason change the name to the true devfs name and make a
symlink to the compat(%n) name given by upstream(guessing the kernel).

So udev changed the name of the dir made by pmount, is gvm even involved
in this proces? I would guess that gvm simply runes mount and maby pmount
dereferences the symlinks.

Also how is volume.policy.desired_mount_point to be changed, so the user
can use only devfs names or only compat names or only old-compat names?

> If it was just a guess, please close this bug.. Otherwise i need a lot
> more
> info :)
>
> Sjoerd
> --
> Isn't it interesting that the same people who laugh at science fiction
> listen to weather forecasts and economists?
> -- Kelvin Throop III
>

__________________________________
Do you Yahoo!?
Yahoo! Mail - 250MB free storage. Do more. Manage less.
http://info.mail.yahoo.com/mail_250