Linux - GeneralThis Linux forum is for general Linux questions and discussion.
If it is Linux Related and doesn't seem to fit in any other forum then this is the place.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
From what I can tell, the problem is that an iso is not a filesytstem. The mount command cannot create a file system, just interpret it. I think the problem is that we need something that can make an ISO file be interpreted or perceived as a device-filesystem. The mount command cannot do it for us....
If your program does a major minor check this thought will for sure fail. But I was just philosophing ...When you mount it as loop device, assume you get next available loop device :MOUNTED=$(losetup -f), how about having your software pointing to the /dev/$MOUNTED.. The major and minor of this will reflect a loopdev and not a CD or DVD, but then again the underlying file will reflect DVD... I have no idea about it but just a thought.
Last edited by my.dying.bride; 11-08-2006 at 02:47 AM.
DVD contents resides on a ISO9660 filesystem. We can have 2 different views of these contents:
An ISO image, i.e. like your hard disk partition.
The individual files (e.g. VOB file), i.e. like the files in yours file system.
The "mount" command allows you to mount the former into the latter, hence it only supports a directory for the second argument. But, you already have the ISO file, and the application also expects an ISO file. So what do you actually want?
First we remove /dev/dvd by "mv /dev/dvd /dev/dvd.bk". Then, 2 possibilities depending on what your application expects:
The application expects the image to be in /dev/dvd. Then, simple. Just "ln -s /path/to/file.iso /dev/dvd", and it is done.
The application expects the image to be in /dev/dvd, plus that it is a device. Then you can use "losetup /dev/dvd /path/to/file.iso". "losetup" is actually what the system does automatically when you do "mount -o loop".
Of course, in both cases, you need to revert /dev/dvd from /dev/dvd.bk after use.
hey, thanks for the "dvd://path/to/dvd.iso", it worked great for me with xine. It would be awesome if someone patched xine and other media players to be able to open ISOs with this method, through the gui, but then again, there's no real way to tell if an iso is a movie or not. Anyways, I've always just resorted to adding all the files on a mounted iso to a playlist, then seeking through all of it to try and find the actual movie...this is a MUCH better option. Again, Thanks!
# if the cd/dvd is not visible in Nautilus make a shortcut to eject the cd/dvd
# create shell script to toggle cd/dvd eject, save in save place like root of profile /home/ME/dvdToggle.sh
# make sure to put the shebang as the first line in the script #!/bin/sh
# Make script executable
# click and drag the executable shell script to the upper menu bar to make a shortcut, change the icon as desired.