Does anyone still care about BSD ptys?
A message that is not in the archive (sent off-list or not yet received): [email protected]
Quoted 8 lines · H. Peter Anvin
Hi all,
Does anyone still care about old-style BSD ptys, i.e.
/dev/pty*? I'm thinking of restructuring the pty system slightly to make it more dynamic and to make use of the new largerdev_t, and I'd like to get rid of the BSD ptys as part of the same patch.-hpa
Quoted 6 lines · H. Peter Anvin
Hi all,
Does anyone still care about old-style BSD ptys, i.e.
/dev/pty*? I'm thinking of restructuring the pty system slightly to make it more dynamic and to make use of the new largerdev_t, and I'd like to get rid of the BSD ptys as part of the same patch.
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.
Signature · 1 line
I doubt like hell this mailer has a sig...
Quoted 8 lines · Bill Davidsen
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
Quoted 12 lines · Theodore Ts'o
Quoted 8 lines · Bill Davidsen
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.
Quoted 6 lines
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.
The way it looks right now it's not going to matter; it appears that (optionally) continuing to supporting BSD ptys will "fall out naturally" at least initially.
Ted, could I ask you to eyeball my patch to see how broken it is?
-hpa
Quoted 5 lines · H. Peter Anvin
The way it looks right now it's not going to matter; it appears that (optionally) continuing to supporting BSD ptys will "fall out naturally" at least initially.
Ted, could I ask you to eyeball my patch to see how broken it is?
Sure, send me your latest version of the patch and I'll take a look at it.
- Ted