Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!husc6!rutgers!super.upenn.edu!eecae!nancy!umix!paul
From: paul@umix.cc.umich.edu ('da Kingfish)
Newsgroups: comp.unix.wizards
Subject: Re: To . or not to .
Message-ID: <2732@umix.cc.umich.edu>
Date: Fri, 20-Nov-87 00:37:03 EST
Article-I.D.: umix.2732
Posted: Fri Nov 20 00:37:03 1987
Date-Received: Sun, 22-Nov-87 18:33:51 EST
References: <648@tut.cis.ohio-state.edu> <9171@mimsy.UUCP> <972@tut.cis.ohio-state.edu> <9363@tekecs.TEK.COM> <905@quacky.UUCP>
Reply-To: paul@umix.cc.umich.edu ('da Kingfish)
Organization: University of Michigan Computing Center, Ann Arbor
Lines: 18
Summary: using // as a network-wide root
UUCP-Path: {uunet,rutgers}!umix!paul


In article <905@quacky.UUCP> dce@quacky.UUCP (David Elliott) writes:
>I have mixed feelings about all of this, but I do hope that the V8
>style (/n/host/...) will win out.

(and someone else later opined that // for a root was a bad idea)

we have apollos here, and they have // meaning the network root.  for
/n/host style names, we just mkdir /n, and create links in there, so
that /n/fleetwood -> //fleetwood.  that seems to work, althought i just
did it quickly to see.

myself, i like apollo and // because there are no mount points, or
mounts to worry about.

--paul
-- 
Trying everything that whiskey cures in Ann Arbor, Michigan.
Over one billion messages read.