Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!ucbvax!NSIPO.NASA.GOV!goldstei
From: goldstei@NSIPO.NASA.GOV (Steve Goldstein)
Newsgroups: comp.protocols.tcp-ip
Subject: Re: syntax of remote pathnames?
Message-ID: <8903241227.AA15842@nsipo.arc.nasa.gov>
Date: 24 Mar 89 12:27:06 GMT
References: <MS-C.606686512.1103527590.mrc@SUMEX-AIM.Stanford.EDU>
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The Internet
Lines: 30

S*T*O*P !!!!!

You all are making things start to look like [you should pardon the 
expression . . .]

				VMS !!!

Part of the beauty of using UNIX is that one needn't have to recall all
the different decorations for hosts, devices, directories, etc. in specifying
a file.  (That's a feature of VMS which drives me up the wall!)

--SG

	 Some of us old-timers have used the convention of putting the host nam
	e in
	 square brackets in "[host]path" format, e.g.:
	 	[WSMR-SIMTEL20.ARMY.MIL]PD1:<MSDOS.NEMACS>EM39EXE.ARC
	 	[SUMEX-AIM.STANFORD.EDU]info-mac/app/contour81.hqx
	 	[SAIL.STANFORD.EDU]MONCOM.UPD[S,DOC]
	 	[AI.AI.MIT.EDU].INFO.;DDT ORDER

	 The path field is, of course, dependent upon the target operating syst
	em and,
	 as the final example shows, can be bizarre, so you need some reasonabl
	e way
	 to infer the path out of context (e.g. using all uppercase, or make it
	 be a
	 wholeline, etc...).

	 -------