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 15:24:31 +0100	[thread overview]
Message-ID: <20131205142431.GA16891@x2.net.home> (raw)
In-Reply-To: <20131205133707.GB17074@olila.local.net-space.pl>

On Thu, Dec 05, 2013 at 02:37:07PM +0100, Daniel Kiper wrote:
> >    agetty --detect-console [baud_rate...] [term]
> 
> Make sens.
> 
> > Note that in login-utils/sulogin-consoles.c we have code to detect
> > consoles for sulogin, for example detect_consoles_from_cmdline().
> 
> Great... I will try to use it. Should I build this file as a library
> and then link into agetty or just link ordinary object file
> (login-utils/sulogin-consoles.o) with it?

 You can move the function (or some fragment of the function) to
 the lib/ttyutils.c, the file is already used for libcommon.so (lib
 used everywhere in the package).

> > 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.)
> 
> That is great. However, I do not know systemd (I only heard about that)
> and maybe my question is stupid but I am curious how it starts getty
> on serial console, i.e. how it gets a name of serial console and
> passes it to getty.

 from kernel command line, more details:
 http://0pointer.de/blog/projects/serial-console.html

    Karel

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

      reply	other threads:[~2013-12-05 14:24 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
2013-12-05 13:37   ` Daniel Kiper
2013-12-05 14:24     ` Karel Zak [this message]

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=20131205142431.GA16891@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