All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 10301] New: systemd/getty unused options
Date: Fri, 08 Sep 2017 09:42:36 +0000	[thread overview]
Message-ID: <bug-10301-163@https.bugs.busybox.net/> (raw)

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.

             reply	other threads:[~2017-09-08  9:42 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-08  9:42 bugzilla at busybox.net [this message]
2017-09-08 16:55 ` [Buildroot] [Bug 10301] systemd/getty unused options bugzilla at busybox.net
2018-01-10 22:15 ` 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@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.