The Mer Wiki now uses your Mer user account and password (create account on https://bugs.merproject.org/)
Size
From Mer Wiki
(Difference between revisions)
(basic notes) |
|||
| Line 1: | Line 1: | ||
| − | Mer is aimed at mobile devices and whilst it is not a minimal/embedded system it can still have a | + | Mer is aimed at mobile devices and whilst it is not a minimal/embedded system it can still have a small footprint. |
= Image size and disk usage = | = Image size and disk usage = | ||
Latest revision as of 12:34, 23 January 2012
Mer is aimed at mobile devices and whilst it is not a minimal/embedded system it can still have a small footprint.
Contents |
[edit] Image size and disk usage
[edit] Filesystems
- ubifs
- This is a favoured solution for small device filesystems
- jffs2
- cramfs
- This filesystem produces extremely small images but is read-only. Mer currently needs to write to the root filesystem (though this should change). Device updates are hard. Cramfs is very easily damaged by bad blocks.
[edit] Image generation
In general remove unneeded packages. Consider using the following directives in kickstart files:
- %packages --excludedocs
- This prevents documentation files from being distributed.
-cjkuni-fonts
[edit] Kernel
In general don't compile and install modules that you won't need. Also check for unwanted code for filesystems etc.
