Re: RFC: Remove pty(4)

2014-11-28 Thread Julian Elischer
On 11/28/14, 2:37 AM, Alfred Perlstein wrote: On Nov 27, 2014, at 1:52 AM, Konstantin Belousov wrote: On Wed, Nov 26, 2014 at 04:41:27PM -0800, Davide Italiano wrote: On Mon, Aug 25, 2014 at 12:37 PM, John Baldwin wrote: On Wednesday, August 20, 2014 11:00:14 AM Davide Italiano wrote: One o

Re: RFC: Remove pty(4)

2014-11-27 Thread Davide Italiano
On Thu, Nov 27, 2014 at 10:37 AM, Alfred Perlstein wrote: > > On Nov 27, 2014, at 1:52 AM, Konstantin Belousov wrote: > >> On Wed, Nov 26, 2014 at 04:41:27PM -0800, Davide Italiano wrote: >>> On Mon, Aug 25, 2014 at 12:37 PM, John Baldwin wrote: On Wednesday, August 20, 2014 11:00:14 AM Davi

Re: RFC: Remove pty(4)

2014-11-27 Thread Alfred Perlstein
On Nov 27, 2014, at 1:52 AM, Konstantin Belousov wrote: > On Wed, Nov 26, 2014 at 04:41:27PM -0800, Davide Italiano wrote: >> On Mon, Aug 25, 2014 at 12:37 PM, John Baldwin wrote: >>> On Wednesday, August 20, 2014 11:00:14 AM Davide Italiano wrote: One of my personal goals for 11 is to get

Re: RFC: Remove pty(4)

2014-11-27 Thread Miguel Clara
I've recently created a port for linux-sublime and some of the packages users might add to sublime require loading pty. I haven't read the full thread so I'm not sure what would actually be removed but If there no reason for it I don't see why waste the time on such a task. is there for example

Re: RFC: Remove pty(4)

2014-11-27 Thread Poul-Henning Kamp
In message <20141127095229.go17...@kib.kiev.ua>, Konstantin Belousov writes: >On Wed, Nov 26, 2014 at 04:41:27PM -0800, Davide Italiano wrote: >> On Mon, Aug 25, 2014 at 12:37 PM, John Baldwin wrote: >> > On Wednesday, August 20, 2014 11:00:14 AM Davide Italiano wrote: >> >> One of my pe

Re: RFC: Remove pty(4)

2014-11-27 Thread Konstantin Belousov
On Wed, Nov 26, 2014 at 04:41:27PM -0800, Davide Italiano wrote: > On Mon, Aug 25, 2014 at 12:37 PM, John Baldwin wrote: > > On Wednesday, August 20, 2014 11:00:14 AM Davide Italiano wrote: > >> One of my personal goals for 11 is to get rid of cloning mechanism > >> entirely, and pty(4) is one of

Re: RFC: Remove pty(4)

2014-11-26 Thread Davide Italiano
On Mon, Aug 25, 2014 at 12:37 PM, John Baldwin wrote: > On Wednesday, August 20, 2014 11:00:14 AM Davide Italiano wrote: >> One of my personal goals for 11 is to get rid of cloning mechanism >> entirely, and pty(4) is one of the few in-kernel drivers still relying >> on such mechanism. >> It's not

Re: RFC: Remove pty(4)

2014-08-25 Thread John Baldwin
On Wednesday, August 20, 2014 11:00:14 AM Davide Italiano wrote: > One of my personal goals for 11 is to get rid of cloning mechanism > entirely, and pty(4) is one of the few in-kernel drivers still relying > on such mechanism. > It's not possible, at least to my understanding, converting pty(4) to

Re: RFC: Remove pty(4)

2014-08-20 Thread Sam Fourman Jr.
Sam Fourman Jr. On Aug 20, 2014 1:00 PM, "Davide Italiano" wrote: > > One of my personal goals for 11 is to get rid of cloning mechanism > entirely, and pty(4) is one of the few in-kernel drivers still relying > on such mechanism. > It's not possible, at least to my understanding, converting pty(4

Re: RFC: Remove pty(4)

2014-08-20 Thread Slawa Olhovchenkov
On Wed, Aug 20, 2014 at 11:00:14AM -0700, Davide Italiano wrote: > One of my personal goals for 11 is to get rid of cloning mechanism > entirely, and pty(4) is one of the few in-kernel drivers still relying > on such mechanism. > It's not possible, at least to my understanding, converting pty(4) t

Re: RFC: Remove pty(4)

2014-08-20 Thread Bryan Drewery
On 8/20/2014 1:13 PM, Julian Elischer wrote: > On 8/20/14, 11:00 AM, Davide Italiano wrote: >> One of my personal goals for 11 is to get rid of cloning mechanism >> entirely, and pty(4) is one of the few in-kernel drivers still relying >> on such mechanism. >> It's not possible, at least to my unde

Re: RFC: Remove pty(4)

2014-08-20 Thread Garrett Cooper
> On Aug 20, 2014, at 11:05, Alfred Perlstein wrote: > >> On 8/20/14 11:00 AM, Davide Italiano wrote: >> One of my personal goals for 11 is to get rid of cloning mechanism >> entirely, and pty(4) is one of the few in-kernel drivers still relying >> on such mechanism. >> It's not possible, at lea

Re: RFC: Remove pty(4)

2014-08-20 Thread Julian Elischer
On 8/20/14, 11:00 AM, Davide Italiano wrote: One of my personal goals for 11 is to get rid of cloning mechanism entirely, and pty(4) is one of the few in-kernel drivers still relying on such mechanism. It's not possible, at least to my understanding, converting pty(4) to cdevpriv(9) as happened w

Re: RFC: Remove pty(4)

2014-08-20 Thread Hans Petter Selasky
On 08/20/14 20:00, Davide Italiano wrote: One of my personal goals for 11 is to get rid of cloning mechanism entirely, and pty(4) is one of the few in-kernel drivers still relying on such mechanism. It's not possible, at least to my understanding, converting pty(4) to cdevpriv(9) as happened with

Re: RFC: Remove pty(4)

2014-08-20 Thread Alfred Perlstein
On 8/20/14 11:00 AM, Davide Italiano wrote: One of my personal goals for 11 is to get rid of cloning mechanism entirely, and pty(4) is one of the few in-kernel drivers still relying on such mechanism. It's not possible, at least to my understanding, converting pty(4) to cdevpriv(9) as happened w

RFC: Remove pty(4)

2014-08-20 Thread Davide Italiano
One of my personal goals for 11 is to get rid of cloning mechanism entirely, and pty(4) is one of the few in-kernel drivers still relying on such mechanism. It's not possible, at least to my understanding, converting pty(4) to cdevpriv(9) as happened with other drivers. This is mainly because we al