Debian Codegraph @

doc/bugs.html

raw
1 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
2 "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
3 <html xmlns="http://www.w3.org/1999/xhtml">
4 <head>
5 <meta name="generator" content="HTML Tidy, see www.w3.org" />
6 <title>HFS+ Utilities, BUGS</title>
7 </head>
8
9 <body>
10 <h2>HFS+ Utilities, BUGS</h2>
11
12 <ul>
13 <li>Disk First Aid will hang with some strange behaviour in case the
14 length of a key does not match the length of the string inside the key
15 (Ill try to report this bug to Apple ;-)</li>
16
17 <li> HFS+ cotains hints for the finder what encoding (Roman, Asiatic,
18 etc. to use. These are not supported. MacOS <i>may</i> react strange on files
19 or folders that are not marked but need such an encoding.
20 </li>
21
22 <li> HFS+ contains POSIX permissions which are not used by MacOS &lt;= 9,
23 but probably by MacOS X. None of the HFS+ utils cares fore those by now.
24 This should be implemented in some later version.</li>
25
26 <li>hpfsck will not complain abut files/folders without thread and vice
27 versa. All sorts of strange results will happen when using such a volume.
28 </li>
29
30 <li>hpfsck will not complain about records without parent. They will not
31 show up, but are still there. Fixing this is a difficult task.</li>
32
33 <li>Error handling ist not always consistent and will need a cleanung
34 once the major goals are reached. You sometimes will get errors without
35 any message (failed: No Error) or errors with wrong explanation
36 (Internal errors that were caught and handled.)</li>
37
38 <li>The conversion from and to unicode does not work fully. Files with
39 extended characters are not created correctly and therefore are not
40 found by MacOS. The sorting of files with extended characters will be
41 different from the result of a "normal" sort. (How does kanji work with
42 linux ?).</li>
43
44 <li>HFS+ allows any charcter as name. MacOS does not allow ':' since it
45 is used as folder seperator. I dont know what MacOS X allows. With
46 hfsplus the standard unix . and .. is used to denote the current and
47 parent directory. Thus using '.' or '..' as filenames will result in
48 unpredictable behaviour.</li>
49
50 <li>Unicode Strings that convert to UTF-8/ISO Strings longer than 255
51 characters will be trunctated. (In case you run into this theoretically
52 bug please send Email to &lt;[email protected]&gt; Im curious :)</li>
53
54 <li>The creation date of a mac volume is set in local time. (So mac
55 programs do not think the volume has changed when the timezone or DST
56 changes). This difference is ignored since Linux/Unix per default only
57 uses UUTC times. (In practice this should not matter.)</li>
58
59 <li>The volume name must not contain the charcter ':' (Which is rather
60 unlikely with MacOS but theoretically possible). This is a limitation of
61 the hfsputils which need to save some information in a text file.</li>
62
63 <li>The Macbinary and BinHex formats contain limitations on the length
64 of filenames, longer names will (hopefully) be truncated.</li>
65
66 <li>The Macbinary and BinHex formats are unable to cope with 64 bit file
67 length. Such files can not be copied using these formats, use raw mode
68 instead.</li>
69
70 <li>The globbing mechanism in hpls and other functions can (per desgin)
71 not match patterns spaning directories so 'a*b' or 'a{/,b}c' will not
72 match 'a/b'. (I dont think a normal ls * does this, perhaps Im
73 --pedantic here :)</li>
74
75 <li>hpls does not support the unix '.' and '..' notation completly. '.'
76 will be shown, but '..' not. hpls '.' and hpls '..' wont work. (hpcd
77 '..' will work :). Since HFS+ does not really have these concepts It is
78 somewhat difficult to implement this completly.</li>
79
80 <li> The Partition code could be a bit better and should release
81 the Memory allocated, but I'm happy its there at all ;-) </li>
82 </ul>
83 <pre>
84 $Id: bugs.html,v 1.3 2002/03/26 20:47:26 klaus Exp $
85 </pre>
86 </body>
87 </html>
88