diff options
author | Kevin Tian <kevin.tian@intel.com> | 2010-07-27 14:45:10 +0800 |
---|---|---|
committer | Richard Purdie <rpurdie@linux.intel.com> | 2010-07-27 22:51:34 -0700 |
commit | 637ad7ef8c3e0bbfcff1df6b0039446d2b251cf8 (patch) | |
tree | d683afb73cb02c8af5f2169cc3ad1dd1e810e3d7 /meta/packages/clutter/clutter-mozembed.inc | |
parent | 218e441dd5b6f45e76464d75e2d06c439347f754 (diff) | |
download | openembedded-core-637ad7ef8c3e0bbfcff1df6b0039446d2b251cf8.tar.gz openembedded-core-637ad7ef8c3e0bbfcff1df6b0039446d2b251cf8.tar.bz2 openembedded-core-637ad7ef8c3e0bbfcff1df6b0039446d2b251cf8.tar.xz openembedded-core-637ad7ef8c3e0bbfcff1df6b0039446d2b251cf8.zip |
bitbake.conf: change inode calculation for genext2fs [BUGFIX#138]
genext2fs 1.4.1 creates minimal inode number based on specified rootfs
directory. This is desired in some embedded devices as storage/memory
are precious. However it's not suitable in development phase where target
rootfs may be changed heavily on the fly (remote debug, test, ...).
Sometimes this may even cause "No space on device" error due to limited
free inodes exhaulted at the 1st boot.
Here a new option is added to allow falling back to original 1.3 behavior,
i.e caculating inode number based on specified bytes-per-inode parameter.
Signed-off-by: Kevin Tian <kevin.tian@intel.com>
Diffstat (limited to 'meta/packages/clutter/clutter-mozembed.inc')
0 files changed, 0 insertions, 0 deletions