Yes, /proc is way cool, you can find out lots of good stuff there, however
have a clue when catting files, some files dont like that :( for instance
cat /proc/kcore
would probably be a bad idea :)

Jamie

On Thu, 27 Apr 2000, Michael J Smith wrote:

> Here's my little secret--
> 
> If you go to /proc you will find files that tell you all about the system.
> Just cat or less or more (less is more, thank you Seth) and you can see
> all sorts of interesting things.  I particularly like pci scsi/ and
> interrupts.
> 
> Michael J Smith
> Flyfisher, Russian Translator, and Professional Linux-Geek-at-Large
> 2250 Patterson #25
> Eugene, OR 97405
> (541) 346-7562
> 
> On Thu, 27 Apr 2000, Bob Crandell wrote:
> 
> > You didn't say you rebooted after you ran lilo.  Try that.
> > 
> > >>> <[EMAIL PROTECTED]> 4/26/2000 6:52:38 PM >>>
> > 
> > Actually, I *think* I have the same problem.  Is there a better
> > way to find out whether or not linux is seeing the memory other
> > than running top?  I've got 256 megs but top shows 
> > Mem:    64040K av
> > in the upper left corner.  *Something* is amiss since it gets really
> > sluggish running netscape.
> > 
> > I tried putting 
> > append="ram=256M" 
> > and also tried 
> > append="mem=256M"
> > (from another recommendation)
> > in my lilo.conf in the "image" section, just before read-only.
> > 
> > After typing "lilo" as root just afterward, I hit 'top' again
> > and it still only shows 64 MB.  Is there something I'm missing?
> > 
> > Curt
> > 
> > On Thu, Apr 20, 2000 at 02:17:01PM -0700, Seth Cohn wrote:
> > > At 11:11 PM 04/20/2000 +0200, you wrote:
> > > >Hi
> > > 
> > > 
> > > HI.  You're in DENMARK?  Ok.... a little far from Eugene
> > > 
> > > Somehow I don't think you're a regular at the meetings.
> > > 
> > > 
> > > >I have a strange problem with my redhat 6.2 linux server.
> > > >It have 256 Mb ram installed but linux only sees 64 Mb, if i run "top".
> > > 
> > > try adding: append="ram=256M"
> > > to your lilo.conf and run lilo.  should work.
> > > 
> > > Seth
> > > 
> > > 
> > 
> 

Reply via email to