From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] Systemd default console
Date: Fri, 20 Sep 2019 16:51:47 +0200 [thread overview]
Message-ID: <20190920165147.765ee765@windsurf> (raw)
In-Reply-To: <CAJ4jsafoQPnGzdvHzn2c7LAZRbORVOhb7PinuSVEmw6_ZitWiQ@mail.gmail.com>
On Fri, 20 Sep 2019 11:47:08 -0300
Carlos Santos <unixmania@gmail.com> wrote:
> > - busybox creates the link
> > /etc/systemd/system/getty.target.wants/console-getty.service, which
> > starts a getty on ttyS0
> > - systemd itself create
> > /run/systemd/generator/getty.target.wants/serial-getty at ttyS0.service
> > automatically (no idea when and how)
> >
> > in and output is perfectly garbled until one of those services is killed.
> > Given that systemd automatically picks up the getty from the
> > commandline, is there any reason for busybox to setup /dev/console?
>
> Do not use BR2_TARGET_GENERIC_GETTY_PORT with systemd.
There's a whole bunch of logic at
https://git.buildroot.org/buildroot/tree/package/systemd/systemd.mk#n435
to do stuff depending on the value of BR2_TARGET_GENERIC_GETTY_PORT. So
it seems kind of odd to recommend to not use
BR2_TARGET_GENERIC_GETTY_PORT with systemd. Shouldn't we fix what's in
systemd.mk so that it works as expected ?
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2019-09-20 14:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-20 13:38 [Buildroot] Systemd default console Norbert Lange
2019-09-20 14:47 ` Carlos Santos
2019-09-20 14:51 ` Thomas Petazzoni [this message]
2019-09-20 15:16 ` Carlos Santos
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=20190920165147.765ee765@windsurf \
--to=thomas.petazzoni@bootlin.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.