Size

Mer is aimed at mobile devices and whilst it is not a minimal/embedded system it can still have a very small footprint.

= Image size and disk usage =

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.

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

Kernel
In general don't compile and install modules that you won't need. Also check for unwanted code for filesystems etc.

= Memory usage =