Be _very_ careful, genisoimage is full of bugs and creates defective filesystems. Do not use it, genisoimage is unmaintained and does not even support files > 4 GB! Other well known bugs in genisoimage create defective directory entries for "." and "..". This is because genisoimage is based on a 5 year old version of mkisofs with additional bugs added that never have been in the original software.
Mkisofs has no known bugs and is well maintained. I see no reason why mkisofs should be the cause for your problem... Well you did not describe the problem in a way that could allow to analyse the background. Possible reasons for your problem could be read errors on the medium, check using: readcd f=/dev/null whether the medium is fully readable. Another possible reason could be a problem in the filesystem driver of the kernel. If a file gives a read error, there should be a kernel message related to the problem. If you are able to extract the file using "isoinfo" using the ISO-9660 name of the file (be careful not to use the defective "isoinfo" that comes with "cdrkit"), the problem is definitely not in mkisofs. BTW: do you use a recent or an outdated mkisofs? The latest version of mkisofs is 2.01.01a66 and FreeBSD by default unfortunately distributes extremely outdated versions..... Jörg -- EMail:jo...@schily.isdn.cs.tu-berlin.de (home) Jörg Schilling D-13353 Berlin j...@cs.tu-berlin.de (uni) joerg.schill...@fokus.fraunhofer.de (work) Blog: http://schily.blogspot.com/ URL: http://cdrecord.berlios.de/private/ ftp://ftp.berlios.de/pub/schily _______________________________________________ firstname.lastname@example.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"