Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Ross Burton <ross.burton@intel.com>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH 0/2] Move systemd binaries to /sbin/systemd
Date: Thu, 11 Apr 2013 17:28:24 +0100	[thread overview]
Message-ID: <cover.1365697555.git.ross.burton@intel.com> (raw)

Hi,

Following the example set by udev, move the binaries to /sbin/systemd and
hardcode less paths in general.  Tested on atom-pc with a .hddimg so the live
boot/initrd paths were tested.

Ross

The following changes since commit 2ef72c3174c8c111678ac7e3cf3d866eaf2c8d77:

  wayland: add necessary dependencies to fix build error (2013-04-11 16:41:13 +0100)

are available in the git repository at:

  git://git.yoctoproject.org/poky-contrib ross/systemd

for you to fetch changes up to 0154334c32234d70dc064fb7dac6b499ca91cf3a:

  initrdscripts: look for new systemd-udevd location (2013-04-11 17:18:19 +0100)

----------------------------------------------------------------
Ross Burton (2):
      systemd: move the binaries to /sbin/systemd
      initrdscripts: look for new systemd-udevd location

 meta/recipes-core/initrdscripts/files/init-live.sh |    2 +-
 .../initrdscripts/initramfs-framework/udev         |    2 +-
 meta/recipes-core/systemd/systemd/init             |   14 +++---
 meta/recipes-core/systemd/systemd_199.bb           |   46 +++++++-------------
 4 files changed, 25 insertions(+), 39 deletions(-)

-- 
1.7.10.4




             reply	other threads:[~2013-04-11 16:48 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-11 16:28 Ross Burton [this message]
2013-04-11 16:28 ` [PATCH 1/2] systemd: move the binaries to /sbin/systemd Ross Burton
2013-04-11 16:28 ` [PATCH 2/2] initrdscripts: look for new systemd-udevd location Ross Burton
2013-04-15 11:00 ` [PATCH 0/2] Move systemd binaries to /sbin/systemd Enrico Scholz
2013-04-15 11:21   ` Koen Kooi
2013-04-15 15:15     ` Richard Purdie
2013-04-15 15:58       ` Enrico Scholz

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.1365697555.git.ross.burton@intel.com \
    --to=ross.burton@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