Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH 0/5] SERIAL_CONSOLES improvements
Date: Tue, 30 Apr 2013 17:52:56 +0100	[thread overview]
Message-ID: <cover.1367340369.git.paul.eggleton@linux.intel.com> (raw)

Having two variables to enable essentially the same behaviour isn't
really desirable, so fix up the handling of SERIAL_CONSOLES, set it
from SERIAL_CONSOLE by default if not set and change everwhere we read
SERIAL_CONSOLE to read from SERIAL_CONSOLES instead. This should allow
us to deprecate SERIAL_CONSOLE whilst retaining compatibility with
machine configurations that still use it. 

Note: I'm a bit concerned about the default setting of SERIAL_CONSOLE in
systemd-serialgetty; I'm not sure why this is needed given that this is
almost always going to be machine-specific. I've left it alone for the
time being however.


The following changes since commit e86538db13605953465aacc3f2fb7d719dad919e:

  neard: add systemd unit file (2013-04-29 15:31:39 +0100)

are available in the git repository at:

  git://git.openembedded.org/openembedded-core-contrib paule/serial-consoles
  http://cgit.openembedded.org/cgit.cgi/openembedded-core-contrib/log/?h=paule/serial-consoles

Paul Eggleton (5):
  sysvinit-inittab: ensure unique label for SERIAL_CONSOLES entries
  bitbake.conf: set SERIAL_CONSOLES from SERIAL_CONSOLE by default
  sysvinit-inittab: remove specific handling of SERIAL_CONSOLE
  shadow-securetty: change to handle SERIAL_CONSOLES
  systemd-serialgetty: change to handle SERIAL_CONSOLES

 meta/conf/bitbake.conf                             |  3 ++
 meta/recipes-core/systemd/systemd-serialgetty.bb   | 45 +++++++++++-----------
 .../sysvinit/sysvinit-inittab_2.88dsf.bb           | 11 ++----
 .../shadow/shadow-securetty_4.1.4.3.bb             | 20 ++++++----
 4 files changed, 42 insertions(+), 37 deletions(-)

-- 
1.8.1.2




             reply	other threads:[~2013-04-30 17:11 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-30 16:52 Paul Eggleton [this message]
2013-04-30 16:52 ` [PATCH 1/5] sysvinit-inittab: ensure unique label for SERIAL_CONSOLES entries Paul Eggleton
2013-04-30 16:52 ` [PATCH 2/5] bitbake.conf: set SERIAL_CONSOLES from SERIAL_CONSOLE by default Paul Eggleton
2013-04-30 21:42   ` Khem Raj
2013-05-01  6:51     ` Paul Eggleton
2013-05-01 17:07       ` Khem Raj
2013-04-30 16:52 ` [PATCH 3/5] sysvinit-inittab: remove specific handling of SERIAL_CONSOLE Paul Eggleton
2013-04-30 16:53 ` [PATCH 4/5] shadow-securetty: change to handle SERIAL_CONSOLES Paul Eggleton
2013-04-30 16:53 ` [PATCH 5/5] systemd-serialgetty: " Paul Eggleton
2013-05-01  7:14 ` [PATCH 0/5] SERIAL_CONSOLES improvements Koen Kooi

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=cover.1367340369.git.paul.eggleton@linux.intel.com \
    --to=paul.eggleton@linux.intel.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