Return to BSD News archive
Path: euryale.cc.adfa.oz.au!newshost.carno.net.au!harbinger.cc.monash.edu.au!munnari.OZ.AU!news.ecn.uoknor.edu!feed1.news.erols.com!cpk-news-hub1.bbnplanet.com!news.bbnplanet.com!mindspring!news.mindspring.com!xanax.HELLCOAST.ORG!halljb From: Jason Hall <halljb@mindspring.com> Newsgroups: comp.unix.bsd.freebsd.misc Subject: ps not using /proc? Date: Sun, 20 Jul 1997 06:08:06 -0400 Organization: MindSpring Enterprises Lines: 20 Message-ID: <Pine.BSF.3.96.970720055917.278B-100000@xanax.HELLCOAST.ORG> NNTP-Posting-Host: user-37kbv0d.dialup.mindspring.com Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Server-Date: 20 Jul 1997 10:09:00 GMT X-Sender: halljb@xanax.HELLCOAST.ORG Xref: euryale.cc.adfa.oz.au comp.unix.bsd.freebsd.misc:44708 Earlier today I wanted to make a small kernel modification so that users could only look at their own processes, I made the adjustment (changing the mode for the /proc/pid directory to 0500 .. compiled, rebooted, tryed doing a ps ax as a normal user and I got everything, then I looked at the ps binary, setgid to kmem =(. Why is FreeBSD still using kmem for getting ps info? Why implement the /proc filesystem if your not going to use it? I'm currently running the latest snapshot, will ps and top be rewritten to use kmem by 3.x-R ? Later. -- Jason Hall <halljb@mindspring.com>