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

[Russell Senior]

>>>>> "Denys" == Denys Dmytriyenko <denis at denix.org> writes:

Denys> On Thu, Mar 15, 2012 at 12:17:37AM -0700, Russell Senior wrote:
>> > 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

Denys> Well, mine gets further (although it's not my main focus now):

Yeah, that was just because i wasn't in the 'disk' group in
/etc/groups.  Thank you to the interwebs for digging that one up for
me.

The compile is finishing for me currently, but I still can't get it to
boot, built on debian/unstable.  The MLO I build doesn't seem to get
recognized by my A4 beaglebone.  The ROM code spits C's at me as if
the microSD card wasn't there.  The microSD card is okay though (an 8
gig Kingston class 10 thing), because I can /sbin/dd the online
angstrom cloud9 demo image[1] on it and that boots.

[1] http://www.angstrom-distribution.org/demo/beaglebone/Angstrom-Cloud9-IDE-eglibc-ipk-v2012.02-core-beaglebone-2012.02.14.img.xz


-- 
Russell Senior, President
russell at personaltelco.net