From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 10301] systemd/getty unused options
Date: Fri, 08 Sep 2017 16:55:43 +0000 [thread overview]
Message-ID: <bug-10301-163-s04tp6nb2d@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-10301-163@https.bugs.busybox.net/>
https://bugs.busybox.net/show_bug.cgi?id=10301
Yann E. MORIN <yann.morin.1998@free.fr> changed:
What |Removed |Added
----------------------------------------------------------------------------
Assignee|unassigned at buildroot.uclibc |yann.morin.1998 at free.fr
|.org |
CC| |yann.morin.1998 at free.fr
Status|NEW |ASSIGNED
--- Comment #1 from Yann E. MORIN <yann.morin.1998@free.fr> ---
Michael, All,
> In menuconfig I can set
> BR2_TARGET_GENERIC_GETTY_TERM
> BR2_TARGET_GENERIC_GETTY_OPTIONS
> but it is only used for busybox and sysvinit.
> So I guess this should be implemented or disabled when systemd is used.
Yes, true.
> Is there any technical reason why this is not implemented?
As far as I understand, systemd will automatically decide the value of
$TERM depending on the type of tty it is spawning on, see:
https://github.com/systemd/systemd/commit/ccf22d4a104e6ed2666d6c5b4031981a84787790#diff-6af423bac2f70681895dc996361e6022
Also, we use the getty services orvided by Systemd as-is; we do not
provide our own, so we rely on systemd's behaviour here.
Now, maybe you could try to add an "Environement=TERM=blabla" directive
in /lib/systemd/system/getty at .service and see if that works.
If that works, we can see to come up with a way to do it.
Similarly for the getty options...
In the meantime, the by-far simplest solutiokn is to hide the options
from the menuconfig when usign systemd! ;-)
Regards,
Yann E. MORIN.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2017-09-08 16:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-08 9:42 [Buildroot] [Bug 10301] New: systemd/getty unused options bugzilla at busybox.net
2017-09-08 16:55 ` bugzilla at busybox.net [this message]
2018-01-10 22:15 ` [Buildroot] [Bug 10301] " bugzilla at busybox.net
2018-01-12 21:11 ` bugzilla at busybox.net
2018-01-16 23:04 ` bugzilla at busybox.net
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=bug-10301-163-s04tp6nb2d@https.bugs.busybox.net/ \
--to=bugzilla@busybox.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.