ruby-core@ruby-lang.org archive (unofficial mirror)
 help / color / mirror / Atom feed
From: "pedz (Perry Smith)" <pedz@easesoftware.com>
To: ruby-core@ruby-lang.org
Subject: [ruby-core:58538] [ruby-trunk - Bug #9144][Open] ptys on AIX version 4 through 7
Date: Sun, 24 Nov 2013 04:14:57 +0900	[thread overview]
Message-ID: <redmine.issue-9144.20131124041456@ruby-lang.org> (raw)


Issue #9144 has been reported by pedz (Perry Smith).

----------------------------------------
Bug #9144: ptys on AIX version 4 through 7
https://bugs.ruby-lang.org/issues/9144

Author: pedz (Perry Smith)
Status: Open
Priority: Normal
Assignee: 
Category: 
Target version: 
ruby -v: ruby 2.0.0p247 (2013-06-27 revision 41674) [powerpc-aix6.1.0.0]
Backport: 1.9.3: UNKNOWN, 2.0.0: UNKNOWN


The best way to open a pty on AIX version 4 through 7 is using what they call "AT&T" mode.  The steps are to first open "/dev/ptc" which opens the master side.  Then to a ttyname on the file descriptor and open the string that is returned to open the slave side.

cat q.c
#include <stdio.h>
#include <fcntl.h>

int main(int argc, char *argv[])
{
  int master = open("/dev/ptc", O_RDWR);
  char *slave_name = ttyname(master);
  int slave = open(slave_name, O_RDWR);
  int n;
  char buf[128];

  printf("slave name is %s\n", slave_name);
  printf("master fd is %d, slave fd is %d\n", master, slave);
  write(master, "blah\n", 5);
  n = read(slave, buf, sizeof(buf));
  printf("n = %d\n", n);
  printf("%*.*s", n, n, buf);
  write(slave, "foodog\n", 7);
  n = read(master, buf, sizeof(buf));
  printf("n = %d\n", n);
  printf("%*.*s", n, n, buf);
  return 0;
}

make q
cc     q.c   -o q

./q
slave name is /dev/pts/9
master fd is 3, slave fd is 5
n = 5
blah
n = 14
blah
foodog

(Note that ECHO is set on the tty which is why we see 'blah' when the slave is read.)

You can also use what the ruby code calls BSD 4.2 ptys.  On my build that I did as simply as possible, I'm not sure which code I got but it is not working.  I have several versions of Ruby and all fail with "can't get Master/Slave device (RuntimeError)"  While "BSD" mode is supported and works, the "AT&T" mode is much nicer.

For AIX version 3, there was a similar approach but instead of /dev/ptc, the master was called /dev/ptm.  

The _IBMESA code in ext/pty/pty.c (which mentions AIX) I don't recognize those names.

There is no need to push any streams modules, etc.  Everything is autopushed.  You might want to add in a grantpt but I'm still not clear when and if that is needed.



-- 
http://bugs.ruby-lang.org/

             reply	other threads:[~2013-11-23 19:43 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-23 19:14 pedz (Perry Smith) [this message]
2013-11-23 20:59 ` [ruby-core:58539] Re: [ruby-trunk - Bug #9144][Open] ptys on AIX version 4 through 7 Perry Smith
2015-02-28 14:59 ` [ruby-core:68349] [Ruby trunk - Bug #9144] " nagachika00
2015-05-20 16:33 ` [ruby-core:69254] " nagachika00
2015-05-21  0:47 ` [ruby-core:69258] " usa

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-list from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.ruby-lang.org/en/community/mailing-lists/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=redmine.issue-9144.20131124041456@ruby-lang.org \
    --to=ruby-core@ruby-lang.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).