Run in ram test results
Paul Gray <[email protected]> Mon, 5 Jan 2004 12:45:29 -0600 (CST)
| Newsgroups | gmane.linux.bbc.devel |
|---|---|
| Message-ID | <[email protected]> |
I pulled the first ISO from movealong with the runinram features (lnx-bbc-i386-2004-01-04T06:00:37-0600.iso). The image (67MB raw total, 65MB singularity) will load just fine on my systems with > 512MB of RAM, but fails on systems with 64MB and 128M of ram (< 2x the base image). The failure is due to out-of-space errors when copying the singularity or lnx.img. When the system is up-and-running, the core image has a ~94MB footprint in ram, so it looks like there's at least a hard limit of 2-times-singularity-size just to load the system in ram. Anyone with a system with 128M < SystemRam < 512M care to chime in on success/failure on loading to ram? To load the system to ram, use "<n> rir" at the boot prompt, where "<n>" specifies the framebuffer mode. (You can also use "runinram" or "toram" instead of "rir".) I'll shoot for 2x the size of /proc/kcore as the pre-test condition for sufficient amounts of available core memory before attempting to load to ram. I'd like to hear if it fails to load on any systems that meet this requirement though. Paul Gray -o) 323 Wright Hall /\\ University of Northern Iowa _\_V Message void if penguin violated ... Don't mess with the penguin No one ever says "Hey, I can't read that ASCII e-mail ya sent me."