All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Søren Holm" <sgh@sgh.dk>
To: yocto@yoctoproject.org
Subject: Re: Yocto with Initial RamFS
Date: Thu, 29 May 2014 17:38:23 +0200	[thread overview]
Message-ID: <2317978.pEesILAVCv@koontz> (raw)
In-Reply-To: <53874D1F.8090504@bsmucker.eu.org>

Torsdag den 29. maj 2014 08:07:11 skrev Brian Smucker:
> Hi,
> 
> Was wondering why this has not been answered.  Maybe it is too dumb of a
> question? If so, let me know or point me to some documentation.
> 

I'm declaring an initramfs-image like this. As you can see the recipe is 
derived from core-image-minimal-initramfs. The package initramfs-vm provides 
the script /init executed on boot.

The "assembling" of the actual bootable image with initramfs and rootfs (in my 
case a squashfs) is done in another script.

<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<
# initramfs for vm-image. Derived from core-image-minimal-initramfs
DESCRIPTION = "Small image capable of booting a a squashfs+aufs filesystem"

IMAGE_INSTALL = "initramfs-vm-boot busybox udev base-passwd"

# Do not pollute the initrd image with rootfs features
IMAGE_FEATURES = ""
IMAGE_LINGUAS = ""
#DISTRO_FEATURES = ""

inherit core-image

IMAGE_FSTYPES = "cpio"

IMAGE_PREPROCESS_COMMAND = "cb16_remote_bloat;"

cb16_remote_bloat() {
        rm -r ${IMAGE_ROOTFS}/boot
}
<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<

-- 
Søren Holm


  reply	other threads:[~2014-05-29 15:38 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-23 18:37 Yocto with Initial RamFS Brian Smucker
2014-05-29 15:07 ` Brian Smucker
2014-05-29 15:38   ` Søren Holm [this message]
2014-05-29 16:49     ` Brian Smucker
2014-05-29 19:38       ` Søren Holm
2014-05-29 19:44         ` Brian Smucker
2014-05-29 20:50       ` Khem Raj

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=2317978.pEesILAVCv@koontz \
    --to=sgh@sgh.dk \
    --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.