Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] FW: Buildroot RFS Login Question
Date: Wed, 08 Feb 2012 22:18:31 +0100	[thread overview]
Message-ID: <87d39p3ty0.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <4F32D55A.6010004@renta.net> (Mark Constable's message of "Thu, 09 Feb 2012 06:04:42 +1000")

>>>>> "Mark" == Mark Constable <markc@renta.net> writes:

 Mark> Right, I was struggling to find the right inittab entry for a
 Mark> "normal" console login and had used /bin/login which seems to
 Mark> demand a non-root login.  Once I tried this it let me in as root
 Mark> without a password...

 Mark> tty1::respawn:/sbin/getty 38400 tty1

 Mark> It would have saved me a lot of time if this entry was in
 Mark> /etc/inittab, even if it was commented out.

We used to have hardcoded tty1/tty2 lines, but we removed those give
lots of error messages if the kernel isn't compiled with virtual
terminals support (which is fairly common on embedded) - See commit
7d9d09db673a.

It's hard to provide sensible defaults for everyone (E.G. names of
UART device nodes differ between boards), but atleast we have the '
We atleast provide the "Port to run a getty (login prompt) on" option
under System configuration to make it easy to configure.

-- 
Bye, Peter Korsgaard

  reply	other threads:[~2012-02-08 21:18 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CB44467D.2D31%donald.poole@swri.org>
2012-01-24 19:59 ` [Buildroot] FW: Buildroot RFS Login Question Poole, Donald R.
2012-01-26  7:01   ` [Buildroot] " Sinan Akman
2012-01-26 14:59     ` Poole, Donald R.
2012-02-07  8:51   ` [Buildroot] FW: " Samuel Martin
2012-02-08  6:28     ` Poole, Donald R.
2012-02-08  6:57       ` Mark Constable
2012-02-08  7:49         ` Peter Korsgaard
2012-02-08  9:38           ` Samuel Martin
2012-02-08 20:04           ` Mark Constable
2012-02-08 21:18             ` Peter Korsgaard [this message]
2012-03-01 15:11               ` Daniel Nyström

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=87d39p3ty0.fsf@macbook.be.48ers.dk \
    --to=jacmet@uclibc.org \
    --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