On Mon, 2004-10-04 at 21:42, nslu-changesets-admin@...
> Have you tested the ramdisk size changes on unslung-image?
Sorry, no I didn't. (hangs head in shame) Your enlargement was causing
problems for openslug. We were seeing errors where the system was
trying to write past the end of the ramdisk. The kernel command line
for openslug only allows a 10M ramdisk.
> You're modifying nslu2.conf, which affects all nslu2 streams of development.
I'l see what can be done to contain the change to openslug.
> I had a problem earlier with the size of the unslung ramdisk, which is
> why I bumped it up. My understanding is we can go from 0x01000000 to
> 0x01cfffff with the ramdisk before we collide with the kernel at
Moving past 10M needs a change to the kernel command line and/or
config. I did some experiments, but was largely unsuccessful getting
openslug to accept the larger ramdisk.
Again, sorry to confuse.
Roy M. Silvernail is roy@..., and you're not
"Progress, like reality, is not optional." - R. A. Hettinga