??? very short topic, no review

 ************* BACK AND FORTH PAGING SUBROUTINE ************

PAGEFLOP

If they want to quit, do so

 If They want to quit subsession, Do SO!

  Decrement LOCAL and GLOBAL Page Counters

FORWARD

  Increment LOCAL and GLOBAL Page Counters

   *************** END PAGEFLOP *********************

  ****** CHAPTER INTERNAL SELECTOR ALGORITHM ******

SELECTOR

   Reset Local Page Counter

SELAGAIN

 CHECK IF ONLY A <CR>

WRONGSEL

YOUR SELECTION IS NOT IN THE 0 - #SELIMIT  RANGE  Please Try Again

P0

Copyright CourseWare Technologies Inc., 1985-88

 Lesson - 9

 MOVING TO A UNIX SYSTEM 

MENU

Moving to UNIX|Topics to Learn|9-0|9,50

   #                  Topic

  ---                -------

   1   -   Moving to a UNIX System from

           a Non-UNIX System

   2   -   Moving Programs between UNIX and

           UNIX Look-Alike Systems

   3   -   Program Portability Problems

   4   -   Program Transferring Tools and Software

   0   -   Return to the Main Menu

P1

Moving to UNIX|Moving from a Non-UNIX System|9-1.1|13,54

     To move from a non-UNIX system to a UNIX system

the requirements include:

      *  a binary UNIX license for your system and

      *  the compilers you intend to use.

     Pitfalls include:

      *  Programs using non-UNIX system calls will 

         not run.

      *  Some programs may need to be modified to 

         call the appropriate UNIX functions.

P2

Moving to UNIX|Moving from a Non-UNIX System|9-1.2|12,54

     Here are some solutions to possible problems:

  * Find a file transferring utility such as kermit.

  * Select a UNIX emulator which uses the current 

    operating system and provides UNIX facilities.

  * Move everything to a UNIX system running in a 

    native mode and translate all programs into C.

  * Move everything to a UNIX system running in a 

    native mode and use the C compiler to recompile.

??? define native mode

P3

Moving to UNIX|Moving Programs between Systems|9-2.1|10,57

     File archiving utilities having a portable format

that permit relatively trouble free data transfer 

between systems include:

                         tar

                         dd

                         cpio

     Most C programs should compile without any problems.

P4

Moving to UNIX|Moving Programs between Systems|9-2.2|6,54

???huh?

     Program modification is required due to inherent 

architecture differences.

     Code transfer, particularly in C is relatively 

trouble free.

P5

Moving to UNIX|Portability Problems|9-3.1|16,54

???hey, this is supposed to be a problems section!

      The assembler, the linker, and the code generator 

need to be changed when porting the C compiler.  The

rest should be trouble-free.

     Porting programs to a UNIX system is easier  

than porting to other systems.

     Most UNIX commands and programs are not machine 

dependent, therefore they are easily ported to other 

systems.

     The number of changes to be made is relatively

small.

P6

Moving to UNIX|Program Transferring Tools|9-4.1|8,56

     For transfers between UNIX or UNIX act-alike systems, 

one should consider the following approaches:

      *  Copy files onto magnetic tape using tar, cpio

         or dd format.

      *  Use uucp, Micnet, or cu to transfer text data.

P7

Moving to UNIX|Program Transferring Tools|9-4.2|7,54

     For transfers between a UNIX and a non-UNIX system, 

consider using:

    *  the kermit general communication utility,

    *  the 3270 bisynchronous communication protocol,

    *  a communications network, or

    *  an intermediary machine.