From: Peter Seiderer <ps.report@gmx.net>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] systemd: let getty instead of serial-getty handle /dev/console
Date: Wed, 21 Sep 2016 22:05:45 +0200 [thread overview]
Message-ID: <20160921220545.238279e6@gmx.net> (raw)
In-Reply-To: <87intpzqge.fsf@dell.be.48ers.dk>
Hello *,
On Wed, 21 Sep 2016 09:01:37 +0200, Peter Korsgaard <peter@korsgaard.com> wrote:
> >>>>> "Yann" == Yann E MORIN <yann.morin.1998@free.fr> writes:
>
> > Floris, All,
> > On 2016-09-09 18:10 +0200, Floris Bos spake thusly:
> >> The serial-getty unit depends on dev-%i.device which does not
> >> seem to be created for /dev/console
> >> Workaround this by letting normal getty unit handle things
> >> if BR2_TARGET_GENERIC_GETTY_PORT is set to 'console'
> >>
> >> Signed-off-by: Floris Bos <bos@je-eigen-domein.nl>
>
> > I haven't tested that, but I think this is OK just on principle.
>
> > I just wonder if that behaves correctly when console is a serial line or
> > anything else (e.g. a VT on HDMI, or through a debug channel...)
>
> Yeah, me too. Does anybody know what the difference exactly is between
> getty/serial-getty, and when one should be used over the other?
>
Tested for the rpi3/glibc/systemd case and failed: I get a doubled
(and unusable) ' Welcome to Buildroot/buildroot login:' on serial and
no login on hdmi...
Regards,
Peter
next prev parent reply other threads:[~2016-09-21 20:05 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-09 16:10 [Buildroot] [PATCH] systemd: let getty instead of serial-getty handle /dev/console Floris Bos
2016-09-11 20:00 ` Thomas Petazzoni
2016-09-11 21:09 ` Yann E. MORIN
2016-09-21 7:01 ` Peter Korsgaard
2016-09-21 20:05 ` Peter Seiderer [this message]
2016-09-21 21:47 ` Floris Bos
2016-09-22 18:50 ` Peter Seiderer
2016-09-22 19:25 ` Floris Bos
2016-09-25 21:44 ` Peter Seiderer
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=20160921220545.238279e6@gmx.net \
--to=ps.report@gmx.net \
--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.