From: George Dunlap <george.dunlap@eu.citrix.com>
To: Ian Campbell <ian.campbell@citrix.com>,
Daniel Kiper <daniel.kiper@oracle.com>
Cc: keir@xen.org, xen-devel@lists.xen.org, ian.jackson@eu.citrix.com,
jbeulich@suse.com, stefano.stabellini@eu.citrix.com
Subject: Re: [PATCH 1/2] xgetty: Do not edit /etc/inittab when switching from Xen to Linux and back
Date: Fri, 15 Nov 2013 10:28:48 +0000 [thread overview]
Message-ID: <5285F760.6020702@eu.citrix.com> (raw)
In-Reply-To: <1384429865.12096.3.camel@hastur.hellion.org.uk>
On 14/11/13 11:51, Ian Campbell wrote:
> On Thu, 2013-11-14 at 12:44 +0100, Daniel Kiper wrote:
>> xgetty establishes serial console name from system boot command
>> line (/proc/cmdline) and then runs getty. This is very useful if
>> someone switches very often between Linux and Xen and uses serial
>> console. xgetty does boring things and runs getty on relevant line.
>> This way nobody needs to worry about /etc/inittab changes anymore.
> This seems like it could be very useful, but it doesn't seem at all Xen
> specific. I think it would be worth trying to get this into an upstream
> -- e.g. agetty (since that is what you appear to shell out to).
I've been using an inittab entry like this:
T0:23:respawn:bash -c "/sbin/getty --noclear -L
$(/etc/find-remote-tty.sh) 115200 vt102"
But having agetty able to search the Linux command-line for the argument
is much better.
-George
next prev parent reply other threads:[~2013-11-15 10:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-14 11:44 xgetty: Smart serial console getty for Xen Daniel Kiper
2013-11-14 11:44 ` [PATCH 1/2] xgetty: Do not edit /etc/inittab when switching from Xen to Linux and back Daniel Kiper
2013-11-14 11:51 ` Ian Campbell
2013-11-14 15:50 ` Daniel Kiper
2013-11-15 10:28 ` George Dunlap [this message]
2013-11-14 11:44 ` [PATCH 2/2] MAINTAINERS: Add XGETTY maintainer Daniel Kiper
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=5285F760.6020702@eu.citrix.com \
--to=george.dunlap@eu.citrix.com \
--cc=daniel.kiper@oracle.com \
--cc=ian.campbell@citrix.com \
--cc=ian.jackson@eu.citrix.com \
--cc=jbeulich@suse.com \
--cc=keir@xen.org \
--cc=stefano.stabellini@eu.citrix.com \
--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;
as well as URLs for NNTP newsgroup(s).