Usenet 1994 January

home *** CD-ROM | disk | FTP | other *** search

/ Usenet 1994 January / usenetsourcesnewsgroupsinfomagicjanuary1994.iso / answers / sco / xenix-diff < prev next >

Wrap

Text File | 1993-09-29 | 35KB | 807 lines

Newsgroups: comp.unix.xenix.sco,news.answers Path: senator-bedfellow.mit.edu!bloom-beacon.mit.edu!news.kei.com!sol.ctr.columbia.edu!usc!cs.utexas.edu!chinacat!chip From: chip@chinacat.unicom.com (Chip Rosenthal) Subject: Welcome to comp.unix.xenix.sco [changes from previous version] Organization: Unicom Systems Development, Austin, TX Date: Wed, 29 Sep 1993 04:24:35 GMT Approved: news-answers-request@MIT.Edu Message-ID: <sco-xenix-diff-930928@chinacat.unicom.com> Followup-To: comp.unix.xenix.sco Supersedes: <sco-xenix-diff-930610@chinacat.unicom.com> Lines: 793 Xref: senator-bedfellow.mit.edu comp.unix.xenix.sco:8916 news.answers:12954 Archive-name: sco-xenix-diff News-answers-archive-name: sco/xenix-diff Posting-frequency: monthly Version: 1.47 *** /tmp/faq28442.prev-version Tue Sep 28 23:23:01 1993 --- /tmp/faq28442.curr-version Tue Sep 28 23:22:59 1993 *************** *** 1,4 **** ! @(#) sco-xenix 1.45 93/06/05 22:03:21 --- 1,4 ---- ! @(#) sco-xenix 1.47 93/09/28 23:07:56 *************** *** 44,51 **** to chip@chinacat.unicom.com. These questions and answers were written 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, and ! Paul Warren. Please examine the date near the top of this message. This message is updated frequently, and any version older than 90 days is possibly --- 43,50 ---- to chip@chinacat.unicom.com. These questions and answers were written 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, and Lawrence Kirby. Please examine the date near the top of this message. This message is updated frequently, and any version older than 90 days is possibly *************** *** 75,81 **** QB1. Can't boot. My system used to work. QB2. Configure(ADM) fails when I modify my system name. ! QB3. I upgraded Xenix. Now I get `parity error' panics. QB4. Login fails without prompting for password. QB5. Can I use `gcc' instead of buying the SCO Development System? QB6. Program `foobar' dumps core with a stack overflow. [Xenix 286] --- 74,80 ---- QB1. Can't boot. My system used to work. QB2. Configure(ADM) fails when I modify my system name. ! QB3. The system is crashing with `parity error' panics. QB4. Login fails without prompting for password. QB5. Can I use `gcc' instead of buying the SCO Development System? QB6. Program `foobar' dumps core with a stack overflow. [Xenix 286] *************** *** 84,89 **** --- 83,89 ---- QB9. Where is crypt? QB10. How can email handle `internet' addresses or use a `smart host'? QB11. Where can I find freely available software for Xenix? + QB12. Why don't my arrow keys work in `vi'? ===> Disk and Filesystem Questions: *************** *** 100,106 **** ===> Communications Questions: QD1. How do I add more than 2 COM ports? ! QD2. Where is the `gettydefs' entry for 19200 serial lines? QD3. How can I have more mscreen(C) sessions? QD4. Upgraded to 2.3.4 and flow control broke with mscreen(C). QD5. Terminals act funny, modems drop characters, help!! --- 100,106 ---- ===> Communications Questions: QD1. How do I add more than 2 COM ports? ! QD2. How do I set a 19,200 baud rate? QD3. How can I have more mscreen(C) sessions? QD4. Upgraded to 2.3.4 and flow control broke with mscreen(C). QD5. Terminals act funny, modems drop characters, help!! *************** *** 108,118 **** QD7. How do I increase the number of `clists'? QD8. How do I change the 16550A trigger level? QD9. How do I adjust the `ttyhog' value? ! QD10. Where can I find TCP/IP? NFS? ! QD11. BSD based uucp can't connect to my machine. ! QD12. uucp truncates my system name to seven characters! ! QD13. What is the uucp `windows' patch? ! QD14. uucp gives `alarm' messages, eventually dies. ===> Display and Graphics Questions: --- 108,117 ---- QD7. How do I increase the number of `clists'? QD8. How do I change the 16550A trigger level? QD9. How do I adjust the `ttyhog' value? ! QD10. BSD based uucp can't connect to my machine. ! QD11. uucp truncates my system name to seven characters! ! QD12. What is the uucp `windows' patch? ! QD13. uucp gives `alarm' messages, eventually dies. ===> Display and Graphics Questions: *************** *** 125,130 **** --- 124,137 ---- QE6. CGI graphics fail on a LaserJet in landscape mode. + ===> Networking Questions: + + QF1. What do I need to run TCP/IP? + QF2. What do I need to run NFS? + QF3. How can I run uucp over TCP/IP? + QF4. What does "NOTICE: tcp sum: src C06C6901, sum 0000B004" mean? + + ===> Xenix and MS-DOS Interoperability Questions: QX1. Can Xenix share a hard disk with MS-DOS? *************** *** 146,163 **** QA1. What is the difference between Unix and Xenix? Xenix is Unix -- or at least one flavor of it. In the late 70's, ! Microsoft licensed the Unix sources from AT&T and ported them to a ! number of platforms. In those days AT&T would license the Unix sources ! but not the Unix name, thus each company had to invent their own name. ! Microsoft picked Xenix. Microsoft did not sell Xenix to end users. ! Instead, they licensed the software to OEMs (Intel, Tandy, Altos, SCO, ! etc.) who provided a finished end-user package. Microsoft no longer ! supports Xenix, and in fact never even offered a 286 or 386 version. ! ! Several Unix implementations for the PC architecture have been tried ! with varying levels of success. SCO Xenix for the PC/XT was one. ! Unfortunately, the PC/XT lacked hardware features required for robust ! Unix operations. The PC/AT offered hardware memory protection, and SCO Xenix/286 took advantage of it. SCO Xenix/386 added demand paged virtual memory. These added features made multiuser PCs viable, and SCO Xenix popular. --- 153,172 ---- QA1. What is the difference between Unix and Xenix? Xenix is Unix -- or at least one flavor of it. In the late 70's, ! Microsoft licensed the Unix sources from AT&T and ported them to ! a number of platforms. In those days, AT&T would license the Unix ! software but not the Unix name, thus each company had to invent ! their own name. Microsoft picked Xenix. Microsoft did not sell ! Xenix to end users. Instead, they licensed the software to OEMs ! (Intel, Tandy, Altos, SCO, etc.) who provided a finished end-user ! package. Microsoft no longer supports Xenix, and in fact never ! even offered a 286 or 386 version. ! ! Several Unix implementations for the PC architecture have been ! tried with varying levels of success. SCO Xenix for the PC/XT ! was one. Nearly all of the PC/XT implementations were clunkers, ! because the machine lacked the hardware necessary for robust Unix ! operations. The PC/AT offered hardware memory protection, and SCO Xenix/286 took advantage of it. SCO Xenix/386 added demand paged virtual memory. These added features made multiuser PCs viable, and SCO Xenix popular. *************** *** 166,183 **** Berkeley enhancements, and adds features to obtain conformance to the System V Interface Definition (SVID). Today, the bulk of the code is from System V. Xenix/386 even has capabilities to execute ! Unix programs. However, it differs in many of the SVID `optional' ! areas people tend to expect of a full System V. For example, SCO ! Xenix lacks a real `inittab'. You need to go to a real System V ! Release 3.2, such as SCO Unix, for all these features. QA2. What is the minimum system required to run Xenix? You can build a minimal, single-user Xenix system with an 80386SX ! computer with 2MB to 4MB RAM and 40MB hard disk. For the Xenix ! development system, you'll want at least an 80386DX computer with ! 4MB RAM and 80MB hard disk. Additional resources (more speed, more RAM, more disk) will be required to support additional users, large applications, networking, or X windows. Xenix/286 will run on a PC/AT, but you will quickly become frustrated with its --- 175,192 ---- Berkeley enhancements, and adds features to obtain conformance to the System V Interface Definition (SVID). Today, the bulk of the code is from System V. Xenix/386 even has capabilities to execute ! Unix programs. It differs, however, in many of the SVID `optional' ! areas people tend to expect of a full System V. SCO Xenix lacks ! a real `inittab', for example. You need to go to a real System V, ! such as SCO Unix, for all these features. QA2. What is the minimum system required to run Xenix? You can build a minimal, single-user Xenix system with an 80386SX ! computer, 2MB to 4MB RAM, and 40MB hard disk. A pretty spiffy ! system, suitible for development, would be an 80386DX computer ! with 4MB RAM and 80MB hard disk. Additional resources (more speed, more RAM, more disk) will be required to support additional users, large applications, networking, or X windows. Xenix/286 will run on a PC/AT, but you will quickly become frustrated with its *************** *** 186,204 **** QA3. Should I buy Unix or Xenix? ! If you are running Xenix now, don't throw it away and buy Unix. ! Xenix will be around for some time. However, if you are new to multi-user computing, you should consider Unix System V Release ! 3.2 or Release 4.0. Xenix is a mature product. There will be ! few future enhancements. Unix has more goodies and better ! performance than Xenix. Unix runs Xenix binaries, so it will do ! most anything Xenix can -- and more. Xenix requires less memory ! and disk space. However, hardware prices are declining and Unix ! is now pretty stable, so these are not great advantages. ! On the other hand there are a number of Xenix enthusiasts who wouldn't switch if you gave them a free copy of Unix. They would ! gladly forgo the new features to avoid the bloat of System V. QA4. What are the current Xenix versions? --- 195,218 ---- QA3. Should I buy Unix or Xenix? ! If you are happy running Xenix now, don't rush to throw it away. ! Xenix will be around for some time. If, however, you are new to multi-user computing, you should consider Unix System V Release ! 3.2 or Release 4.X. ! There are a number of reasons why Xenix is slowly fading. It is ! a mature product. There will be few future enhancements. Fewer ! and fewer vendors are supporting it. Nearly every program written ! for Xenix will run under Unix too. Unix offers a lot more goodies ! and better performance than Xenix. ! ! One advantage to Xenix is that it requires less memory and disk ! space. At today's hardware prices that usually isn't a big deal. ! There are certain applications, however, where this is attractive. ! ! Although Unix has a lot more to offer, a number of Xenix enthusiasts wouldn't switch if you gave them a free copy of Unix. They would ! gladly forego the new features to avoid the bloat of System V. QA4. What are the current Xenix versions? *************** *** 227,236 **** QA5. Where can I get Xenix fixes? ! SCO provides Support Level Supplements (SLS) at no charge. They ! may be downloaded by anonymous uucp from SCO's `sosco' machine. ! To retrieve a shopping list of available SLSs, add one of the ! following to your `/usr/lib/uucp/Systems' file: # Telebit (PEP) modem sosco Any ACU 19200 14084291786u gin:-BREAK-gin:-BREAK-gin: uusls --- 241,256 ---- QA5. Where can I get Xenix fixes? ! SCO provides Support Level Supplements (SLS) at no charge. There ! are several places that make them available through anonymous uucp ! and anonymous ftp. ! ! Internet users may retrieve SLSs by anonymous ftp from `ftp.sco.com' ! (see /SLS/info) and `ftp.uu.net' (see /vendor/sco/SLS/info). ! ! SLSs may be downloaded with anonymous uucp from SCO's `sosco' ! machine. To retrieve a shopping list of available SLSs, add one ! of the following to your `/usr/lib/uucp/Systems' file: # Telebit (PEP) modem sosco Any ACU 19200 14084291786u gin:-BREAK-gin:-BREAK-gin: uusls *************** *** 388,408 **** This bug has been fixed in 2.3.4. ! QB3. I upgraded Xenix. Now I get `parity error' panics. ! Starting with Xenix 2.3.3, memory parity errors are detected by ! the kernel. In previous versions, parity errors would cause the ! system to go silently flaky, but continue running. Now, when a ! parity error occurs, the machine will panic saying: PANIC: memory failure - parity error ! If you get this error after installing an update, Xenix didn't ! break your machine -- it's been broken all along. The most likely ! cause of this error truly is memory problems. Run a good memory ! diagnostic overnight to try to locate the problem. Keep the cover ! on the computer while running diagnostics; heat tends to push a ! marginal memory chip into failure. This problem can also be caused by a marginal power supply. Xenix boxes often have more power hungry peripherals than your run of --- 408,434 ---- This bug has been fixed in 2.3.4. ! QB3. The system is crashing with `parity error' panics. ! Everybody knows there are eight bits to a byte. Why, then, do ! PCs use 9-bit wide memory? That last bit is a parity check bit. ! It lets the system detect when data get corrupted while sitting ! in memory or in transit to the CPU. ! ! Prior to Xenix 2.3.3, parity errors were silently ignored. In ! these releases the system would continue to run -- for a while ! anyway. These days, if a parity error is detected the system ! will panic immediately and say: PANIC: memory failure - parity error ! Like the message says, this is almost always caused by memory ! problems. If it happens, run a good memory diagnostic overnight ! to try to locate the problem. Keep the cover on the computer ! while running diagnostics; heat tends to push a marginal memory ! chip into failure. Similarly, running the system with the cover ! off might make the problem go away. If it does, possible causes ! are marginal chips or bad ventilation. This problem can also be caused by a marginal power supply. Xenix boxes often have more power hungry peripherals than your run of *************** *** 428,434 **** Yes, but the task is bigger than you think. A compiler alone doesn't do any good if you lack header files, libraries, linker, etc. Don't forget about make, yacc, lex, etc. Fortunately, the ! repetoire of GNU software has grown to the point where you can fill in all these pieces. Many folks, particularly Steve Bleazard and Ronald Khoo have done a lot of work getting `gcc' and the GNU utilities running on Xenix. So, with anonymous FTP access and a --- 454,460 ---- Yes, but the task is bigger than you think. A compiler alone doesn't do any good if you lack header files, libraries, linker, etc. Don't forget about make, yacc, lex, etc. Fortunately, the ! repertoire of GNU software has grown to the point where you can fill in all these pieces. Many folks, particularly Steve Bleazard and Ronald Khoo have done a lot of work getting `gcc' and the GNU utilities running on Xenix. So, with anonymous FTP access and a *************** *** 443,450 **** Next, an alpha test version of a `libc' for Xenix is available from kate.ibmpcug.co.uk (in /ftp/pub/xenix/libc) and unix.secs.oakland.edu (in /pub/xenix); files XLIBC.README.Z and xlibc.shar.Z. It is ! based on the Berkley Networking Release 2 tape. The library is ! distibuted as a modification set and assumes that the aforementioned gcc distribution has already been installed. --- 469,476 ---- Next, an alpha test version of a `libc' for Xenix is available from kate.ibmpcug.co.uk (in /ftp/pub/xenix/libc) and unix.secs.oakland.edu (in /pub/xenix); files XLIBC.README.Z and xlibc.shar.Z. It is ! based on the Berkeley Networking Release 2 tape. The library is ! distributed as a modification set and assumes that the aforementioned gcc distribution has already been installed. *************** *** 484,489 **** --- 510,517 ---- typesetters. Chris Lewis's `psroff' allows old troff to work with various devices, including Postscript and LaserJet printers. Version 3.0 is available from the comp.sources.unix archives. + Another alternative is Rick Richardson's `jetroff', available in + the comp.sources.misc archives. For production work, consider purchasing a device independent troff. Some of the suppliers of `ditroff' are Elan, Image Network, *************** *** 490,499 **** Leverage, and SoftQuad. Another alternative is the `groff' package by the Free Software ! Foundation. You can find it in any of the FSF archives -- but you ! will need `g++' to compile it. You will still need a backend program ! to use a LaserJet with `groff'. Some possibilities are `psroff' ! and `dvi2xx' on ftp.wu-wien.ac.at. QB9. Where is crypt? --- 518,527 ---- Leverage, and SoftQuad. Another alternative is the `groff' package by the Free Software ! Foundation. You can find it in any of the FSF archives -- but ! you will need `g++' to compile it. You will still need a backend ! program to use a LaserJet with `groff'. Some possibilities are ! `psroff', `jetroff', and `dvi2xx' on ftp.wu-wien.ac.at. QB9. Where is crypt? *************** *** 509,515 **** that supports encryption but not decryption, and it does not include the crypt(C) command. A number of non-domestic archive sites, for example the European GNU mirror sites, carry `crypt' ! replacements which were developed outside the US to avoid this export silliness. --- 537,543 ---- that supports encryption but not decryption, and it does not include the crypt(C) command. A number of non-domestic archive sites, for example the European GNU mirror sites, carry `crypt' ! replacements that were developed outside the US to avoid this export silliness. *************** *** 594,599 **** --- 622,637 ---- Unix oriented but some of it might work with Xenix + QB12. Why don't my arrow keys work in `vi'? + + For versions 2.3.3 and prior, probably because your `termcap' + entry does not have then defined properly. For version 2.3.4, + it's because `vi' is broke. If you have an older version of Xenix + laying around, you might consider grabbing `vi' off of it instead. + Note, however, that 2.3.4 `vi' gets its terminal information from + the `terminfo' database, while prior versions use `termcap'. + + ****************************************************************************** ********************** Disk and Filesystem Questions *********************** ****************************************************************************** *************** *** 611,628 **** QC2. Why won't Xenix recognize my SCSI disk? ! Not all versions of Xenix support SCSI and those that do won't run ! all SCSI adapters. First, verify your N1 floppy says `Type: 386GT' ! and not `Type: 386AT'. The AT version of Xenix (now obsolete) does ! not include any SCSI support. ! ! The GT version supports a limited number of SCSI host adapters. The ! Adaptec AHA-154x is supported. We've also used compatibles such as ! the Bustek BT-542B. 2.3.4 also supports WD1009V-SE1/2 and WD-7000-FASST2. ! If you've got something different, you probably need to get a driver ! from the board vendor. The `SCO Hardware Compatibility Guide' (contact ! SCO sales for one) should be consulted whenever you have any hardware ! compatibility questions. Some typical installation mistakes are: --- 649,666 ---- QC2. Why won't Xenix recognize my SCSI disk? ! Not all versions of Xenix support SCSI. Those that do only support ! certain SCSI adapters. First, verify your N1 floppy says `Type: ! 386GT' and not `Type: 386AT'. The AT version of Xenix (now ! obsolete) does not include any SCSI support. ! ! The GT version supports a limited number of SCSI host adapters. ! The Adaptec AHA-154x is supported. We've also used compatibles ! such as the Buslogic BT-542B. 2.3.4 added support for the ! WD-7000-FASST2. If you've got something different, you have to ! get a driver from the board vendor. The `SCO Hardware Compatibility ! Guide' (contact SCO sales for one) should be consulted whenever ! you have any hardware compatibility questions. Some typical installation mistakes are: *************** *** 639,644 **** --- 677,688 ---- terminators. The terminators must be removed from everything else on the SCSI chain. + Note that some SCSI disk controllers mimic the standard ST-506 + interface. No special support is required for them; Xenix boots + thinking you've got a plain old disk controller. See the instructions + that came with your controller for details on cabling, strapping, + terminating, etc. + Note: If you are using Xenix 386GT 2.3.1-2.3.3 you should install xnx252b for ISA or xnx150 for MCA. This is an improved SCSI driver that yields a significant performance improvement. *************** *** 706,716 **** Xenix maintains a list of available disk blocks. As files are deleted, the released blocks are appended to this free list. ! Ideally, one would allocate adjacent blocks for new files. However, ! blocks are added to and removed from the free list without regard ! for location. Eventually, new files will be created with their ! data blocks scattered all around the disk. This fragmentation is ! undesirable because it slows down disk accesses. To slow down the tendency towards fragmentation, periodically reorder the blocks in the free list. To do this, dismount the --- 750,762 ---- Xenix maintains a list of available disk blocks. As files are deleted, the released blocks are appended to this free list. ! Ideally, adjacent disk blocks would be used to create and grow ! files so that all the parts of the file sit together on the disk. ! Disk blocks, unfortunately, are allocated to files in the order ! they appear on the free list and without regard for location. ! Eventually, new files will be created with their data blocks ! scattered all around the disk. This fragmentation is undesirable ! because it slows down disk accesses. To slow down the tendency towards fragmentation, periodically reorder the blocks in the free list. To do this, dismount the *************** *** 766,777 **** QC7. Can I put a CD-ROM drive on my Xenix system? ! No. The difficulty is not making Xenix talk to a CD-ROM drive. ! That's easy. The problem is that a CD-ROM needs to be mounted so ! you can access the files on it, so Xenix would have to be extended ! with support for ISO-9660/High Sierra file systems. Now, that's ! the tough part. Refer to the FAQ on why Xenix doesn't have NFS ! for additional information on why that's so difficult. ****************************************************************************** --- 812,822 ---- QC7. Can I put a CD-ROM drive on my Xenix system? ! No. Sure, it would be easy for somebody to write a device driver ! to talk to a CD-ROM drive. But that's not the whole story. If ! you want to use a CD-ROM, you need to be able to mount it as an ! ISO-9660/High Sierra filesystem. That's not so easy. See the ! FAQ on NFS for additional info. ****************************************************************************** *************** *** 843,859 **** Reboot your system, and the new serial port should be there. ! QD2. Where is the `gettydefs' entry for 19200 serial lines? For historical reasons, terminal speeds of 19200 and 38400 are ! called `EXTA' and `EXTB', not `B19200' and `B38400'. Entries `n' ! and `o' in the `/etc/gettydefs' file are for 19200 and 38400, ! respectively. Once logged in you can change the line speed with ! the `stty' command: ! ! stty 9600 # set to 9600 bps (bits per second) ! stty exta # set to 19200 bps ! stty extb # set to 39400 bps A smart serial card is recommended for these two highest speeds. --- 888,905 ---- Reboot your system, and the new serial port should be there. ! QD2. How do I set a 19,200 baud rate? For historical reasons, terminal speeds of 19200 and 38400 are ! called `EXTA' and `EXTB'. So, in the `/etc/gettydefs' file you ! need to say `EXTA' and `EXTB', not 19200 and 38400. These speeds ! are already available there as entries `n' and `o', respectively. ! ! Similarly, with the `stty' command you need to say: ! ! stty 9600 # set to 9600 ! stty exta # set to 19200 ! stty extb # set to 39400 A smart serial card is recommended for these two highest speeds. *************** *** 915,927 **** QD4. Upgraded to 2.3.4 and flow control broke with mscreen(C). ! The 2.3.4 version of mscreen(C) was changed to run the tty line totally ! raw. This is required so that the ^S and ^Q keys are passed onto ! programs that need them, such as `emacs' and Foxbase. An unfortunate ! side effect of handling flow control on the pty side rather than the ! tty side is that response to flow control is a lot more sluggish. Now, ! when you hit ^S you might get another screenful of data before the ! display actually freezes. If you never run any applications that require full 8-bit transparency, one way to make flow control more responsive is to rename `mscreen' --- 961,974 ---- QD4. Upgraded to 2.3.4 and flow control broke with mscreen(C). ! The 2.3.4 version of mscreen(C) was changed to run the tty line ! totally raw. This is required so that the ^S and ^Q keys are ! passed on to programs that need them, such as `emacs' and Foxbase. ! An unfortunate side effect of handling flow control on the other ! side of the session rather than directly by the tty is that response ! to flow control is a lot more sluggish. Now, when you hit ^S you ! might get another screenful of data before the display actually ! freezes. If you never run any applications that require full 8-bit transparency, one way to make flow control more responsive is to rename `mscreen' *************** *** 1072,1099 **** * $q ! QD10. Where can I find TCP/IP? NFS? ! ! TCP/IP = many places. NFS = forget it. ! ! Years ago, before SCO released a TCP/IP for Xenix, several vendors ! had products. These include Novell (the old `Excelan Lan Workplace' ! package), and Network Research Corp. Those packages are getting ! pretty old and crufty. We recommend the SCO package. You need ! to purchase and install either the SCO Streams Runtime or SCO ! Streams System before loading TCP/IP. ! ! Nobody makes an NFS for Xenix, and don't hold your breath waiting ! for one. Newer versions of Unix provide either a `vnode' (BSD ! Unix) or `filesystem switch' (System V 3.2 and beyond) mechanism, ! that supports new filesystem types. With Xenix, the filesystem ! support must be coded right into the kernel. The task of merging ! NFS code with VP/ix hacks, Xenix-net hacks, etc. is more than can ! be justified. - - QD11. BSD based uucp can't connect to my machine. - BSD based uucp sends even parity. Xenix uucp expects no parity. Add: --- 1119,1126 ---- * $q ! QD10. BSD based uucp can't connect to my machine. BSD based uucp sends even parity. Xenix uucp expects no parity. Add: *************** *** 1105,1111 **** xnxbox Any uucp 19200 5553333 "" P_ZERO "" \r in:--in: nuucp ! QD12. uucp truncates my system name to seven characters! This misfeature was introduced in the xnx155b supplement. The story we hear is that SCO broke their `uucp' to cater to systems --- 1132,1138 ---- xnxbox Any uucp 19200 5553333 "" P_ZERO "" \r in:--in: nuucp ! QD11. uucp truncates my system name to seven characters! This misfeature was introduced in the xnx155b supplement. The story we hear is that SCO broke their `uucp' to cater to systems *************** *** 1130,1139 **** untruncated name. ! QD13. What is the uucp `windows' patch? uucp transmits data in packets, usually 64 bytes apiece. An ! acknowledgement is required for every packet sent -- but not immediately. A window of unacknowledged packets is allowed. The default window size is three, that means `uucico' won't stop sending unless it falls more than three packets behind. A three --- 1157,1166 ---- untruncated name. ! QD12. What is the uucp `windows' patch? uucp transmits data in packets, usually 64 bytes apiece. An ! acknowledgment is required for every packet sent -- but not immediately. A window of unacknowledged packets is allowed. The default window size is three, that means `uucico' won't stop sending unless it falls more than three packets behind. A three *************** *** 1160,1166 **** the protocol startup. ! QD14. uucp gives `alarm' messages, eventually dies. If you run uucp in debugging mode (`uutry -x9') and see it get stuck like: --- 1187,1193 ---- the protocol startup. ! QD13. uucp gives `alarm' messages, eventually dies. If you run uucp in debugging mode (`uutry -x9') and see it get stuck like: *************** *** 1286,1291 **** --- 1313,1392 ---- ****************************************************************************** + *************************** Networking Questions *************************** + ****************************************************************************** + + + QF1. What do I need to run TCP/IP? + + The SCO TCP/IP Run-Time includes *almost* everything you need to + connect a Xenix system to a TCP/IP network. You get the drivers + for several popular network interface cards (NICs), the protocol + stacks, and most of the familiar programs like `telnet' and `rcp'. + We say `almost' because the TCP/IP package requires Streams, and + that's an extra-cost option. You need to buy and install the + Streams Run-Time before you can load TCP/IP. Furthermore, if you + want to develop or compile network programs, you will need the + TCP/IP Development System too. + + + QF2. What do I need to run NFS? + + Unix. :-) + + Nobody offers an NFS for Xenix, and don't hold your breath waiting + for one. It is very difficult adding new filesystem types to + Xenix. The `FS' in NFS does stand for `File System' after all. + + Newer versions of Unix provide mechanisms that allow new filesystem + types to be added easily (the `vnode' mechanism in BSD Unix and + the `filesystem switch' in System V 3.2 and beyond). With Xenix, + the filesystem support must be coded right into the kernel. The + task of merging NFS code with VP/ix hacks, Xenix-net hacks, etc. + is more than can be justified. And because it requires kernel + source, it is unlikely a third party would do this. + + + QF3. How can I run uucp over TCP/IP? + + The Xenix `uucico' doesn't know about networking, and the Xenix + TCP/IP package doesn't do anything to solve that problem. Chip + Rosenthal <chip@chinacat.unicom.com> has published a program called + `uucpm' that works around this problem to allow an SCO Xenix system + perform uucp transfers across the network. Contact him if you + need a copy. + + + QF4. What does "NOTICE: tcp sum: src C06C6901, sum 0000B004" mean? + + That a bad TCP segment was received. One possible reason for this + is a buffer overrun caused by a slow system, a lousy network card, + or a heavy network load. Most TCP/IP implementations silently + detect these errors and ask the remote system to re-transmit. + SCO's TCP/IP decides to whine to the console as well. + + You can tell what the other system is by getting out your hex + calculator (c.f. the bc(C) command) and plugging in the `src' + address. In the above example, 0xC0=192, 0x6C=108, 0x69=105, and + 0x01=1. So the sending machine was 192.108.105.1. + + If you get these messages on occasion or only under heavy network + load, don't worry too much. If they are frequent then consider a + faster network card with more buffering, a faster computer, or + go looking for cabling problems. + + If you get tired of seeing these messages, you can shut them off: + + cp /xenix /xenix.save # make a backup! + adb -w /xenix # use "/etc/_fst" if no "adb" + * tcpprintfs/d + _tcpprintfs: 1 # currently "1" -> enabled + * tcpprintfs/w 0 # set to "0" -> disabled + _tcpprintfs: 0x1= 0x0 + * $q + + + ****************************************************************************** *************** Xenix and MS-DOS Interoperability Questions **************** ****************************************************************************** *************** *** 1450,1453 **** 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.45 ] --- 1551,1554 ---- 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.47 ]