Path: utzoo!mnetor!uunet!seismo!sundc!pitstop!sun!amdcad!ames!nrl-cmf!ukma!gatech!udel!rochester!rutgers!im4u!ut-sally!utah-cs!utah-gr!stride!stride1!mitch
From: mitch@stride1.UUCP (Thomas P. Mitchell)
Newsgroups: comp.unix.wizards
Subject: Re: //host vs "mount point"
Message-ID: <702X@stride.Stride.COM>
Date: 21 Jan 88 00:00:00 GMT
References: <648@tut.cis.ohio-state.edu> <1668@tut.cis.ohio-state.edu> <35000@sun.uucp> <38d18d4f.4580@hi-csc.UUCP>
Sender: news@stride.Stride.COM
Reply-To: mitch@stride1.UUCP (Thomas P. Mitchell)
Organization: MicroSage Comp. Sys. Inc., 680 S. Rock Blvd, Reno, NV 89502
Lines: 36

In article <38d18d4f.4580@hi-csc.UUCP> giebelhaus@hi-csc.UUCP (Timothy R. Giebelhaus) writes:
>In article <35000@sun.uucp>, brent%terra@Sun.COM (Brent Callaghan) writes:
>> Another good reason for "just another directory" is that it leaves
>> open the possibility of having nodes other than host names under
>> the directory.  Consider the following:
>> 
>> 	/host/<hostid>	- file systems on other hosts
>> 	/home/<userid>	- users home directories
>> 	/src/<version>	- other source trees
>> 
>But the // directory is just another directory.

The use of "//" in a file name string bothers me.  

I just had a case of gnu-emacs parsing a file name
"/usr/me//.temp-filename" as "/.temp-filename".  Not being
superuser at the time I saw the error message. Searching found
that my environment variable "$HOME" was being set to
"/usr/mitch/".  Changing the environment "$HOME" to "/usr/mitch"
made the problem go away.

I did not see the problem sooner because many utilities reduce
"//" to "/" (try ls //).  Emacs saw the double "/" and assumes
that the user is over-riding a default and goes with the new file
name.

Well thanks for the soap.





Thomas P. Mitchell (mitch@stride1.Stride.COM)
Phone:	(702) 322-6868 TWX:	910-395-6073
MicroSage Computer Systems Inc. a Division of Stride Micro.
Opinions expressed are probably mine.