Return to BSD News archive
Newsgroups: comp.os.386bsd.development
Path: sserve!newshost.anu.edu.au!munnari.oz.au!news.Hawaii.Edu!ames!haven.umd.edu!decuac!pa.dec.com!e2big.mko.dec.com!peavax.mlo.dec.com!paik
From: paik@mlo.dec.com (Samuel S. Paik)
Subject: Re: A challenge to all true kernel hackers - conditional symlinks.
Message-ID: <1993Mar17.022003.12845@peavax.mlo.dec.com>
Sender: usenet@peavax.mlo.dec.com (USENET News System)
Organization: Digital Equipment Corporation
References: <C3ow4H.FID@BitBlocks.com> <JKH.93Mar10215639@whisker.lotus.ie> <C3qzvC.2ps@bcstec.ca.boeing.com> <1993Mar17.000717.12690@fcom.cc.utah.edu>
Date: Wed, 17 Mar 1993 02:20:03 GMT
Lines: 24
In article <1993Mar17.000717.12690@fcom.cc.utah.edu> terry@cs.weber.edu (A Wizard of Earth C) writes:
>The other fact, that the name space is only polluted for names beginning
>with "$(" means that collisoin is unlikely anyway, so the pollution is
>not disenfranchising "$", "(", and ")" as filename characters, but is
>instead diasallowing "$(" file names only.
Why would you want to restrict variables to only start at the
beginning of a file name, besides reducing name space pollution?
I'm virtually positive I had things like
/usr/local/bin --> /usr/local/bin.$(ARCH)
back when I was on Domain. (Apollo had two CPU architectures, the
m68k and PRISM). Then again, you can just as easily have
/usr/local/bin --> /usr/local/$(ARCH)/bin
as well (and in fact, nowadays I do this in my PATH variable...)
Sam Paik
Device Dependent Graphics
Alpha Personal Systems Software Group
Digital Equipment Corporation