logo

oasis-root

Compiled tree of Oasis Linux based on own branch at <https://hacktivis.me/git/oasis/> git clone https://anongit.hacktivis.me/git/oasis-root.git

uudecode.1p (7230B)


  1. '\" et
  2. .TH UUDECODE "1P" 2017 "IEEE/The Open Group" "POSIX Programmer's Manual"
  3. .\"
  4. .SH PROLOG
  5. This manual page is part of the POSIX Programmer's Manual.
  6. The Linux implementation of this interface may differ (consult
  7. the corresponding Linux manual page for details of Linux behavior),
  8. or the interface may not be implemented on Linux.
  9. .\"
  10. .SH NAME
  11. uudecode
  12. \(em decode a binary file
  13. .SH SYNOPSIS
  14. .LP
  15. .nf
  16. uudecode \fB[\fR-o \fIoutfile\fB] [\fIfile\fB]\fR
  17. .fi
  18. .SH DESCRIPTION
  19. The
  20. .IR uudecode
  21. utility shall read a file, or standard input if no file is specified,
  22. that includes data created by the
  23. .IR uuencode
  24. utility. The
  25. .IR uudecode
  26. utility shall scan the input file, searching for data compatible with
  27. one of the formats specified in
  28. .IR uuencode ,
  29. and attempt to create or overwrite the file described by the data (or
  30. overridden by the
  31. .BR \-o
  32. option). The pathname shall be contained in the data or specified by
  33. the
  34. .BR \-o
  35. option. The file access permission bits and contents for the file to be
  36. produced shall be contained in that data. The mode bits of the created
  37. file (other than standard output) shall be set from the file access
  38. permission bits contained in the data; that is, other attributes of the
  39. mode, including the file mode creation mask (see
  40. .IR umask ),
  41. shall not affect the file being produced. If either of the
  42. .IR op
  43. characters
  44. .BR '\(pl'
  45. and
  46. .BR '\-'
  47. (see
  48. .IR chmod )
  49. are specified in symbolic mode, the initial mode on which those
  50. operations are based is unspecified.
  51. .P
  52. If the pathname of the file resolves to an existing file and the
  53. user does not have write permission on that file,
  54. .IR uudecode
  55. shall terminate with an error. If the pathname of the file resolves to
  56. an existing file and the user has write permission on that file, the
  57. existing file shall be overwritten and, if possible, the mode bits of
  58. the file (other than standard output) shall be set as described above;
  59. if the mode bits cannot be set,
  60. .IR uudecode
  61. shall not treat this as an error.
  62. .P
  63. If the input data was produced by
  64. .IR uuencode
  65. on a system with a different number of bits per byte than on the target
  66. system, the results of
  67. .IR uudecode
  68. are unspecified.
  69. .SH OPTIONS
  70. The
  71. .IR uudecode
  72. utility shall conform to the Base Definitions volume of POSIX.1\(hy2017,
  73. .IR "Section 12.2" ", " "Utility Syntax Guidelines".
  74. .P
  75. The following option shall be supported by the implementation:
  76. .IP "\fB\-o\ \fIoutfile\fR" 10
  77. A pathname of a file that shall be used instead of any pathname
  78. contained in the input data. Specifying an
  79. .IR outfile
  80. option-argument of
  81. .BR /dev/stdout
  82. shall indicate standard output.
  83. .SH OPERANDS
  84. The following operand shall be supported:
  85. .IP "\fIfile\fR" 10
  86. The pathname of a file containing the output of
  87. .IR uuencode .
  88. .SH STDIN
  89. See the INPUT FILES section.
  90. .SH "INPUT FILES"
  91. The input files shall be files containing the output of
  92. .IR uuencode .
  93. .SH "ENVIRONMENT VARIABLES"
  94. The following environment variables shall affect the execution of
  95. .IR uudecode :
  96. .IP "\fILANG\fP" 10
  97. Provide a default value for the internationalization variables that are
  98. unset or null. (See the Base Definitions volume of POSIX.1\(hy2017,
  99. .IR "Section 8.2" ", " "Internationalization Variables"
  100. for the precedence of internationalization variables used to determine
  101. the values of locale categories.)
  102. .IP "\fILC_ALL\fP" 10
  103. If set to a non-empty string value, override the values of all the
  104. other internationalization variables.
  105. .IP "\fILC_CTYPE\fP" 10
  106. Determine the locale for the interpretation of sequences of bytes of
  107. text data as characters (for example, single-byte as opposed to
  108. multi-byte characters in arguments and input files).
  109. .IP "\fILC_MESSAGES\fP" 10
  110. .br
  111. Determine the locale that should be used to affect the format and
  112. contents of diagnostic messages written to standard error.
  113. .IP "\fINLSPATH\fP" 10
  114. Determine the location of message catalogs for the processing of
  115. .IR LC_MESSAGES .
  116. .SH "ASYNCHRONOUS EVENTS"
  117. Default.
  118. .SH STDOUT
  119. If the file data header encoded by
  120. .IR uuencode
  121. is
  122. .BR \-
  123. or
  124. .BR /dev/stdout ,
  125. or the
  126. .BR \-o
  127. .BR /dev/stdout
  128. option overrides the file data, the standard output shall be in the
  129. same format as the file originally encoded by
  130. .IR uuencode .
  131. Otherwise, the standard output shall not be used.
  132. .SH STDERR
  133. The standard error shall be used only for diagnostic messages.
  134. .SH "OUTPUT FILES"
  135. The output file shall be in the same format as the file originally
  136. encoded by
  137. .IR uuencode .
  138. .SH "EXTENDED DESCRIPTION"
  139. None.
  140. .SH "EXIT STATUS"
  141. The following exit values shall be returned:
  142. .IP "\00" 6
  143. Successful completion.
  144. .IP >0 6
  145. An error occurred.
  146. .SH "CONSEQUENCES OF ERRORS"
  147. Default.
  148. .LP
  149. .IR "The following sections are informative."
  150. .SH "APPLICATION USAGE"
  151. The user who is invoking
  152. .IR uudecode
  153. must have write permission on any file being created.
  154. .P
  155. The output of
  156. .IR uuencode
  157. is essentially an encoded bit stream that is not cognizant of byte
  158. boundaries. It is possible that a 9-bit byte target machine can
  159. process input from an 8-bit source, if it is aware of the requirement,
  160. but the reverse is unlikely to be satisfying. Of course, the only data
  161. that is meaningful for such a transfer between architectures is
  162. generally character data.
  163. .SH EXAMPLES
  164. None.
  165. .SH RATIONALE
  166. Input files are not necessarily text files, as stated by an early
  167. proposal. Although the
  168. .IR uuencode
  169. output is a text file, that output could have been wrapped within
  170. another file or mail message that is not a text file.
  171. .P
  172. The
  173. .BR \-o
  174. option is not historical practice, but was added at the request of WG15
  175. so that the user could override the target pathname without having to
  176. edit the input data itself.
  177. .P
  178. In early drafts, the [\c
  179. .BR \-o
  180. .IR outfile ]
  181. option-argument allowed the use of
  182. .BR \-
  183. to mean standard output. The symbol
  184. .BR \-
  185. has only been used previously in POSIX.1\(hy2008 as a standard input indicator.
  186. The standard developers did not wish to overload the meaning of
  187. .BR \-
  188. in this manner. The
  189. .BR /dev/stdout
  190. concept exists on most modern systems. The
  191. .BR /dev/stdout
  192. syntax does not refer to a new special file. It is just a magic cookie
  193. to specify standard output.
  194. .SH "FUTURE DIRECTIONS"
  195. None.
  196. .SH "SEE ALSO"
  197. .IR "\fIchmod\fR\^",
  198. .IR "\fIumask\fR\^",
  199. .IR "\fIuuencode\fR\^"
  200. .P
  201. The Base Definitions volume of POSIX.1\(hy2017,
  202. .IR "Chapter 8" ", " "Environment Variables",
  203. .IR "Section 12.2" ", " "Utility Syntax Guidelines"
  204. .\"
  205. .SH COPYRIGHT
  206. Portions of this text are reprinted and reproduced in electronic form
  207. from IEEE Std 1003.1-2017, Standard for Information Technology
  208. -- Portable Operating System Interface (POSIX), The Open Group Base
  209. Specifications Issue 7, 2018 Edition,
  210. Copyright (C) 2018 by the Institute of
  211. Electrical and Electronics Engineers, Inc and The Open Group.
  212. In the event of any discrepancy between this version and the original IEEE and
  213. The Open Group Standard, the original IEEE and The Open Group Standard
  214. is the referee document. The original Standard can be obtained online at
  215. http://www.opengroup.org/unix/online.html .
  216. .PP
  217. Any typographical or formatting errors that appear
  218. in this page are most likely
  219. to have been introduced during the conversion of the source files to
  220. man page format. To report such errors, see
  221. https://www.kernel.org/doc/man-pages/reporting_bugs.html .