You are not being lied to. All of the files in /proc do not realy exist.
This means that until you read them there is nothing there. When you do read
them the kernel creats the information that is displayed on the spot. Try
cat /proc/meminfo or cat /proc/mounts and the command line to see what I
mean. Right now the difference with kcore is that it is a snapshot of your
memory at that point. If you type cat /proc/kcore then you will see what is
in you memory. Most of it will be crap but some times you will see words
from programs that you have run or files that you have saved. That is why
knoq reports it as 95mb because if it didn't then you would have no memory.
BTW looking at kcore will contuine for ever because the memory is allways
been updated. Also writing anything to kcore is a very bad idea. At best it
will crash your system. Also I think that the 1mb difference is the memory
taken by the kernel, but don't quote me on that.

Mark Hillary

----- Original Message -----
From: "bascule" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Wednesday, January 03, 2001 11:57 PM
Subject: Re: [newbie] core file


> thanks tom,
> yes i have 96mb ram, it's a bit unnerving to know that file sizes can be
lied
> about/misreported like that, is it just /dev/ entries that do this ? i
know
> this has confused me before, i'm a gui person really and i need to know
when
> to trust what konq is telling me!
>
> bascule
>
> On Wednesday 03 January 2001  9:30 pm, you wrote:
> > On Wednesday 03 January 2001 02:45 pm, bascule wrote:
> > > i have found a file named /dev/core which is approx 95mb (so it is
> > > claimed) which points to /proc/kcore also 95mb in size, this confuses
> > > me on 2 fronts, how could a symlink be 95mb in size and is this
> > > normal, /proc/...being a virtual filesystem - do i need to delete
> > > this file or not
> > >
> > > bascule
> >
> >    These aren't really files. Yes, they're vitual, sometimes called
> > pretend files. My /dev/core is 256mb.  That's the amount of ram I have.
> > I take it you have 96 ?
> > type  'du -ch /dev/*'  (try /proc/* too) and you'll see that most all
> > the 'files' in /dev are -0- byte.    The total for the whole /dev
> > directory should only be something over 100k, mostly due to many 1/2k
> > dir listings.  Don't delete anything in either /dev or /proc
>


Reply via email to