All of lore.kernel.org
 help / color / mirror / Atom feed
From: Markus Svilans <msvilans@aeonyx.ca>
To: "yocto@yoctoproject.org" <yocto@yoctoproject.org>
Subject: Deploying Yocto built images on x86
Date: Mon, 04 Nov 2013 13:58:21 -0500	[thread overview]
Message-ID: <5277EE4D.2080303@aeonyx.ca> (raw)

[-- Attachment #1: Type: text/plain, Size: 1243 bytes --]

Dear list,

What do people do for deploying Yocto built images to actual x86 hardware?

I am researching how to build an appliance type Linux box on x86 
hardware, but I am unclear on what are the generally accepted methods 
for doing that. The box would need to have a read-only rootfs, mounted 
in RAM, with one or more partitions for storing persistent files.

I am looking for some method, where I could bitbake a recipe, that will:

  * build a FAT image for syslinux and initramfs files
  * build one or more small ext3/4 partitions for persistent storage
    (config files, log files, etc.)
  * generate a single binary image, that can be easily installed to a
    hard drive (via dd or other tool), and will automatically handle the
    various partitions, boot record, etc. on the target hard drive


The following presentation from 2006 mentions the mkimg and imgloader 
tools, that appear to do just that:
http://elinux.org/images/1/1b/Jordan_crouse_celf_2006.pdf

But there seems to be no mention of the mkimg / imgloader tools anywhere 
online. What happened to them? Are they proprietary AMD tools?


Any insights or links to good literature would be much appreciated.

Thanks very much
Markus



[-- Attachment #2: Type: text/html, Size: 1841 bytes --]

             reply	other threads:[~2013-11-04 18:59 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-04 18:58 Markus Svilans [this message]
2013-11-07 18:45 ` Deploying Yocto built images on x86 Darren Hart
2013-11-07 19:00   ` Markus Svilans

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=5277EE4D.2080303@aeonyx.ca \
    --to=msvilans@aeonyx.ca \
    --cc=yocto@yoctoproject.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.