Return to BSD News archive
Path: sserve!newshost.anu.edu.au!munnari.oz.au!news.Hawaii.Edu!ames!olivea!uunet!usc!howland.reston.ans.net!agate!dog.ee.lbl.gov!hellgate.utah.edu!fcom.cc.utah.edu!cs.weber.edu!terry
From: terry@cs.weber.edu (A Wizard of Earth C)
Newsgroups: comp.os.386bsd.development
Subject: Re: A challenge to all true hackers: objects and types
Message-ID: <1993Mar27.081223.2547@fcom.cc.utah.edu>
Date: 27 Mar 93 08:12:23 GMT
References: <JKH.93Mar20153113@whisker.lotus.ie> <ARNEJ.93Mar24113744@chanur.imf.unit.no> <C4FEo2.8no@sugar.neosoft.com>
Sender: news@fcom.cc.utah.edu
Organization: Weber State University (Ogden, UT)
Lines: 31
In article <C4FEo2.8no@sugar.neosoft.com> peter@NeoSoft.com (Peter da Silva) writes:
>In article <ARNEJ.93Mar24113744@chanur.imf.unit.no> arnej@imf.unit.no (Arne Henrik Juul) writes:
>> I also think that variant links using environment variables is a BAD
>> idea.
>
>I think that's a reasonable conclusion. How about variant links using
>some other set of per-process/per-uid symbolic name space?
As I pointed out in the previous post, this is based on the bad assumption
that a process may modify it's own environment or that of it's parent, both
of which are not allowed.
I don't think that the environment variable method should be thrown out
outright, since it works successfully already in several implementations.
An "environmnet that isn't" is functionally equivalent to process or system
logical names (ala VMS), depending on implementation. This functionality
would not necessarily be the target of variant links.
Terry Lambert
terry@icarus.weber.edu
terry_lambert@novell.com
---
Any opinions in this posting are my own and not those of my present
or previous employers.
--
-------------------------------------------------------------------------------
"I have an 8 user poetic license" - me
Get the 386bsd FAQ from agate.berkeley.edu:/pub/386BSD/386bsd-0.1/unofficial
-------------------------------------------------------------------------------