All of lore.kernel.org
 help / color / mirror / Atom feed
From: Darren Hart <dvhart@linux.intel.com>
To: Martin Jansa <martin.jansa@gmail.com>
Cc: Yocto Project <yocto@yoctoproject.org>
Subject: Re: New recipes not installing in core-image-minimal
Date: Fri, 27 Jan 2012 09:13:55 -0800	[thread overview]
Message-ID: <4F22DB53.8060400@linux.intel.com> (raw)
In-Reply-To: <20120127103001.GC3779@jama.jama.net>



On 01/27/2012 02:30 AM, Martin Jansa wrote:
> On Fri, Jan 27, 2012 at 03:52:58PM +0530, Joshua Immanuel wrote:
>> Hello Martin,
>>
>> On Fri, 2012-01-27 at 09:08 +0100, Martin Jansa wrote:
>>>> Perhaps, but it didn't fix this particular problem. Neither
>>>> /usr/bin/ranpwd nor /etc/init.d/genmac appear in the rootfs.
>>>> However, each still appears in their respective workdir/image:
>>>
>>> Are they in workdir/packages-split/genmac/etc/init.d/genmac
>>> workdir/packages-split/ranpwd/etc/init.d/ranpwd 
>>
>> I too have a similar issue when I try to include a manually constructed
>> fstab file into the rootfs image. The file is available in the following
>> locations
>>      1. core2-poky-linux/${PN}-${PV}-${PR}/etc/fstab
>>      2. core2-poky-linux/${PN}-${PV}-${PR}/packages-split/${PN}/etc/fstab
>>
>> but not in the final rootfs image. May be I am missing something
>> trivial.
> 
> Maybe it depends on used package-manager bud I guess that at least
> opkg will refuse to overwrite /etc/fstab provided by base-files by
> /etc/fstab from your fancy PN and even if it allows it in do_rootfs, 
> then it's not good idea for image with online package management,
> because your custom fstab will be overwritten as soon as base-files are
> changed.
> 
> Why not .bbappend base-files and customize fstab there?

This is how I am modifying /etc/network/interfaces and this is working
fine for me. Joshua, I'd second Martin's suggestion.

--
Darren

> 
>> Eager to know the solution on this thread.
>>
>> Regards
>> Joshua
>> -- 
>> Joshua Immanuel
>> HiPro IT Solutions Private Limited
>> http://hipro.co.in
> 
> 
> 
>> _______________________________________________
>> yocto mailing list
>> yocto@yoctoproject.org
>> https://lists.yoctoproject.org/listinfo/yocto
> 
> 
> 
> 
> _______________________________________________
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto

-- 
Darren Hart
Intel Open Source Technology Center
Yocto Project - Linux Kernel


  reply	other threads:[~2012-01-27 17:14 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-27  1:29 New recipes not installing in core-image-minimal Darren Hart
2012-01-27  1:42 ` Saul Wold
2012-01-27  1:57   ` Darren Hart
2012-01-27  8:08     ` Martin Jansa
2012-01-27 10:22       ` Joshua Immanuel
2012-01-27 10:30         ` Martin Jansa
2012-01-27 17:13           ` Darren Hart [this message]
2012-01-30 11:02             ` Joshua Immanuel
2012-01-27  8:02 ` Martin Jansa
2012-01-27  8:06   ` Darren Hart
2012-01-31 18:21     ` Darren Hart

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=4F22DB53.8060400@linux.intel.com \
    --to=dvhart@linux.intel.com \
    --cc=martin.jansa@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.