From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: Jaap de Jong <jaap.dejong@nedap.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: can't login??
Date: Mon, 20 Aug 2012 13:19:15 +0100 [thread overview]
Message-ID: <2859322.LbdxQNuYuz@helios> (raw)
In-Reply-To: <5032290C.1090403@nedap.com>
On Monday 20 August 2012 14:09:48 Jaap de Jong wrote:
> What I'm trying to do is get an image that looks as much the same as the
> one I made under oe-classic.
> Perhaps my approach is not the way to go?
> I was using base-image.bb under oe-classic as the basis and added some
> packages to get to our needed set of applications.
There's nothing wrong with that - you can construct the image in whatever
manner you wish. You may wish to take advantage of the new functionality
provided by core-image.bbclass, but that is entirely optional.
> On 08/20/2012 12:34 PM, Paul Eggleton wrote:
> > Is "debug-tweaks" in IMAGE_FEATURES?
>
> (To answer your question. No, it is not. More of that in my previous mail)
The way things work now, zap_root_password is automatically run when post-
processing the image, unless debug-tweaks is in IMAGE_FEATURES (typically, one
would add this via EXTRA_IMAGE_FEATURES in local.conf). This is a replacement
for DISTRO_TYPE = "debug" / "release" in OE-Classic. The assumption is that if
you're actually producing a production image, you really don't want people to
be able to log into it as root with no password.
Cheers,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
next prev parent reply other threads:[~2012-08-20 12:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-20 10:06 can't login?? Jaap de Jong
2012-08-20 10:33 ` Andrei Gherzan
2012-08-20 10:34 ` Paul Eggleton
[not found] ` <5032290C.1090403@nedap.com>
2012-08-20 12:19 ` Paul Eggleton [this message]
2012-08-20 15:42 ` Elvis Dowson
2012-08-20 15:45 ` Paul Eggleton
2012-08-20 23:54 ` Slater, Joseph
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=2859322.LbdxQNuYuz@helios \
--to=paul.eggleton@linux.intel.com \
--cc=jaap.dejong@nedap.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 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.