From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 10036] Buildroot builds Raspbian Jessie headless image presenting incorrect prompt
Date: Tue, 11 Jul 2017 21:49:27 +0000 [thread overview]
Message-ID: <bug-10036-163-0x3Eu1liWX@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-10036-163@https.bugs.busybox.net/>
https://bugs.busybox.net/show_bug.cgi?id=10036
Arnout Vandecappelle <arnout@mind.be> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|--- |INVALID
Status|NEW |RESOLVED
--- Comment #2 from Arnout Vandecappelle <arnout@mind.be> ---
Please use the mailing list or IRC for questions. The bug tracker is for
reporting bugs.
The "buildroot login:" prompt appears because your system is configured with
"buildroot" as hostname - this is the default. If you want to change this, look
for the BR2_TARGET_GENERIC_HOSTNAME in "make menuconfig".
sudo is not found because you have not installed it. Look for BR2_PACKAGE_SUDO
in "make menuconfig".
If all this is not clear, you may want to consult
http://buildroot.org/manual.html
By the way, you can't build a raspbian image from Buildroot, there are quite a
few Required packages missing and the skeleton is different.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2017-07-11 21:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-11 20:45 [Buildroot] [Bug 10036] New: Buildroot builds Raspbian Jessie headless image presenting incorrect prompt bugzilla at busybox.net
2017-07-11 21:29 ` [Buildroot] [Bug 10036] " bugzilla at busybox.net
2017-07-11 21:49 ` bugzilla at busybox.net [this message]
2017-07-11 22:48 ` bugzilla at busybox.net
2017-07-12 7:51 ` 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-10036-163-0x3Eu1liWX@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox