From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: Amit Tomer <amittomer25@gmail.com>
Cc: yocto@yoctoproject.org
Subject: Re: How /etc/passwd packed into my final image
Date: Wed, 16 Oct 2013 11:33:15 +0100 [thread overview]
Message-ID: <2360903.vJkMptqlar@helios> (raw)
In-Reply-To: <1453346.6uHgHqcMcF@fedora-fisso>
On Wednesday 16 October 2013 10:20:24 Davide Soldan wrote:
> In data mercoledì 16 ottobre 2013 00:01:13, Amit Tomer ha scritto:
> > I wanted to modify the content of /etc/passwd but don't know how
> > /etc/passwd files is packed into final image
> >
> > After the build process ,passwd file goes to
> >
> > "tmp/work/k2-poky-linux-gnueabi/image-k2/1.0-r0/rootfs/etc/passwd"
> >
> > this loaction
> >
> > Now I see image-k2.bb file but could not find any rule that will pack
> > passwd file to
> > final image.
> >
> > Can anybody how it is packed and way to modify it.
> >
> > Thanks
> > Amit
> > _______________________________________________
> > yocto mailing list
> > yocto@yoctoproject.org
> > https://lists.yoctoproject.org/listinfo/yocto
>
> Hi,
> I think that the recipe that creates passwd file is under
> poky/meta/recipes-core/base-passwd (I'm on dora branch). Maybe with a
> bbappend of that recipe you can change the passwd file with yours... Cheers
Rather than modifying it in base-passwd, with master or 1.5 I'd recommend
using extrausers.bbclass / EXTRA_USERS_PARAMS (see meta-
yocto/conf/local.conf.sample.extended for an example of how to use it).
Cheers,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
next prev parent reply other threads:[~2013-10-16 10:33 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-16 7:01 How /etc/passwd packed into my final image Amit Tomer
2013-10-16 8:20 ` Davide Soldan
2013-10-16 10:33 ` Paul Eggleton [this message]
2013-10-16 10:57 ` Amit Tomer
2013-10-16 11:13 ` Amit Tomer
2013-10-16 11:31 ` Amit Tomer
2013-10-16 11:47 ` Paul Eggleton
2013-10-16 11:50 ` Amit Tomer
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=2360903.vJkMptqlar@helios \
--to=paul.eggleton@linux.intel.com \
--cc=amittomer25@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.