loopback devices

[Johannes Berg]

On Sat, 2006-10-28 at 00:29 +0200, Robert Millan wrote:

> Can that be handled separately?  One could have a script that invokes losetup
> via gksu, and register it as a file handler for *.iso (I do that myself).

Sure. But that requires being able to su/sudo.

> I'm not sure if there is any advantage in handling the actual mount in hal/gvm.
> Perhaps it makes more sense to put it all together in the same script?

I guess, especially since you say:

> I was thinking only about users who have access to root account, actualy.

If you just want some GUI integration you don't need hal I'd think, a
script should be fine.

> > Basically, mounting CDs, USB devices etc works by just plugging them in.
> > But loop devices are always there and the iso images are also always
> > there so it needs an explicit by the user to associate some file with a
> > loop and then mount that.
> 
> There's this new path, /dev/loop/[0-9], where device nodes are linked/unlinked
> dynamicaly unlike /dev/loop[0-9].  Maybe that helps?

Does that really happen? Does the kernel do uevents for loop devices?

johannes
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 828 bytes
Desc: This is a digitally signed message part
Url : http://lists.freedesktop.org/archives/hal/attachments/20061028/b5fe64ec/attachment.pgp