[meta-ti] [Angstrom-devel] Can't build cloud9 image

[Richard Purdie]

On Sun, 2012-03-04 at 06:17 -0700, Gary Thomas wrote:
> On 2012-03-04 06:09, Koen Kooi wrote:
> > Op 4 mrt. 2012, om 14:02 heeft Gary Thomas het volgende geschreven:
> >> On 2012-03-04 05:46, Koen Kooi wrote:
> >>> Op 3 mrt. 2012, om 13:51 heeft Gary Thomas het volgende geschreven:
> this so I can build the full cloud9-image?
> >>>
> >>> At the risk of responding to a practical joke: /etc/fstab entries need to be created with the user flag for the loop devices, the error message even includes the exact entry you need to add.
> >>
> >> I see that, but what if I'm "Joe user" who can't (or doesn't want to)
> >> edit /etc/fstab?
> >
> > Then you can't build this image.
> >
> >>   Everything else builds with no special "root" style
> >> privileges, why does this one image need it?
> >
> > Simply put: because the tools suck. A this point in time there is no tool (or tools plural) that allows creating 2 partitions (vfat and extX) and concatenating them into a valid image with an MBR. The biggest lack is something like 'genfatfs', mcopy is a step in the right direction but is too limited to work in this scenario.
> > And genext2fs will likely OOM on a lot of buildmachines.
> 
> But this is just to be able to generate a packed image that can be
> copied directly to media?  Maybe that should be a different image
> type, like the .u-boot images?  Then it would be obvious what's
> being done and why.  In my case, I'm more than happy running a script
> to copy the appropriate files to my SD card, etc. and I don't care
> (nor especially want) a packed image.

Just for reference, the directdisk stuff that was in OE-Core did
something like this (create an MBR with a couple of partitions following
it). It was removed as having some minor bugs and being unneeded but the
code might prove an interesting starting point to addressing this
problem. To come back, it would need to be a proper IMAGE_FSTYPES entry.

Cheers,

Richard