Is proc file system standardized across distro

alred · 03-25-2005, 08:40 AM

sometimes i feel like using proc file system to get infomation/status,
which is the directory /proc in my redhat9,
but afraid that proc file system is not standardized across distro
i using redhat9 it's impossible for me to verify this concern myself.
Any advice and suggestion from anybody who play
with proc file system before ?

thanks in advance

itsme86 · 03-25-2005, 09:44 AM

It depends on how the kernel is compiled. I personally recompile my kernel after installing any distro so it's optomized for the system I'm running it on and for the way I'm going to use the computer.

It's possible to even not compile /proc support into the kernel, but it's not a likely scenario. Anyway, the real question is whether the /proc filesystem is standard across different kernel versions, and the answer is that the fundamental stuff you can be pretty sure will stay the same, but there are small things that change.

alred · 03-25-2005, 12:22 PM

Can user applications write/update to the proc file system through coding?
or only the kernel can write/update to the proc file system.

alred · 03-26-2005, 01:13 AM

after itsme86 telling proc filesystem is a kernel stuff
do some searching and found this
interesting for me and decided to post it here for those who
had not already know,

[http://www-106.ibm.com/developerwork...y/l-adfly.html

sounds like a "window registry" for me
thanks itsme86

Kdr Kane · 03-26-2005, 05:57 AM

I believe that a distro must have the proc filesystem to be LSB compliant. And most of the distros are moving to be compliant.

www.linuxbase.org

alred · 03-27-2005, 02:37 PM

Quote:

I believe that a distro must have the proc filesystem to be LSB compliant. And most of the distros are moving to be compliant.

good news for everybody,hopes that it doesn't degenerated into a "install into /usr/bin(or lib) or /use/local/bin(or lib) or
/opt" kind of confusion

jlliagre · 03-27-2005, 03:19 PM

Quote:

good news for everybody,hopes that it doesn't degenerated into a "install into /usr/bin(or lib) or /use/local/bin(or lib) or
/opt" kind of confusion

Confusion is part of today's linux experience, cleaning the mess and reducing this confusion is part of what LSB is promoting.