From: Riko Ho <antonius.riko@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] systemd question?
Date: Thu, 25 May 2017 10:03:00 +0800 [thread overview]
Message-ID: <6ed89ee4-7373-2e12-0919-4e6e7a227673@gmail.com> (raw)
Hello Everyone,
I tried to start with systemd initialization and got this message below:
=====
You are in emergency mode. After logging in, typ/bin/sh:
/home/bianchi77/buildrd
You are in emergency mode. After logging in, type "journalctl -xb" to view
system logs, "systemctl reboot" to reboot, "systemctl default" or ^D to
try again to boot into default mode.
/bin/sh: /home/bianchi77/buildroot/output/host/usr/sbin/sulogin: not found
You are in emergency mode. After logging in, type "journalctl -xb" to view
system logs, "systemctl reboot" to reboot, "systemctl default" or ^D to
try again to boot into default mode.
/bin/sh: /home/bianchi77/buildroot/output/host/usr/sbin/sulogin: not found
You are in emergency mode. After logging in, type "journalctl -xb" to view
system logs, "systemctl reboot" to reboot, "systemctl default" or ^D to
try again to boot into default mode.
/bin/sh: /home/bianchi77/buildroot/output/host/usr/sbin/sulogin: not found
You are in emergency mode. After logging in, type "journalctl -xb" to view
system logs, "systemctl reboot" to reboot, "systemctl default" or ^D to
try again to boot into default mode.
/bin/sh: /home/bianchi77/buildroot/output/host/usr/sbin/sulogin: not found
You are in emergency mode. After logging in, type "journalctl -xb" to view
system logs, "systemctl reboot" to reboot, "systemctl default" or ^D to
try again to boot into default mode.
/bin/sh: /home/bianchi77/buildroot/output/host/usr/sbin/sulogin: not found
You are in emergency mode. After logging in, type "journalctl -xb" to view
system logs, "systemctl reboot" to reboot, "systemct/bin/sh:
/home/bianchi77/bud
====
What do you reckon I missed here ? thanks
--
*
/*******/
Sent by Ubuntu LTS 16.04,
??,
Regards,
Riko Ho
/*******/
*
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20170525/7b4422d0/attachment.html>
reply other threads:[~2017-05-25 2:03 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=6ed89ee4-7373-2e12-0919-4e6e7a227673@gmail.com \
--to=antonius.riko@gmail.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox