>From: [EMAIL PROTECTED]

>[EMAIL PROTECTED] wrote:

>>After the disk is written, I can mount the disk from Linux
>>(2.2.25, glibc 2.2.5) in iso9660 mode. However, for files that
>>originally have a Apple resource fork (from Netatalk), it seems
>>that the resource fork instead of the data fork is visible to
>>Linux. Stranger still, this does not happen if I mount the CD
>>image file instead of the CDROM disk. It seems that mkisofs
>>generates identical inode numbers for both forks (in iso9660
>>mode), and the way the files are laid out are making at least
>>the Linux kernel confused.

>I don't use mkisofs or Linux, but I do recall that the difference
>between a "resource fork" and a "data fork" in the ISO9660 format
>is merely the setting of a single bit.  That bit indicates that
>the first extent of the file is a "resource fork".  Otherwise it
>is a "data fork".

mkisofs has passed the compliance test for Picture CDs from Kodak.

If you have problems without using HFS, they are definitely a result
of a Linux bug.

J�rg

 EMail:[EMAIL PROTECTED] (home) J�rg Schilling D-13353 Berlin
       [EMAIL PROTECTED]                (uni)  If you don't have iso-8859-1
       [EMAIL PROTECTED]        (work) chars I am J"org Schilling
 URL:  http://www.fokus.fraunhofer.de/usr/schilling ftp://ftp.berlios.de/pub/schily


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to