From: Trevor Woerner <twoerner@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] docs: Configuration path update
Date: Mon, 21 Nov 2011 17:06:46 -0500 [thread overview]
Message-ID: <1321913206-10645-1-git-send-email-twoerner@gmail.com> (raw)
From: Trevor Woerner <twoerner@gmail.com>
Update the procedure for modifying /etc/inittab's getty line with
the correct port and baud values to reflect their current names and
locations in the Buildroot configuration.
Signed-off-by: Trevor Woerner <twoerner@gmail.com>
---
docs/buildroot.html | 6 +++---
1 files changed, 3 insertions(+), 3 deletions(-)
diff --git a/docs/buildroot.html b/docs/buildroot.html
index 2314d10..d5be127 100644
--- a/docs/buildroot.html
+++ b/docs/buildroot.html
@@ -1787,9 +1787,9 @@ Starting dropbear sshd: generating rsa key... generating dsa key... OK</pre>
<p>then it means that your system is running, but didn't start a
shell on the serial console. In order to have the system start a
shell on your serial console, you have to go in the Buildroot
- configuration, <code>Target options</code>, enable <code>Generic
- serial port config</code>, and select the serial port and speed
- you would like to use for the shell. This will automatically tune
+ configuration, <code>System configuration</code>, and modify
+ <code>Port to run a getty (login prompt) on</code> and
+ <code>Baudrate to use</code> as appropriate. This will automatically tune
the <code>/etc/inittab</code> file of the generated system so that
a shell starts on the correct serial port.</p>
--
1.7.6.233.gd79bc
next reply other threads:[~2011-11-21 22:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-21 22:06 Trevor Woerner [this message]
2011-11-21 22:20 ` [Buildroot] [PATCH] docs: Configuration path update Peter Korsgaard
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=1321913206-10645-1-git-send-email-twoerner@gmail.com \
--to=twoerner@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