rescue-dg_v0.9.1-beta

This marks what is probably a good, workable/working Kirkwood device rescue rootfs for NAND. The selection of target packages probably won't change much since there isn't much more room. There are, though, some possible deletions that might save some kilobytes of room:

• unneeded drivers in the kernel/modules (e.g. the rtc modules: these can be reduced quite a bit, but I'll need feedback from the community in order to ascertain what can be eliminated, and what is essential)
• certain target packages that are useless (maybe pipe_progress and others); again community feedback can help
• best compression (lzo, gzip, ... ?)
• trimming out busybox just a bit, in case there is some overlap between target packages and busybox functions

For anyone who is wondering, although mtdparts declares mtd2 to be 32MB in size, 27MB is close the limit for how large the rootfs.mtd2.img can be. (With 24.9MB for the rootfs.mtd2.img, df -h reports 3.4 MB remaining, and some of that is needed for overhead.)

rescue-dg_v0.9-beta

This marks what is probably a good, workable/working Kirkwood device rescue rootfs for NAND. The selection of target packages probably won't change much since there isn't much more room. There are, though, some possible deletions that might save some kilobytes of room:

• unneeded drivers in the kernel/modules (e.g. the rtc modules: these can be reduced quite a bit, but I'll need feedback from the community in order to ascertain what can be eliminated, and what is essential)
• certain target packages that are useless (maybe pipe_progress and others); again community feedback can help
• best compression (lzo, gzip, ... ?)
• trimming out busybox just a bit, in case there is some overlap between target packages and busybox functions

For anyone who is wondering, although mtdparts declares mtd2 to be 32MB in size, 25MB is close the limit for how large the rootfs.mtd2.img can be. (With 24.9MB for the rootfs.mtd2.img, df -h reports 3.0 MB remaining, and some of that is needed for overhead.)