summaryrefslogtreecommitdiff
path: root/docs
diff options
context:
space:
mode:
authorTrevor Woerner <twoerner@gmail.com>2011-11-21 17:06:46 -0500
committerPeter Korsgaard <jacmet@sunsite.dk>2011-11-21 23:17:52 +0100
commita51194985af9ffa7e9c956b58ef32132748c7d0b (patch)
tree05cd65afd3a3d7a01aef01ade143adb8b0d13299 /docs
parent32bea4a1cf9968a4e46a6ecd7fd878e6f0159511 (diff)
docs: Configuration path update
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> Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
Diffstat (limited to 'docs')
-rw-r--r--docs/buildroot.html6
1 files changed, 3 insertions, 3 deletions
diff --git a/docs/buildroot.html b/docs/buildroot.html
index 2314d1095..d5be1276c 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>