If you decide where to plant the wiki page, I'll be happy to document all the steps necessary to go from rootfs to a running raspi. I can toss on the extra steps I took for this "proof of concept" I built as well for now, though those steps will be irrelevant when there is a CentOS rootfs. It does use the kernel compiled specifically for the board from the raspi foundation, as well as the necessary binary firmware.
One thing to consider is that when it comes to the arm boards, in my opinion, where people will be turning to CentOS is for their home servers. They want the security, stability and support cycle that centos provides for the Pi that's their file server, or owncloud server, or dovecot/postfix, that is running non stop and problem free in the closet. Its unlikely that the media lovers will be turning to CentOS except for minidlna or media tomb. Starting developers may also be attracted to using an enterprise grade system instead of the bleeding edge distros, so some basic gpio pin usage may be done. So at the very least, a collection of how to's in regard to common home server applications may be beneficial, as a lot of these devices aren't targeted to those of us using Linux the last 20 years, but for those who are starting out learning. I'll be happy to write any up that we feel would be good to have. Maybe we even want to think of including some things like samba, owncloud, dlna server, etc in an image for that reason as well (things that centos already provides for the x86-64). Just some thoughts.
I'll paste the link to the image below. I did build it on a 16gb SD card as I had nothing smaller laying around, but I can always find a $4 4gb card to help generate future images depending on how its decided to generate them in the future- if we provide a full image for different boards, or just instruct on how to use the generic image. Maybe we'll want a minimal image and a GUI image even.
I shrunk it up a bit more to what I felt was a good balance of what a minimal install should have, and I exported the list from yum to the /root/ directory, so you can mount the image and grab the list without having to extract it from the yum or rpm databases. The / partition has 672mb of data on it.
Also, I didn't notice a dhcp service built, so to use the image you will need to set a static one the old fashioned way (ifconfig and 'route add default x') .
The pass1 and buildroot repos added are disabled by default.
Root password is blank, and obviously would need to be set before allowing the internet (and all its lovely bots) to touch it.
-David

https://drive.google.com/open?id=0B6w0L-XWgP4sVGpkS1l5dnE2bkk&authuser=0






On May 30, 2015 7:22:27 AM CDT, Fabian Arrotin <arrfab@centos.org> wrote:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 30/05/15 14:20, Fabian Arrotin wrote:
 On 30/05/15 13:26, cc35359@gmail.com wrote:
 Its just a mostly bare install, less than a GB of space used to 
 run. There are still a few packages I can likely clean off, but 
 there is nothing there beyond what you have compiled already at 
 least. I can put the image file on Google drive (I could host
 the image on the centos pi itself to allow a download, but I only
 have 1mbit upload speed), that way you can at least mount it and
 see what is there, or i can just dump the installed package list
 for you. I will look into slimming it up even further, but is
 there a specific
goal in mind for the minimal rootfs: is it a
 size goal, or simply "all thats needed to boot, take a keyboard
 as input, and access yum repos on a network"? Getting it working
 was step 1, at least its proof that your hard work is paying off
 :) Do we want anyone else to be able to download the image as
 well in order to look for major faults yet, or wait until the
 next phase when you have a rootfs built?
 
 
 Well, you can upload it where you can, and then I can grab it and
 put it somewhere else (like buildlogs.centos.org ? ) so that people
 can have a look and test it. What I'd like to see though is also
 documenting that on wiki.centos.org. For example, have you used the
 kernel-4.0.0 rpm package built and available in the c7-buildroot 
 (http://armv7.dev.centos.org/repodir/c7-buildroot/kernel/), or
 have you used the one from another distro ? etc .. So if someone
 has expertise with specific boards, we can all write/centralize
 that on the wiki, so that we can then eventually automate the
 various .img files creation, for all kind of specific boards, etc
 ..
 
 Do you have already have a wiki account ? We can use a generic
 "entry" page for arm32 (like the existing 
 http://wiki.centos.org/SpecialInterestGroup/AltArch/Arm32 page) ,
 but moving content like plague builder access somewhere else (a
 sub-page) and do something like /Raspberry1 , or /Odroid , etc ..)
 
 What do you (all) think ?
 

Just to add that we'll probably have to write (or integrate ?) some
scripts to init the
node, like for the resize2fs, etc .. so basically
what other distro have also for that kind of boards ...


- -- 

Fabian Arrotin
The CentOS Project | http://www.centos.org
gpg key: 56BEC54E | twitter: @arrfab
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (GNU/Linux)

iEYEARECAAYFAlVpq4MACgkQnVkHo1a+xU7YIACfT10b7tKb2blRsT51PgXgCs89
87kAn2sugXx2BE6PobfM1ROxOMCfNQ8k
=1c02
-----END PGP SIGNATURE-----

Arm-dev mailing list
Arm-dev@centos.org
http://lists.centos.org/mailman/listinfo/arm-dev