Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!ames!ucsd!ucsdhub!esosun!seismo!uunet!visdc!jiii
From: jiii@visdc.UUCP (John E Van Deusen III)
Newsgroups: comp.unix.wizards
Subject: Porting the BSD 4.3 Tahoe distribution to System V
Summary: Relationships of sgtty.h, termio.h, stty(), and ioctl()?
Keywords: stty ioctl sgtty termio stdio
Message-ID: <464@visdc.UUCP>
Date: 9 Feb 89 22:08:21 GMT
Reply-To: jiii@visdc.UUCP (John E Van Deusen III)
Organization: VI Software Development, Boise, Idaho
Lines: 30

I am attempting to port some of the BSD 4.3 Tahoe software to a Unix V.0
(Uniplus+) machine.  In posting the following questions, I assume that
the porting problems are of interest to more people than just me:

     A: Is there is any documentation, especially of the include files,
        somewhere in the release.  Any man(1) entries?

     B: What is the difference between the ioctl(2) system call
        utilizing the <termio.h> include file and the ioctl(2) call
        using <sttyb.h>.  My system has both include files, but they are
        clearly not compatible.  I have no documentation for sgttyb.h on
        my machine and including both in the same source file causes
        complaints about redefining things.  My version of sgtty.h does
        not define CBREAK.  Is CBREAK equivalent to RAW?

     C: The BDS software, (for libcurses), uses a stty() system call
        with a pointer to a sgtty structure.  I have stty() in the libc
        archive, but it is not documented.  The result of using it seems
        to be a hung terminal.  To make the BSD software work, does
        everything have to be rewritten in terms of ioctl() calls and
        termio.h defines?

     D: The BSD software often deals directly with variables defined in
        stdio.h.  The scanw.c routine of libcurses, contains the line
        junk._flag = _IOREAD|_IOSTRG; What does _IOSTRG mean?  Is is
        equivalent to _IOMYBUF?
--
John E Van Deusen III, PO Box 9283, Boise, ID  83707, (208) 343-1865

uunet!visdc!jiii