Return to BSD News archive
Newsgroups: comp.unix.bsd
Path: sserve!manuel.anu.edu.au!munnari.oz.au!uunet!pmafire!mica.inel.gov!ux1!fcom.cc.utah.edu!cs.weber.edu!terry
From: terry@cs.weber.edu (A Wizard of Earth C)
Subject: Re: 4.3BSD (all variants!) question about <sys/proc.h> and p_ruid
Message-ID: <1992Oct20.195600.2703@fcom.cc.utah.edu>
Sender: news@fcom.cc.utah.edu
Organization: Weber State University (Ogden, UT)
References: <1842@lysator.liu.se>
Date: Tue, 20 Oct 92 19:56:00 GMT
Lines: 36
In article <1842@lysator.liu.se> pen@lysator.liu.se (Peter Eriksson) writes:
>Do all versions of 4.3BSD (and later versions) contain a "p_ruid" member
>in the 'struct proc' structure? Is it in 386BSD? In BSD/386?
386BSD has it; every system that makes a distinction between SUID programs
and programs run by a particular UID has it. In SVR4, it's u_ruid.
On deficiency in BSD, in this vein, is the lack of a p_epid in the proc
struct to allow remote file access locking within the local system; the
reason lockd is required is that one can not distinguish one clients locks
from another; this is a real performance bottleneck for NFS clients.
>Is it only 386BSD that has the kvm_*() routines or is that part in
>4.4BSD as well? And in BSD/386?
Uh ...you lost me here -- you mean kern_malloc.c?
Try:
cd /sys
find . -name \*.c -exec grep \^kvm_ {} \; -print
I don't think it'll show anything for you either.
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
-------------------------------------------------------------------------------