Quote:
Originally Posted by UnknownUser
I made a new image from stable today, until now, I had been using an image I made from the testing repos. both created with deboostrap with arch=armel.
Both of them freeze while doing things on the kindle, but are fine when copied back to a host PC and ran with user-mode qemu.
with the squeeze image, I didn't need to call apt-update, since it was already done on the host-pc before copying over. I even managed to do an apt-get install from the kindle without it crashing! unfortunately, it wasn't that the problem went away, it just seems like it just managed to finish before freezing. I tryed to install another larger package, and froze while unpacking...
( good news though! I can play tetris as long as I like! )
|
There once was a major problem with "apt-get update" in that it used a tremendous amount of memory.
That should have been dealt with by now, but perhaps it still requires more resources than are available.
One way to minimize the resource requirements -
have an absolute minimum number of repositories listed in /etc/apt/sources.list
If that doesn't do it - now that you are running Deb-6 (which should be a fairly close match in age with the Kindle kernel) - - -
It will not be changing that often - you can copy off you chroot environment file and do the "apt-get update" and "apt-get dist-upgrade" under qemu - say once every 2 or 3 months.
The two hung processes you noticed both take large amounts of ram - the log rotate only needs it briefly but it probably made its request at "just the wrong time" during the apt-get update fetch.
You should be able to manage when (and if) the log rotate daemon runs - it is usually a cron job. Do a crontab -l and edit it with crontab -e as required to make it behave.
PS:
This is not impossible to do - I run Debian on my NSLU-2 with only 32Mbyte of ram, and have successfully rebuilt the Debian base install packages from source (twice).
Added note: It does take awhile - like days, its only a 233Mhz machine.
