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

[Russell Senior]

>>> 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.

FWIW, I added the /etc/fstab entry provide (for /dev/loop2) but I
still get this at the end (from build/tmp-angstrom_2010_x-eglibc/work/beaglebone-angstrom-linux-gnueabi/cloud9-image-1.0-r0/temp/log.do_rootfs

[...]
./media/mmc1/
./media/union/
./media/realroot/
loop: can't delete device /dev/loop1: Permission denied
loop: can't delete device /dev/loop2: Permission denied
loop: can't delete device /dev/loop3: Permission denied
/dev/loop1: Permission denied

>>  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.

Are you familiar with makebootfat?

  http://linux.die.net/man/1/makebootfat


-- 
Russell Senior, President
russell at personaltelco.net