public inbox for util-linux@vger.kernel.org
 help / color / mirror / Atom feed
From: Karel Zak <kzak@redhat.com>
To: Daniel Kiper <daniel.kiper@oracle.com>
Cc: util-linux@vger.kernel.org, xen-devel@lists.xen.org
Subject: Re: [RFC PATCH] sgetty: Smart serial console getty
Date: Thu, 5 Dec 2013 12:05:08 +0100	[thread overview]
Message-ID: <20131205110508.GC8058@x2.net.home> (raw)
In-Reply-To: <1386196297-2398-1-git-send-email-daniel.kiper@oracle.com>


 Hi Daniel,

On Wed, Dec 04, 2013 at 11:31:37PM +0100, Daniel Kiper wrote:
> Very often when I was switching from Xen to Linux I was forced
> to change /etc/inittab to make serial console working. It was
> boring so I thought how to solve that problem. I was not able
> to find sensible solution. So I decided to write something.
> Here it is.

Would be better to extend agetty(1) to read console name from kernel
command line rather than introduce a special wrapper?

Something like:

   agetty --detect-console [baud_rate...] [term]

Note that in login-utils/sulogin-consoles.c we have code to detect
consoles for sulogin, for example detect_consoles_from_cmdline().

We did a lot of work to consolidate and clean up agetty and kill
things like mingetty in last years. So I'd like to have only util,
especially if all the magic is just console name only.

> I posted this patch earlier to Xen-devel list but Ian Campbell
> stated that it is more generic and maybe I should try to include

yeah, that's probably a generic issue.

BTW, I guess that systemd does not use hardcoded console names (like
/etc/inittab), ... just for the record :-) (I have no problem to
support classic inittab.)

    Karel

-- 
 Karel Zak  <kzak@redhat.com>
 http://karelzak.blogspot.com

  reply	other threads:[~2013-12-05 11:05 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-04 22:31 [RFC PATCH] sgetty: Smart serial console getty Daniel Kiper
2013-12-05 11:05 ` Karel Zak [this message]
2013-12-05 13:37   ` Daniel Kiper
2013-12-05 14:24     ` Karel Zak

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=20131205110508.GC8058@x2.net.home \
    --to=kzak@redhat.com \
    --cc=daniel.kiper@oracle.com \
    --cc=util-linux@vger.kernel.org \
    --cc=xen-devel@lists.xen.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox