This chapter tells you how to use the
setld
command to perform
the following tasks:
Display an inventory of software subsets or files within a software subset
Install or remove software subsets after an update or full installation
For more information about the
setld
command, see the
setld(8)
reference
page.
setld
[-D root-path]
-c subset-id message
setld
[-D root-path]
-d subset-id
[
subset-id...
]
setld
[-D root-path]
-i
[subset-id [ subset-id... ] ]
setld
[-D root-path]
-l location
[subset-id [ subset-id... ] ]
setld
[-D root-path]
-v subset-id
[
subset-id...
]
Table 10-1
provides a brief description of the options
for the
setld
command:
| Option | Description |
-D |
In conjunction with any other option,
specifies an alternative root directory.
For example:
# setld -D /usr/doctools -i |
|
The directory specified must be the root directory of an entire system hierarchy. Do not attempt to use this option to place software in a directory that is not a system root. |
-l |
Loads the software kits that are in the
specified location; if software subsets are specified, only the named software subsets
are installed.
For example:
# setld -l /mnt/ALPHA/BASE DNABASE100 |
-c |
Runs the configuration phase of the named
software subset's subset control program (SCP).
Refer to the document supplied by
your software vendor for the command syntax.
For example:
# setld -c DNABASE100 INSTALL |
-i |
Displays a list of software subsets and
their installation status.
If a software subset is named, displays a list of that
software subset's contents.
For example:
# setld -i OSFMANOS440 |
-v |
Runs the named software subset's Installation
Verification Procedure (IVP).
For example:
# setld -v OSFMANOS440To verify
the files of a specific subset, use the
fverify
command.
The
fverify
command reports missing files and inconsistencies in file size,
checksum, user ID, group ID, permissions, and file type.
Refer to the
fverify(8)
reference page for more information. |
-d |
Deletes the named software subset or software
subsets.
For example:
# setld -d OSFMANOS440 OSFMANOP440 |
To list all the options available for the
setld
command,
use the
-h
option:
#setld -h
You can use the
setld
command to display an inventory of
the software subsets recognized by your system, showing the status (installed or not
installed) of each software subset.
To display a software subset inventory, use the
setld
-i
command with the following syntax:
/usr/sbin/setld
[-D root_path]
-i
[subset-id subset-id...]
The following command shows the status of the software subsets:
#/usr/sbin/setld -iSubset Status Description ------ ------ ----------- OSFACCT440 System Accounting Utilities (System Administration) OSFAFM440 Adobe Font Metric Files (Printing Environment) OSFBASE440 installed Base System (- Required -) OSFBIN440 installed Standard Kernel Objects (Kernel Build Environment)
.
.
.
If you use the
-i
option to specify a software subset,
the
setld
command displays a list of the files in the specified
software subset.
This is useful if you want to determine which software subset you
need to reload or delete if a particular file is damaged or deleted.
The following command displays the files in the OSFCLINET440 software subset:
#/usr/sbin/setld -i OSFCLINET440./etc/.new..acucap ./etc/.new..hosts
.
.
.
./usr/sbin/bindsetup ./usr/sbin/fddi_config
Use the
-D
option to specify a root directory other
than the system root.
This section describes how to install software subsets from a specified location.
Note
Use the
dfcommand to display statistics on free disk space before loading software subsets with thesetldcommand. See thedf(1) reference page for more information.
To install a software subset, log in as
root, and
use the
setld
-l
command with the following
syntax:
/usr/sbin/setld
[-D root_path]
-l location
[subset-id [ subset-id... ] ]
The location variable specifies the location of the software subset that you want to install. You can specify the following location variables:
hostname:
specifies
the name of the remote host (RIS server).
directory specifies the disk distribution directory.
The subset-id variable specifies the name of the software subset. If you do not specify a subset-id variable, a list of software subsets is displayed, which lets you choose the software subsets to install. If you specify one or more subset-id variables, only those software subsets are installed.
To install software subsets from CD-ROM, use the following procedure:
Note
The distribution path given in the following examples is for the base operating system CD-ROM. For other distribution kits, refer to the document supplied by your software vendor.
Place your CD-ROM optical disk in its caddy and insert the CD-ROM into the disk drive.
As superuser or
root, create a directory to be
the mount point for the CD-ROM.
This example creates a directory called
/mnt:
#mkdir /mnt
Mount the CD-ROM on
/mnt.
Refer to
Appendix B
if you do not know how to determine the location of the
CD-ROM device.
The following example assumes the CD-ROM device is located on
the
c
partition of the
rz4
disk:
#mount -r /dev/rz4c /mnt
After mounting
the CD-ROM, you can change to the
/mnt
( cd /mnt ) directory to view the directories located on the CD-ROM.
To install a base software subset, enter a command similar to the following:
#setld -l /mnt/ALPHA/BASE
Note
If you are using a RIS server as the source of the software, make sure your system is registered as a client of the RIS server, then enter a command similar to the following:
#setld -lris_server_name:
The
setld
command displays a numbered list of software
subset descriptions and prompts you to enter the number of the software subsets you
want to install.
Enter the number or numbers associated with the software subsets you want to install. There may be more software subsets presented in the menu than can be displayed on a single screen. You can either select software subsets in each screen or select them all together on the last screen. If you select software subsets as each screen is displayed, all your choices are presented for you to confirm on the final screen. You also can change your choices or redisplay the software subset options.
Only the software subsets not yet installed on your system are displayed. The software subset selection list looks similar to the following:
The subsets listed below are optional:
There may be more optional subsets than can be presented on a
single screen. If this is the case, you can choose subsets screen
by screen or all at once on the last screen. All of the choices
you make will be collected for your confirmation before any subsets
are installed.
- General Applications:
1) Additional Terminfo databases
2) Computer Aided System Tutor
3) DOS tools
4) GNU Emacs
5) Local Area Transport (LAT)
6) UNIX(tm) SVID2 Compatibility
7) UNIX(tm) to UNIX(tm) Copy Facility
- Kernel Build Environment:
8) ATM Kernel Header and Common Files
9) ATM Kernel Modules
10) Logical Storage Manager Kernel Header and Common Files
11) Logical Storage Manager Kernel Modules
12) POLYCTR advfs Kernel Modules
- Kernel Software Development:
13) ATM Kernel Objects
14) Hardware Kernel Objects
15) Logical Storage Manager Kernel Objects
16) POLYCTR advfs Kernel Objects
17) Standard Kernel Objects
- Mail Applications:
18) DECwindows Mail Interface
19) RAND Corp. Mail Handler (MH)
- Network-Server/Communications:
20) ATM Commands
21) Additional Networking Services
22) Dataless Management Services
23) Remote Installation Service
--- MORE TO FOLLOW ---
Enter your choices or press RETURN to display the next screen.
Choices (for example, 1 2 4-6):
- Printing Environment:
24) Adobe Font Metric Files
- Reference Pages:
25) Ref Pages: Admin/User
26) Ref Pages: CDE Admin/User
27) Ref Pages: CDE Development
28) Ref Pages: Programming
29) Ref Pages: Realtime
30) Ref Pages: Windows Admin/User
31) Ref Pages: Windows Programming
- Software Development:
32) CDA(tm) Software Development
33) CDA(tm) for X/Motif Development
34) CDE Software Development and Programming Examples
35) GNU Revision Control System
36) Ladebug Debugger Version 4.0
37) Ladebug Debugger Version 4.0 Release Notes
38) Ladebug Debugger Window Interface
39) Ladebug Debugger remote server
40) Realtime Software Development
41) Software Development Desktop Environment
42) Source Code Control System
43) Standard Header Files
44) Static Libraries
45) X Window and X/Motif Header Files
46) X Window and X/Motif Programming Examples
47) X Window and X/Motif Software Development
48) X Window and X/Motif Static Libraries
Choices (for example, 1 2 4-6): 25 30
- Supplemental Documentation:
49) XIE Version 5 Online Documentation
- System Administration:
50) C2-Security
51) C2-Security GUI
52) Kernel Debugging Tools
53) Logical Storage Manager
54) Logical Storage Manager GUI
55) Logical Volume Manager
56) Obsolete Commands and Utilities
57) Obsolete Locale databases
58) POLYCTR advfs
59) Single-Byte European Locales
60) System Accounting Utilities
61) System Exercisers
- Text Processing:
62) Doc. Preparation Tools
63) Doc. Preparation Tools Extensions
- Windowing Environment:
64) DECwindows 75dpi Fonts
65) LK201 Keyboard Support
66) LK411 Keyboard Support
67) LK421 Keyboard Support
68) LK444 Keyboard Support
69) PCXAL Keyboard Support
70) X Customizations for OEM
71) X Servers for Open3D
72) X Servers for PCbus
73) X/Motif 1.1
- Windows Applications:
74) Additional DECwindows Applications
--- MORE TO FOLLOW ---
Add to your choices or press RETURN to display the next screen.
Choices (for example, 1 2 4-6): 25 30 62
75) Additional X Applications
76) CDE Additional Applications
77) Demo X Applications
78) Nested X Server
79) Old Additional DECwindows Applications
80) Virtual X Frame Buffer
The following choices override your previous selections:
81) ALL of the above
82) CANCEL selections and redisplay menus
83) EXIT without installing any subsets
Add to your choices, choose an overriding action or
press RETURN to confirm previous selections.
Choices (for example, 1 2 4-6): 25 30 62
After you enter your choices, the following confirmation message is displayed:
You are installing the following optional subsets:
- Reference Pages:
Ref Pages: Admin/User
Ref Pages: Windows Admin/User
- Text Processing:
Doc. Preparation Tools
Is this correct? (y/n):
After you confirm your choice, messages similar to the following display as the software subsets are loaded and configured:
Checking file system space required to install selected
subsets:
File system space checked OK.
3 subset(s) will be installed.
Loading 1 of 3 subset(s)....
Doc. Preparation Tools
Copying from server1 (inet)
Verifying
Loading 2 of 3 subset(s)....
Ref Pages: Admin/User
Copying from server1 (inet)
Working....Fri Dec 17 11:46:17 EST 1999
Verifying
Loading 3 of 3 subset(s)....
Ref Pages: Windows Admin/User
Copying from server1 (inet)
Verifying
3 of 3 subset(s) installed successfully.
Configuring "Doc. Preparation Tools " (OSFDCMT440)
Configuring "Ref Pages: Admin/User " (OSFMANOS440)
Configuring "Ref Pages: Windows Admin/User " (OSFMANWOS440)
If you are installing from CD-ROM, after the software subsets are installed, unmount the CD-ROM.
#umount /dev/rz4c
To install operating system software subsets on Remote Installation Services (RIS) clients, refer to Sharing Software on a Local Area Network.
If you select a software subset that has a dependency on another subset that is not yet selected or is not already installed, you will see a message similar to the following during subset loading:
Checking file system space required to install selected subsets:
File system space checked OK.
1 subset(s) will be installed.
Loading 1 of 1 subset(s)....
setld:
Error installing "Ref Pages: Admin/User " (OSFMANOS440)
This subset requires following subset(s) to operate correctly:
"Doc. Preparation Tools " (OSFDCMT440)
setld:
Please install required subset(s) first.
0 of 1 subset(s) installed successfully.
In the previous example, the reference
page software subset was not installed because it requires the installation of the
Doc.
Preparation Tools (OSFDCMT440).
The
setld
command will not install software subsets with
dependencies without installing the software subset on which the dependency occurs.
You must invoke the
setld
command again and make sure you select
all software subsets along with their dependencies.
Appendix D describes each software subset and shows the dependencies between software subsets (if any).
Certain base operating system products (such as the Logical Storage Manager,
Advanced File System, and Local Area Transport) contain a kernel component.
If you
use
setld
to install one of these software subsets after the installation,
you must run the
doconfig
utility to rebuild the kernel with the
new kernel component; otherwise the option to use the product will not be available.
After building a new kernel, reboot with the new kernel to make the product available
for use.
Refer to
Table D-4
in
Appendix D
for
a list of the base OS software subsets that contain kernel components for which you
must run
doconfig
to build a new kernel.
Refer to the
doconfig(8)
reference
page for more information.
If you install the Asynchronous Transfer Mode (ATM) DGLTA adapter after installing
the operating system, you must boot the system from the generic kernel
genvmunix, install the ATM software subsets from the CD-ROM, and then run the
doconfig
program to rebuild your system kernel to enable the added ATM support.