All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Theodore Ts'o" <tytso@mit.edu>
To: Bill Davidsen <davidsen@tmr.com>
Cc: "H. Peter Anvin" <hpa@zytor.com>, linux-kernel@vger.kernel.org
Subject: Re: Does anyone still care about BSD ptys?
Date: Tue, 10 Feb 2004 16:52:25 -0500	[thread overview]
Message-ID: <20040210215225.GA1666@thunk.org> (raw)
In-Reply-To: <4029364F.9030905@tmr.com>

On Tue, Feb 10, 2004 at 02:51:43PM -0500, Bill Davidsen wrote:
> Sorry, last reply "just went" for some reason... ijn any case I hope the 
> number and tone of replies has shown that a number of people DO care, 
> and that "you can just program around it with your effort instead of 
> mine" isn't going to be popular.
> 
> In other words, this sounds more like 2.7 material where people expect 
> things to change than something which should just suddenly break in 2.6. 
> Violation of Plauger's Law of Least Astonishment and all that.

I think the discussion has always been that this would be a 2.7 item.  

However, it might be useful to make 2.6 start issueing printk's *now*
when a program uses a BSD pty, so that application programs have
plenty of notice that they will be going away.

						- Ted

  reply	other threads:[~2004-02-10 21:53 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1ne1M-1Oc-1@gated-at.bofh.it>
2004-02-10 19:47 ` Does anyone still care about BSD ptys? Bill Davidsen
2004-02-10 19:51 ` Bill Davidsen
2004-02-10 21:52   ` Theodore Ts'o [this message]
2004-02-10 22:02     ` H. Peter Anvin
2004-02-11  5:31       ` Theodore Ts'o
2004-02-09 16:57 Joerg Pommnitz
2004-02-10 17:23 ` H. Peter Anvin
     [not found] <c07c67$vrs$1@terminus.zytor.com.suse.lists.linux.kernel>
     [not found] ` <c07i5r$ctq$1@news.cistron.nl.suse.lists.linux.kernel>
     [not found]   ` <20040209100940.GF21151@parcelfarce.linux.theplanet.co.uk.suse.lists.linux.kernel>
     [not found]     ` <20040209104729.GA19401@traveler.cistron.net.suse.lists.linux.kernel>
2004-02-09 14:45       ` Andi Kleen
2004-02-09 17:23         ` H. Peter Anvin
  -- strict thread matches above, loose matches on Subject: below --
2004-02-09 13:49 Albert Cahalan
2004-02-09 17:14 ` H. Peter Anvin
2004-02-09 17:18   ` Albert Cahalan
2004-02-09 20:32     ` Andries Brouwer
2004-02-10 11:40     ` Dominik Kubla
2004-02-09  7:17 H. Peter Anvin
2004-02-09  7:21 ` David Weinehall
2004-02-09  7:29   ` H. Peter Anvin
2004-02-09  8:12     ` Ricky Beam
2004-02-09  8:19       ` H. Peter Anvin
2004-02-09  8:59 ` Miquel van Smoorenburg
2004-02-09 10:09   ` viro
2004-02-09 10:47     ` Miquel van Smoorenburg
2004-02-10  1:33     ` bill davidsen
2004-02-10  2:07       ` H. Peter Anvin
2004-02-09 18:06   ` Olaf Hering
2004-02-09  9:29 ` Nick Craig-Wood
2004-02-09 12:47   ` Jamie Lokier
2004-02-09 13:40     ` Nick Craig-Wood
2004-02-09 14:00       ` Richard B. Johnson
2004-02-09 17:51         ` Dominik Kubla
2004-02-09 18:27           ` Richard B. Johnson
2004-02-09 20:59             ` Athanasius
2004-02-10 11:16             ` Dominik Kubla
2004-02-10 17:19               ` H. Peter Anvin
2004-02-10  0:47 ` Karl Tatgenhorst
2004-02-10  0:52   ` H. Peter Anvin
2004-02-10  1:35     ` Karl Tatgenhorst

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=20040210215225.GA1666@thunk.org \
    --to=tytso@mit.edu \
    --cc=davidsen@tmr.com \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.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 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.