On Fri, 2003-10-17 at 09:37, Brett Franck wrote:
>
> Oh, yeah, um, well, yeah right I did that too...I added another 64MB ram
> to my box.who'd a thunk that a memory size increase would send Tripwire
> into alarm?
>
> Thanks Bret!! :-)
>
> Brett
>
No problem, Brett
Bret
--
redhat-
- Original Message -
From: "Bret Hughes" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Friday, October 17, 2003 9:33 AM
Subject: Re: KCORE Change
> On Fri, 2003-10-17 at 09:15, Brett Franck wrote:
> > All,
> >
> > My tripwire reported this
ff "portmap" because I'm not using
> NFS.
>
>
>
> Rule Name: Critical devices (/proc/kcore)
> Severity Level: 100
> -
me: Critical devices (/proc/kcore)Severity Level:
100---Modified:"/proc/kcore"---
TWUPD details show this..concerns
me.
Rule
On Tue, 16 Sep 2003 09:24:41 +0100
"Anthony Hay" <[EMAIL PROTECTED]> wrote:
> Anyone know why I can't see the PC BIOS at F hex in proc/kcore?
>
Hi Anthony,
/proc/kcore is not a raw memory image, it's actually in the
ELF object format. Its header is 4K whi
Anyone know why I can't see the PC BIOS at F hex in proc/kcore?
--
redhat-list mailing list
unsubscribe mailto:[EMAIL PROTECTED]
https://www.redhat.com/mailman/listinfo/redhat-list
We just installed Red Hat 9 on a Compaq Evo D510 SFF. A tool we use that
reads DMI data from the IBMPC BIOS failed. We found the BIOS is not
where we expected it at offset 0xF in /proc/kcore, but at offset
0xF3000 instead. I thought /proc/kcore was a straight-forward map of
physical memory
Dear Madhvi,
/proc is nothing but your physical memory ( i mean random access memory
of your machine !!!) . kcore is the file which has the data that is currently
loaded into the memory
Thanks
K.Deepak
madhvi wrote:
HiI
am having memory problems on my server (RH7.1) When
Hi
I am having memory problems on my server
(RH7.1)
When I do ls -lF on /proc , what does the the
following line mean
-r 1
root root 536875008 Jun 26 15:46
kcoreCan this be the reason why I am getting memory shortage
problems?
Madhvi
