Opkg incompatible with suspend

[Glenn]

For many image eons the opkg seems to be incompatible with suspend:
http://wiki.openmoko.org/wiki/Manuals/SHR#opkg_upgrade_issues

Suggestion:

Somebody ought to make an application/script or modify opkg so it 
checks the following:

Is the battery/accumulator charged enough for an upgrade?
or else
Is the phone powered enough via the USB port? Is Settings->Power at 
500mA or is the Openmoko power supply supplying power?

Is the internet reachable?

Is dns working?

(A short but sufficient NAND-flash or ext2/3 consistency check ought 
to be done?)

(Is enough file system space available?)

(If it is possible to check the opkg database consistency, then it 
should be done once every boot, but only if this script is run?)

(Is the needed servers reachable via http, ftp or whatever?)

If the above is met the upgrade can begin or else the user should be 
informed what is needed, before an upgrade can begin.

-

If the user press the "suspend" button, what should then happen?

If the USB power is cut what should then happen?

-

More generally something ought to test (persistently) for resources 
before launching an application and afterwards:

If an application can not make changes to the file system, it can be 
started without restrictions or popup recommendations.

The FSO ought to "intercept" all applications that might make changes 
to the file system and inform of low power and request commit before 
lanching them, if insufficiently power is available.

The FSO ought to "intercept" all applications that might need 
internet access and request commit (or wait for transparent 
establishing of the internet access) before lanching them, if no 
internet access is available.

The FSO ought to "intercept" all applications that might need GPS 
access and request commit (or wait for transparent establishing of 
the GPS access) before lanching them, if no GPS access is available.

Glenn