All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ramkumar Ramachandra <artagnon@gmail.com>
To: Al Viro <viro@zeniv.linux.org.uk>
Cc: LKML <linux-kernel@vger.kernel.org>, Richard Weinberger <richard@nod.at>
Subject: Re: [PATCH] um: change defconfig to stop spawning xterm
Date: Mon, 22 Jul 2013 15:15:14 +0530	[thread overview]
Message-ID: <CALkWK0=0NWediExGCwJ3R-O+7V_9sgGzJPUaXgaTEka5O05N=Q@mail.gmail.com> (raw)
In-Reply-To: <CALkWK0kj=maJgrLV11h8GzJ-L24KWDzgCAiZa97rieJKUXeW_A@mail.gmail.com>

Ramkumar Ramachandra wrote:
> [1]: http://lists.freedesktop.org/archives/systemd-devel/2013-July/012152.html

... and the patches were rejected.  Lennart says that UML providing
/dev/tty* is wrong, and that UML should call them /dev/hvc* (or
something).  Can we do something about the situation?  Can we remove
/dev/tty*, and provide /dev/hvc*?  Will we be breaking existing users?

Thanks.

Lennart Poettering wrote:
> UML shouldn't be penalized for not implementing some terminal emulation,
> but it should be penalized for doing so under the label of "VT support",
> which it simply is not providing.
>
> They can call their ttys any way they want. If the call them
> /dev/tty[1..64] however, then they need to implement the VC
> interfaces. All of them.
>
> Also note that some hypervisors implement /dev/hvc0, /dev/xvc0,
> /dev/hvsi0 and suchlike. Theser are also ttys, which are used for
> interfacing in a VT-like way the virtual machines. But they do not claim
> to ve the real VT, they hence picked different tty names.
>
> UML should follow the same route: pick some name you like, or even
> better, pick one of the existing hypervisor tty names if the interface
> and usecase is the same, but do not use /dev/tty[1..64], because that is
> the VT subsystem.
>
> systemd handles the hvc0, xvc0, hvsi0 automatically already. We'd be
> happy if UML could make use of the same logic.

  reply	other threads:[~2013-07-22  9:45 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-19 18:20 [PATCH] um: change defconfig to stop spawning xterm Ramkumar Ramachandra
2013-07-19 18:44 ` Richard Weinberger
2013-07-19 19:44   ` Ramkumar Ramachandra
2013-07-22  9:45     ` Ramkumar Ramachandra [this message]
2013-07-22 10:38       ` Richard Weinberger
2013-07-22 10:43         ` Ramkumar Ramachandra
2013-07-22 11:48           ` Ramkumar Ramachandra
2013-07-22 22:32           ` Lennart Poettering
2013-07-23  5:40             ` Richard Weinberger
2013-07-23  5:47               ` richard -rw- weinberger
2013-07-23  7:57                 ` Al Viro
2013-07-24 16:49                   ` Lennart Poettering
2013-07-24 16:38               ` Lennart Poettering
2013-07-22 12:40       ` Al Viro
2013-07-22 13:02         ` Ramkumar Ramachandra
2013-07-22 13:20           ` Richard Weinberger
2013-07-22 13:42             ` Ramkumar Ramachandra
2013-07-22 14:08               ` Richard Weinberger
2013-07-22 15:33                 ` Ramkumar Ramachandra
2013-07-22 19:29                   ` Richard Weinberger
2013-07-22 20:01                     ` Ramkumar Ramachandra

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='CALkWK0=0NWediExGCwJ3R-O+7V_9sgGzJPUaXgaTEka5O05N=Q@mail.gmail.com' \
    --to=artagnon@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=richard@nod.at \
    --cc=viro@zeniv.linux.org.uk \
    /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.