Reply
Thread Tools
Flandry's Avatar
Posts: 1,559 | Thanked: 1,786 times | Joined on Oct 2009 @ Boston
#1
The optification continues apace, but i wonder if it might not be a good idea anyway to make app manager more intelligent. What about building in a safeguard so that it will examine the package in question and grey it out/disable install if the package would fill root (or maybe any partion for more general usefullness).

It seems that deb tools should be able to ascertain how much space will be taken on each partition. If automating it is not practical, new fields, e.g.:

X-space-in-root

X-space-in-opt

might do the job, although more disruptively.

After reading about the state that filling root puts the N900 into, preventing normal users from filling the partitions seems like a good idea...

http://maemo.org/community/brainstor...ill_partition/

Last edited by qgil; 2009-10-31 at 21:19. Reason: Brainstorm tag
 

The Following 4 Users Say Thank You to Flandry For This Useful Post:
Posts: 2,102 | Thanked: 1,309 times | Joined on Sep 2006
#2
It's a bit harder than that as the root partition is a compressed filesystem, so the size reported by the debian packaging tools may not correspond to the size it actually uses.

It's a good idea though, and certainly worth some thought. At the very least it could issue a warning when it looks like it may run out of space.
 

The Following 3 Users Say Thank You to lardman For This Useful Post:
JosefA's Avatar
Posts: 71 | Thanked: 54 times | Joined on Oct 2009
#3
I'm not sure I want my package manager to tell me what to do.

From my perspective, I'd rather Extras have a strict "optified or GTFO" policy, and users told they're on their own if they use extras-devel or extras-testing.
 

The Following User Says Thank You to JosefA For This Useful Post:
Posts: 3,319 | Thanked: 5,610 times | Joined on Aug 2008 @ Finland
#4
Originally Posted by lardman View Post
It's a bit harder than that as the root partition is a compressed filesystem, so the size reported by the debian packaging tools may not correspond to the size it actually uses.
Another consideration is that the package itself has no idea how many filesystems will it's contents be spread over. Some of it might go to root, some to opt, some to Mydocs, some even to the external MMC, etc.
 
Flandry's Avatar
Posts: 1,559 | Thanked: 1,786 times | Joined on Oct 2009 @ Boston
#5
Thanks, i did not realize the root partition was compressed.

After working with the debian packaging system (and surely it knows which directories the files go to), it seems like it should be straightforward to calculate which filesystem each file in a package goes on.

Even using a repository where everything is optified, it's still possible to fill a partition. For example, /opt itself isn't any too large if a user goes crazy installing big packages.

Even in the present app manager there is a blue pill and red pill mode. Why not make the blue pill mode more bulletproof?
__________________

Unofficial PR1.3/Meego 1.1 FAQ

***
Classic example of arbitrary Nokia decision making. Couldn't just fallback to the no brainer of tagging with lat/lon if network isn't accessible, could you Nokia?
MAME: an arcade in your pocket
Accelemymote: make your accelerometer more joy-ful
 
Posts: 3,319 | Thanked: 5,610 times | Joined on Aug 2008 @ Finland
#6
Originally Posted by Flandry View Post
After working with the debian packaging system (and surely it knows which directories the files go to), it seems like it should be straightforward to calculate which filesystem each file in a package goes on.
What I'm saying is that the packager has no idea how these partitions look like on the user side, only the presumption that nothing has been changed compared to the factory layout. In time, people might reformat, repartition, change filesystems, rebase/clone their roots, etc, all of which can influence the actual location (and amount) of actual package content.
 
Flandry's Avatar
Posts: 1,559 | Thanked: 1,786 times | Joined on Oct 2009 @ Boston
#7
Originally Posted by attila77 View Post
What I'm saying is that the packager has no idea how these partitions look like on the user side, only the presumption that nothing has been changed compared to the factory layout. In time, people might reformat, repartition, change filesystems, rebase/clone their roots, etc, all of which can influence the actual location (and amount) of actual package content.
I hadn't considered the case where the user has repartitioned. This is clearly an advanced user situation and not the usual case. Would it not be appropriate still to ship with App Manager set up to assume the default filesystem, and let those who chose to repartition also disable the protection? We're really trying to protect the average user here, not the hackers.
__________________

Unofficial PR1.3/Meego 1.1 FAQ

***
Classic example of arbitrary Nokia decision making. Couldn't just fallback to the no brainer of tagging with lat/lon if network isn't accessible, could you Nokia?
MAME: an arcade in your pocket
Accelemymote: make your accelerometer more joy-ful
 
Reply

Tags
app manager, full partition, optify, smart installer

Thread Tools

 
Forum Jump


All times are GMT. The time now is 15:13.