From: Olof Johansson <olof@lixom.net>
To: ramkumarj Ramkumar <ramkumarj2000@gmail.com>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: Loop at starting pid 164, tty '': '/sbin/getty'
Date: Mon, 24 Dec 2007 13:38:00 -0600 [thread overview]
Message-ID: <20071224193800.GA3382@lixom.net> (raw)
In-Reply-To: <4f8c3030712240120m30d68b37g8b5f099294c6d769@mail.gmail.com>
Hi,
On Mon, Dec 24, 2007 at 05:20:10PM +0800, ramkumarj Ramkumar wrote:
> I would be very grateful if the following questions could be addressed,
>
> 1. Does the inittab format changed for Linux 2.6. The old one was from
> mkrootfs (which I think is pretty old). I could see some changes in the
> "respawn" line.
Inittab isn't tied to the kernel, but to the init process. So no, it
should not have changed between 2.4 and 2.6.
> 2. Is it required to run the tty0 along with ttyS0. Is this is mandatory. I
> assumed all these days console and ttyS0 should be sufficient.
tty0 is normally one of the vga consoles. It shouldn't be needed if all
you have is serial.
> 3. A very basic question : What is the clear difference between ttyS0 ( UART
> Driver ), console and tty0. To my understanding, ttyS0 is the first port
> UART 's driver (for 16550/8250) which deals with the hardware as such by
> writing and reading the registers. tty0 is virtual console, something to do
> with telnet sessions. But I dont clearly understand why console and tty0 are
> both required or not. Please correct me if my understanding is wrong.
ttyS<x> are normally 8250-compatible uarts, yes. pts/<x> is remote
connections such as telnet or ssh-based ones. tty<x> are normally the
local vga consoles.
-Olof
prev parent reply other threads:[~2007-12-24 19:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-22 8:51 Loop at starting pid 164, tty '': '/sbin/getty' ramkumarj Ramkumar
2007-12-24 4:09 ` Olof Johansson
2007-12-24 9:20 ` ramkumarj Ramkumar
2007-12-24 19:38 ` Olof Johansson [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=20071224193800.GA3382@lixom.net \
--to=olof@lixom.net \
--cc=linuxppc-embedded@ozlabs.org \
--cc=ramkumarj2000@gmail.com \
/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).