All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ramkumar Ramachandra <artagnon@gmail.com>
To: Richard Weinberger <richard@nod.at>
Cc: Al Viro <viro@zeniv.linux.org.uk>,
	LKML <linux-kernel@vger.kernel.org>,
	Lennart Poettering <lennart@poettering.net>
Subject: Re: [PATCH] um: change defconfig to stop spawning xterm
Date: Mon, 22 Jul 2013 17:18:32 +0530	[thread overview]
Message-ID: <CALkWK0k_twGS_DYetD6c4GO0ORU0yqyiENamz=NuZ0D6Ap1b6w@mail.gmail.com> (raw)
In-Reply-To: <CALkWK0mpH9XHL2PZK47Lb9frf9hFNQ8sjF2_0p7VJnY8XWhiGw@mail.gmail.com>

> Richard Weinberger wrote:
>> Lennart, can you please explain us why /dev/tty[1..64] is forced to
>> have virtual console support?

The crux of Lennart's argument seems to be that several applications
depend on it, and that applications have to bend over backwards when
those expectations are broken [1].  He has also pointed out that
hypervisor applications implement /dev/hvc0, /dev/xvc0, and /dev/hvsi0
by convention (which serve the same purpose), and that systemd
supports them.  I'm not going to argue about hard rules, because it's
clearly possible to enable CONFIG_TTY and disable CONFIG_VT in the tty
driver (the Kconfig allows this), as um Linux has done.

Since um Linux behaves more like a "container" application, is it
feasible to replace the /dev/tty* with /dev/hvc* in a
backward-compatible manner?  I think it is, although I may be missing
something: we just have to deprecate "tty" in the command-line options
to actually point to /dev/hvc*, and enable HVC_DRIVER/HVC_CONSOLE,
right?  It should be fairly straightforward to deprecate drivers/tty.c
in favor of a newer drivers/hvc.c, I think.

Let me know if I've said something stupid, so I can stop writing the patches.

Thanks.

[1]: http://lists.freedesktop.org/archives/systemd-devel/2013-July/012212.html

  reply	other threads:[~2013-07-22 11:49 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
2013-07-22 10:38       ` Richard Weinberger
2013-07-22 10:43         ` Ramkumar Ramachandra
2013-07-22 11:48           ` Ramkumar Ramachandra [this message]
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='CALkWK0k_twGS_DYetD6c4GO0ORU0yqyiENamz=NuZ0D6Ap1b6w@mail.gmail.com' \
    --to=artagnon@gmail.com \
    --cc=lennart@poettering.net \
    --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.