Hi
Is there a possibility to mount an iso file to be able to access the
information on it?
I know this is possible on Solaris/Unix so I hope that also under
SuSE/Linux!
Thank you.
--
ovidiu pascui
Hi, You can mount it with this command: mkdir /mnt/iso mount myiso.iso /mnt/iso/ -t iso9660 -o ro,loop=/dev/loop0 Where myiso.iso is your ISO file. On Tuesday 24 June 2003 12:04, ovidiu pascui wrote:
Hi Is there a possibility to mount an iso file to be able to access the information on it? I know this is possible on Solaris/Unix so I hope that also under SuSE/Linux! Thank you.
-- Best regards ******************************** Nick Katsamas Systems Administration Athens NOC - FORTHnet S.A. e-Mail: nkat@forthnet.gr ********************************
On Tue, 24 Jun 2003, Nick Katsamas wrote:
You can mount it with this command: mkdir /mnt/iso mount myiso.iso /mnt/iso/ -t iso9660 -o ro,loop=/dev/loop0 Where myiso.iso is your ISO file.
I do it this way mount myiso.iso /mnt/iso -t iso9660 -o loop I think loop=/dev/loop0 may be a default option. While I have never experimented with what happens if I write to the ISO filesystem, or whether it is supported by mount for iso9660. Anyone? Rohit ********************************************************* Disclaimer This message (including any attachments) contains confidential information intended for a specific individual and purpose, and is protected by law. If you are not the intended recipient, you should delete this message and are hereby notified that any disclosure, copying, or distribution of this message, or the taking of any action based on it, is strictly prohibited. ********************************************************* Visit us at http://www.mahindrabt.com
On Tue, 2003-06-24 at 12:40, Rohit wrote:
On Tue, 24 Jun 2003, Nick Katsamas wrote:
You can mount it with this command: mkdir /mnt/iso mount myiso.iso /mnt/iso/ -t iso9660 -o ro,loop=/dev/loop0 Where myiso.iso is your ISO file.
I do it this way
mount myiso.iso /mnt/iso -t iso9660 -o loop
I think loop=/dev/loop0 may be a default option. While I have never experimented with what happens if I write to the ISO filesystem, or whether it is supported by mount for iso9660. Anyone?
Hi
I tried both options (with and without loop0) but I always get this
error message.
wolf:mount x.iso /mnt/iso1 -t iso9660 -o ro,loop=/dev/loop0
mount: wrong fs type, bad option, bad superblock on /dev/loop0,
or too many mounted file systems
--
ovidiu pascui
On Tue, 24 Jun 2003, ovidiu pascui wrote:
I tried both options (with and without loop0) but I always get this error message.
wolf:mount x.iso /mnt/iso1 -t iso9660 -o ro,loop=/dev/loop0 mount: wrong fs type, bad option, bad superblock on /dev/loop0, or too many mounted file systems
Send me the output of following. pwd file x.iso ********************************************************* Disclaimer This message (including any attachments) contains confidential information intended for a specific individual and purpose, and is protected by law. If you are not the intended recipient, you should delete this message and are hereby notified that any disclosure, copying, or distribution of this message, or the taking of any action based on it, is strictly prohibited. ********************************************************* Visit us at http://www.mahindrabt.com
On Tue, 24 Jun 2003, ovidiu pascui wrote:
Send me the output of following. pwd file x.iso ovi@xxx:~/temp> pwd /home/ovi/temp ovi@xxx:~/temp> file x.iso x.iso: data
I can not help you. My findings are the same as yours. I was trying to guess whether you were mounting to the directory where you already are [not so].. Have you tried to do this as root? I can do it only as root. Else not permitted... rohit ********************************************************* Disclaimer This message (including any attachments) contains confidential information intended for a specific individual and purpose, and is protected by law. If you are not the intended recipient, you should delete this message and are hereby notified that any disclosure, copying, or distribution of this message, or the taking of any action based on it, is strictly prohibited. ********************************************************* Visit us at http://www.mahindrabt.com
On Tue, 2003-06-24 at 14:03, Rohit wrote:
I can not help you.
My findings are the same as yours. I was trying to guess whether you were mounting to the directory where you already are [not so]..
Have you tried to do this as root? I can do it only as root. Else not permitted...
yes, I tried to mount it using su.
There is also a nice app called EzISO. I think I got it from apps.kde.org or somewhere. It makes it very easy to mount iso files (also as user) Regards, Marco. On Tuesday 24 June 2003 14:07, ovidiu pascui wrote:
On Tue, 2003-06-24 at 14:03, Rohit wrote:
I can not help you.
My findings are the same as yours. I was trying to guess whether you were mounting to the directory where you already are [not so]..
Have you tried to do this as root? I can do it only as root. Else not permitted...
yes, I tried to mount it using su.
Send me the output of following. pwd file x.iso ovi@xxx:~/temp> pwd /home/ovi/temp ovi@xxx:~/temp> file x.iso x.iso: data
I can not help you.
My findings are the same as yours. I was trying to guess whether you were mounting to the directory where you already are [not so]..
I tried this on the RedHat box I use at work, and got the following: $ file rhl73-disc1.iso rhl73-disc1.iso: ISO 9660 CD-ROM filesystem data Is there a difference in the file command that RedHat and SuSE include? -- trey
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, On Tue, 24 Jun 2003, Trey Gruel wrote:
I tried this on the RedHat box I use at work, and got the following:
$ file rhl73-disc1.iso rhl73-disc1.iso: ISO 9660 CD-ROM filesystem data
How nice of them.
Is there a difference in the file command that RedHat and SuSE include?
Yes, it's the /etc/magic file that determines this. Looks like SuSE's
could need an update. You can simply copy over Red Hat's magic file or
simply add the missing parts from there to the SuSE one.
Bye,
LenZ
- --
- ------------------------------------------------------------------
Lenz Grimmer
On Tue, 24 Jun 2003 21:20:07 +0200 (CEST)
Lenz Grimmer
Yes, it's the /etc/magic file that determines this. Looks like SuSE's could need an update. You can simply copy over Red Hat's magic file or simply add the missing parts from there to the SuSE one.
I don't know why SuSE is shipped with such an outdated file package. For example the one in 8.1 is version 3.37 while the latest is 4.03. This one package I always replace. Charles -- Microsoft is not the answer. Microsoft is the question. NO (or Linux) is the answer. (Taken from a .signature from someone from the UK, source unknown)
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Tue, 24 Jun 2003, Charles Philip Chan wrote:
I don't know why SuSE is shipped with such an outdated file package. For example the one in 8.1 is version 3.37 while the latest is 4.03. This one package I always replace.
I assume you told SuSE about this as well? http://www.suse.de/feedback/
Bye,
LenZ
- --
- ------------------------------------------------------------------
Lenz Grimmer
On Wed, 25 Jun 2003 09:58:21 +0200 (CEST)
Lenz Grimmer
I assume you told SuSE about this as well? http://www.suse.de/feedback/
I haven't yet, but I will send a feedback. Charles -- I did this 'cause Linux gives me a woody. It doesn't generate revenue. (Dave '-ddt->` Taylor, announcing DOOM for Linux)
On Tue, 24 Jun 2003, Trey Gruel wrote:
I tried this on the RedHat box I use at work, and got the following:
$ file rhl73-disc1.iso rhl73-disc1.iso: ISO 9660 CD-ROM filesystem data
Is there a difference in the file command that RedHat and SuSE include?
There must be [by results] a difference in contents of the way they have implemented magic file. :-( In this case RHL seems to have bagged the award. Rohit ********************************************************* Disclaimer This message (including any attachments) contains confidential information intended for a specific individual and purpose, and is protected by law. If you are not the intended recipient, you should delete this message and are hereby notified that any disclosure, copying, or distribution of this message, or the taking of any action based on it, is strictly prohibited. ********************************************************* Visit us at http://www.mahindrabt.com
On 24 Jun 2003 13:09:10 +0200
ovidiu pascui
wolf:mount x.iso /mnt/iso1 -t iso9660 -o ro,loop=/dev/loop0 mount: wrong fs type, bad option, bad superblock on /dev/loop0, or too many mounted file systems
You can try udf instead of iso9660 as the fstype to see if it works. Charles -- "Whip me. Beat me. Make me maintain AIX." (By Stephan Zielinski)
In article <1056452949.3409.1.camel@wolf.physik.uni-halle.de>,
ovidiu pascui
Hi I tried both options (with and without loop0) but I always get this error message. wolf:mount x.iso /mnt/iso1 -t iso9660 -o ro,loop=/dev/loop0 mount: wrong fs type, bad option, bad superblock on /dev/loop0, or too many mounted file systems I would just use:
mount -o loop x.iso /mnt works for me ;-) nik
Will this also work if you create an image of a floppy? Here's what I want to do: 1. created an image of a floppy using dd 2. modify some files inside the image 3. copy image to floppy 4. repeat process (about 200 times) Nick Katsamas wrote:
Hi,
You can mount it with this command:
mkdir /mnt/iso
mount myiso.iso /mnt/iso/ -t iso9660 -o ro,loop=/dev/loop0
Where myiso.iso is your ISO file.
On Tuesday 24 June 2003 12:04, ovidiu pascui wrote:
Hi Is there a possibility to mount an iso file to be able to access the information on it? I know this is possible on Solaris/Unix so I hope that also under SuSE/Linux! Thank you.
--
+------------------------------------------
| José J. Cintrón -
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, On Tue, 24 Jun 2003, Jose J. Cintron wrote:
Will this also work if you create an image of a floppy?
Well, sure! You can loop-mount any filesystem.
Here's what I want to do:
1. created an image of a floppy using dd 2. modify some files inside the image 3. copy image to floppy 4. repeat process (about 200 times)
No problem.
dd if=/dev/fd0 of=/tmp/foo
mount -t vfat -o loop /tmp/foo /mnt
cd /mnt
<modify the files>
umount /mnt
dd if=/tmp/foo of=/dev/floppy
Bye,
LenZ
- --
- ------------------------------------------------------------------
Lenz Grimmer
I don't know why everybody needs all those options, but I always run: mount -o loop <path-to-iso> <path-to-mountpoint> and I've never had any problems with it with SuSE 8.2. Op dinsdag 24 juni 2003 11:04, schreef ovidiu pascui:
Hi Is there a possibility to mount an iso file to be able to access the information on it? I know this is possible on Solaris/Unix so I hope that also under SuSE/Linux! Thank you.
-- ICQ: 51854780
participants (10)
-
Charles Philip Chan -
Jose J. Cintron -
Lenz Grimmer -
Marco Karsten -
Nick Katsamas -
Nik -
ovidiu pascui -
Rohit -
Trey Gruel -
Z_God