dd iso to usb stick - what filesystem is used?

[bertaerts]

Code: Select all

su
cd Mageia-4-beta2-LiveDVD-KDE4-x86_64-DVD
mount -o loop Mageia-4-beta2-LiveDVD-KDE4-x86_64-DVD.iso /mnt/iso


is a perfectly readable iso file.

Code: Select all

dd if=Mageia-4-beta2-LiveDVD-KDE4-x86_64-DVD.iso of=/dev/sde

makes a USB stick with a bootable and hidden partition.
What filesystem is used?
GParted says unknown file system
I can not mount the USB stick in KDE to have a look at the files.
How do I get access to the USB stick?

[Ken-Bergen]

diskdrake sees mine as a "Hidden HPFS/NTFS" partition but will not mount it without first formatting it.

Question is, why do you wish to mount it and look at the files in it?

[lula]

You can mount the whole device, not the first partition, the system still sees it as an iso filesystem (e.g. mine is /dev/sdb)

Code: Select all

mount /dev/sdb /mnt/
mount | grep sdb
/dev/sdb on /mnt type iso9660 (ro,relatime)


[doktor5000]

Question is, why do you wish to mount it and look at the files in it?

Yep, as that can easily done via a loop mount as you showed already ...

[jiml8]

To mount a particular partition within an iso:

Find the partitions in the image:

Code: Select all

parted imagename.iso unit b print

Choose the desired partition and assign it to an available loop device:

Code: Select all

losetup -o<starting byte of partition from previous command> /dev/loopN imagename.iso

Then mount it:

Code: Select all

mount /dev/loopN mountpoint

Later, unmount it and release the loop device:

Code: Select all

umount mountpoint
losetup -d /dev/loopN

[doktor5000]

FWIW, first and second step can be combined via kpartx. kpartx -l to list partitions and kpartx -a to automatically create the loop devices.

[filip]

But it would still be read only?

[doktor5000]

Yep, if you want to modify the image contents, you need to mount it, copy the contents to a separate directory, do your modifications there and recreate the image.
For specific modifications there are apps like isomaster, but iso images in general (and in turn loopback mounts of those) are per definition readonly.