> AFAIK mkisofs sorts the contents of each directory strictly
> alphabetically,
> diving into subdirectories according to their place in their parent, so
> first
> /a/a/a, then /a/a/b, /a/b, /a/c/a etc. up to /z/z/z.
>
> (And indeed, the farther from the center (i.e. at the end of the image)
> the
> more effect the "shaking" of the motor has.)
[Allison, Jason A.]
When I perform a:
mkisofs -d -L -l -v -o /dist/party3rd.img ../party3rd
The debug that is put out does not correspond to your statement on
the directory being sorted alphabetically. The output will say:
Scanning ../party3rd
Scanning ../party3rd/advfs
Scanning ../party3rd/cdtools
....
Scanning ../party3rd/wuftp
Scanning ../party3rd/cpplib
Scanning ../party3rd/netscape
Scanning ../party3rd/netscape/messaging-354
Scanning ../party3rd/nsr
If I do a du -k * from the parent, the sizes are as follows (the du
-k is not in this order of course):
4667 advfs
477 cdtools
....
195 wuftp
171 cpplib
251897 netscape
84454 netscape/messaging-354
49443 nsr
What are your thoughts?
Jason
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
