From: "Adamski, Krzysztof (Nokia - PL/Wroclaw)" <krzysztof.adamski@nokia.com>
To: "Enrico Weigelt, metux IT consult" <lkml@metux.net>
Cc: Vincent Whitchurch <vincent.whitchurch@axis.com>,
Greg KH <gregkh@linuxfoundation.org>,
"jslaby@suse.com" <jslaby@suse.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] tty: Add NULL TTY driver
Date: Fri, 12 Apr 2019 13:12:05 +0000 [thread overview]
Message-ID: <20190412131156.GB28707@localhost.localdomain> (raw)
In-Reply-To: <eb11752c-7c20-2a39-d4a7-3be7282b4144@metux.net>
On Fri, Apr 12, 2019 at 01:40:56PM +0200, Enrico Weigelt, metux IT consult wrote:
>On 12.04.19 09:30, Adamski, Krzysztof (Nokia - PL/Wroclaw) wrote:
>
>> Well, that depends. If the program doing those writes expects /dev/console
>> to be a tty device, then it cannot be any file.
>
>According to Vincent's mail, the actual problem is just systemd.
>Changing the kernel just for making one specific userland program
>(which happens to be written by somebody, who even doesn't know the
>semantics of rm -R) happy, sounds pretty strange for me.
>
>I'm not opposed to the general idea of having a dummy tty driver,
>but please for some actually sane usecases, not just working around
>broken userland :p
I don't want to start a flame but if that userspace would be written by
somebody else, would that change anything? :) Anyways, historically we
did not have many convinence usitlities in the kernel and now we do. So
does the fact that "this might be convinient but is not strictly
necessary" a blocker to get something into the kernel?
Krzysztof
next prev parent reply other threads:[~2019-04-12 13:12 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-03 11:33 [PATCH] tty: Add NULL TTY driver Vincent Whitchurch
2019-04-03 13:12 ` Greg KH
2019-04-03 14:11 ` Vincent Whitchurch
2019-04-05 8:39 ` Enrico Weigelt, metux IT consult
2019-04-05 9:00 ` Vincent Whitchurch
2019-04-05 12:32 ` Enrico Weigelt, metux IT consult
2019-04-11 13:05 ` Adamski, Krzysztof (Nokia - PL/Wroclaw)
2019-04-12 7:17 ` Enrico Weigelt, metux IT consult
2019-04-12 7:34 ` Adamski, Krzysztof (Nokia - PL/Wroclaw)
[not found] ` <0a50343e-6ebe-f725-82f7-5c127b5ce2e6@nokia.com>
2019-04-12 11:40 ` Enrico Weigelt, metux IT consult
2019-04-12 13:12 ` Adamski, Krzysztof (Nokia - PL/Wroclaw) [this message]
2019-04-11 15:28 ` Vincent Whitchurch
2019-04-12 11:31 ` Enrico Weigelt, metux IT consult
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=20190412131156.GB28707@localhost.localdomain \
--to=krzysztof.adamski@nokia.com \
--cc=gregkh@linuxfoundation.org \
--cc=jslaby@suse.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lkml@metux.net \
--cc=vincent.whitchurch@axis.com \
/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.