Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 26 May 1998 22:02:31 +0200
From:      Poul-Henning Kamp <phk@critter.freebsd.dk>
To:        Mike Smith <mike@smith.net.au>
Cc:        sos@FreeBSD.ORG, dfr@nlsystems.com, cvs-committers@FreeBSD.ORG, cvs-all@FreeBSD.ORG, cvs-user@FreeBSD.ORG, cvs-gnu@FreeBSD.ORG, cvs-usrbin@FreeBSD.ORG
Subject:   Re: cvs commit: src Makefile src/gnu/usr.bin Makefile src/gnu/usr.bin/as Makefile src/gnu/usr.bin/ld Makefile sr 
Message-ID:  <1291.896212951@critter.freebsd.dk>
In-Reply-To: Your message of "Tue, 26 May 1998 11:48:51 PDT." <199805261848.LAA00570@dingo.cdrom.com> 

next in thread | previous in thread | raw e-mail | index | archive | help
In message <199805261848.LAA00570@dingo.cdrom.com>, Mike Smith writes:
>> >The only other posibility would be to add a new "symlinkvarspace" to
>> >each process, settable via some other means, (Poul allready screams
>> >sysctl, sysctl!! :)), I still like the environment vars better, and
>> >it is much easier used in scripts etc, but again I also know they
>> >are hell to implement...
>> 
>> No, I don't scream "sysctl!!", but this is the way to do it, and it
>> is not hard.
>
>Er, maybe.  It makes per-session variance somewhat difficult though.

No.  The problem is that using env-vars is not only messy and unwieldy
but also slow and prone to security problems.

Using a specific namespace which is inherited on fork will DTRT and
be efficient at the same time, without breaking scripts which happen
to use the "wrong" name for an env-var...

--
Poul-Henning Kamp             FreeBSD coreteam member
phk@FreeBSD.ORG               "Real hackers run -current on their laptop."
"ttyv0" -- What UNIX calls a $20K state-of-the-art, 3D, hi-res color terminal

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe cvs-all" in the body of the message



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1291.896212951>