You are not logged in.
Pages: 1
One of my users asked to the possibility of mounting iso files.
In order to accomplish that I created a directory called /mnt/isoimage and a directory called /home/iso, the latter with chmod 770, I created a group for people who can mount iso images and /home/iso is now of root:isomounters . Added her to isomounters group and added a line to fstab:
/home/iso/image.iso /mnt/isoimage auto ro,user,noauto,noexec,loop 0 0
Finally I told her: use ln -s /your/image/full/path.iso /home/iso/image.iso && mount /mnt/isoimage
This simple solution works, but I dislike users may use /home/iso as storage place instead of only create the symbolic link.
Is it avoidable?
Thanks
Offline
Don't you need -o loop and -t iso9660 mount options in your fstab?
About your problem: i don't know, it basically comes down to the question whether one can use different "source" files (dev nodes etc) for one fstab entry. i'ld like to know this too
< Daenyth> and he works prolifically
4 8 15 16 23 42
Offline
Maybe it is more clear:
#<file system> <dir> <type> <options> <dump> <pass>
/home/iso/image.iso /mnt/isoimage auto ro,user,noauto,noexec,loop 0 0
As you can see the option loop IS set, about the filesystem I usually set auto for removable devices, yet... Yes, iso9660 is more precise.
Last edited by ezzetabi (2007-02-21 22:35:04)
Offline
I think that what you'll like to do is possible with fuseiso (it's in aur)
Offline
As you can see the option loop IS set, about the filesystem I usually set auto for removable devices, yet... Yes, iso9660 is more precise.
You're right, my mistake
FuseIso is a FUSE module to mount ISO filesystem images (.iso, .nrg, .bin, .mdf and .img files). It currently support plain ISO9660 Level 1 and 2, Rock Ridge, Joliet, and zisofs.
neat !
< Daenyth> and he works prolifically
4 8 15 16 23 42
Offline
Pages: 1