Adding SunOS Release 4.x Support to a Solaris 2.4 Server

This section explains how to prepare a Solaris 2.4 server so it can serve SunOS release 4.x diskless and dataless clients.

---

Note - Ensure that all system data has been restored before you use the commands in this procedure. The /export file system is particularly important because it contains client information. See Chapter 3, "Installation and Configuration Changes."

---

Some sites will need to continue using SunOS release 4.x clients after the server has been upgraded to Solaris 2.4 software. For instance, Sun 3 systems cannot run Solaris 2.2 or later and must continue to use SunOS release 4.x.

When a SunOS release 4.x /export partition is set up on a server running Solaris 2.4 software, it is referred to as multiple OS operation. Multiple OS operation enables the server to continue serving SunOS release 4.x clients while it runs the Solaris 2.4 operating environment.

The multiple OS operation package is called SUNWhinst and includes three programs, which you will need to run to set up a SunOS release 4.x /export directory on a Solaris 2.4 server. The three programs are:

• discover4x - This program analyzes the support that remains for SunOS release 4.x clients after the server has migrated to the Solaris 2.4 operating environment. The program looks at the SunOS release 4.x client support and creates the databases that are required for installation of SunOS release 4.x diskless/dataless clients on the Solaris 2.4 server. If client support for a given architecture is missing, discover4x attempts to notify users that they will have to re-install this support using install4x. If there are SunOS release 4.x clients with the same architecture as the server that migrated to the Solaris 2.4 operating environment, you must re-install that architecture using the install4x command.
• install4x - This program is used to install the components of a SunOS release 4.x system required to support diskless/dataless clients that existed before the migration to the Solaris 2.4 operating environment.
• convert4x - This program updates the Solaris 2.4 server with information about all the existing SunOS release 4.x clients. This command is used after issuing the discover4x and install4x commands. The updated information enables the existing SunOS release 4.x clients to work with the Solaris 2.4 server.

Before beginning any of these installation procedures, ensure that the SUNWhinst package is properly loaded. Use the pkginfo(1) command to generate a list of installed packages and then check the list to ensure that all necessary packages were installed, including the SUNWhinst package.

For details on loading packages, see the Software and AnswerBook Packages Administration Guide section on adding and removing packages.

Running discover4x

discover4x analyzes the support that remains for SunOS release 4.x clients after the server has migrated to the Solaris 2.4 operating environment.

As superuser (root), type the following.

# discover4x

The discover4x program runs from 1 - 60 seconds, depending on the amount of software examined.

discover4x may report messages such as the following.

Setting up proto root for sun4c arch Updating server databases to include sun4c sunos 4.1.2 support Support for sun4c clients must be added using install4x, if \ sun4c clients are served by this machine.

If your site has completed a custom Solaris 2.4 installation that changed the location of the /export directory, discover4x examines that directory if you invoke it with the directory name as a single argument. For instance, if the /export software is stored in /clients directory, use the following command.

# discover4x /clients

Setting Up the CD-ROM Drive for install4x

Run the install4x program on a server with the Solaris 2.4 operating environment using one of the three procedures listed in the following section.

• "Using a Local CD-ROM Drive" if the system has a local CD-ROM drive
• "Using a Remote CD-ROM Drive (Solaris 2.4)" if the system will use a remote CD-ROM drive on a system running the Solaris 2.4 operating environment
• "Using a Remote CD-ROM Drive (SunOS release 4.x)" if the system will use a remote CD-ROM drive on a system running SunOS release 4.x

Insert the SunOS release 4.x CD into the CD-ROM drive before you proceed.

Using a Local CD-ROM Drive

If you are running install4x on a system with a local CD-ROM drive, after you install the CD into the drive, Volume Management automatically mounts the CD directory on /cdrom/volume1/s0.

Using a Remote CD-ROM Drive (Solaris 2.4)

If install4x is to use a CD-ROM drive on a remote system running the Solaris 2.4 operating environment, after you install the CD into the drive, Volume Management automatically mounts the CD directory on /cdrom/volume1/s0. Then execute the following command.

# share -F nfs -o ro /cdrom/volume1/s0

If you are not sharing other NFS systems at boot time, you need to invoke the mountd(1M) and nfsd(1M) daemons.

Type the following commands on the local system.

# mkdir /cdrom # mount -F nfs -o ro cd-host:/cdrom/volume1/s0 /cdrom

Using a Remote CD-ROM Drive (SunOS Release 4.x)

If install4x is to use a CD-ROM drive on a remote system that is running SunOS release 4.x, type the following as superuser on the remote system.

# mkdir /cdrom # mount -t hsfs -r /dev/sr0 /cdrom

Once you have typed the previous commands, edit the /etc/exports and insert the following line.

/cdrom -ro

Then type the following command on the remote system.

# exportfs /cdrom

Type the following commands on the local system.

# mkdir /cdrom # mount -F nfs -o ro cd-host:/cdrom /cdrom

Running install4x

After you use one of the previous procedures, the CD is mounted on /cdrom. Now invoke install4x by typing the following.

# /usr/sbin/install4x -m /cdrom/volume1/s0 -e /export

If the -m option is not specified, the following prompt is displayed.

Enter name of directory where the 4.1* cd is mounted [/cdrom]:

If the -e option is not specified, the following prompt is displayed.

Enter name of export directory [/export]:

As before, if your site has customized the location of the /export directory, you can direct install4x to load software to a different directory by specifying additional arguments as in the following.

# /usr/sbin/install4x -m /cdrom -e /clients

Choosing Software to Load

install4x displays the Install Main Menu shown here.

*** 4.1* Install Main Menu *** Choose an Architecture (then select modules to load): Modules Loaded Selected [a] sun4.sun4c.sunos.4.1.2 8 0 [b] sun4.sun4.sunos.4.1.2 8 0 [c] sun4.sun4m.sunos.4.1.2 7 0 or begin the loading process for all selected modules: [L] Load selected modules or abort without loading any modules: [Q] Quit without loading +-------------------+ | Disk Usage: | Type any bracketed letter to select that function. | 0K Selected | | 53634K Free | Type ? for help. +-------------------+

The Install Main Menu screen presents several options. The first set (labeled here as a, b, and c) is used to specify the architecture for which software is to be loaded. Other options enable the user to direct software loading to begin (L), quit the program (Q), or ask for help (?).

After you choose each appropriate architecture, the program displays the Module Selection.

Select sun4.sun4c.sunos.4.1.2 modules: +[a] R proto root................240K | [o] User_Diag................6352K +[b] R usr.....................26240K | [p] Manual...................7456K +[c] R Kvm......................4832K | +[q] D TLI........................48K +[d] R Install...................936K | [r] D RFS.......................912K [e] D Networking...............1040K | [s] D Debugging................2928K [f] D System_V.................4008K | [t] SunView_Programmers......1840K [g] D Sys......................5288K | [u] Shlib_Custom.............1376K [h] C SunView_Users............2664K | [v] Graphics.................1784K [i] SunView_Demo..............512K | +[w] uucp......................608K +[j] Text......................712K | +[x] Games....................3136K [k] Demo.....................4264K | [y] Versatec.................5960K [l] C OpenWindows_Users.......25936K | [z] Security..................312K [m] C OpenWindows_Demo.........4288K | [A] OpenWindows_Programmers.10200K [n] C OpenWindows_Fonts........7840K | Module + = already loaded R = Required C= Common Legend: ** = selected for loading D = Desirable Others are optional Select [a-A] or a Quick-Pick Option: +-------------------+ [1] All Required Modules [4] All Optional Modules | Disk Usage: | [2] All Desirable Modules [5] All Modules | 0K Selected | [3] All Common Modules | 53634K Free | or [D] (done) to return to the main screen +-------------------+

Packages already loaded are shown on the Module Selection screen with a + before the selection letter (that is, in the previous screen the packages associated with letters a, b, c, d, j, q, w, and x are already loaded). Note that loading packages for one architecture may cause those packages to show as being loaded for other architectures since many packages are shared.

Select modules to load by typing the associated character that is shown in brackets. Pressing the key associated with a module toggles the selection status (that is, will select or deselect the module, depending on its previous status). Modules selected to be loaded have ** displayed before the selection character. You can reload modules already present by answering Y or y when asked to confirm the apparent redundancy.

SunSoft has determined which software must be loaded for a release to operate normally (shown with R to the right of the selection letter), which software is commonly loaded (shown as C), and which software should be loaded (shown as D).

Additionally, the Module Selection screen readily enables you to pick groups of modules to be loaded. When you enter a 1, it marks all required modules for loading. When you enter a 2, it marks all recommended modules. When you enter a 3, it marks all commonly loaded modules. When you enter a 4, it marks all optional modules. When you enter a 5, it marks all modules shown on the Module Selection screen.

Return to the Install Main Menu by typing D.

*** 4.1* Install Main Menu *** Choose an Architecture (then select modules to load): Modules Loaded Selected [a] sun4.sun4c.sunos.4.1.2 8 0 [b] sun4.sun4.sunos.4.1.2 8 0 [c] sun4.sun4m.sunos.4.1.2 7 0 or begin the loading process for all selected modules: [L] Load selected modules or abort without loading any modules: [Q] Quit without loading +-------------------+ | Disk Usage: | Type any bracketed letter to select that function. | 0K Selected | | 53634K Free | Type ? for help. +-------------------+

By typing L on the Install Main Menu, you can load all selected modules. Output similar to the following is displayed.

Installing module 'proto root' [size: 248K] in directory /export/exec/proto.root.sunos.4.1.2 ... Updating server databases ... Press any key to continue:

Running convert4x

convert4x updates the Solaris 2.4 server with information about all SunOS release 4.x clients. The following files and directories are updated when you run convert4x:

• /tftpboot - Directory containing network bootable images
• /etc/dfs/dfstab - File containing file systems exported via NFS
• /etc/inet.conf - File containing list of servers that inetd(1M) invokes when it receives an Internet request
• /etc/bootparams - File containing per-client boot specifications
• /etc/hosts - File containing IP-to-host name mapping

The following steps detail how to run convert4x:

1. Make certain that the Ethernet addresses are entered in the /etc/ethers file for the clients you are converting. This is necessary because convert4x invokes the rpc.rarpd(1m) daemon.

2. Run convert4x by typing the following.

# /usr/sbin/convert4x

Optionally, you can specify a single fully qualified path to the location to an alternate client hierarchy. By default, convert4x looks in /export.

As convert4x runs, it displays information on the screen about the actions taken by the script. It warns you if there are any discrepancies in client information. If there is insufficient information for a given client, convert4x reports the error and exits.

If the convert4x is successful for existing clients, you do not have to re-add them using Host Manager. Use the following section to add new SunOS release 4.x clients.

Using Host Manager to Add SunOS Release 4.x Diskless/Dataless Clients

Host Manager makes it relatively simple to install clients as long as you have the information you need before you start. Table 10-1 lists this information.

Table 10-1

Client Type	The client's configuration type (standalone, diskless, or dataless)
Host Name	The client's host name
IP Address	The client's IP address
Ethernet Address	The client's Ethernet address
Timezone Region	The major geographic time zone region
Timezone	The local time zone
File Server	The client's file server
Media Server	A system from which to access software remotely
OS Release	The client's architecture and operating system version
Root/Swap Paths	Path names for the client's root file system and swap area
Swap Size	The swap size (in megabytes) for a diskless client
Terminal Type	For SunOS 4.1.x systems only: Provides a field to specify the terminal type for a diskless client

If you are setting up a Solaris 2.4 server for SunOS release 4.x clients, run the programs in the SUNWhinst package before you add clients with Host Manager.

When you display Host Manager from the Administration Tool, choose a file server and select the proper SunOS release 4.x version from the OS Release pull-down menu in the Add Host pop-up window.