All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marcin Juszkiewicz <marcin@juszkiewicz.com.pl>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [PATCH] image.bbclass: remove tmp/rootfs after image creation unless you set a variable
Date: Wed, 17 Jun 2009 19:31:27 +0200	[thread overview]
Message-ID: <200906171931.28562.marcin@juszkiewicz.com.pl> (raw)
In-Reply-To: <1245258640-1623-1-git-send-email-clarson@mvista.com>

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

Dnia środa, 17 czerwca 2009 o 19:10:40 Chris Larson napisał(a):
> Set IMAGE_KEEPROOTFS to something other than the empty string to keep
> tmp/rootfs around after image creation, otherwise it will be removed,
> as it's not a fully functional filesystem, and causes much confusion
> among users as a result.
>
> Signed-off-by: Chris Larson <clarson@mvista.com>

Acked-by: Marcin Juszkiewicz <marcin@juszkiewicz.com.pl>

I am also tired of explaining to users why tmp/rootfs should not be used 
as nfsroot.

Regards, 
-- 
JID:      hrw@jabber.org
Website:  http://marcin.juszkiewicz.com.pl/
LinkedIn: http://www.linkedin.com/in/marcinjuszkiewicz

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 204 bytes --]

  parent reply	other threads:[~2009-06-17 17:42 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-17 17:10 [PATCH] image.bbclass: remove tmp/rootfs after image creation unless you set a variable Chris Larson
2009-06-17 17:29 ` Tom Rini
2009-06-17 17:31 ` Marcin Juszkiewicz [this message]
2009-06-17 17:40 ` Rolf Leggewie
2009-06-17 17:47   ` Rolf Leggewie
2009-06-17 17:54     ` Chris Larson
2009-06-17 17:52   ` Roman I Khimov
2009-06-17 18:01 ` Richard Purdie
2009-06-17 18:08   ` Chris Larson
2009-06-17 19:08   ` Tom Rini
2009-06-18 12:43     ` Richard Purdie
2009-06-17 19:07 ` Leon Woestenberg
2009-06-17 19:11   ` Christopher Larson
2009-06-17 19:13   ` Phil Blundell
2009-06-17 19:27   ` Chris Larson

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=200906171931.28562.marcin@juszkiewicz.com.pl \
    --to=marcin@juszkiewicz.com.pl \
    --cc=openembedded-devel@lists.openembedded.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.