On 22 Nov 2002, Dhee Reddy wrote:
> Just tried to look up some info and saw that the /proc filesystem
> doesn't
> contain any files.
> Shouldn't they contain entries correcponding to all the processes
> ? truely -- dhee
In fresh 5.0 installs, procfs is not enabled by default. Right now there
appear to be two tools in the system that pay a price for this:
(1) procfs -e relies on grubbing through /proc/<pid>/mem to find
environmental variables -- everything else, it can get through
sysctl().
(2) truss currently relies on procfs, albeit not working very well. There
were a set of patches floating around to make truss use ptrace(),
which is the direction we probably do want to take this. If someone
could finish up that work, it would be great.
The reasons to deprecate procfs are many-fold -- not least that there are
existing interfaces in the kernel that provide most or all of its features
at a substantially lower risk. You just have to see the kernel-related
security advisories for FreeBSD, Linux, Solaris, etc, over the last five
years to understand why we want to turn it off if we can. :-) There has
also been a concerted effort to move userland system monitoring tools away
from using /dev/kvm (direct kernel memory access) and towards using the
sysctl() MIB interface, reducing the level of privilege required to run
the monitoring tools.
Robert N M Watson FreeBSD Core Team, TrustedBSD Projects
[EMAIL PROTECTED] Network Associates Laboratories
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
