Browse Prior Art Database

Directory oriented FTP commands (RFC0775)

IP.com Disclosure Number: IPCOM000003823D
Original Publication Date: 1980-Dec-01
Included in the Prior Art Database: 2000-Sep-13
Document File: 5 page(s) / 9K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

D. Mankins: AUTHOR [+3]

This text was extracted from a ASCII Text document.
This is the abbreviated version, containing approximately 31% of the total text.

RFC 775 Directory oriented FTP commands Page 1

DIRECTORY ORIENTED FTP COMMANDS

David Mankins (dm@bbn-unix)

Dan Franklin (dan@bbn-unix)

A. D. Owen (ADOwen@bbnd)

As a part of the Remote Site Maintenance (RSM) project for ARPA,

BBN has installed and maintains the software of several DEC PDP-

11s running the Unix operating system. Since Unix has a tree-

like directory structure, in which directories are as easy to

manipulate as ordinary files, we have found it convenient to

expand the FTP servers on these machines to include commands

which deal with the creation of directories. Since there are

other hosts on the ARPA net which have tree-like directories,

including Tops-20 and Multics, we have tried to make these

commands as general as possible.

We have added four commands to our server:

XMKD child

Make a directory with the name "child".

XRMD child

Remove the directory with the name "child".

XPWD

Print the current working directory.

XCUP

Change to the parent of the current working

directory.

The "child" argument should be created (removed) as a

subdirectory of the current working directory, unless the "child"

string contains sufficient information to specify otherwise to

the server, e.g., "child" is an absolute pathname (in Multics and

Unix), or child is something like "" to Tops-20.

RFC 775 Directory oriented FTP commands Page 2

REPLY CODES

The XCUP command is a special case of XCWD, and is included to

simplify the implementation of programs for transferring

directory trees between operating systems having different

syntaxes for naming the parent directory. Therefore we recommend

that the reply codes for XCUP be identical to the reply codes of

XCWD.

Similarly, we recommend that the reply codes for XRMD be

identical to the reply codes for its file analogue, DELE.

The reply codes for XMKD, however, are a bit more complicated. A

freshly created directory will probably be the object of a future

XCWD command. Unfortunately, the argument to XMKD may not always

be a suitable argument for XCWD. This is the case, for example,

when a Tops-20 subdirectory is created by giving just the

subdirectory name. That is, with a Tops-20 server FTP, the

command sequence

XMKD MYDIR

XCWD MYDIR

will fail. The new directory may only be referred to by its

"absolute" name; e.g., if the XMKD command above were issued

while connected to the directory , the new

subdirectory could only be referred to by the name

.

Even on Unix and Multics, however, the argument given to XMKD may

not be suitable. If it is a "re...