All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alexey Brodkin <Alexey.Brodkin@synopsys.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] system: run getty on boot console by default
Date: Tue, 23 Dec 2014 12:32:00 +0000	[thread overview]
Message-ID: <1419337919.2781.6.camel@synopsys.com> (raw)
In-Reply-To: <CAGm1_ktp7gkprBXNLTvd3gE7LMv_9cyUXyF3eb3r83OGPie0NQ@mail.gmail.com>

Hi Yegor,


On Tue, 2014-12-23 at 13:18 +0100, Yegor Yefremov wrote:
> On Tue, Dec 23, 2014 at 1:06 PM, Alexey Brodkin
> <Alexey.Brodkin@synopsys.com> wrote:
> > We used to specify explicitly serial port with all its settings
> > for init to instantiate getty.
> >
> > This limits usecases when the same one rootfs could be used.
> >
> > For example following cases won't work well with hardcoded
> > serial console settings:
> >  * On the same board other serial port is expected to be used
> >  * The same rootfs is intended to be used on different boards with
> >    different serial ports (like ttySx vs ttyAMAx or even ttyx)
> >
> > With this change by default we rely on "console" specified in
> > kernel's boot command line.
> >
> > What is important getty will be set on the last console
> > specified in bootargs.
> >
> > For example is a kernel comand line:
> > --->---
> > bootargs="... console=tty0 console=ttyS3,115200n8..."
> > --->---
> >
> > This now will instantiate serial console on ttyS3 but not on tty0.
> >
> > Tested with both Busybox and SysV init.
> 
> But can you login as root via /dev/console? AFAIK it was the main
> problem by this approach. There is also another alternative: cttyhack

Probably I don't quite understand your question.
What is a problem with "/dev/console"?

I do login as root with these new settings:
--->---
# whooami
root
--->---

Did I miss something?

-Alexey

  reply	other threads:[~2014-12-23 12:32 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-23 12:06 [Buildroot] [PATCH] system: run getty on boot console by default Alexey Brodkin
2014-12-23 12:18 ` Yegor Yefremov
2014-12-23 12:32   ` Alexey Brodkin [this message]
2014-12-23 13:57     ` Yegor Yefremov
2014-12-23 14:35       ` Alexey Brodkin
2014-12-23 19:52         ` Thomas Petazzoni
2014-12-23 21:18           ` Alexey Brodkin
2014-12-23 22:10             ` Thomas Petazzoni
2014-12-24  9:03               ` Alexey Brodkin
2015-01-09 18:15                 ` Alexey Brodkin
2015-01-10 16:10 ` Thomas Petazzoni
2015-01-12 22:07 ` Thomas Petazzoni

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=1419337919.2781.6.camel@synopsys.com \
    --to=alexey.brodkin@synopsys.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.