All of lore.kernel.org
 help / color / mirror / Atom feed
From: Charles Krinke <charles.krinke@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] Switching to /dev/ttyX
Date: Thu, 14 Apr 2011 15:40:09 -0700	[thread overview]
Message-ID: <BANLkTinoehuK5-xrtQSKyAVu3BdChV7HmA@mail.gmail.com> (raw)
In-Reply-To: <BANLkTi=_zF-UOK2PQPxewXb7bPO00mzuAQ@mail.gmail.com>

What I am currently doing is commenting out the three tty's, tty1, tth2 &
tty3 and then uncommenting ttyS0 in /etc/inittab on the mounted root
filesystem.

I would appreciate some discussion from someone who is familiar with the
location of /etc/inittab in buildroot's build so we could modify it before
the rootfs is created.



On Thu, Apr 14, 2011 at 12:50 AM, Thomas De Schampheleire <
patrickdepinguin+buildroot@gmail.com> wrote:

> Hi,
>
> In /etc/inittab, you have e.g.
>
> tty1::respawn:/sbin/getty 38400 tty1
> tty2::respawn:/sbin/getty 38400 tty2
> tty3::respawn:/usr/bin/tail -f /var/log/messages
>
> By default I'm connected to the board on a serial line, e.g. /dev/ttyS0
>
> My question is: how can I access the other /dev/tty's?
> I tried the chvt command, but that does nothing: the command just
> completes but nothing changes on the shell.
>
> 'tty' always shows /dev/ttyS0.
>
> Thanks,
> Thomas
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot
>



-- 
Charles Krinke
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20110414/7f2f70d1/attachment.html>

  parent reply	other threads:[~2011-04-14 22:40 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-14  7:50 [Buildroot] Switching to /dev/ttyX Thomas De Schampheleire
2011-04-14  9:02 ` Baruch Siach
2011-04-14 22:40 ` Charles Krinke [this message]
2011-04-15  0:04 ` Michael J. Hammel
2011-04-18  8:34   ` Thomas De Schampheleire
2011-04-19 20:25 ` Thomas Petazzoni
2011-04-20  1:48   ` Charles Krinke

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=BANLkTinoehuK5-xrtQSKyAVu3BdChV7HmA@mail.gmail.com \
    --to=charles.krinke@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.