From: Andrea Arcangeli <andrea@suse.de>
To: Rik van Riel <riel@conectiva.com.br>
Cc: Andi Kleen <ak@suse.de>, Alan Cox <alan@lxorguk.ukuu.org.uk>,
linux-kernel@vger.kernel.org, margit@margit.com
Subject: Re: Linux 2.4.19 patch for Suse compatibility
Date: Tue, 19 Nov 2002 15:48:01 +0100 [thread overview]
Message-ID: <20021119144801.GN29722@dualathlon.random> (raw)
In-Reply-To: <Pine.LNX.4.44L.0211191132280.1571-100000@duckman.distro.conectiva>
On Tue, Nov 19, 2002 at 11:32:45AM -0200, Rik van Riel wrote:
> On 19 Nov 2002, Andi Kleen wrote:
> > Alan Cox <alan@lxorguk.ukuu.org.uk> writes:
>
> > > This was discussed on the kernel list about four to six weeks ago and
> > > rejected then as well. See the previous discussion
> >
> > Actually I don't remember it being rejected, just the discussion dropped
> > off and there was no suggestion on how to solve the problem this ioctl
> > solves in a better way.
>
> So, what problem does it try to solve ?
how can you find the real device behind /dev/console without such ioctl?
An userspace hack watching /proc/cmdline wouldn't be reliable.
Andrea
next prev parent reply other threads:[~2002-11-19 14:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4.3.2.7.2.20021119122403.00b50d70@mail.dns-host.com.suse.lists.linux.kernel>
[not found] ` <1037710510.11563.5.camel@irongate.swansea.linux.org.uk.suse.lists.linux.kernel>
2002-11-19 12:48 ` Andi Kleen
2002-11-19 13:32 ` Rik van Riel
2002-11-19 14:12 ` Andi Kleen
2002-11-19 14:48 ` Andrea Arcangeli [this message]
2002-11-19 12:53 Margit Schubert-While
-- strict thread matches above, loose matches on Subject: below --
2002-11-19 11:34 Margit Schubert-While
2002-11-19 12:55 ` Alan Cox
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=20021119144801.GN29722@dualathlon.random \
--to=andrea@suse.de \
--cc=ak@suse.de \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=margit@margit.com \
--cc=riel@conectiva.com.br \
/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
all inboxes | Powered by JetHome®