Subject: Welcome to comp.unix.xenix.sco [changes from previous version]
Newsgroups: comp.unix.xenix.sco,news.answers
From: chip@chinacat.unicom.com (Chip Rosenthal)
Date: Mon, 26 Sep 1994 00:15:43 GMT

Archive-name: sco-xenix-diff
News-answers-archive-name: sco/xenix-diff
Posting-frequency: monthly
Version: 1.58

*** /tmp/faq20590.prev-version	Sun Sep 25 19:14:42 1994
--- /tmp/faq20590.curr-version	Sun Sep 25 19:14:40 1994
***************
*** 1,4 ****
! @(#) sco-xenix 1.56 94/07/17 19:26:45
  
  ------------------------------
  
--- 1,4 ----
! @(#) sco-xenix 1.58 94/08/29 06:15:57
  
  ------------------------------
  
***************
*** 40,46 ****
  by Chip Rosenthal, Jeff Liebermann, Ronald Florence, Chip Salzenberg,
  Ronald Khoo, Vic Michael, and Stephen Bleazard.  Helpful contributions
  and comments have been provided by Andrew Phillips, Peter Funk, Paul
! Warren, Lawrence Kirby, Kai Ruottu, Ray Malitzke, and Chet Creider.
  
  Please examine the date near the top of this message.  Any version
  older might be obsolete.  The most up-to-date version of this FAQ may
--- 40,47 ----
  by Chip Rosenthal, Jeff Liebermann, Ronald Florence, Chip Salzenberg,
  Ronald Khoo, Vic Michael, and Stephen Bleazard.  Helpful contributions
  and comments have been provided by Andrew Phillips, Peter Funk, Paul
! Warren, Lawrence Kirby, Kai Ruottu, Ray Malitzke, Chet Creider, Greg
! Lehey, and Marc Brumlik.
  
  Please examine the date near the top of this message.  Any version
  older might be obsolete.  The most up-to-date version of this FAQ may
***************
*** 295,300 ****
--- 296,305 ----
      This modem supports V.32 transfers, but not PEP.  We've been told
      this system is often behind the other sites.
  
+ 	[LATE BREAKING NEWS:  We've been told that "sosffm" has moved.
+ 	If anybody knows where it went, please let the FAQ editor
+ 	know.  Thanks. -ed]
+ 
      Add to your `/usr/lib/uucp/Permissions' file:
  
          # REQUEST files only - i.e. cannot send to sosco.
***************
*** 994,1001 ****
      can try editing the `/dev/ttyp' string in the `mscreen' binary and
      totally rename the pty devices.
  
!     Finally, edit `/etc/ttys' (and `/etc/ttytype') to tell them about
!     the new pty lines, and run `enable' upon each of the lines.
  
  
  QD4.  Upgraded to 2.3.4 and flow control broke with mscreen(C).
--- 999,1015 ----
      can try editing the `/dev/ttyp' string in the `mscreen' binary and
      totally rename the pty devices.
  
!     An alternative method to relieve the conflict between `mscreen'
!     and TCP/IP is to use an `.mscreenrc' file.  If you create a surplus
!     of TCP/IP ptys, you can steal some of them for `mscreen'.  Just
!     create an `.mscreenrc' and enter the names of the ptys you want
!     `mscreen' to use.  Since the TCP/IP utilities start at the bottom,
!     steal from the top and work down.  The catch?  You have to put an
!     `.mscreenrc' file into the home directory of *every* user who will
!     be using `mscreen'.  Bleych.
! 
!     If necessary, ensure you edit `/etc/ttys' to add the new ptys.
!     Don't forget to `enable' the lines to start a `getty' on them.
  
  
  QD4.  Upgraded to 2.3.4 and flow control broke with mscreen(C).
***************
*** 1594,1597 ****
  representations, nor do we accept any liability for any damage resulting
  from the use or misuse of information or procedures in this document.
  
! [ end of sco-xenix 1.56 ]
--- 1608,1611 ----
  representations, nor do we accept any liability for any damage resulting
  from the use or misuse of information or procedures in this document.
  
! [ end of sco-xenix 1.58 ]