1/* @(#)TODO	1.9 08/11/27 joerg */
2	1) Finish multiple paths.  Update nlink count on directories if it is
3	different than what stat returned.  Save the nlink count that we store in
4	the rock ridge attributes so know when we don't have to adjust it.
5
6
7Andy Polyakov <appro@fy.chalmers.se>
8Well, it was rather hard to get it wrong... But the answer is "yes" if
9you have to hear this very word.
10
11And while we're discussing this code. A *cosmetic* *suggestion*.
12Consider modifying two lines above the "if(is_directory)" as following:
13
14        set32(&fe->uid,0);
15        set32(&fe->gid,0);
16
17or to any other small number. Problem is that with -1 as now 'ls -l'
18results in wider output which is rather annoying (it has to print
194294967295 twice while it formats for 8 chars).
20
21Cheers. A.
22
23/*--------------------------------------------------------------------------*/
24
25Option to modify Volume id, ... in PVD after the image has been
26created?
27
28/*--------------------------------------------------------------------------*/
29http://www.y-adagio.com/public/standards/iso_cdromr/tocont.htm
30
31Annex B has:
32
33Changes from ISO 9660:1988 to this International Standard:
34
35a) The Volume Descriptor Version is changed to indicate the new structure;
36     Version number 2 indicated the new specification.
37b) The File Structure Version is changed to indicate the new structure;
38     Version number 2 indicated the new specification.
39c) The limitation in the Depth of Hierarchy is lifted;
40     The levels in the hierarchy can exceed eight.
41d) The File Identifier is not separated to components;
42     The SEPARATORS are not specified.
43     A complex file name can be expressed.
44e) The File Identifier does not have File Version Numbers;
45     File with and without Version Numbers should not exist in the same directory.
46f) The character used for filling byte positions which are specified to be characters is subject to agreement
47between the originator and the recipient of the volume;
48g) The length of File Identifier is limited to 207;
49     Long file name can be expressed.
50h) The length of a Directory Identifier is limited to 207;
51     Long directory name can be expressed.
52/*--------------------------------------------------------------------------*/
53
54Extent # auch als off_t statt int
55
56Wenn HFS, dann max File size == 2 GB?
57
58/*--------------------------------------------------------------------------*/
59
60Files mit ';' im Namen
61
62/*--------------------------------------------------------------------------*/
63
64> Betreff: Re: [Cdrecord-developers] No HFS MultiSession possible
65>
66> >From: "Sam" <samuel@macuta.de>
67>
68> >I have tried everything - with no success.
69> >What I want do do is a CD Extra with a Hybrid Data Track. So
70> >i burn the
71> >first session (audio), read th -msinfo and then try to
72> >create a hybrid
73> >ISO/HFS track at the given sector.
74> >e.g.: mkisofs -C 0,15582 -J -r -hfs -o "C:\dat.iso" "C:\dat"
75>
76> If this is on DOS, then the filenames are not valid.
77> A '\' may not appear inside a DOS filername and '\' is not a
78> valid path name
79> separator. The official path name separator is '/'
80
81This was just an example! I know how to make ISO files with any
82other options but *multisession hfs* (-C .,. -hfs). I tried it
83also in Linux eith the same error message.
84
85> >I tried to do it without -J and/or -r, Windows and Linux,
86> and so on...
87> >When doing it without -hfs, it works. When doing it with
88> -hfs but without -C
89> >0,15582 it works, too.
90>
91> >The error is:
92> >Implementation botch: Initial Padbock should start at 15582
93> but starts at
94> >15583.
95>
96> create aone or two small tar files with a sample directory
97> data that allows to
98> reproduce the problem....
99
100It can be reproduced with any directory. If you use Linux try this:
101
102mkisofs -C 0,15582 -hfs -o "test.iso" "/var/log"
103
104Please try this and tell me if it produceses the same error message.
105It seams, that hfs can't be written for a cd extra
106(audio+data multisession without importing the first session).
107
108/*--------------------------------------------------------------------------*/
109Koblinger Egmont <egmont@uhulinux.hu>
110
111Using 2.01a23 on Linux, ix86, I created a bootable CD-ROM. The important
112options to mkisofs were these:
113-boot-load-size 4 -no-emul-boot -boot-info-table -b boot/isolinux.bin
114-c boot/boot.cat -J -T -hide-joliet-trans-tbl -r -hide-rr-moved
115
116Then I found that this CD boots correctly on many machines, but doesn't
117boot on many other ones (which are correct hardware too, e.g. my one is
118an Abit BX6 from about 1999).
119
120Some debugging showed me that these machines have problem accessing the
121contents of the CD beyond thirty-some megabytes from BIOS, hence they need
122the boot image and the boot catalog files to go somewhere at the beginning
123of the disc. However, it seems to me that mkisofs doesn't handle these
124files specially, they go to the same position as if they were simple files
125not related to booting.
126
127Then I read README.sort and told mkisofs to put these files at the
128beginning. Now the CD boots on every machine.
129
130My request is: would it be possible to teach mkisofs to automatically put
131the boot image and boot catalog files at the beginning of the iso image?
132(Maybe implemented by adding 1 to their sorting weight so that one can
133override this with the -sort option).
134
135And, in the mean time, mkisofs/README.sort ends with a comment:
136"I have no idea if this is really useful ..."
137In case you shouldn't accept my suggestion for some reason, then at least
138this comment should be changed to "It is useful to put boot images at the
139beginning of the disc ..."
140/*--------------------------------------------------------------------------*/
141Andere Dinge die im Zeitplan davor kommen:
142
143-       Win32/MINGW Port
144
145-       Weitere Boot Unterstuetzung (IRIX, HPUX, ...)
146
147
148/*--------------------------------------------------------------------------*/
149
150Eine Option damit man Symlinks erkennt die aus dem Image herausragen?
151
152/*--------------------------------------------------------------------------*/
153
154Ist es noetig hinter einer Path Table mit ungerader Sektorzahl einen
155Padblock zu schreiben?
156
157        path_blocks = ISO_BLOCKS(path_table_size);
158        if (path_blocks & 1)
159                path_blocks++;
160
161gleiches fuer jpath_blocks
162
163/*--------------------------------------------------------------------------*/
164Warning: Disabling Joliet support for DVD-Video.
165