From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 8331] New: kexec fails due to missing /usr/sbin/shutdown
Date: Fri, 11 Sep 2015 10:05:54 +0000 (UTC) [thread overview]
Message-ID: <bug-8331-163@https.bugs.busybox.net/> (raw)
https://bugs.busybox.net/show_bug.cgi?id=8331
Summary: kexec fails due to missing /usr/sbin/shutdown
Product: buildroot
Version: 2015.05
Platform: PC
OS/Version: Linux
Status: NEW
Severity: minor
Priority: P5
Component: Other
AssignedTo: unassigned at buildroot.uclibc.org
ReportedBy: ian_ormshaw at waters.com
CC: buildroot at uclibc.org
Estimated Hours: 0.0
Chaining a new kernel using kexec fails as /usr/sbin/shutdown is missing.
creating a link in the skeleton, or overlay file system from /usr/sbin/shutdown
to /sbin/shutdown fixes the problem.
--
Configure bugmail: https://bugs.busybox.net/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
next reply other threads:[~2015-09-11 10:05 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-11 10:05 bugzilla at busybox.net [this message]
2015-09-13 20:20 ` [Buildroot] [Bug 8331] kexec fails due to missing /usr/sbin/shutdown bugzilla at busybox.net
2015-09-15 7:40 ` bugzilla at busybox.net
2015-09-15 7:48 ` bugzilla at busybox.net
2015-09-15 8:20 ` bugzilla at busybox.net
2015-09-15 8:28 ` bugzilla at busybox.net
2015-09-15 9:22 ` bugzilla at busybox.net
2015-09-15 9:41 ` bugzilla at busybox.net
2015-09-15 9:42 ` bugzilla at busybox.net
2015-09-15 9:46 ` bugzilla at busybox.net
2015-09-15 11:25 ` bugzilla at busybox.net
2015-09-15 13:05 ` [Buildroot] [Bug 8331] kexec wants shutdown in /sbin, but systemd installs it in /usr/sbin bugzilla at busybox.net
2015-09-15 13:07 ` bugzilla at busybox.net
2015-10-14 9:44 ` bugzilla at busybox.net
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=bug-8331-163@https.bugs.busybox.net/ \
--to=bugzilla@busybox.net \
--cc=buildroot@busybox.net \
/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.