Tenex interface to UCSB's Simple-Minded File System (RFC0409)
Original Publication Date: 1972-Dec-01
Included in the Prior Art Database: 2019-Feb-12
Internet Society Requests For Comment (RFCs)
Network Working Group J. White Request for Comments: 409 SRI-ARC NIC: 12401 8 December 1972 Related RFCs: 122, 399
TENEX Interface To UCSB’s Simple-Minded File System
A subsystem for TENEX called SMFS has been written to interface ARPANET TENEX users to the Simple-Minded File System at UCSB-MOD75 (see NIC 5834 / RFC 122 and NIC 11917 / RFC 399). The Simple-Minded File System is a resident server process at UCSB which currently manages approximately 10K pages of on-line, direct-access storage.
Using the simple command language or the subsystem here described, the user can transfer files to and from UCSB, and delete and rename them while they reside at Santa Barbara. Files stored at UCSB may be read and/or write protected, and a file archived to UCSB from the TENEX system can be retrieved from another.
This document is intended to provide users with the information necessary to use SMFS from a terminal; the reader is assumed familiar with TENEX.
SMFS is currently installed at SRI-ARC (note in particular that the ARC EXEC WILL NOT give the user any ’GENERAL SUBSYSTEMS NOT AVAILABLE FOR NIC USE’ flack about invoking SMFS).
Copies of the source file are available upon request from the NIC. Bug reports and comments upon the code and documentation are solicited by the author, and may be sent to JEW through the Journal.
SMFS can archive at Santa Barbara any file resident in a TENEX file system except:
(1) Long files (in the strict, TENEX sense), and
(2) Files whose directory name, filename, or extension contains other than alphameric characters, or whose combined length exceeds 32 characters (this limitation arises because of naming restrictions imposed at UCSB).
White [Page 1]
RFC 409 TENEX INTERFACE TO SIMPLE-MINDED FILE SYSTEM December 1972
III. OPERATING INSTRUCTIONS
SMFs is invoked like any other subsystem --- by typing its name followed by a carriage return (CR). SMFS responds with the herald ’UCSB Archival System (ver n date)’ followed by its prompt character ’#’. Whenever SMFS types its prompt character, it expects the user to respond with a command (’?’ will generate a list of all valid commands).
The user selects a command by typing its first letter (here and throughout the exchange, upper- and lower-case alphabetics are interchangeable). SMFS acknowledges a command it recognizes by typing the remaining characters of the keyword, and rejects those it doesn’t by typing ’?’.
If the command requires arguments, SMFS prompts the user for each one in turn by describing it in parentheses. If the argument is a keyword, SMFS will list the set of alternatives (separated by slashes). The user selects one by typing its first letter. Again, SMFS acknowledges a valid selection by completing it; if the user’s response is in error, SMFS prompts for the parameter a second time. If the argument is not a keyword (e.g., a filename), the user enters an appropriate character string terminated by a CR. Commands with no predicate are sim...