Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Patrick Ohly <patrick.ohly@intel.com>
To: Christopher Larson <clarson@kergoth.com>
Cc: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 1/1] rootfsdebugfiles.bbclass: quick-and-dirty installation of additional files
Date: Tue, 14 Apr 2015 09:42:56 +0200	[thread overview]
Message-ID: <1428997376.23267.134.camel@intel.com> (raw)
In-Reply-To: <CABcZAN=54ffzEd5u7926uqXde8ecamQuQv2h34S+DRdF4KPNdw@mail.gmail.com>

On Mon, 2015-04-13 at 09:07 -0700, Christopher Larson wrote:
> 
> On Mon, Apr 13, 2015 at 8:44 AM, Patrick Ohly <patrick.ohly@intel.com>
> wrote:
>         The main motivation for this class was the observation that
>         a) a core-image can hang under qemu when the kernel does not
>            have enough entropy to generate the ssh host key
>         b) ssh complains about changing ssh host key files when
>            rebooting the same machine with different images
>         
>         For debugging it is okay to reuse an ssh host key generated on
>         the device
>         before. There may be also similar use cases, so the class is
>         generic enough to
>         also copy more than one file or directory, with
>         dropbear_rsa_host_key given as
>         example.
>         
>         The documentation and naming of the class makes it clear that
>         it
>         should not be used for production images.
>         
>         Signed-off-by: Patrick Ohly <patrick.ohly@intel.com>
> 
> Freescale's merge-files recipe may be worth looking at as an
> alternative to this.

Thanks for mentioning it. Yes, that's also a way to do it. It seems a
bit more complicated to set up (all files must be in a common "merge"
directory) and does not seem to support sub-directories (-maxdepth 1),
so it is a bit less flexible than the ROOTFS_DEBUG_FILES that I was
proposing. On the other hand, the files get packaged properly (well, if
one is careful about adapting the default MIT license as needed).

For my use case, I still prefer the quick-and-dirty approach.

-- 
Best Regards, Patrick Ohly

The content of this message is my personal opinion only and although
I am an employee of Intel, the statements I make here in no way
represent Intel's position on the issue, nor am I authorized to speak
on behalf of Intel on this matter.





  reply	other threads:[~2015-04-14  7:43 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-13 15:44 [PATCH 0/1] ssh host key Patrick Ohly
2015-04-13 15:44 ` [PATCH 1/1] rootfsdebugfiles.bbclass: quick-and-dirty installation of additional files Patrick Ohly
2015-04-13 16:07   ` Christopher Larson
2015-04-14  7:42     ` Patrick Ohly [this message]
2015-04-14 14:41       ` Christopher Larson
2015-04-13 20:16 ` [PATCH 0/1] ssh host key Sven Ebenfeld

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=1428997376.23267.134.camel@intel.com \
    --to=patrick.ohly@intel.com \
    --cc=clarson@kergoth.com \
    --cc=openembedded-core@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox