[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#66009: 32 Mb, but "Sorry, not enough memory" (caused by new kernels sysinfo syscall)



>>>>> " " == Erik Andersen <andersen@codepoet.org> writes:

     > I can implement a correct solution for the way the kernel
     > currently changed right now (not requiring such a hack).  I
     > asked on the boot-floppies mailing list and it was agreed to
     > _not_ do anything about this, and that 2.4.x kernels were not a
     > potato boot-floppy target.

     > The "correct" way to work around the change is the copy the
     > 2.2.x and the 2.4.x sysinfo structs into the busybox source
     > tree, giving them unique names.  Then on boot, call uname to
     > decide which struct to use, and then, if the kernel is 2.4.x
     > also take ito account sysinfo.mem_unit.  This is ugly, but
     > workable.

I thing you could initialise sysinfo.mem_unit with 1, then call
sysinfo(). Since 2.2 has just padding there, sysinfo.mem_unit should
remain 1 and on 2.4 it would be set to reflect the page size.

That way sysinfo.mem_unit could be used in both cases.

     > For the moment, it was agreed to _not_ fix this in the boot
     > floppies for potato, so I am not touching it unless asked to by
     > Adam Di Carlo (potato boot floppies team lead).

May the Source be with you.
			Goswin



Reply to: