Roland Silver wrote:
>
> Nathan,
> I read your reply to Benjamin Edelman, where you asked the question
>
> >2) Check the contents of /proc/meminfo to make sure you have all the
> >memory and swap you think you do (you do boot with the linux "mem="
> >option, right?).
>
> I'm new to the Linux environment, running Blackdown jdk1.1.7v3 on an i386.
> I'm not sure whether or not I'm booting with the linux "mem=" option.
> 1. What's the reason for doing so?
> 2. How do I set up the boot operation to do so?
Until the 2.2 kernel, Linux needs help discovering more than 64M of
RAM... I don't know why. Assuming you boot using LILO, you'll have a
lilo.conf that contains lines looking something like this:
image=/boot/vmlinuz-2.2.5-15
label=linux
root=/dev/hda3
read-only
This describes a particular kernel disk image and some other things
needed to boot. You can add a parameter that specifies the memory size
in the indented lines:
mem=128m
(or however much you have). But it's a good idea before you do that to
create an alternative entry in LILO to *try it* first. For example, add
some lines that copy the existing lines, with a different label and with
the new info:
image=/boot/vmlinuz-2.2.5-15
label=newlinux
root=/dev/hda3
mem=128m
read-only
run /sbin/lilo to process your new configuration. Reboot... when you get
the LILO prompt, answer "newlinux" instead of letting it use the default
(which is presumably "linux").
Another way to try the same experiment is not to mess with lilo.conf,
but answer "linux mem=128m" when you get the LILO prompt at boot time.
Anyway... if everything works - the system comes up and you seem to have
your memory, you can add the "mem=" to your default LILO entries, run
/sbin/lilo, and you're in business.
It would probably be a good idea to read
http://www.linuxdoc.org/HOWTO/mini/LILO.html, rather than just relying
on my sketchy instructions here.
Hope this helps...
Nathan
----------------------------------------------------------------------
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
