DIRECTIONS for UNPACKING QUICK START This document provides a brief set of instructions for the AdMigration Toolkit; however, the user must still read the complete documentation provided. The user should have the READ ME document and the two following files: AMToolkit-2.2a.shar......................Binaries and PostScript documentation to run Admigration tool set AMToolkit-2.2a.src.shar..................Source code, Makefile and Documentation source Essentially, the user must carry out two steps to enable the AdMigration Toolkit: 1) Create a directory and enter it. 2) Unpack the shar files in the directory. These steps will create all elements required to run the AdMigration tool set. ABSTRACT This suite of tools, in the AdMigration-2.2a Toolkit, expedites migration from Solaris 1.0 to Solaris 2.x. The migration is carried out in two stages, first on the Solaris 1.0 side, and then on the Solaris 2.x side. Before starting and for details, the user should read "Converting from Solaris 1.0 to 2.x using Admigration" and other documentation as you see fit. If the documentation set is incomplete, the user should contact the supplier of the copy of the Toolkit at hand. The binary Toolkit includes a set of "ed-std-1.0-xxx" files. These files represent a virgin 1.0 system, and are templates used in preparing differentials in the 1.0 files that will be reconstituted in the Solaris environment. If these files become lost, incomplete or are not picked up, the Admigration Toolkit will still perform their conversion by employing complete copies of the user's 1.0 files. WARNING: As with all upgrade and migration tool kits, some of the saved data is never used; however, the user should consider that this information is retained for reference and completeness. STEP-BY-STEP The following steps outline installation and use of the Admigration Toolkit (NOTE: Users using the binaries distribution, should skip to Step 4. Otherwise, compile the oldworld souirce under Solaris 1.0 and neworld, moveme and scriptrans under Solaris 2.x.): 1) Unpack the shar's by either executing the file or using /bin/sh. For example: example% AMToolkit-2.2a.shar This will create the necessary directories below your current directory and then populate them.. If you unpack both shars, this process will create the exec,and src, subdirectories, and fill them with about 1.5 MB of files. NOTE: The "uudecode" utility must be part of your system (in your path) to successfully unpack the files. If you don't have it and you're on a Solaris 2.x based system,,you must first pkgadd(1m) the SUNWbnuu package before proceeding., Otherwise it's usr/bin/uudecodeeither locally or on your favorite server. You do this by entering the bourne shell and executing the files: example% sh $ sh AMToolkit-2.2a.shar [much text scrolls by on the screen] $ sh AMToolkit-2.2a.src.shar $ exit example% You will find a "pop-up" software license that appears as you unpack the shar files, and also when you first run the binaries. READ THE LICENSE! It restricts you, so don't accept the license unless you want to abide by it. If you don't want to abide by it, delete the shar files, and send an e-mail message to admigration@fanmail.eng.sun.com confirming that you will not use this software. 2) Print and read all of the documents and man pages located in the DOC directory. NOTE: Frame users may take advantage of the book file to print everything except the manpages. These can be printed from the ps directory in either tree. 3) Create and install the files for oldworld from the source tree. NOTE: If you are using binaries from the distribution, skip to Step 4. When building from source, oldworld must be compiled on a Solaris 1.0 system; neworld, moveme and scriptrans must be compiled on a Solaris 2.0 system. The Makefile tries to do this for you but you must first set the following variables in it so that they reflect your insatllation. For example: SVR4HOST=sunflower # Solaris 2.x based host 4XHOST=alladdin # Solaris 1.x based host SRCHOME=/home/myname/admigration/src # where you put the soruces 4) Execute oldworld as follows: example% oldworld -v where is a return. Users must watch for errors in this pass, and correct as necessary. 4a) If this step proceeds smoothly, the user should re-execute oldworld in the following manner: example% oldworld -ivy [-d ] Users, with no floppy disk, must add -d to the command so that output will go to the specified device. (The default is floppy) 5) Back up all user information that will be required under Solaris 2.x. For example, .chsrc, .profile, and scripts. 6) INSTALL Solaris 2.x using the standard Solaris mechanisms . 7) Create and install the files for neworld from the source tree. (See step 3) NOTE: If the user is using the binaries from the distribution, he should skip to Step 8. This works only if the user has installed the unbundled compiler. 8) Execute neworld in multi-user mode as follows: example% neworld -v Watch for errors, etc. in this pass and make all necessary corrections. 9) If the installation is proceeding smoothly, re-execute neworld as follows: example% neworld -vy [-d ] As in step (4a), users, with no floppy disk, must add -d to the command so that output will go to the specified device. (Remember, the default is floppy) 10) Restore all files from the backup media. 11) For each user now under Solaris 2.x, execute moveme: example% moveme -y USER0 ... USERn 12) Execute scriptran as needed to translate any shell scripts: example% scriptran -y -U USER file0 ... fileN 13) At this point, the installation is complete. Notice: The Admigration tools are the result of joint project of SMCC and Sunsoft. They are provided as a free Solaris migration aid to Sun customers. THESE AIDS ARE NOT A PRODUCT AND ARE NOT SUPPORTED by Sun or its OEMs. We hope they help you, and have done what we can to make sure they do. These tools can be copied and distributed under the terms of the license included in the binary and source versions of the software. The Admigration tools and this documentation are not products; they are not for sale, and no support is available for them from Sun. Source for the software is included so that users can fix, modify, or enhance the tools to fit their unique needs. However, user modifications are "derivative works" and are therefore owned by Sun. Users may redistribute changes to the code or the documentation only if users also send a copy of the changes, or the sources and binaries, to Sun. Send your comments, questions, or suggestions to the following e-mail address: admigration@fanmail.eng.sun.com. This document was specifically prepared for SunSoft customers, and is not standard Sun Microsystems, Inc. documentation. This documentation is intended to provide technical information to SunSoft customers. This information is believed to be correct, but it may contain errors and omissions, and is subject to change without notice. Roadmap to the Documentation: Some of the documentation in the Admigration package is intended for general customer use whilesome should be reserved for technical support personnel.or software developers. This Roadmap provides suggestions as to the expected audience. 1. "Directions for Unpacking" and "Roadmap to the Documentation" - Not for customer use. 2. "Executive Summary Presentation" - Customer use. 3. "Converting from Solaris 1.0 to 2.x" - Customer use. 4. "Background Design Spec" - Not for customer use. 5. "Background Design Presentation" - Not for customer use. 6. Manual Pages - Customer use. What's New The following are the most significant changes that have been made to the Admigration Toolkit since it FCS'd in October. There are, of course, many cosmetic updates: 1. [93/06/29] Added scripts for enabling nisplus 2. [93/06/29] Added scripts for enabling JumpStart or autoinstallation 3. [93/05/13] Added a batch facility and Solaris 2.2 capability 4. [93/05/13] Ensure that any exportable filesystems, restored via use of neworld, are exported at next reboot by automatically enabling /etc/dfs/sharetab.