2 .TH mkmanifest 1 "09Jan13" mtools-4.0.18
4 mkmanifest - makes list of file names and their DOS 8+3 equivalent
17 This manpage has been automatically generated from mtools's texinfo
18 documentation, and may not be entirely accurate or complete. See the
19 end of this man page for details.
23 The \fR\&\f(CWmkmanifest\fR command is used to create a shell script (packing
24 list) to restore Unix filenames. Its syntax is:
26 \&\fR\&\f(CWmkmanifest\fR [ \fIfiles\fR ]
28 \&\fR\&\f(CWMkmanifest\fR creates a shell script that aids in the restoration of
29 Unix filenames that got clobbered by the MS-DOS filename restrictions.
30 MS-DOS filenames are restricted to 8 character names, 3 character
31 extensions, upper case only, no device names, and no illegal characters.
33 The mkmanifest program is compatible with the methods used in
34 \&\fR\&\f(CWpcomm, arc,\fR and \fR\&\f(CWmtools\fR to change perfectly good Unix
35 filenames to fit the MS-DOS restrictions. This command is only useful if
36 the target system which will read the diskette cannot handle VFAT long
40 You want to copy the following Unix files to a MS-DOS diskette (using the
41 \&\fR\&\f(CWmcopy\fR command).
61 converts the names to:
85 mkmanifest very_long_name 2.many.dots illegal: good.c prn.dev Capital >manifest
91 \&\fRwould produce the following:
96 mv very_lon very_long_name
97 mv 2xmany.dot 2.many.dots
108 Notice that "good.c" did not require any conversion, so it did not
109 appear in the output.
111 Suppose I've copied these files from the diskette to another Unix
112 system, and I now want the files back to their original names. If the
113 file "manifest" (the output captured above) was sent along with those
114 files, it could be used to convert the filenames.
118 The short names generated by \fR\&\f(CWmkmanifest\fR follow the old convention
119 (from mtools-2.0.7) and not the one from Windows 95 and mtools-3.0.
123 .SH Viewing\ the\ texi\ doc
124 This manpage has been automatically generated from mtools's texinfo
125 documentation. However, this process is only approximative, and some
126 items, such as crossreferences, footnotes and indices are lost in this
127 translation process. Indeed, these items have no appropriate
128 representation in the manpage format. Moreover, not all information has
129 been translated into the manpage version. Thus I strongly advise you to
130 use the original texinfo doc. See the end of this manpage for
131 instructions how to view the texinfo doc.
134 To generate a printable copy from the texinfo doc, run the following
140 ./configure; make dvi; dvips mtools.dvi
149 To generate a html copy, run:
154 ./configure; make html
160 \&\fRA premade html can be found at
161 \&\fR\&\f(CW\(ifhttp://www.gnu.org/software/mtools/manual/mtools.html\(is\fR
164 To generate an info copy (browsable using emacs' info mode), run:
169 ./configure; make info
177 The texinfo doc looks most pretty when printed or as html. Indeed, in
178 the info version certain examples are difficult to read due to the
179 quoting conventions used in info.