From: Mark Hatle <fray@mvista.com>
To: Martin Hicks <mort@bork.org>
Cc: Aman <aman@mistralsoftware.com>,
linuxppc embedded <linuxppc-embedded@lists.linuxppc.org>
Subject: Re: Serial Console Login Fails
Date: Wed, 23 Apr 2003 07:59:10 -0500 [thread overview]
Message-ID: <3EA68E1E.7090201@mvista.com> (raw)
In-Reply-To: <20030423123015.GI553@bork.org>
Martin Hicks wrote:
> On Wed, Apr 23, 2003 at 07:41:40AM +0530, Aman wrote:
>
>>"T0:23:respawn:/sbin/getty -L ttyS0 9600 vt100"
>>Bcos of which during the linux bootup , there wont be console message on the
>>screen , after some time , there is a login prompt
>><none>login:
>>If I try login then it waits for some seconds and then display the same i.e
>><none>login:
>
>
> You don't have "ttyS0" in /etc/securetty
Actually if that was the case you'd get a login denied message of some type..
If you don't have an /etc/securetty then it allows all logins.. (that is the
typical setup of systems we recommend for our customers development systems..)
The problem is that they are missing either the pam libraries or they are
missing /bin/login. Turn on syslogd, set a console to go right to a shell and
look at the output of /var/log/messages. This will tell you what is missing.
It is usually /bin/login is missing, secondary cause is PAM (or a module) is
missing, or that your /etc/passwd and/or /etc/group files are missing or corrupt.
(I wonder if we should create a FAQ for this list and post it once a month..
this question/answer come up at _LEAST_ once a week.. doesn't anyone read the
list archives?)
--Mark
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2003-04-23 12:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-23 2:11 Serial Console Login Fails Aman
2003-04-23 12:30 ` Martin Hicks
2003-04-23 12:59 ` Mark Hatle [this message]
2003-04-23 13:46 ` Aman
2003-04-23 13:59 ` Martin Hicks
2003-04-23 14:13 ` Mark Hatle
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=3EA68E1E.7090201@mvista.com \
--to=fray@mvista.com \
--cc=aman@mistralsoftware.com \
--cc=linuxppc-embedded@lists.linuxppc.org \
--cc=mort@bork.org \
/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;
as well as URLs for NNTP newsgroup(s).