On Fri, May 14, 2010 at 07:12:50AM -0700, Arjan van de Ven wrote: > On 5/14/2010 1:32, Neil McGovern wrote: > >1) On disk format - This was due to be stabilised by 2009, and it's > >still not. A standardised on disk format must be a pre-requisite to > >using it as a default file system. > > it is stabilized.. I don't understand why you claim it's not. > The upstream developers say it is (but of course they reserve the right to > extend > it with new features, just like ext3 and ext4 have been doing for years), > and have shown since 2.6.30 or so that they can keep it stable. >
Simply because upstream say that it isn't stable until 1.0 > >2) File system support - various utilities still don't support btrfs, > >especially bootloaders (RedBoot, grub etc) > > MeeGo uses syslinux as bootloader, and we've added support to that (for 1.1). > My understanding > is that grub2 also works with btrfs, but we're not using that. > And for devices that won't be using syslinux? Given the targets of MeeGo, there will be devices that require more specialist bootloaders. However, this is probably work aroundable by use of an ext2/3 /boot partition. > >3) btrfs still does not handle all out-of-space conditions gracefully > > we haven't seen any oops like things since 2.6.33-stable anymore.... > earlier we saw one or two, and worked together with the upstream developers > to resolve those quickly. > Again, this comes from upstream's website. Perhaps an indication of the target for using btrfs as default may help. Neil -- Neil McGovern Software Development Team Leader, Intel:Core - Amino Communications _______________________________________________ MeeGo-dev mailing list [email protected] http://lists.meego.com/listinfo/meego-dev
