2010/5/13 Graham Cobb <[email protected]>: > On Thursday 13 May 2010 01:38:59 David Austin wrote: >> Also, if btrfs is the preferred filesystem for MeeGo then future devices >> will have better configurations to support it. It's pretty clear that the >> N900 is going to be the minimum (or worst) hardware that MeeGo will >> run on. We have to expect that the N900 will suffer a little because >> of that. > > If the specualtion in this thread so far is accurate then the N900 is likely > to suffer a *lot* in order to run MeeGo. In particular, the proposal seems > to be to put the whole filesystem on the plug-in memory card. This has many > advantages (including simplicity, and the ability to multiboot back to Maemo > 5, and no /opt problem whether ext3 or btrfs is used) but it will have a > couple of major disadvantages: (i) speed, and (ii) losing the ability to use > removable memory cards. > > I agree with that decision but we need to realise that that is fine as a test > system for developers, but is not a supportable end user configuration.
<community hat> Let's just step back a second, because this thread is very quickly turning into a trainwreck without good reason. First off, the trend is to move away from NAND, there has been work mentioned regarding that Maemo Harmattan is going towards eMMC as well. This makes sense, because there's no /opt problem. We have then made the move to ext3/MMC, at first, using the microSD, as it's easier for initial setup and try-out by users. There is no technical reason why this same deployment can be done to the 32gb MMC. The organisational one is that users traditionally don't like to lose 32 gb worth of data ;) Now, on a handset - I would love being able to make block devices with fat32 on top for USB export, snapshot my system before a SSU, etc. I love these things on my ZFS setup. And the N900 should be able to support this just as well as any other ARM handset. A x86 handset will have exact same issues as a N900 would, if they used a eMMC. Now, back to the supportable end user config. We are underneath the MeeGo project umbrella - our work is delivering a stable hardware adaptation that links with a handset vertical together with a MeeGo Core. Not a second class citizen in the MeeGo project, but a full fledged reference implementation to the best of our abilities. A proper hardware adaptation is first step to make a supportable end user configuration. So from that point of view, it is a component for 'developers'. But this hardware adaptation is not a 'hack'. It is made by professionals and hopefully soon non-Nokia-or-subcontractors-affiliated system developers, professionals in their own right, as well. We have to support a proper handset configuration on top of it - if it was a hack, it wouldn't be suitable for that. But it isn't a Nokia product. Ask Nokia for that, not MeeGo :) </community hat> Regards, Carsten Munk _______________________________________________ MeeGo-dev mailing list [email protected] http://lists.meego.com/listinfo/meego-dev
