<p>On 26 Aug 2011 10:51, "Jon Masters" <<a href="mailto:jcm@redhat.com">jcm@redhat.com</a>> wrote:<br>
><br>
> Folks,<br>
><br>
> We are hosting another one of our regular Fedora 15 hardfp Virtual<br>
> Fedora Activity Day today Friday August 26th 2011, at 14:00UTC (10:00<br>
> Eastern Daylight Time). The purpose of this session is to co-ordinate<br>
> the continued bootstrap of F15 hardfp (hardware floating point).<br>
><br>
> Previously, we performed initial bootstrap (stage1), then proceeded to<br>
> get RPM working natively within an ARMv7 hardfp environment (stage2),<br>
> then got yum and mock working (stage3). We are now in what we are<br>
> calling "stage4" in which we are rebuilding the world of packages using<br>
> mock, but are not yet using Koji to do so - that will be stage5, the<br>
> final stage before we are able to say that we have completed bringup.<br>
><br>
> We need helping building packages within a mock environment for F15. To<br>
> do this, we have made your life as a (potential) volunteer somewhat more<br>
> straightforward through the creation of a standard image that you can<br>
> install onto an ARMv7 compatible board (tested on Panda, we believe this<br>
> should also work on Beagle, and can be made to run on Tegra-2 boards</p>
<p>The builder I've enabled runs on the new OLPC within a chroot and that seems to work very well. I'm not sure if the kernel is a hfp one, but I don't think that was a requirement.</p>
<p>> like Trimslice with a replacement kernel - ask us for assistance). Once<br>
> you have done this, the resulting system will contain a simple script<br>
> that you can use to randomly retrieve a package that needs building and<br>
> have it build without you having to even issue a single mock command :)<br>
><br>
> To participate, visit the following link:<br>
><br>
> <a href="http://scotland.proximity.on.ca/fedora-arm/f15hardfp/bootstrap/rootfs_stage4_20110825/">http://scotland.proximity.on.ca/fedora-arm/f15hardfp/bootstrap/rootfs_stage4_20110825/</a><br>
><br>
> Follow the instructions contained within the readme file to extract the<br>
> "uboot", "boot", and "root" archives onto an SD Card for your device.<br>
> These instructions will destroy whatever is already installed. If you<br>
> are familiar with using chroots, you can also retrieve the "root" image<br>
> and chroot into it if you would prefer (after bind mounting /proc, /dev,<br>
> etc.). We generally prefer not using chroots at this stage however.<br>
><br>
> Once you have followed the setup instructions:<br>
><br>
> 0). Configure /etc/sysconfig/network<br>
> and /etc/sysconfig/network-scripts/ifcfg-eth* according to your setup.<br>
> The ones in that image statically assign "<a href="http://tenaya.bos.jonmasters.org">tenaya.bos.jonmasters.org</a>".<br>
><br>
> 1). Login to your board as root (password is "fedora"). Change the<br>
> password if you would like to do so.<br>
><br>
> 2). Become the "builder" user. You can either "su - builder" or you can<br>
> "passwd builder", and then login remotely/on the console.<br>
><br>
> 3). Optional, but recommended, use "screen -S builder" or similar to<br>
> start a screen session that you can leave running.<br>
><br>
> 4). Run the simple building script: ./arm-rebuild.sh<br>
><br>
> 5). Monitor the arm mailing list. It is likely that a newer version of<br>
> the builder script will be posted later today or before Monday. When<br>
> that happens, we may change the SSH keys used in the build image, which<br>
> would have the effect of forcing everyone to update. The purpose of that<br>
> being to prevent any existing builders running the older script version.<br>
> Instructions will be posted for updating a couple files will be posted.<br>
><br>
> Please join us on IRC: #fedora-arm on <a href="http://irc.freenode.org">irc.freenode.org</a>.<br>
><br>
> Further documentation will be provided on the Fedora ARM wiki today,<br>
> however this email should provide sufficient setup information now.<br>
><br>
> Jon.<br>
><br>
><br>
> --<br>
> devel mailing list<br>
> <a href="mailto:devel@lists.fedoraproject.org">devel@lists.fedoraproject.org</a><br>
> <a href="https://admin.fedoraproject.org/mailman/listinfo/devel">https://admin.fedoraproject.org/mailman/listinfo/devel</a><br>
</p>