util-linux.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Karel Zak <kzak@redhat.com>
To: util-linux@vger.kernel.org
Cc: Lennart Poettering <lennart@poettering.net>
Subject: Re: agetty and special chars @ and #
Date: Fri, 16 Nov 2012 11:14:19 +0100	[thread overview]
Message-ID: <20121116101419.GC20338@x2.net.home> (raw)
In-Reply-To: <20121114142720.GA23414@boole.suse.de>

On Wed, Nov 14, 2012 at 03:27:20PM +0100, Dr. Werner Fink wrote:
> Indeed this is a good solution ... but in the case of systemd and its
> getty generator we may think about a /etc/agettytab with a similar
> syntax scheme as the old /etc/inittab to be able to provide agetty
> options based on the used tty line.  Clearly this /etc/agettytab should
> be parsed by agetty and options for the specified tty are found:
> 
>   1:tty1:--noclear %p
>   2:tty2:%p
>   3:tty3:%p
>   4:tty4:%p
>   5:tty5:%p
>   6:tty6:%p
>   S0:ttyS0:--erase-chars # --kill-chars @ -mt 60 %p 9600,2400,1200
>   S1:ttyS0:-L 9600 %p 9600 vt102

 Hmm, I guess it's still possible to create tty line specific config
 file on systems with systemd. I'd like to avoid another place where
 will be configuration.

 Lennart?



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

  reply	other threads:[~2012-11-16 10:14 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-07 16:58 agetty and special chars @ and # Karel Zak
2012-11-12 10:04 ` Dr. Werner Fink
2012-11-12 13:29   ` Karel Zak
2012-11-14 14:27     ` Dr. Werner Fink
2012-11-16 10:14       ` Karel Zak [this message]
2012-11-16 12:47         ` Lennart Poettering
2012-11-16 13:05           ` Karel Zak
2012-11-20  0:47             ` Lennart Poettering
2012-11-20  9:26               ` [util-linux] " Dr. Werner Fink
2012-11-20 16:59                 ` Lennart Poettering

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=20121116101419.GC20338@x2.net.home \
    --to=kzak@redhat.com \
    --cc=lennart@poettering.net \
    --cc=util-linux@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).