| Summary: | The many variables affecting the rootfs size of the image need documenting | ||
|---|---|---|---|
| Product: | [Documentation] Quick Start | Reporter: | Joshua Lock - Disabled <josh> |
| Component: | quick-start | Assignee: | Scott Rifenbark <srifenbark> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | Medium | CC: | jessica.zhang, poky.doc.watcher, poky.watcher, sgw |
| Version: | unspecified | ||
| Target Milestone: | 1.2 | ||
| Hardware: | x86 | ||
| OS: | Multiple | ||
| URL: | ec6b9d77d10a95f0a2d460dca3cf8eab5dfbf0c0 | ||
| Whiteboard: | 05-jan-20012: Resolved/Fixed | ||
| OS type for building Yocto: | --- | Type of Regression: | --- |
| Verified: | Documentation change: | --- | |
|
Description
Joshua Lock - Disabled
2011-05-26 13:48:45 UTC
There is a thread on oe-core discussing this that will likely contain much of the required detail: http://lists.linuxtogo.org/pipermail/openembedded-core/2011-May/003030.html I have added three new glossary entries to the glossary appendix: IMAGE_ROOTFS_SIZE, IMAGE_OVERHEAD_FACTOR, and IMAGE_ROOTFS_EXTRA_SPACE. The descriptions are robust enough to stand on their own and allow a user to understand how the image size is computed as well as how to request extra free disk space or increase the percentage of overhead. While these entries I feel satisfy this bug, I will later be adding in user information into the YP Development Manual that addresses image size in general. I am not tying that to this bug though. For the entries see commit ID ec6b9d77d10a95f0a2d460dca3cf8eab5dfbf0c0 at http://git.yoctoproject.org/cgit.cgi/yocto-docs/commit/?id=ec6b9d77d10a95f0a2d460dca3cf8eab5dfbf0c0 |