decode /proc
in [General Linux]
|
From: J G Miller on 31 Jan 2010 14:13 On Sun, 31 Jan 2010 14:04:41 -0500, Lew Pitcher wrote: > So, unless the OP is willing to read /proc (even by way of a > client-server sort of application-level architecture), he's out of luck. > His only way into the data that /proc provides is through read syscalls > against /proc files in a running Linux system. Thanks for the explicit explanation. I would suggest your final point also explains why Peter, the original poster, has not returned to the discussion.
From: peter on 1 Feb 2010 02:25 I am here, I posted a post a few days ago. Thanks for the replies. I guess I have no way to read the /proc from outside. May be i need to write a agent that run inside the linux, then read the information from it from outside. thanks from Peter
From: unruh on 1 Feb 2010 09:46 On 2010-02-01, peter <cmk128(a)gmail.com> wrote: > I am here, I posted a post a few days ago. > > Thanks for the replies. I guess I have no way to read the /proc from > outside. May be i need to write a agent that run inside the linux, > then read the information from it from outside. > thanks > from Peter Maybe if you told us what it is that you really want to do someone could give some useful advice. I do not know what "read the /proc from outside" could mean. /proc only exists if the linux kernel is running. If it is not running, it does not exist, and there is nothing to read. What does "from the outside" mean? How would you imagine being able to read kernel things "from the outside" and at the same time not being able to read /proc as a filesystem?
From: Tauno Voipio on 1 Feb 2010 11:44 unruh wrote: > On 2010-02-01, peter <cmk128(a)gmail.com> wrote: >> I am here, I posted a post a few days ago. >> >> Thanks for the replies. I guess I have no way to read the /proc from >> outside. May be i need to write a agent that run inside the linux, >> then read the information from it from outside. >> thanks >> from Peter > > Maybe if you told us what it is that you really want to do someone could > give some useful advice. I do not know what "read the /proc from > outside" could mean. /proc only exists if the linux kernel is running. > If it is not running, it does not exist, and there is nothing to read. > What does "from the outside" mean? How would you imagine being able to > read kernel things "from the outside" and at the same time not being > able to read /proc as a filesystem? It seems that the OP is running a virtual machine or debugger, and he is interested to look at /proc entries without running the target system. -- Tauno Voipio
From: spike1 on 1 Feb 2010 13:41
And verily, didst Tauno Voipio <tauno.voipio(a)notused.fi.invalid> hastily babble thusly: > unruh wrote: >> On 2010-02-01, peter <cmk128(a)gmail.com> wrote: >>> I am here, I posted a post a few days ago. >>> >>> Thanks for the replies. I guess I have no way to read the /proc from >>> outside. May be i need to write a agent that run inside the linux, >>> then read the information from it from outside. >>> thanks >>> from Peter >> >> Maybe if you told us what it is that you really want to do someone could >> give some useful advice. I do not know what "read the /proc from >> outside" could mean. /proc only exists if the linux kernel is running. >> If it is not running, it does not exist, and there is nothing to read. >> What does "from the outside" mean? How would you imagine being able to >> read kernel things "from the outside" and at the same time not being >> able to read /proc as a filesystem? > > > It seems that the OP is running a virtual machine or debugger, > and he is interested to look at /proc entries without running > the target system. > I think he wants to read them from the running system from OUTSIDE the virtual machine... for some peculiar reason. -- | spike1(a)freenet.co,uk | "Are you pondering what I'm pondering Pinky?" | | Andrew Halliwell BSc | | | in | "I think so brain, but this time, you control | | Computer Science | the Encounter suit, and I'll do the voice..." | |