From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 12811] bootstrap stuck and no login prompt
Date: Fri, 24 Apr 2020 19:02:06 +0000 [thread overview]
Message-ID: <bug-12811-163-WU2pWS2Gf7@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-12811-163@https.bugs.busybox.net/>
https://bugs.busybox.net/show_bug.cgi?id=12811
Peter Seiderer <ps.report@gmx.net> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |INVALID
--- Comment #3 from Peter Seiderer <ps.report@gmx.net> ---
> Thanks. I naively assumed such changed would be done automatically.
No..., buildroot is not about automatically customizing every possible
selection of features..., just a starting point for your own project (see below
and [1] for customize support)...
> It worked for the cmdline.txt.
Good news...
> For the openssh however, I assume that is a change that can only be done with post-scripts?
Yes, one of the many possibilities to customize your project, see [1] for
alternatives...
Closing the bug (as it is not a bug, but a feature ;-)), feel free to turn to
the mailing list for further questions/support...
[1] https://buildroot.org/downloads/manual/manual.html#rootfs-custom
--
You are receiving this mail because:
You are on the CC list for the bug.
prev parent reply other threads:[~2020-04-24 19:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-23 10:29 [Buildroot] [Bug 12811] New: bootstrap stuck and no login prompt bugzilla at busybox.net
2020-04-23 19:51 ` [Buildroot] [Bug 12811] " bugzilla at busybox.net
2020-04-24 6:55 ` bugzilla at busybox.net
2020-04-24 19:02 ` bugzilla at busybox.net [this message]
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-12811-163-WU2pWS2Gf7@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.