Adding SunOS Release 4 Support to a Solaris 7 Server
This section explains how to prepare a Solaris 7 system to serve SunOS release 4 diskless client.
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, Converting a SunOS Release 4 System to the Solaris 7 Environment.
Some sites continue to use SunOS release 4 clients systems after a server has been upgraded with Solaris 7 software.
Systems such as Sun-3TM machines, for example, cannot be upgraded with Solaris 2.2 or Solaris 7 software. For those systems and other SunOS release 4 clients on a Solaris 7 network, you can add the SUNWhinst package to the /export partition on the server to establish the multiple OS operation required for SunOS release 4 clients.
The SUNWhinst package includes three programs you run to configure the /export directory on a Solaris 7 server. The three programs are:
-
discover4x - This program analyzes the support that remains for SunOS release 4 clients after the Solaris 7 operating environment has been installed on a server. The program looks at the SunOS release 4 client support and creates the databases that are required for installation of SunOS release 4 diskless clients on the Solaris 7 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 clients with the same architecture as the server that migrated to the Solaris 7 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 system required to support diskless clients that existed before the migration to the Solaris 7 operating environment.
-
convert4x - This program updates the Solaris 7 server with information about all the existing SunOS release 4 clients. This command is used after issuing the discover4x and install4x commands. The updated information enables the existing SunOS release 4 clients to work with the Solaris 7 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 adding and removing packages, see System Administration Guide, Volume I.
Running discover4x
discover4x analyzes the support that remains for SunOS release 4 clients after the server has migrated to the Solaris 7 operating environment.
As superuser, 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 7 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 7 operating environment using one of the three procedures listed in the following section.
-
If the system has a local CD-ROM drive, see "Using a Local CD-ROM Drive"
-
If the system will use a remote CD-ROM drive on a system running the Solaris 7 operating environment, see "Using a Remote CD-ROM Drive (Solaris 7 Software)"
-
If the system will use a remote CD-ROM drive on a system running the SunOS release 4 software, see "Using a Remote CD-ROM Drive (SunOS Release 4 Software)"
Insert the SunOS release 4 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, Volume Management automatically mounts the CD directory on /cdrom/volume1/s0 after you install the CD into the drive.
Using a Remote CD-ROM Drive (Solaris 7 Software)
If install4x is to use a CD-ROM drive on a remote system running the Solaris 7 operating environment, Volume Management automatically mounts the CD directory on /cdrom/volume1/s0. Then type the following command after you install the CD into the drive.
|
# 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 Software)
If install4x is to use a CD-ROM drive on a remote system that is running the SunOS release 4 software, 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. Invoke install4x by typing the following command.
|
# /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 command.
|
# /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
Selected Loaded
[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 module +----------------------+
| Disk Usage: |
or abort without loading any modules | 0K Selected |
| 53634K Free |
[Q] Quit without loading +----------------------+
Type any bracketed letter to select that function.
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 +[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 OpenWin_Users.25936K | [z] Security.............312K [m] C OpenWin_Demo...4288K | [A] OpenWindows_Progr..10200K [n] C OpenWin_Fonts..7840K | Module + = already loaded R = Required C= Common Legend: ** = selected for loading D = Desirable Others opt Select [a-A] or a Quick-Pick Option: +-------------------+ [1] All Req'd Modules [4] All Opt Moduls | Disk Usage: | [2] All Desr'ble Mod [5] All Modules | 0K Selected | [3] All Common Modules | 53634K Free | or [D] (done) to return to the main scrn +-------------------+ |
Packages already loaded are shown on the Module Selection screen with a plus sign (+) 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, the module is selected or deselected). Modules selected to be loaded have asterisks (**) displayed before the selection character. You can reload modules already present by answering Y or y when asked to confirm the apparent redundancy.
The software you must be load in order for a release to operate normally is shown with an R to the right of the selection letter. Software that commonly loaded is shown as with a C, and software it is desirable to load is shown with a D.
The Module Selection screen 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 +-------------------+
| Disk Usage: |
or abort without loading any modules: | 0K Selected |
| 53634K Free |
[Q] Quit without loading +-------------------+
Type any bracketed letter to select that function.
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 7 server with information about all SunOS release 4 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 by 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
Before running convert4x, 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.
As superuser, run convert4x by typing the following command.
|
# /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 convert4x is successful for existing clients, you do not have to add clients again using Solstice Host Manager.
- © 2010, Oracle Corporation and/or its affiliates