Mailing List ArchiveSupport open source code!
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]memory holes and kernel params
- To: "'tlug@example.com'" <tlug@example.com>
- Subject: memory holes and kernel params
- From: "Doughty, Michael" <Doughty_Michael@example.com>
- Date: Thu, 26 Jul 2001 19:05:18 +0900
- Delivered-To: tlug@example.com
- List-Help: <mailto:tlug-request@example.comsubject=help>
- List-Post: <mailto:tlug@example.com>
- List-Subscribe: <mailto:tlug-request@example.comsubject=subscribe>
- List-Unsubscribe: <mailto:tlug-request@example.comsubject=unsubscribe>
- Old-Return-Path: <Doughty_Michael@example.com>
- Reply-To: tlug@example.com
- Resent-From: tlug@example.com
- Resent-Message-ID: <GlQV_.A.6-.4t-X7@example.com>
- Resent-Sender: tlug-request@example.com
Ok, here is the deal. I have an ancient Compaq 1500 beast that I have dropped linux on. But I have a minor problem, in that it has a memory hole that is causing the kernel a bit of grief. Now I know I can warn it about the memory hole in lilo.conf with a line like: append="mem=##M@example.com" What I don't know, and can't find any documentation on, is what do the ## stand for? Does this line say I have a contiguous block of RAM that is ## in size starting at 16M, or does it say I have a total of ## in ram, with a 1MB hole running from 15M-16M? ie, if I have 128M of physical memory and a memory hole at 15-16M, should my lilo line look like: append="mem=112M@example.com" or append="mem=128M@example.com" Thanks, Michael
Home | Main Index | Thread Index
- Prev by Date: Re: Office documents
- Next by Date: Re: Office documents
- Prev by thread: Re: Automating multiple font encoding additions in fonts.dir
- Next by thread: RE: memory holes and kernel params
- Index(es):
Home Page Mailing List Linux and Japan TLUG Members Links