[OE-core] my plan for an OE-based "installer" image

Robert P. J. Day rpjday at crashcourse.ca
Fri Jun 17 11:42:31 UTC 2016


  (i asked about this on the YP list a while back, but since this is
really a basic OE question, i'll re-ask it here with more detail.)

  i want to build an "installer" image for a powerpc system i'm
working with, and i have what i think is a reasonable design, so i'll
describe it and just want to know what others think about it, and if
i'm overlooking anything critically important or fatal, or possibly
something much simpler that already exists.

  first, i already have a functioning build for the powerpc target
board for u-boot and the kernel and a rootfs and so on, so i already
have all the info i need for configuration and cross-compilation.

  next, i am allowed to assume i have a functioning u-boot on the
target board, which is capable of downloading a live image which will
(obviously) run strictly out of RAM and will be responsible for
formatting the attached hard drive, then fetching (tftp) the root
filesystem, untarring it onto the drive, etc.

  i'm assuming the best strategy would be to create a live image using
something like core-image-minimal-initramfs.bb -- seems pretty obvious
that i want a skeletal rootfs that does little more than format the
hard drive, then populate it, set some u-boot env vars, then reboot to
let the system come up. sound reasonable so far?

  finally, as for the program that does all that installation work,
i'm familiar with a number of OE layers that have .bbclass files that
define creating an SD card image for the target board. here's one for
the raspberry pi:

http://git.yoctoproject.org/cgit/cgit.cgi/meta-raspberrypi/tree/classes/sdcard_image-rpi.bbclass

obviously, those bbclass files are designed to be used to create image
files for the target board, but i can't do that in my case. however,
i can certainly take the equivalent utility and add it to the live
image so it does all the same work while running out of RAM to do the
same thing to the actual hard drive.

  does this sound like a reasonable plan? am i overlooking something
important? am i choosing the right OE image recipe as a basis? is
there already something that does this? thoughts?

rday

p.s. oh, and if i can do this, i'm going to try to simulate all this
with a qemuppc image. it seems like that's doable, i can just
configure a qemuppc image with some fake hard drive and everything
should work, no?

-- 

========================================================================
Robert P. J. Day                                 Ottawa, Ontario, CANADA
                        http://crashcourse.ca

Twitter:                                       http://twitter.com/rpjday
LinkedIn:                               http://ca.linkedin.com/in/rpjday
========================================================================




More information about the Openembedded-core mailing list