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