I wrote up a document for creating the necessary raspi image based off of a generic rootfs. Whenever you get the wiki positioned the way you want, let me know and I can wikify my instructions. In regards to the generic rootfs, I started to play with a couple ideas on a raspberry pi itself, pushing the packages from rpm/yum onto a separate partition (USB stick) to see if that does work well enough. I'm going to time travel back and see if I can see how fedora had started to build their's in case there was a more efficient method we handnt thought of. ---------------------------- 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.centos.org/pipermail/arm-dev/attachments/20150603/11b9bdfd/attachment-0006.html>