From: Darren Hart <dvhart@linux.intel.com>
To: Leon Woestenberg <sidebranch.openembedded@gmail.com>
Cc: Yocto Project <yocto@yoctoproject.org>
Subject: Re: [PATCH V3 0/3] New distribution definition for poky-tiny
Date: Wed, 28 Dec 2011 21:55:58 -0800 [thread overview]
Message-ID: <4EFC00EE.8080105@linux.intel.com> (raw)
In-Reply-To: <CAMvUbCx59KWAN0qeS5Ga9mAb9cMPVvxeKxJS6f6OYC2+mbu0Xw@mail.gmail.com>
On 12/28/2011 05:07 PM, Leon Woestenberg wrote:
> Hello Darren,
>
>
> On Thu, Dec 29, 2011 at 12:45 AM, Darren Hart <dvhart@linux.intel.com
> <mailto:dvhart@linux.intel.com>> wrote:
>
> V3:
> o Rebase on master
> o Dependent on oe-core series "Fixes for tiny distros and
> linux-yocto-tiny"
>
> RFC V2:
> o Use VIRTUAL-RUNTIME_keymaps as suggested by Martin Jansa
> o Drop poky-common abstraction as suggested by Richard Purdie in
> favor of POKY_DEFAULT_EXTRA_R* variables.
>
> Poky-tiny defines a new distro policy for building tiny Linux
> images. Rather
>
>
> Such images are useful for small Linux firmwares, both often also
> require a read-only fs img.
>
> Does this current image require write access at first boot?
I have done a readonly first-boot successfully, and as Chris points out,
it is one of the policy goals. That said, I have not yet looked to see
if there are some post-inst scripts which should be run. There isn't any
kind of init going on, and we'll need to decide how to best handle that
for poky-tiny. Right now I boot using an initramfs with root=/dev/ram0,
it reads an empty /init and falls back to /bin/sh - a more robust and
functional init is probably needed even for poky-tiny.
--
Darren Hart
Intel Open Source Technology Center
Yocto Project - Linux Kernel
prev parent reply other threads:[~2011-12-29 5:56 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-28 23:45 [PATCH V3 0/3] New distribution definition for poky-tiny Darren Hart
2011-12-28 23:45 ` [PATCH 1/3] distro: Add POKY_DEFAULT_EXTRA_R* variables Darren Hart
2011-12-28 23:45 ` [PATCH 2/3] distro: Add poky-tiny distro definition Darren Hart
2012-01-04 0:19 ` Khem Raj
2012-01-04 16:16 ` Darren Hart
2012-01-04 16:31 ` Chris Larson
2012-01-04 13:56 ` Leon Woestenberg
2012-01-04 14:12 ` Richard Purdie
2011-12-28 23:45 ` [PATCH 3/3] image_types: Ensure /init exists for cpio rootfs archives Darren Hart
2011-12-28 23:52 ` Darren Hart
2011-12-28 23:54 ` [PATCH] " Darren Hart
2011-12-29 17:39 ` Chris Larson
2011-12-30 8:25 ` Andrea Adami
2011-12-30 23:18 ` Darren Hart
2012-01-03 14:57 ` Andrea Adami
2012-01-04 0:07 ` Saul Wold
2012-01-04 23:49 ` Andrea Adami
2012-01-05 0:05 ` Andrea Adami
2012-01-05 12:30 ` Richard Purdie
2012-01-05 23:36 ` Darren Hart
2012-01-06 1:00 ` Andrea Adami
2012-01-06 1:10 ` Andrea Adami
2012-01-06 10:57 ` Richard Purdie
2012-01-06 22:58 ` Andrea Adami
2012-01-10 23:07 ` Andrea Adami
2012-01-10 23:28 ` Andrea Adami
2011-12-29 0:16 ` [PATCH V3 0/3] New distribution definition for poky-tiny Chris Larson
2011-12-29 1:07 ` Leon Woestenberg
2011-12-29 1:51 ` Chris Larson
2011-12-29 2:12 ` Leon Woestenberg
2012-01-06 11:52 ` Richard Purdie
2011-12-29 5:55 ` Darren Hart [this message]
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=4EFC00EE.8080105@linux.intel.com \
--to=dvhart@linux.intel.com \
--cc=sidebranch.openembedded@gmail.com \
--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.