Editing Opt Problem
Warning: You are not logged in.
Your IP address will be recorded in this page's edit history.
The edit can be undone.
Please check the comparison below to verify that this is what you want to do, and then save the changes below to finish undoing the edit.
Latest revision | Your text | ||
Line 1: | Line 1: | ||
= The /opt Problem = | = The /opt Problem = | ||
- | There is not enough space on | + | There is not enough space on root to fit all applications, therefore additional partition has to be used. But just how? |
- | There is a section in the Maemo 5 Developer Guide explaining the basics: | + | There is a section in the Maemo 5 Developer Guide explaining the basics: |
- | + | http://wiki.maemo.org/Documentation/Maemo_5_Developer_Guide/Packaging%2C_Deploying_and_Distributing/Installing_under_opt_and_MyDocs | |
= Current situation = | = Current situation = | ||
Line 11: | Line 11: | ||
* 32GB eMMC: /home ~2GB (ext3), /home/user/MyDocs ~29GB (vfat), swap 0.7GB | * 32GB eMMC: /home ~2GB (ext3), /home/user/MyDocs ~29GB (vfat), swap 0.7GB | ||
* symlink: /opt/ -> /home/opt/ | * symlink: /opt/ -> /home/opt/ | ||
- | * OneNAND is | + | * OneNAND is faster (hard numbers? read? write? small blobs? big blobs?) |
- | + | ||
- | + | ||
- | + | ||
* Decisions were taken in a "what shall we do about /opt?" BOF at the [[Maemo Summit 2009]]. Minutes: http://lists.maemo.org/pipermail/maemo-developers/2009-October/021289.html | * Decisions were taken in a "what shall we do about /opt?" BOF at the [[Maemo Summit 2009]]. Minutes: http://lists.maemo.org/pipermail/maemo-developers/2009-October/021289.html | ||
Line 21: | Line 18: | ||
* Firmware should be flashable. | * Firmware should be flashable. | ||
* Should not break applications. | * Should not break applications. | ||
- | * One should be able to install more | + | * One should be able to install more that 256mb worth of software. |
- | * Standards compliance, less need to make | + | * Standards compliance, less need to make uncompatible quirks. |
* A fix should be doable after shipping (before shipping, probably not?) | * A fix should be doable after shipping (before shipping, probably not?) | ||
- | = Current problems / developer and packaging issues = | + | == Current problems / developer and packaging issues == |
This should be a list of current problems developers are experiencing related to optification: | This should be a list of current problems developers are experiencing related to optification: | ||
Line 34: | Line 31: | ||
* [[/Non-Optified_packages|List of non-optified packages and applications]] - Please feel free to add every piece of software which is using too much space in rootfs | * [[/Non-Optified_packages|List of non-optified packages and applications]] - Please feel free to add every piece of software which is using too much space in rootfs | ||
- | |||
- | |||
- | |||
- | |||
= Possible solutions, even the bad ones = | = Possible solutions, even the bad ones = | ||
Line 54: | Line 47: | ||
==== Have a 2-5gb partition on the emmc for addon packages mounted to /usr/local or /opt ==== | ==== Have a 2-5gb partition on the emmc for addon packages mounted to /usr/local or /opt ==== | ||
* Most apps by default usually go there | * Most apps by default usually go there | ||
- | * for /opt store according to the FHS standard /opt/<package> and symlink to /opt | + | * for /opt store according to the FHS standard /opt/<package> and symlink to /opt/{bin,lib,share,...} |
* Having ld.so.conf and PATH set properly avoids all the symlink madness | * Having ld.so.conf and PATH set properly avoids all the symlink madness | ||
* Don't do symlinks for /usr/local|/opt - make it a real partition | * Don't do symlinks for /usr/local|/opt - make it a real partition | ||
Line 62: | Line 55: | ||
==== store addon packages completely in /home/opt hierarchy ==== | ==== store addon packages completely in /home/opt hierarchy ==== | ||
- | |||
* like previous solution but on the standard /home partition | * like previous solution but on the standard /home partition | ||
- | * very clean solution | + | * very clean solution if speed advantage of OneNAND over eMMC turns out to be a myth |
* /etc and /var could be copied there as well and mounted to root using bind. This way OneNAND would only be changed be reflashes and if /home is not mounted (e.g., by a keypress during boot) a fallback system could boot from unmodified OneNAND. | * /etc and /var could be copied there as well and mounted to root using bind. This way OneNAND would only be changed be reflashes and if /home is not mounted (e.g., by a keypress during boot) a fallback system could boot from unmodified OneNAND. | ||
- | |||
==== During packaging move all files >500kb to /opt and symlink to root ==== | ==== During packaging move all files >500kb to /opt and symlink to root ==== | ||
Line 102: | Line 93: | ||
* How much faster OneNAND is? Numbers? | * How much faster OneNAND is? Numbers? | ||
* Can flasher flash on eMMC? | * Can flasher flash on eMMC? | ||
- | |||
- | |||
==== Use mount -o bind (or -o rbind) ==== | ==== Use mount -o bind (or -o rbind) ==== | ||
Line 125: | Line 114: | ||
* Maybe somebody can see something good in this? | * Maybe somebody can see something good in this? | ||
* Difficult hack.. would need all the tools etc to be visible in the chroot. | * Difficult hack.. would need all the tools etc to be visible in the chroot. | ||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
[[Category:Development]] | [[Category:Development]] |
Learn more about Contributing to the wiki.