[OE-core] [PATCH 1/1] rootfsdebugfiles.bbclass: quick-and-dirty installation of additional files
Christopher Larson
clarson at kergoth.com
Tue Apr 14 14:41:10 UTC 2015
On Tue, Apr 14, 2015 at 12:42 AM, Patrick Ohly <patrick.ohly at intel.com>
wrote:
> 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 at 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 at 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.
Indeed, both approaches have value, depending on one's needs, I think.
--
Christopher Larson
clarson at kergoth dot com
Founder - BitBake, OpenEmbedded, OpenZaurus
Maintainer - Tslib
Senior Software Engineer, Mentor Graphics
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openembedded.org/pipermail/openembedded-core/attachments/20150414/b44b3116/attachment-0002.html>
More information about the Openembedded-core
mailing list