An app would be great, methinks. Why nobody wrote one yet is beyond me.

Just list packages and check would move to /opt/reclaim and ln -s, while unchecking moved them back.

Who knows - there may be an app or script out there we haven't located. In any case, I'll write a script eventually that is 'safe' and one that is more aggressive (I don't have time to go through the app process). I /suppose/ I could add 'clean' 'unclean' commands to it, but I may have to push that to debatestorming to figure out if people really want that and what the commands should say, stew in there for a while and then push off to some future update that won't have a date :-)

Another suggestion that I found 'accidentally' whilst laying in bed last night messing with it. Don't like or use one or both of the themes? This is easy enough to remove and re-install later, but each one frees up ~3%:

(assuming everyone who knows apt and it requires root as well as making sure the theme being removed isn't the one being used):

//the blue wave theme named Nokia Nseries: frees ~8MB:
apt-get remove hildon-theme-alpha

//the orange them named Digital Nature: frees ~7MB:
apt-get remove hildon-theme-beta

To be safe, you can easily see what theme you are using by checking default symlink:

0x90:~# ls -l /usr/share/themes/default
lrwxrwxrwx 1 root root 23 Oct 30 03:31 /usr/share/themes/default -> /usr/share/themes/alpha

(I don't know if this would affect a future SSU or anything else - shouldn't, but like I said, apparently updates check for various files to be in certain 'places' - they shouldn't bother with this, but who knows.)

Now, why wouldn't those be optified? Haven't tried symlinking to /opt to see how it works, but will probably get around to that today.

Nope - duh. This has nothing to do with what you are currently running. Seems a 'safe' fallback.

If you remove alpha theme, change symlink to beta.

As always, at your own risk.

Uhmmm, there have been several reports that themes break if the alpha/bet a are removed, because not all themes change all UI elements.

If you lose the close buttons on windows after a reboot, you did a baaaad thing.

Oh, and, I can't swear, but in PR1.1 I think a large portion of Python was optified, so the hint (from 1.01) didn't get you much space.

Oh, and, once you have 30-40 MB free, stop. Each part that is on the root means that it's faster. Optification is a tradeoff between speed and space. Don't overdo it. :)

Interesting, I manually rm -r alpha and changed default symlink some time ago. IIRC, I ran like that for a week (not unusal for me to flash weekly so far). I later forgot about so never removed it again then saw it was a package (thanks to Storage Manager). I removed it last night and have restarted several times today - so far I haven't seen anything. Close buttons are still there and are orange rather than blue :-) Good info though so now I'll pay closer attention. I haven't seen those reports, but maybe they did an rm -r like I did last time (though I didn't lose a close button then). The apt-get remove handles the default symlink - I just added that in case.

RE: optified, yeah, like I said, I didn't get anything out of that other than a messy df.

Dude, I'm on a mission to have 100MB free. I want to be the root master. Right now I am at 75MB free. It hasn't bricked yet so that's good news. It sped up on boot too, instead of 5-minutes, it's down to 6.5-minutes - the higher the better, right? :-)

Didn't I see a lot of people having probs installing SSU w/only 30MB free?

But, yeah, good advice for us - no huge benefit to a bunch of free root space other than not having to worry about it and moving too much out of nand will affect performance for some things.

If I run into an issue w/theme I'll post back (or any other issues I find in my ventures).

BTW: Don't want to take this thread off topic, but a little side road: I happened onto this bug and thought, "cool, 'pwnedyou' will look great on people's stereo", but found a few things even though someone says it's fixed. If I change with fmtx_client or manually, it changes initially - can rerun fmtx_client or cat the files several times, looks good, then reverts back to default "Nokia ". I can enable/disable, it'll still appear fine, but for some random reason, it reverts (w/out a restart). Then, noticed the power_level issue so checked on that - yup, drops tx pwr when plugged into usb then back to full pwr when unplugged. However, when I disable the radio, it is still showing power (has 113 - not sure if radio is on though or what) - time/enable/disable/etc - nothing changes it back to 0 until a restart... if you feel like looking at that. Doubt it drains battery much, but w/all the battery complaints after 1.1, each bit helps:

https://bugs.maemo.org/show_bug.cgi?id=7271

Don't mess with the missionary man I always say. Or Eurythmics. Can't remember.

Point is, it's going to be longer to boot and ... 6.5 minutes? Rili? I'd throw away my PC if it ever booted in half that.

Distracting. Point is, at some point during this quest you may lose some data that is required by something, like OTA upgrade or somesuch. And you will not know what you did. Keep testing.

I wouldn't overdo it, but frankly your kind if people is invaluable for the rest of us. If people were like me they'd never know what happens if one removes Chinese fonts because I don't do anything I'm not fairly sure of. We're called chicken.

Never flashed my device and, frankly, even rebooting makes my teeth itch. I didn't reboot any computers this year. I'm a sysadmin and a coder.

PR 1.1 required 42M free to install, people recommended 45. Might be different depending on localization.

You keep at it, we anxiously await more tales from the rootfs crypt. Just remember we don't pay for new N900s.

Edit: as for the bug, make sure you have their version and if it still happens, post and vote. They should reopen and fix if it's broken. I don't have a radio in my car to test.