Re: Maemo Unification Proposal
Well, it's sick to have / on a 256M disk. But it's still not a good idea to move vital parts of the system to a slower partition. And they reside in /usr (see libstdc++6)
I'd suggest moving / to /dev/mmcblk0. Altogether - we get rid of the problem of small rootfs. And we take the opposite of optification - we do nandification - move the vital parts of the system (libc6, libstdc++, glib, hildon) to NAND. Beautiful, isn't it? We still get the blazing fast performance for vital components and we don't have any problems with full rootfs. The only issue may be the boot process, but I don't know how big it will be. Generally, the boot components are usually vital. |
Re: Maemo Unification Proposal
Quote:
I found this post; but do not know whether it is recommended or not... be careful! jm |
Re: Maemo Unification Proposal
Quote:
|
Re: Maemo Unification Proposal
Quote:
We should leave the contacts entry. Then developers - add support for it (so that clicking the address may open modRana, mapper, etc.). If no app is found, a pop-up should be shown that no compatible application has been found. |
Re: Maemo Unification Proposal
Quote:
|
All times are GMT. The time now is 02:34. |
vBulletin® Version 3.8.8