From owner-freebsd-current Wed Aug 28 20:02:12 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id UAA06788 for current-outgoing; Wed, 28 Aug 1996 20:02:12 -0700 (PDT) Received: from VX23.CC.MONASH.EDU.AU (vx23.cc.monash.edu.au [130.194.1.23]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id UAA06783 for ; Wed, 28 Aug 1996 20:02:08 -0700 (PDT) Received: from moa.cc.monash.edu.au (george@moa.cc.monash.edu.au) by vaxc.cc.monash.edu.au (PMDF V5.0-6 #16291) id <01I8UKMZL38O984W34@vaxc.cc.monash.edu.au>; Thu, 29 Aug 1996 13:01:00 +1000 Received: (george@localhost) by moa.cc.monash.edu.au (8.6.10/8.6.4) id NAA08388; Thu, 29 Aug 1996 13:00:50 +1000 Date: Thu, 29 Aug 1996 13:00:50 +1000 From: George Scott Subject: Re: FreeBSD malloc.c, -lmalloc, and squid. To: terry@lambert.org Cc: current@FreeBSD.org Message-id: <199608290300.NAA08388@moa.cc.monash.edu.au> Content-transfer-encoding: 7BIT Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk > The tentative implementation I was favoring used the following model: > > 1) Process logical names > > o Hung of proc struct of current process I'm not sure what this means! Could these logicals be accessed as a directory structure in procfs? Something like /proc/127/env/SHELL which can be read, written and unlinked to do getenv, setenv and unsetenv respectively for process 127? This would allow access to be controlled with the normal filesystem mode bits and would save us from having to have yet another set of system calls to implemented. The down side would be that having a procfs mounted would be almost mandatory. While I'm at it, creating a /proc/127/parent as a link to /proc/125 (meaning that pid 125 is the parent of pid 127) would allow neat things such as shell scripts that could set their parents environment variables with a simple: echo "new value" >/proc/curproc/parent/env/PATH George. -- George Scott George.Scott@cc.monash.edu.au Systems Programmer, Caulfield Computer Centre, Monash University