2011/1/28 Arjan van de Ven <ar...@linux.intel.com>: > On 1/28/2011 4:04 AM, Carsten Munk wrote: >> >> Hi, >> >> We just noticed we (N900 images) seem to be the only ones using btrfs >> on Handset images[1] [2]. When was this change made and is it an >> error? If not, why? >> >> Do we have a new default filesystem for the default configuration? > > MeeGo's default filesystem is BTRFS (and has been since before MeeGo 1.0) > > Unfortunately some hardware adaptation's have a buggy > bootloader-architecture currently and are unable to use BTRFS. > (and somehow making a small /boot that is ext3 with / being btrfs is > hard....) > > This is detrimental to performance and storage use on those platforms, and I > would expect that the owners of those platforms > have a vested interest to fix these issues to make their platforms work > better with MeeGo and at least match their competition in features and > performance... > But sometimes my expectations don't match reality.
Agreed - we're using btrfs as there's benefits to using it (COW really helps when copying sample media on startup) and because we were told to :) Shouldn't we have at least one set of the IA images to be using btrfs? That is, in order to weed out issues related to btrfs in MeeGo in image creation and be sure we've QA'ed this for both architectures? Currently, -none- of the .ks'es on IA are using btrfs. Perhaps netbook does upon install, but that won't help in image creation QA. BR Carsten Munk _______________________________________________ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev
