*line 1: Unknown output type = >*line 1: UNKNOWN DIRECTIVE D ^= $D *line 1: FAULTY FORMAT AT $ $A$r-0.25 *line 2: UNKNOWN DIRECTIVE D = _ $D *line 2: UNKNOWN DIRECTIVE W *line 3: UNKNOWN DIRECTIVE U $W $U *line 3: MISPLACED DIRECTIVE A *line 3: FAULTY FORMAT AT " *line 3: MISPLACED DIRECTIVE A *line 3: FAULTY FORMAT AT . $A just=1; left=1"; line=6.5" *line 4: UNKNOWN DIRECTIVE F =14 $F14 s=1.0 14 *line 6: MISPLACED DIRECTIVE A *line 6: FAULTY FORMAT AT . *line 6: FAULTY FORMAT AT . $A left=0.75";nls=1.0 *line 7: UNKNOWN DIRECTIVE D ^=^ $D *line 8: UNKNOWN DIRECTIVE D =% __ $D Communications within the CS department 3/11/86 This HELP section covers all aspects of communications, file transfer and access to remote printers etc. within the CS department (Not just the APMs). *line 17: SPURIOUS DIRECTIVE U *line 17: UNKNOWN DIRECTIVE U 1 $U Overview *line 18: UNKNOWN DIRECTIVE U $U These tables give an overview of what file transfers are possible and brief details of the commands involved. These are described in later sections of this note. *line 26: SPURIOUS DIRECTIVE U *line 26: UNKNOWN DIRECTIVE U 1.1 $U File transfer - initiated by SENDER *line 27: UNKNOWN DIRECTIVE U $U Snd\Rec> ECSVAX CSTVAX APM/FS CHEOPS GEC 63s EMAS Micros ITSPNA v------------------------------------------------------------------------------ ECSVAX | Copy ftp tofs - ftp ftp Kermit/3 ftp CSTVAX | hhcp cp tofs rcp/9 hhcp hhcp - rcp/9 APM/FS | eftp eftp eftp - - - - - Unix/* | - rcp/9 - cp - - - rcp/9 GEC 63s| hhcp hhcp - - cp? hhcp ? hhcp? EMAS | Transfer Transfer - - Transfer Transfer Kermit Transfer Micros | Kermit/3 - - - ? Kermit/3 Various Kermit ITSPNA | hhcp rcp/9 tofs rcp/9 hhcp? hhcp Kermit cp *line 43: SPURIOUS DIRECTIVE U *line 43: UNKNOWN DIRECTIVE U 1.2 $U File transfer - initiated by RECIPIENT *line 44: UNKNOWN DIRECTIVE U $U Snd\Rec> ECSVAX CSTVAX APM/FS CHEOPS GEC 63s EMAS Micros ITSPNA v------------------------------------------------------------------------------ ECSVAX | Copy hhcp/1 eftp tftp hhcp Transfer Kermit/3 hhcp/1 CSTVAX | ftp/2 cp eftp rcp/9 hhcp Transfer - rcp/9 APM/FS | fromfs fromfs eftp - - - - fromfs Unix/* | unixget/8 rcp/9 - cp - - - rcp/9 GEC 63s| ftp hhcp - - cp? transfer ? hhcp? EMAS | ftp hhcp - - hhcp? transfer Kermit/3 hhcp Micros | Kermit/3 - - - ? Kermit/3 Various Kermit ITSPNA | ftp/2 rcp/9 - rcp/9 hhcp? transfer Kermit cp *line 60: SPURIOUS DIRECTIVE U *line 60: UNKNOWN DIRECTIVE U 1.3 $U Remote Log-on *line 61: UNKNOWN DIRECTIVE U $U Host > ECSVAX CSTVAX APM/FS CHEOPS EdNet Pad | ITSPNA Suns v-------------------------------------------------------- ECSVAX | * rlogin - rlogin host CSTVAX/ITSPNA | pad rlogin - rlogin pad APM/FS | vax - - - - CHEOPS/Suns | - rlogin - - - GEC 63s | ? ? - ? - EdNet | /5 /5 /5 /5 * *line 76: SPURIOUS DIRECTIVE U *line 76: UNKNOWN DIRECTIVE U 1.4 $U Notes *line 77: UNKNOWN DIRECTIVE U $U /* Unix hosts include Cheops, Suns and Orion. The other Unix systems (CSTVAX, ITSPNA, GEC 63s) are special cases for one reaon or another. /1 Tftp is an alternative to hhcp /2 Unixget is an alternative to ftp. See /8 /3 Xtalk is an alternative to Kermit /5 Most CS hosts are accessible via the Gandalf. Call CS-GANDALF from a PAD then respond ECSVAX, CHEOPS, CSTVAX or APM as appropriate /8 RUN ECSSYS:UNIXGET _ /9 Don't forget to set up a .rhosts file on each participating machine. This should contain one line per host giving host name and your id. /10 On ITSPNA, fsprint, tofs and fromfs are ~gdmr/fs/fsprint, ~gdmr/fs/tofs and ~gdmr/fs/fromfs respectively. See HELP FILETRANSFER /CS lpr -Plpcs *line 97: SPURIOUS DIRECTIVE U *line 97: UNKNOWN DIRECTIVE U 2 File $U transfer utilities talking to APM Filestores *line 98: UNKNOWN DIRECTIVE U $U This note describes how to communicate with the Computer Science Department's Filestore B from cstvax and itspna and from ECSVAX to all filestores. Users can transfer files to and from directories on the filestore, can send files to be printed on the M/H printer, and (cstvax only) can send files to be printed on the laser printed in the photocopier room. *line 110: SPURIOUS DIRECTIVE U *line 110: UNKNOWN DIRECTIVE U 2.1 $U General notes on UNIX file transfer commands *line 111: UNKNOWN DIRECTIVE U $U Transfers take place over a serial link (RS232 @ 9600 baud), so don't expect miracles of speed. The serial line is not shareable, and the utilities run setuid and employ advisory locks to enforce this. This is the source of the (somewhat unhelpful) error message "operation would block", which means that someone else is using the line and you'll have to back off and retry later. There is at present no direct way to transfer files to and from filestore C, neither are there any plans to provide such. Shell metacharacters, including wildcards, are interpreted/expanded (by the shell) in the usual way. *line 131: SPURIOUS DIRECTIVE U *line 131: UNKNOWN DIRECTIVE U 2.2 To $U and from CSTVAX and ITSPNA *line 132: UNKNOWN DIRECTIVE U $U On cstvax, the utilities are in the directory /usr/local, while on itspna they are in ~gdmr/fs -- thus you can either prepend the appropriate path or include the directory in your search list. *line 139: SPURIOUS DIRECTIVE U *line 139: UNKNOWN DIRECTIVE U 2.2.1 $U UNIX to Filestore (TOFS) *line 140: UNKNOWN DIRECTIVE U $U To transfer files from the UNIX host to filestore B, use the command tofs: TOFS [-u filestore-user] [-p password] file file file ..... The parts in "[..]" are optional. If -u is specified the next item in the argument list will be used as the filestore username; otherwise the filestore username will be taken to be the same as the UNIX username. If -p is specified the next item in the argument list will be used as the filestore password; otherwise the user will be prompted. One or more files can be transferred using this command. The filenames at the UNIX and filestore ends are the same. They must, of course, be valid filestore names (12 or fewer of alphabetic, numeric, '$', '.', ''). _ *line 158: SPURIOUS DIRECTIVE U *line 158: UNKNOWN DIRECTIVE U 2.2.2 $U Filestore to UNIX (FROMFS) *line 159: UNKNOWN DIRECTIVE U $U To transfer files from filestore B to the UNIX host, use the command fromfs: FROMFS [-u filestore-user] [-p password] file with the parts in "[..]" being as for tofs. One file can be transferred per invocation of the utility. *line 170: SPURIOUS DIRECTIVE U *line 170: UNKNOWN DIRECTIVE U 2.2.3 $U UNIX to Filestore printer (MHPRINT) *line 171: UNKNOWN DIRECTIVE U $U To send files to the machine halls printer use the command mhprint. This allows one or more files to be sent for printing and takes the form: MHPRINT file file file ..... *line 180: SPURIOUS DIRECTIVE U *line 180: UNKNOWN DIRECTIVE U 2.2.4 $U CSTVAX to CSTVAX laser printer *line 181: UNKNOWN DIRECTIVE U $U To send files to the laser printer (cstvax only) use the command newlaser. NEWLASER file file file ..... *line 190: SPURIOUS DIRECTIVE U *line 190: UNKNOWN DIRECTIVE U 2.3 To $U and from ECSVAX (Initiated on ECSVAX) *line 191: UNKNOWN DIRECTIVE U $U *line 195: SPURIOUS DIRECTIVE U *line 195: UNKNOWN DIRECTIVE U 2.3.1 $U ECSVAX to Filestore (TOFS) *line 196: UNKNOWN DIRECTIVE U $U This command sends files to the Filestore over the ethernet. The user can select which filestore is to be used, and the user number on the filestore where the file is to be put. The file inherits the same name as it had to VAX. Format: TOFS filespec[,filespec[,...]] Parameters are a list of one or more filenames, separated by commas (',') or plus signs ('+'). Wildcards are accepted. Qualifiers may be applied to the command verb in which case they apply to all the files, or to an individual filespec in which case they apply only to that filespec overriding any global qualifiers e.g. /FS. *line 215: SPURIOUS DIRECTIVE U *line 215: UNKNOWN DIRECTIVE U 2.3.1.1 $U /FS *line 216: UNKNOWN DIRECTIVE U $U /FS = filestore /FS=A /FS=B (default) /FS=C /FS=P This is used to select which filestore is to be used. *line 229: SPURIOUS DIRECTIVE U *line 229: UNKNOWN DIRECTIVE U 2.3.1.2 $U /USER *line 230: UNKNOWN DIRECTIVE U $U /USER = username /USER=JGH This parameter chooses the filestore directory which is to receive the file. If it is omitted, then it defaults to the same directory as the VAX username. The TOFS program always prompts for the associated password, which is not echoed. *line 244: SPURIOUS DIRECTIVE U *line 244: UNKNOWN DIRECTIVE U 2.3.2 $U Filestore to ECSVAX (FROMFS) *line 245: UNKNOWN DIRECTIVE U $U This command fetches files from the Filestore over the ethernet. The user can select which filestore is to be used, and the user number (directory) on the filestore where the file is to be fetched from. Format: FROMFS filespec The parameter is the name of the file on VAX which is to be created. Qualifiers may be applied to the command verb to control the operation of the FROMFS program. *line 260: SPURIOUS DIRECTIVE U *line 260: UNKNOWN DIRECTIVE U 2.3.2.1 $U /FS *line 261: UNKNOWN DIRECTIVE U $U /FS = filestore /FS=A /FS=B (default) /FS=C /FS=P This is used to select which filestore is to be used. *line 274: SPURIOUS DIRECTIVE U *line 274: UNKNOWN DIRECTIVE U 2.3.2.2 $U /USER *line 275: UNKNOWN DIRECTIVE U $U /USER = username /USER=JGH This parameter chooses the filestore directory where the file is to be fetched from. If it is omitted, then it defaults to the same directory as the VAX username. The FROMFS program always prompts for the associated password, which is not echoed. *line 288: SPURIOUS DIRECTIVE U *line 288: UNKNOWN DIRECTIVE U 2.3.2.3 $U /FILE *line 289: UNKNOWN DIRECTIVE U $U /FILE = fsname /FILE=$TEMP This parameter allows the user to fetch files which have a different name on the filestore from the name that they are required to have on the VAX. This parameter chooses the filestore filename to be used. *line 303: SPURIOUS DIRECTIVE U *line 303: UNKNOWN DIRECTIVE U 2.4 To $U and from ECSVAX (Initiated on APMs) and between APM filestores *line 304: UNKNOWN DIRECTIVE U $U See HELP EFTP *line 312: SPURIOUS DIRECTIVE U *line 312: UNKNOWN DIRECTIVE U 3 Unix $U file transfer utilities *line 313: UNKNOWN DIRECTIVE U $U These sections have been taken directly from Unix MAN sections on ITSPNA and Cheops and there may be slight differences between machines. Consult MAN on the appropriate machine for definitive information. *line 322: SPURIOUS DIRECTIVE U *line 322: UNKNOWN DIRECTIVE U 3.1 $U Unix command rcp - Remote File Copy (BSD) *line 323: UNKNOWN DIRECTIVE U $U SYNTAX rcp file1 file2 rcp [-r] file ... directory file or directory is either a remote file name of the form "rhost:path", or a local file name (containing no : characters, or a / before any :s). If path is not a full pathname, it is interpreted relative to the login directory on rhost. A path on a remote host may be quoted (using \, ", or ') so the metacharacters are interpreted remotely. OPTIONS -r copies each subtree (when any of the source files is a directory) rooted at that name; in this case the destination must be a directory. DESCRIPTION Rcp copies files between machines. Rcp does not prompt for passwords; the current local user name must exist on rhost and allow remote command execution via rsh(1C). Rcp handles third party copies, where neither source nor target files are on the current machine, though the source and target machines must be on the same network. Hostnames may also take the form "rhost.rname" to use rname rather than the current user name on the remote host. EXAMPLES If user1 (the user on the local system) needs to copy a file from sys2 (the remote system) and he has a login on sys2, then he does the following: $ rcp sys2:path/filename1 sys1:path/filename2 If user1 (the user on the local system) needs to copy a file from sys2 (the remote system) and he is listed in a .rhost file on sys2, (i.e., sys1 user1, (sys1 is the local system)), then he must do the following: $ rcp sys2.user2:path/filename1 sys1:path/filename2 The .rhosts file is located in either user2's HOME directory (on sys2), or the root directory on sys2. SPECIAL CONSIDERATIONS o Rcp does not always detect the fact that a target of a copy might be a file in cases where only a directory should be legal. o The user cannot be root. o Rcp can be confused by any output generated by commands in a .login, .profile, or .cshrc file on the remote host. For example, the "Where are you?" message is produced because the .cshrc contains a biff. SEE ALSO ftp(1C), rsh(1C), rlogin(1C) *line 400: SPURIOUS DIRECTIVE U *line 400: UNKNOWN DIRECTIVE U 3.2 $U Unix command hhcp - host to host file transfer *line 401: UNKNOWN DIRECTIVE U $U SYNOPSIS hhcp [ -ACFLORS:abcfilmoqrstx ] [ SpecialOptions ] _ transmitfile receivefile _ _ DESCRIPTION Hhcp copies transmitfile into receivefile _ _ using NIFTP 80 Protocol. Either transmitfile or receivefile _ _ should be on a remote machine, in which case it should appear in the form ftpentityname[!|:]pathname _ _ ie "!" or ":" can be used to separate the host from the path Ftpentityname is the name of the NIFTP 80 entity on the remote _ _ machine. This must either appear in the network directory, or else be the Transport Service address of the entity (or the X25 address of the remote host if the TS address is the standard name "FTP"). eg hhcp /usr/keith/SEND kl!RECEIVE[1045,3307] or hhcp kl!SEND[1045,3307] /usr/keith/RECEIVE or hhcp SEND 6000000/FTP!RECEIVE[1045,3307] or hhcp 6000000!SEND[1045,3307] RECEIVE Input may be piped into hhcp, in which case transmitfile should _ be absent. pr file | hhcp [options] receivefile _ eg nroff doc.n | hhcp -L rlda!/usr/bill/doc An FTP connexion may require calls to be set up across several networks. If hhcp recognizes from the structure of the Transport Service address (see netdir(5)) mapped from a given name that authorization is required at one or more gateways between net- works, then the user is prompted for appropriate authorization fields (see getgwauth(3)). If the filename on the local machine is not a complete pathname it is prefixed with the current directory. If the remote machine is another unix, and receivefile is a _ pathname preceded by ~user, then ~user is ultimately replaced by that user's login directory on the remote system. eg hhcp file rlda!~bill/file The pathname part of ftpentityname!pathname must be in a form _ _ intelligible to the remote machine. If this pathname includes shell metacharacters, the pathname must be escaped using double quotes eg hhcp file othersys!"path>name" _ The user must always supply access authorization, in the form of a name and a password. This information should be as required by the remote NIFTP 80 entity, so that the password may be either a login password or a special file transfer password. These authorization strings are transmitted to the remote FTP as User- name and Username Password attributes. Other attributes may be selected by use of the command line options. Selected attributes are input by hhcp either by prompting the user, or by searching an attribute storage file for a list of attributes pertaining to the remote NIFTP entity. If such a list (see hhstore(1)) is present, selected attributes are always taken from the storage file unless the -t option is used. The command options are: A select Account and Account password attributes L Generate a transfer log (see hhlog (1)) C encrypt file before transmission (inter-Unix transfers only). F Use NIFTP-80 text format mode (hex) 0080. This implies NO text formatting by imbedded characters in the file and NO formatting actions on end of transfer record. The default (no flag) uses text format mode (hex) 0001 where end of record implies new line action. No actions are implied by embedded characters. o select Output device type and Output device type qualifier attributes. A remote pathname is not necessary eg hhcp -o file rlpb a select a non-default (= make or replace) mode of access attribute. The supplied attribute must be a character string and one of "replace","append","read and remove","append or make" and "make". b select a binary word size attribute for binary transfers. This option is not necessary if the file to be transferred is in a.out(5) format. Such files are recognized as binary, and are transmitted using a default Binary Word Size (16 on PDP-11 and LSI-11, 32 on VAX). A user-supplied value must be a multiple of 8 bits. f select a File password attribute s select a Special Options attribute. If prompted, the user should prefix a numerical character string response with a '#' if this parameter is to be transmitted as a 16 bit value rather than a character string. eg special options: #123 Use of this option cancels file encryption if the -C option is also present. x The transferred file is to be submitted for execution on the remote host. This forces mode of access "take job input"; it supercedes any mode of access requested via the -a option. c Print the queue entry (username and username password attributes are encrypted) l Send a local transmitfile to line-printer (LPR) on the _ remote machine. A remote pathname is not required. eg hhcp -l textfile kl _ O prompt for an Action Message attribute. The response should be a character string, terminated with EOF. i prompt for an Information Message attribute. The response should be a character string, terminated with EOF. S "SpecialOptions" _ The next argument on the command line is taken as a string representing the Special Options attribute. If the first character of the string is a '#', then the remainder (which must be numeric) is converted into and transmitted as a 16 bit integer value. Otherwise, the string is transmitted without modification. eg hhcp -lS "/unit:daisy" document kl hhcp -S #123 file ykda!rfile The use of the -S option overrides the use of the -s option. R make the call reverse charge if over a chargeable network (eg PSS). t select nominated attributes by prompting; do not search attribute storage file q queue the file only: do NOT invoke hhP daemon. For each file, hhcp reports a Transfer Identifier. This is useful for subsequent calls on hhq, hhrm, and hhlog. SEE ALSO nac(1). Authorise users for network access nd(1) Interrogate network directory hhq(1) Display transfer queue hhrm(1) Remove items from the transfer queue hhstore(1) create entries in attribute storage file hhlog(1) Print the transfer log netdir(5) directory entry structure FILES /usr/lib/x25/directory for the network directory file /usr/lib/x25/accounts/* for authorization /usr/lib/x25/hhstore/* for attribute storage files /dev/net? for access to network /usr/lib/x25/hhP for NIFTP P process /usr/lib/x25/hhQ for NIFTP Q process /usr/spool/hhcp/* for HHCP spool files *line 612: SPURIOUS DIRECTIVE U *line 612: UNKNOWN DIRECTIVE U 3.3 $U Unix command tftp - user interface to the DARPA TFTP protocol *line 613: UNKNOWN DIRECTIVE U $U ORIGIN 4.2BSD SYNOPSIS tftp [ host [ port ] ] DESCRIPTION Tftp is the user interface to the ARPANET standard Trivial File Transfer Protocol. The program allows a user to transfer files to and from a remote network site. The client host with which tftp is to communicate may be specified on the command line. If this is done, tftp will immediately attempt to establish a connection to a TFTP server on that host. Otherwise, tftp will enter its command interpreter and await instructions from the user. When tftp is awaiting commands from the user, the prompt tftp> appears. The following commands are recognized by tftp: connect connect to remote tftp mode set file to transfer mode put send file get receive file quit exit tftp verbose toggle verbose mode trace toggle packet tracing status show current status rexmt set total retransmission ? print help information timeout set total retransmission timeout The use of tftp does not require an account or password on the remote system. Due to the lack of authentication infor- mation, tftp will allow only publicly readable files to be accessed. BUGS The search permissions of the directories leading to the files accessed are not checked. *line 678: SPURIOUS DIRECTIVE U *line 678: UNKNOWN DIRECTIVE U 4 $U ECSVAX command FTP: File transfer to the X25 network *line 679: UNKNOWN DIRECTIVE U $U Allows file transfer between Vax and other computer systems using the 'Blue Book` protocol. The commands DEVICE, USER and ACCOUNT specify information relevant to the remote computer system. The SEND and FETCH commands are used to transfer files. The QUEUE command monitors progress of transfers, and the REMOVE command can be used to cancel requests. *line 692: SPURIOUS DIRECTIVE U *line 692: UNKNOWN DIRECTIVE U 4.1 $U ACCOUNT *line 693: UNKNOWN DIRECTIVE U $U Used to select an account and account password on the remote computer system. Format is : ACCOUNT If desired, may be typed on the line following the command, in which case it is not echoed. If the logical name FTP$ACCOUNT is assigned on entry to FTP, it is translated as giving a account name, optionally separated by spaces from an account password. *line 711: SPURIOUS DIRECTIVE U *line 711: UNKNOWN DIRECTIVE U 4.2 $U DEVICE *line 712: UNKNOWN DIRECTIVE U $U Used to select the remote computer system. Format is : DEVICE [ []] is a mnemonic for the remote site is an optional output device name at the site is an optional output device qualifier at the site If the logical name FTP$DEVICE is assigned on entry to FTP, it is translated as giving a remote name, optionally separated by spaces from a device name and a device qualifier. Type HELP PLACES for a list of current remote site mnemonics. *line 732: SPURIOUS DIRECTIVE U *line 732: UNKNOWN DIRECTIVE U 4.3 $U EXIT *line 733: UNKNOWN DIRECTIVE U $U Causes the FTP program to terminate and a return to Vax command level. Format is : EXIT An equivalent effect may be obtained by typing ctrl-z at any time. *line 746: SPURIOUS DIRECTIVE U *line 746: UNKNOWN DIRECTIVE U 4.4 $U FETCH *line 747: UNKNOWN DIRECTIVE U $U Used to send a file to Vax from the currently selected remote computer system. Format is : FETCH [/FAILMAIL] [/NOMAIL] [/] [/] [/] [/PASSWORD []] By default, the user is sent mail when the file transfer request has been dealt with. If the /FAILMAIL qualifier is used, mail is only sent in the event of failure. If /NOMAIL is used, no mail is sent in any event. The qualifier specifies the format that the file is to have on Vax. It should be used when the remote computer does not know that the file is to be created in a format other than the default, which is text in records with automatic newline at end of record. Specifiable formats are: /VMS : Any format file from a remote VAX/VMS computer /BINARY : Undefined format file (e.g. Imp -b file) /FTN : Fortran file with column one controls /NOCR : Text file with no automatic newline at end of record The qualifier specifies the action to be taken on Vax when the file arrives. If it is omitted, the file is simply created. Specifiable actions are: /REPLACE : A previous version of the file must be replaced /?REPLACE : A previous version of the file should be replaced if it exists /APPEND : This file must be appended to a previous version /?APPEND : This file should be appended to a previous version if it exists /JOB : This file should be sent to the system batch queue /PRINT : This file should be sent to the system printer The qualifier specifies the action to be taken on the remote computer system. If it is omitted, is a file, which is preserved after transmission. Specifiable actions are: /DELETE : File is deleted after transmission /DESTROY : File is deleted as it is transmitted /JOB : File to be taken from a batch queue /PRINT : File to be taken from an output queue If the /PASSWORD qualifier is specified, then a remote file password may be typed unechoed on the following line. If echoing is not important, it may be given as . If a filename contains the characters newline, space, tab, /, or ", the offending character(s) (doubled in the case of ") may be enclosed within string quotes, e.g. "/usr/crap", "fred jim", fred" "jim. *line 802: SPURIOUS DIRECTIVE U *line 802: UNKNOWN DIRECTIVE U 4.5 $U HELP *line 803: UNKNOWN DIRECTIVE U $U Allows file transfer between Vax and other computer systems using the 'Blue Book` protocol. Type HELP PLACES for a list of known sites. The commands DEVICE, USER, and ACCOUNT specify information relevant to the remote computer system. The SEND and FETCH commands are used to transfer files. The QUEUE command monitors progress of transfers, and the REMOVE command can be used to cancel requests. For further information, type HELP . Additional information available: ACCOUNT DEVICE EXIT FETCH HELP PLACES QUEUE REMOVE SEND USER *line 823: SPURIOUS DIRECTIVE U *line 823: UNKNOWN DIRECTIVE U 4.6 $U List of known FTP destinations *line 824: UNKNOWN DIRECTIVE U $U ABDN Aberdeen ABDN.CSVAX Aberdeen CS Vax ADADG Data General ADA BUSH Bush Emas CAM.CL Cambridge Computer Lab CAM.ENG-ICF Cambridge GEC CSTVAX CS Unix Vax EDAI AI Unix EDEE EE Vax EDLING Linguistics Vax EDXA Edinburgh DEC-10 EMAS Edinburgh Emas EPISTEMI Epistemics Unix ERCVAX ERCC Vax EUSIP Speech Tech. Unix FSTORE ERCC Filestore GEOVAX Geography Vax GLA.EKVA Kelvin labs HW.GA Heriot-Watt GEC IC.DOC.IGEC Imperial CS IKBS GEC IC.DOC.IVAX Imperial CS IKBS Vax ITS63A ITS GEC 63 A ITS63B ITS GEC 63 B ITSPNA ITS Power Node A LANCS.VAX1 Lancaster Vax LEEDS.LEVA Leeds Vax LIV.IBM Liverpool IBM MAN.CS.CAD Manchester CAD Vax MAN.CS.UX Manchester CS Unix NCL.MTS Newcastle MTS OX.VAX1 Oxford Vax 1 OX.VAX2 Oxford Vax 2 OX.VAX3 Oxford Vax 3 PHYVAX Physics Vax RL.GB Rutherford B RL.IB Rutherford CMS RL.PC Rutherford Prime C RL.PE Rutherford Prime E RL.PF Rutherford Prime F ROE.GECA Observatory GEC ROE.STAR Observatory Vax SALF.E Salford SYSE ST-AND.SAVA St Andrews Vax A ST-AND.SAVB St Andrews Vax B STIR.CS Stirling CS STIR.VAXA Stirling Vax SUSSEX.VAX2 Sussex Vax 2 UCL.CS UCL Gateway UCL.STAR UCL Starlink Vax UEA.PROTEUS East Anglia Vax UKC.EAGLE Kent Eagle UKC.HAWK Kent Hawk UMGR UMIST GEC 63 WARWK.DAISY Warwick Daisy WARWK.PA Warwick Prime YORK.BALHAM York Gateway YORK.KL York DEC-10 YORK.MINSTER York Unix Vax *line 860: SPURIOUS DIRECTIVE U *line 860: UNKNOWN DIRECTIVE U 4.7 $U QUEUE *line 861: UNKNOWN DIRECTIVE U $U Displays one or more FTP queues. Format is : QUEUE [] If is omitted, then all queues are displayed. *line 873: SPURIOUS DIRECTIVE U *line 873: UNKNOWN DIRECTIVE U 4.8 $U REMOVE *line 874: UNKNOWN DIRECTIVE U $U Used to remove a file transfer request from a queue. Format is : REMOVE is obtained by using the QUEUE command to locate the relevant request. *line 887: SPURIOUS DIRECTIVE U *line 887: UNKNOWN DIRECTIVE U 4.9 $U SEND *line 888: UNKNOWN DIRECTIVE U $U Used to send a file from Vax to the currently selected remote computer system. Format is : SEND [/FAILMAIL] [/NOMAIL] [/VMS] [/DELETE] [/] [/PASSWORD []] By default, the user is sent mail when the file transfer request has been dealt with. If the /FAILMAIL qualifier is used, mail is only sent in the event of failure. If /NOMAIL is used, no mail is sent in any event. If the /VMS qualifier is used, the remote computer is assumed to be a VAX running VMS, and so any format of file may be sent with the guarantee that all of its VMS file attributes will be preserved in the new file. If the /DELETE qualifier is used, the file is deleted after transmission. The qualifier specifies the action to be taken on the remote computer system. If it is omitted, the file is simply created (but note that some systems may demand that a file with the same name does not already exist). Specifiable actions are: /REPLACE : A previous version of the file must be replaced /?REPLACE : A previous version of the file should be replaced if it exists /APPEND : This file must be appended to a previous version /?APPEND : This file should be appended to a previous version if it exists /JOB : This file should be sent to a batch job queue /PRINT : This file should be sent to an output queue If the /PASSWORD qualifier is specified, then a remote file password may be typed unechoed on the following line. If echoing is not important, it may be given as . If a filename contains the characters newline, space, tab, /, or ", the offending character(s) (doubled in the case of ") may be enclosed within string quotes, e.g. "/usr/crap", "fred jim", fred" "jim. *line 932: SPURIOUS DIRECTIVE U *line 932: UNKNOWN DIRECTIVE U 4.10 $U USER *line 933: UNKNOWN DIRECTIVE U $U Used to select a username and password on the remote computer system. Format is : USER If desired, may be typed on the line following the command, in which case it is not echoed. If the logical name FTP$USER is assigned on entry to FTP, it is translated as giving a username, optionally separated by spaces from a password. *line 951: SPURIOUS DIRECTIVE U *line 951: UNKNOWN DIRECTIVE U 5 $U Document printing *line 952: UNKNOWN DIRECTIVE U $U Printer> mc hall mc hall 6301 2419 3421 1417 16-- EdNet Orion Sender | c.itoh Toshiba PTronix Laser Laser Laser Laser Var. ? v----------------------------------------------------------------------------- ECSVAX | FSPrint MHprint - laser laser lpr/14 lpr/16 netprint - CSTVAX | FSprint LPR/? - newlaser- lpr/14 lpr/16 ? ? APM/FS | P - - laser laser - - - - Unix(*)| - LPR/? - - - lpr/14 lpr/16 - - GEC 63s| ? ? ? ? ? ? ? ? ? EMAS | - - - - - - - list - ITSPNA | FSprint LPR/CS lpr/7 tofs tofs lpr/4 lpr/4 hhprint ? Orion | - - - - - - - - lpr /4 Print queue unknown /7 lpr -Pcsmsc /14 ECSVAX: lpr /P=LW14 Unix: lpr -p lw14 /16 ECSVAX: lpr /P=lw16 Unix: lpr -p lw16 See also overview note /10 *line 974: SPURIOUS DIRECTIVE U *line 974: UNKNOWN DIRECTIVE U 5.1 $U Whereabouts and general description of printers *line 975: UNKNOWN DIRECTIVE U $U In the machine halls... There is the C.Itoh 600 attached to Filestore B (one of the QSART ports) and driven by it. Accessed by PRINT from APMs. FSPRINT from ECSVAX, ~gdmr/fs/fsprint from itspna. There is a Toshiba attached to the Gandalf and driven by ECSVAX and CSTAVX This device is rather slow for large volumes of output. The queue lp is accessible from all the other 4.2BSD machines which are regarded as equivalent hosts by CSTVAX (all the Suns, basically), as the printer daemon mechanism transparently (to the user) transfers files between machines. This printer can print only TEXT files. In the copier room (2417?)... There is the original prototype APM/Laser printer attached to the 2Mb Ethernet. This prints LAYOUT 1.5 script and TeX DVI and is accessed by LASER command from ECSVAX and APM. Authorisation is required to use this. In Sidney's outer office (3421) ... There is a CLAN laser printer driven from an APM. This despools from B::LP2: and prints LAYOUT 2.0 script. Commands unknown. In 1619... There is an Apple LaserWriter attached to CSTVAX, and thus accessible from al the 4.2BSD equivalent hosts. It prints DVI and text (no LAYOUT). There's a Spinwriter on the back of a Bantam on a direct line to ECSVAX. When the PRINT button on the Bantam is depressed the printer is connected transparently to ECSVAX. The command "LAYOUT/NEC=TT: file" can be used to print (old-style) LAYOUT files. In the M.Sc workroom (6301) ... There is a Printronix printer, accessible directly from ITSPNA. This will be replaced by a Toshiba when it is fixed. At the Tower... There's a LaserWriter driven by the Macs, and an HP LaserJet attached to EMAS and despooling its .LPIS1 queue. There's also the CS1 printer (another Printronix) on level 3 accessible as .lpcs1. ECSVAX can send stuff to the printers spooled by Filestore B (c.itoh and PC-room laser printer). These printers are also accessible from cstvax and itspna via RS232 links to Filestore B (two more qsart ports). The large HP plotter is attached directly to ECSVAX, as is one of the small plotters. The other plotters are attached to a APM. *line 1032: SPURIOUS DIRECTIVE U *line 1032: UNKNOWN DIRECTIVE U 5.2 $U APM command PRINT *line 1033: UNKNOWN DIRECTIVE U $U See HELP PRINT for full description. Summary: Command is P - - printers are: -mh (m/c halls printer) only params are: -c -l -dp *line 1048: SPURIOUS DIRECTIVE U *line 1048: UNKNOWN DIRECTIVE U 5.3 $U Unix command lpr - Off Line Print (BSD) *line 1049: UNKNOWN DIRECTIVE U $U SYNTAX lpr [-Pprinter] [-#num] [-C class] [-J job] [-T title] [-i [numcols]] [-w#] [-plrmhs] [name ...] OPTIONS -C class specifies a classification for use on the burst page. -f uses a filter that interprets the first character of each line as a standard FORTRAN carriage control character. -h suppresses the printing of the burst page. -i [numcols] indents the output. If the next argument is numeric, it is used as the number of blanks to be printed before each line; otherwise, 8 characters are printed. -J job specifies the job name to print on the burst page. Normally, the first file name is used. -l uses a filter allowing control characters to be printed and supresses page breaks. -m sends mail upon completion. -p causes pr(1) to format the files (equivalent to print). -Pprinter forces output to a specific printer. Normally, the default printer is used (site dependent), or the value of the environment variable PRINTER is used. -r removes the file upon completion of spooling (with the -s option). -s uses symbolic links. Usually files are copied to the spool directory. The -s option uses symlink(2) to link data files rather than trying to copy them so large files can be printed. The files should not be modified or removed until they have been printed. -T title specifies the title used by pr(1) instead of the file name. -wn specifies the page width for pr. -#num specifies multiple copies of output, where num is the number of copies desired of each file named. DESCRIPTION Lpr uses a spooling daemon to print the named files when facilities become available. If file names do not appear, the standard input is used. EXAMPLES $ lpr -C "Lincoln Labs" foo.c $ lpr -C causes the system name to be replaced on the burst page by Lincoln Labs, and the file foo.c to be printed. $ lpr -#3 foo.c bar.c more.c $ lpr -#3 prints three copies of the files foo.c, bar.c, and more.c. $ cat foo.c bar.c more.c | lpr -#3 $ This example prints three copies of the concatenation of the files. SPECIAL CONSIDERATIONS o Large files may be truncated. o Various other filters and associated options are built into this command for use with devices not currently supported in UTX/32 (e.g., the Benson Varian raster printer). To use any of these, the proper definitions must be placed in /etc/printcap. Refer to printcap(4). To use -f, there should be an entry similar to rf=/usr/bin/asa in the system printcap file. FILES /etc/passwd personal identification /etc/printcap printer capabilities data base /usr/lib/lpd* line printer daemons /usr/spool/* directories used for spooling /usr/spool/*/cf* daemon control files /usr/spool/*/df* data files specified in "cf" files /usr/spool/*/tf* temporary copies of "cf" files /usr/lib/lpf standard filter (various filters are specified in /etc/printcap) DIAGNOSTICS o Lpr objects to printing binary files. o Lpd(8) may print diagnostics in the daemon's log file regarding missing spool files. o If a user other than root prints a file and spooling is disabled, lpr prints a message and does not put jobs in the queue. o If a connection to lpd on the local machine cannot be made, lpr prints a message stating the daemon cannot be started. SEE ALSO lpq(1), lprm(1), pr(1), symlink(2), printcap(4), lpd(8) FTNOTE printed on 04/11/86 at 12.25 Program stopped