very easy and powerfull way for make ISO file

[mfaridi]

which way is best and powerful way for make ISO file from directories ????

[erno]

You can use mkisofs to create iso files. It's included in cdrtools package.

[scottro]

The man page has various examples as well, including one that does exactly what you're asking.

[hydra]

http://www.freebsd.org/doc/en_US.ISO...ating-cds.html

[ephemera]

if you want something easy and powerful go with 'k3b'.
its a front end for the various cd/dvd tools like mkisofs, cdrecord etc.

[mfaridi]

Thanks Guys
Can I make ISO file with dd and cat ???

[Carpetsmoker]

Yes, both will work:

# cat /dev/acd0 > myimage.iso
# dd if=/dev/acd0 of=anotherimage.iso

[mfaridi]

Originally Posted by Carpetsmoker

Yes, both will work:

# cat /dev/acd0 > myimage.iso
# dd if=/dev/acd0 of=anotherimage.iso

So I understand I can use dd and cat for make ISO files from CDROM and CD

IS this true ???

[Carpetsmoker]

No, it's not true, I was lying earlier. (<-- joke)

An "ISO file" or "disk image" is just a filesystem inside a file, cat and dd will both just make a "raw copy" of anything, here are some example uses (Not very useful, just proof of concept):

Make a floppy image and write put it to another floppy
# cat /dev/fd0 > floppy.img
# cat floppy.img > /dev/fd1

Copy a partition:
# cat /dev/ad0s1a > /dev/ad1s1a

Copy CDROM to disk and mount it
# cat /dev/acd0 > /dev/ad0s1d
# mount_cd9660 /dev/ad0s1d /mnt/cdrom

"Secure" erase a disk
# cat /dev/random > /dev/ad0

Make a backup
# cat /dev/ad0 | gz > backup.img.gz

[Oliver_H]

@Carpetsmoker

How could I check the image after burning?

[tuck]

Oliver: isovfy is part of cdrecord.

[Carpetsmoker]

tar(1) supports ISO9660:
% tar tf image.iso
% tar tf /dev/acd0

More reliable would be:

# mdconfig -at vnode -f image.iso
# mount -t cd9660 /dev/md0 /mnt/md0
# cd /mnt/md0

# find . -type f -exec md5 {} \; > ~/MD5.img[/cmd]
# cd -
# umount /mnt/md0; mdconfig -du0

[burn image]

# mount -t cd9660 /dev/acd0 /mnt/acd0
# cd /mnt/acd0
# find . -type f -exec md5 {} \; > ~/MD5.disc
# diff -u ~/MD5.img MD5.disc

If I remember correctly, the GNU version of md5 can read a file and check the files automatically, but it seems BSD md5 doesn't have this functionality...

[tuck]

Ah uh oh shame on me... I thought verifying if the .iso isn't broken or else like that, not verifying if the data is correctly writen...

[Oliver_H]

Thx

>not verifying if the data is correctly writen...

Yes this was my intention.

[ephemera]

Originally Posted by Carpetsmoker

More reliable would be:

# mdconfig -at vnode -f image.iso
# mount -t cd9660 /dev/md0 /mnt/md0
# cd /mnt/md0

# find . -type f -exec md5 {} \; > ~/MD5.img[/cmd]
# cd -
# umount /mnt/md0; mdconfig -du0

[burn image]

# mount -t cd9660 /dev/acd0 /mnt/acd0
# cd /mnt/acd0
# find . -type f -exec md5 {} \; > ~/MD5.disc
# diff -u ~/MD5.img MD5.disc

this method has the advantage that you would know which files are corrupted.

but if you just want to check if the cd is an corrupted or not:

$ md5 < image.iso > image.md5

[burn image]

$ dd < /dev/acd0 bs=2k | md5 | cmp - image.md5 && echo Ok

[ephemera]

actually, no need to use md5 this would likely be much faster:

$ dd < /dev/acd0 bs=2k | cmp - image.iso && echo Ok


btw, calculating the checksum of all the files being burned (similiar to what carpetsmoker suggested) and storing it in a file on the cd (say file.md5) is IMO a good idea. so that if the cd develops problems in the future you can easily tell which files are ok by comparing the files on the cd with their md5sums in file.md5.

[18Googol2]

Originally Posted by ephemera

btw, calculating the checksum of all the files being burned (similiar to what carpetsmoker suggested) and storing it in a file on the cd (say file.md5) is IMO a good idea.

Sure it is, especially for a big one. Thats what I do if I need to seed a torrent file

It also a good idea if you enclose a SHA256 checksum in the package as well

[mfaridi]

thanks all guys you help to learn many information abut ISO .

[ephemera]

Originally Posted by 18Googol2

It also a good idea if you enclose a SHA256 checksum in the package as well

while sha1/sha256 are crypographically more secure than md5 they more expensive to calculate - something to keep in mind for checksumming large files.

[18Googol2]

Yeah, nobody cares to spoof my torrent's MD5s, my torrents are crap btw

The fact is, an algorithm is said to be secure if its impossible to generate identical hash strings, from different source, which is not the case of MD5. Also MD5 hash can be decrypted with rainbow table. I reakon we will be moving to SHA256 in near future, so what I was saying is to get yourself be familiar with SHA256 is not a bad idea