HFS PROBLEMS/LIMITATIONSI have had to make several assumptions on how I expect the modified libhfs routines to work; however, there may be situations that I haven't thought of or that happen when these assumptions fail. Therefore I can't guarantee that mkisofs will work as expected (although I haven't had a major problem yet). Most of the HFS features work fine; however, some are not fully tested. These have been marked as Alpha. Although HFS filenames appear to support upper and lowercase letters, the file system is case-insensitive; i.e., the filenames "aBc" and "AbC" are the same. If a file is found in a directory with the same HFS name, then mkisofs will attempt, where possible, to make a unique name by adding "_" characters to one of the filenames. HFS file/directory names that share the first 31 characters have _N' (N == decimal number) substituted for the last few characters to generate unique names. Care must be taken when "grafting" Apple/Unix files or directories (see previous sections for the method and syntax involved). It is not possible to use a new name for an Apple/Unix encoded file/directory. For example, if an Apple/Unix encoded file called "oldname" is added to the CD, then you cannot use the command line: mkisofs -o output.raw -hfs newname=oldname cd_dir mkisofs will be unable to decode "oldname." However, you can graft Apple/Unix encoded files or directories as long as you do not attempt to give them new names as previously. When creating an HFS volume with the multisession options -M and -C, only files in the last session will be in the HFS volume; i.e., mkisofs cannot add existing files from previous sessions to the HFS volume. Symbolic links (as with all other non-regular files) are not added to the HFS directory. Hybrid volumes may be larger than pure ISO9660 volumes containing the same data. The resulting hybrid volume can be accessed on a Unix machine by using the hfsutils routines. However, no changes should be made to the contents of the volume as, it's not a "real" HFS volume. Using the -mac-name option will not currently work with the -T option. The Unix name will be used in the TRANS.TBL file, not the Macintosh name. Although mkisofs does not alter the contents of a file, if a binary file has its TYPE set as 'TEXT,' it may be read incorrectly on a Macintosh. Therefore, a better choice for the default TYPE may be '????'. The -mac-boot-file option may not work at all. It may not work with PC Exchange v2.2 or higher files (available with MacOS 8.1). DOS media containing PC Exchange files should be mounted as type msdos (not vfat) when using Linux. The SFM format is only partially supportedsee the "HFS Macintosh File Formats" section. It is not possible to use the the -sparc-boot or -generic-boot options with the -boot-hfs-file or -prep-boot options. |