text stringlengths 0 99.6k |
|---|
usually is not sent. |
FFFFiiiilllleeeennnnaaaammmmeeee CCCCoooonnnnssssiiiiddddeeeerrrraaaattttiiiioooonnnnssss |
o+ File names should be translated to lower case unless the |
sending system supports upper/lower case file names. This |
is a convenience for users of systems (such as Unix) which |
store filenames in upper and lower case. |
o+ The receiver should accommodate file names in lower and |
upper case. |
o+ When transmitting files between different operating |
systems, file names must be acceptable to both the sender |
and receiving operating systems. If not, transformations |
should be applied to make the file names acceptable. If |
the transformations are unsuccessful, a new file name may |
be invented be the receiving program. |
Chapter 13 Rev 10-27-87 Typeset 10-27-87 31 |
Chapter 13 ZMODEM Protocol 32 |
If directories are included, they are delimited by /; i.e., |
"subdir/foo" is acceptable, "subdir\foo" is not. |
LLLLeeeennnnggggtttthhhh The file length and each of the succeeding fields are |
optional.[1] The length field is stored as a decimal string |
counting the number of data bytes in the file. |
The ZMODEM receiver uses the file length as an estimate only. |
It may be used to display an estimate of the transmission time, |
and may be compared with the amount of free disk space. The |
actual length of the received file is determined by the data |
transfer. A file may grow after transmission commences, and |
all the data will be sent. |
MMMMooooddddiiiiffffiiiiccccaaaattttiiiioooonnnn DDDDaaaatttteeee A single space separates the modification date |
from the file length. |
The mod date is optional, and the filename and length may be |
sent without requiring the mod date to be sent. |
The mod date is sent as an octal number giving the time the |
ccccoooonnnntttteeeennnnttttssss of the file were last changed measured in seconds from |
Jan 1 1970 Universal Coordinated Time (GMT). A date of 0 |
implies the modification date is unknown and should be left as |
the date the file is received. |
This standard format was chosen to eliminate ambiguities |
arising from transfers between different time zones. |
FFFFiiiilllleeee MMMMooooddddeeee A single space separates the file mode from the |
modification date. The file mode is stored as an octal string. |
Unless the file originated from a Unix system, the file mode is |
set to 0. rz(1) checks the file mode for the 0x8000 bit which |
indicates a Unix type regular file. Files with the 0x8000 bit |
set are assumed to have been sent from another Unix (or |
similar) system which uses the same file conventions. Such |
files are not translated in any way. |
SSSSeeeerrrriiiiaaaallll NNNNuuuummmmbbbbeeeerrrr A single space separates the serial number from the |
file mode. The serial number of the transmitting program is |
stored as an octal string. Programs which do not have a serial |
number should omit this field, or set it to 0. The receiver's |
use of this field is optional. |
__________ |
1. Fields may not be skipped. |
Chapter 13 Rev 10-27-87 Typeset 10-27-87 32 |
Chapter 13 ZMODEM Protocol 33 |
NNNNuuuummmmbbbbeeeerrrr ooooffff FFFFiiiilllleeeessss RRRReeeemmmmaaaaiiiinnnniiiinnnngggg Iff the number of files remaining is sent, |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.