[Buildroot] [Bug 10301] New: systemd/getty unused options

[Buildroot] [Bug 10301] New: systemd/getty unused options

[bugzilla at busybox.net]

https://bugs.busybox.net/show_bug.cgi?id=10301

            Bug ID: 10301
           Summary: systemd/getty unused options
           Product: buildroot
           Version: 2017.08
          Hardware: All
                OS: Linux
            Status: NEW
          Severity: minor
          Priority: P5
         Component: Other
          Assignee: unassigned at buildroot.uclibc.org
          Reporter: posted at heine.so
                CC: buildroot at uclibc.org
  Target Milestone: ---

Hi,

I stumbled across a minor issue with the getty configuration when using
systemd.

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.

I would supply a patch, but first wanted to know: Is there any technical reason
why this is not implemented? 

Regards,
Michael

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Buildroot] [Bug 10301] systemd/getty unused options

[bugzilla at 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.

[Buildroot] [Bug 10301] systemd/getty unused options

[bugzilla at busybox.net]

https://bugs.busybox.net/show_bug.cgi?id=10301

--- Comment #2 from Thomas Petazzoni <thomas.petazzoni@free-electrons.com> ---
I've submitted at http://patchwork.ozlabs.org/patch/858587/ a patch that hides
those options when systemd is used.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Buildroot] [Bug 10301] systemd/getty unused options

[bugzilla at busybox.net]

https://bugs.busybox.net/show_bug.cgi?id=10301

--- Comment #3 from Thomas Petazzoni <thomas.petazzoni@free-electrons.com> ---
Fixed by
https://git.buildroot.org/buildroot/commit/?id=5e23eb5da7b3848cc6b317af9d8c23aac3a13260.
Thanks!

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Buildroot] [Bug 10301] systemd/getty unused options

[bugzilla at busybox.net]

https://bugs.busybox.net/show_bug.cgi?id=10301

Thomas Petazzoni <thomas.petazzoni@free-electrons.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|ASSIGNED                    |RESOLVED
         Resolution|---                         |FIXED

-- 
You are receiving this mail because:
You are on the CC list for the bug.