Does anybody know whether the ptm/s grantpt/unlockpt/etc. stuff is a
standard outside Solaris? It seems like each person that writes a
package adds the caveat that it probably won't work on anything but
Solaris.
I've already got a message from someone using AIX saying that his machine
looks SVR4-ish (i.e. no /vmunix), but he seems to have no /dev/ptmx. (It's
inconclusive so far, since he hasn't replied with the tests I suggested,
but it's a bad sign.)
Please copy me directly, I'm not on the alias anymore.
Thanks,
-Eric
----- Begin Included Message -----
From: Tim Bunce <Tim.Bunce@ig.co.uk>
Newsgroups: comp.lang.perl.misc
Subject: Re: RELEASE: Term::Pty 0.1 for Solaris 2.4
Lines: 70
Sender: news@ig.co.uk
X-Nntp-Posting-Host: ig.co.uk
Organisation: Paul Ingram Group, Software Systems, +44 1 483 424424
In article <458q9o$i6h@ns.ccsn.edu>, Russell Mosemann <mose@ns.ccsn.edu> wrote:
> Tom Christiansen was quoted as saying:
> > > You should probably just give up on perl for expect stuff.
>
> Eric Arnold then states his case that it _can_ be done in Perl, and
> he backs it up with code! Later Eric makes the statement
>
> > The main problem being that Perl has no interface to ptm functions
> > like "grantpt" and "ptsname". Making a C linkable module seems
> > like overkill. Is there a POSIX standard for this, which could place
> > it in the POSIX module?
>
> > Perl5 does have a good socket module, which should be used, I guess,
> > but it doesn't have Streams stuff like "I_PUSH", etc. So, system
> > dependencies will still have to live in the Comm.pl package.
>
> Both of these are very good points. A few weeks back I was looking
> for code which would allow a perl script to talk to the passwd program.
> That's all I wanted it to do. chat2.pl wasn't up to the task on
> Solaris, and I couldn't find any other scripts. So, I set out to write
> my own. I ran into several problems along the way, but with help from
> perl people like you I was able to solve them.
> The result of my efforts is Term::Pty 0.1, a set of routines that are
> as faithful as possible to the man pages for ptm and pts for creating a
> pseudoterminal under Solaris 2.4. It includes a dynamic module for
> loading the grantpt, ptsname and unlockpt functions and making them
> available to a perl script.
Sigh. I don't suppose many people know the one about London Buses but
roughly paraphrased it goes something like "You wait for ages for a
Pty module to come along and then two turn up at once!"
I recently added this to the Module List (to be posted on the 10th):
5) Networking, Device Control (modems) and InterProcess Communication
Name DSLI Description Info
----------- ---- -------------------------------------------- -----
Ptty adcf Pseudo terminal interface functions NI-S +
NI-S Nick Ing-Simmons <nik@tiuk.ti.com>
(I've CC'd this to Nick).
It's a pity that you didn't announce the fact that you were working
on this either here or on perl5-porters so we could have avoided the
duplication of effort. Sigh.
> Term::Pty is not a Swiss army knife. It does only one thing and it
> does it well for what I want it to do.
It looks quite comprehensive.
> This code is not portable and only works under Solaris 2.4, that I know of.
I _think_ Nick's module has been tested on a copule of other platforms.
> I do not plan on developing Term::Pty any more. It works, and I have
> too many other things to do.
Okay. Can we agree then that Nick will 'own' the Pseudo Terminal
Interface pumpkin and consolidate your code into his if/where applicable?
Let's, at the very least, agree an interface to pty management.
> Russell Mosemann Concordia College Voice: (402) 643-7445
> Computing Center Seward, NE 68434 Fax: (402) 643-4073
Tim.
----- End Included Message -----
standard outside Solaris? It seems like each person that writes a
package adds the caveat that it probably won't work on anything but
Solaris.
I've already got a message from someone using AIX saying that his machine
looks SVR4-ish (i.e. no /vmunix), but he seems to have no /dev/ptmx. (It's
inconclusive so far, since he hasn't replied with the tests I suggested,
but it's a bad sign.)
Please copy me directly, I'm not on the alias anymore.
Thanks,
-Eric
----- Begin Included Message -----
From: Tim Bunce <Tim.Bunce@ig.co.uk>
Newsgroups: comp.lang.perl.misc
Subject: Re: RELEASE: Term::Pty 0.1 for Solaris 2.4
Lines: 70
Sender: news@ig.co.uk
X-Nntp-Posting-Host: ig.co.uk
Organisation: Paul Ingram Group, Software Systems, +44 1 483 424424
In article <458q9o$i6h@ns.ccsn.edu>, Russell Mosemann <mose@ns.ccsn.edu> wrote:
> Tom Christiansen was quoted as saying:
> > > You should probably just give up on perl for expect stuff.
>
> Eric Arnold then states his case that it _can_ be done in Perl, and
> he backs it up with code! Later Eric makes the statement
>
> > The main problem being that Perl has no interface to ptm functions
> > like "grantpt" and "ptsname". Making a C linkable module seems
> > like overkill. Is there a POSIX standard for this, which could place
> > it in the POSIX module?
>
> > Perl5 does have a good socket module, which should be used, I guess,
> > but it doesn't have Streams stuff like "I_PUSH", etc. So, system
> > dependencies will still have to live in the Comm.pl package.
>
> Both of these are very good points. A few weeks back I was looking
> for code which would allow a perl script to talk to the passwd program.
> That's all I wanted it to do. chat2.pl wasn't up to the task on
> Solaris, and I couldn't find any other scripts. So, I set out to write
> my own. I ran into several problems along the way, but with help from
> perl people like you I was able to solve them.
> The result of my efforts is Term::Pty 0.1, a set of routines that are
> as faithful as possible to the man pages for ptm and pts for creating a
> pseudoterminal under Solaris 2.4. It includes a dynamic module for
> loading the grantpt, ptsname and unlockpt functions and making them
> available to a perl script.
Sigh. I don't suppose many people know the one about London Buses but
roughly paraphrased it goes something like "You wait for ages for a
Pty module to come along and then two turn up at once!"
I recently added this to the Module List (to be posted on the 10th):
5) Networking, Device Control (modems) and InterProcess Communication
Name DSLI Description Info
----------- ---- -------------------------------------------- -----
Ptty adcf Pseudo terminal interface functions NI-S +
NI-S Nick Ing-Simmons <nik@tiuk.ti.com>
(I've CC'd this to Nick).
It's a pity that you didn't announce the fact that you were working
on this either here or on perl5-porters so we could have avoided the
duplication of effort. Sigh.
> Term::Pty is not a Swiss army knife. It does only one thing and it
> does it well for what I want it to do.
It looks quite comprehensive.
> This code is not portable and only works under Solaris 2.4, that I know of.
I _think_ Nick's module has been tested on a copule of other platforms.
> I do not plan on developing Term::Pty any more. It works, and I have
> too many other things to do.
Okay. Can we agree then that Nick will 'own' the Pseudo Terminal
Interface pumpkin and consolidate your code into his if/where applicable?
Let's, at the very least, agree an interface to pty management.
> Russell Mosemann Concordia College Voice: (402) 643-7445
> Computing Center Seward, NE 68434 Fax: (402) 643-4073
Tim.
----- End Included Message -----