Re: /proc file system

Hey, guys.

> >you have to read the kernel source code to figure what it does.

   There are a number of things in /proc that I've been able to figure out 
what they do, even though I've never read kernel source for it.  There are 
others (directories with just numbers in them) that I'm just plain clueless 
about.
   Lots of Unix machines have this same issue, and it's not a problem specific 
to Linux.  It's not something new users will often have to handle.

> Or you can Google your way to answer.
> This has worked for me.

   Somebody has to have the answer and make that answer available on the web 
for Google to have it in the first place...  but once it's there, then yes, 
this works.  The only problem is if everybody took this attitude, after which 
time there wouldn't be any answers to search for anymore.

> Also I find that /proc is mush easier to understand then the Windows
> Registry. Items in /proc make sense to me.

   The windows registry - *sigh*  I'll pass.  Yeah, /proc is a lot more 
understandable than the registry, even without looking at kernel source at 
all, NOR doing a google search...

> The point I am making is the registry keeps information buried deep and
> scattered. /proc tends to be simpler and direct. I find this easier then
> the Windows Registry.

   Even worse: the registry entires themselves are in directories that are 
just not human readable and get down to information that looks arbitrary.  
Delete the wrong registry key and your machine is hosed, and GOOD LUCK 
figuring out how to put it back if you didn't write it down first...
   And, naturally, there's tons of time to write them down because there just 
aren't that many registry keys, right?  *ahem*  Nevermind...

	- Chris

-- 
Chris Knadle
Chris.Knadle-15hjz6xD4c1Wk0Htik3J/[email protected]