what does /proc or proc stand for?

what does /proc or proc stand for?

Post by yuan tze » Sat, 10 Apr 1993 12:10:34

Hi folks, can one of you explain to me what is /proc
and proc stuff?    Is these things related to filesystem?
Thanks for the help.  --yuan

1. PROPOSAL: /proc standards (was dot-proc interface [was: /proc

Just think about it for a minute.

There are three ways to address "/proc":
 - 100% binary interface
  * human interaction doesn't belong in the kernel - period.
 - optimally formated text
  * not designed for humans, but in human format ("text")
 - human readable
  * thus the entire OS is reduced to "cat" and "echo"

Providing more than one interface/format means code duplication.  It doesn't
matter how much is actually compiled.  Someone has to write it.  Others have
to maintain it.  Suddenly a change in one place becomes a change in dozens
of places.

Personally, I vote for a 100% binary interface. (no surprise there.)  It
makes things in kernel land so much cleaner, faster, and smaller.  Yes,
it increases the demands on userland to some degree.  However, printf/scanf
is one hell of a lot more wasteful than a simple mov.

For my worst case scenerio, answer this:
  How do you tell how many processors are in a Linux box?

The kernel already knows this, but it isn't exposed to userland.  So, one
must resort to ass-backward, stupid shit like counting entries in
/proc/cpuinfo.  And to make things even worse, the format is different for
every arch! (I've been bitching about this for four (4) years.)

And for those misguided people who think processing text is faster than
binary, you're idiots.  The values start out as binary, get converted to
text, copied to the user, and then converted back to binary.  How the hell
is that faster than copying the original binary value? (Answer: it isn't.)

And those who *will* complain that binary structures are hard to work with,
(you're idiots too :-)) a struct is far easier to deal with than text
processing, esp. for anyone who knows what they are doing.  Yes, changes
to the struct do tend to break applications, but the same thing happens
to text based inputs as well.  Perhaps some of you will remember the stink
that arose when the layout of /proc/meminfo changed (and broke, basically,


To unsubscribe from this list: send the line "unsubscribe linux-kernel" in

More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

2. Multiple name servers in resolv.conf

3. PROPOSAL: /proc standards (was dot-proc interface [was: /proc stuff])

4. Modem Interrogation

5. /proc/stat description for proc.txt

6. Flash Disk for Linux

7. /proc/mounts or /proc/mtab

8. terminal emulation and vi

9. /proc/net/tcp and /proc/net/udp

10. /proc/kcore vs. /proc/meminfo

11. /proc/<pid>/stat does not jive with proc(5) man page

12. ipv4: move proc stuff from net/ipv4/af_inet.c to net/ipv4/proc.c

13. proposal /proc/console (was /proc/vidinfo)