o The -I option presents the output in long form, showing inode number, size in kilobytes (1024 bytes), protection mode, number of hard links, user, group, size in bytes, and modification time.
Ifthe file is a special file the size field will instead contain the major and minor device numbers.
Ifthe file is a symbolic link the pathname of the linked-to file is printed preceded by' .. >'. The format is identical to that of find -Is.
o The -c option specifies to use the given cutoff date to decide which files to print, rather than the date of the file /etc/sys_conflsystem-configured. The cutoff date format is -c mmddhhmm[yy], with month, day, hour, minute, and optional year in numeric form. This is the same format as for /usr/5binltouch.
reinst_sys has been modified since OS/MP 4.1B, so be sure to extract the new ver-sion from the
OSIMP4.1 C media. If you installed preinstall as shown above, then the server already contains the version ofreinst_sys that it needs and you may skip to the
Installingsection below.
Extracting reinst_sys
The following explains four different methods of extracting reinst_sys into the /us-r/etc directory. You must be logged in as root.
Extracting reinst_sys via a Local Tape Drive
Extracting reinst_sys via a Remote Tape Drive
Routing from the system being installed to the tapehost must exist. Refer to the
Sys-tem Network and Administration Guide(101481). The local machine must be listed
in /etc/hosts, or in the NIS/YP hosts database, and I.rhosts on
tapehos t.Installing OS/MP 4.1 C on a server using reinst_sys 193
Extracting reinst_sys via a Local CD-ROM Drive
Create a mount point directory (if one doesn't exist), mount the CD-ROM drive, and extract reinst_sys as follows:
Extracting reinst_sys via a Remote CD-ROM Drive or the Network
When installing over the network, or when using a remote CD-ROM drive, create a mount point directory (if one doesn't exist), and mount the CD-ROM drive on the remote machine, referred to here as nethosts, as follows:
Install reinst_sys using the following commands:
In this example, replace ne thos t with the actual name of the remote host ma-chine, and replace cdrom with the actual path name or mount point.
194 Installing OS/MP 4.1 C on a server using reinsCsys
Installing ...
This section covers the OSIMP 4.1 C installation on Series5, Series5E, Series6 and S4000 systems.
During installation, you can request help at any prompt by entering a question mark. Table 21 shows edit commands available when entering text in response to prompts:
Table 21. Input Editing Commands
Character Interpretation
backspace (A H) delete last input character
delete (A?) delete last input character
AU erase input line
AR redisplay input line
AW delete input up to '/' or whitespace
AC cancel input, returning to nearest menu
ESC cancel input, returning to nearest menu
AL redisplay entire screen
return (AM) end input
newline (AJ) end input
If a string is too long to be displayed in the available space, the beginning of the string is displayed as " ... ". This allows display of the end of the string, which is usually of more interest.
Keywords can be shortened to any unique prefix (such as 'co' for 'continue'), ex-cept for 'yes' and 'no', which must always be spelled out.
Fatal errors during software installation are usually reported by messages begin-ning with System error or Internal error and ending with a "#"
prompt. If a fatal error occurs, software installation may be restarted by entering:
where A J is the linefeed character. The command stty sane may not be echoed (and is intended to fix exactly that problem). In the event of a fatal error during software installation, please report the problem to Solbourne customer support.
Installing OS/MP 4.1 C on a server using reinst_sys 195
Installing Software
Installing software has two distinct stages: gathering information and modifying the system. No permanent changes are made to the system until all information has been provided.
There are three information gathering menus:
o
Standard Filesystem Definition - specifies where the standard filesystems (root (I), swap, and /usr, optionally /var and /tmp) are located.o
Installation Media Identification - Determines the installation media from which to install (tape, CD-ROM, or network directory), and determines where.that media is located.
o
Package Selection - allows selecting of which optional software packages are to be installed.All three menus provide the command cancel. The first two also provide the com-mand previous. These commands allow you to return to prior menus, optionally discarding any changes that have been made.
cancel always returns to the shell terminating reinst_sys.
previous always returns to the previous menu (which is the shell, in the case of the Filesystem Definition menu). The changes discarded in this case are those made in the menu you are leaving.
cancel has higher priority than previous. In other words, if you use previous to leave a menu without discarding changes, then cancel from that menu and discard changes, the changes made in the earlier menu are also discarded.
The Standard Filesystem Definition menu defines where the mandatory filesys-terns are located. These filesystems (except for root) may be either on a local disk partition or provided by a disk server. If root is to be on a remote system, install the system as a client of that system, even if the system actually contains a disk. You can add entries for any local disks to /etdfstab after installing the system as a disk-less client.
Any changes made to the standard filesystems with partition(8) will appear in this menu.
reinst_sys has the following options:
reinst_sys [-m] [-n] [-r /root/path] [-fhost/device/path] [-a arch]
-m
-n
-r /root/path
Don't mount or newfs filesystems Don't newfs filesystems
Pretend /root/path is really / -f host:/device/path What tape device to use
-a arch What cpu architecture to use - overrides cpustatus
196 Installing OS/MP 4.1 C on a server using reinscsys
In general, you will not need to use any of these options except perhaps the -a op-tion. The -f option will be set while running reinst .... sys.
The -a option is to be used when you are upgrading or changing the architecture of your machine. Suppose you have a machine with Series5 CPUs, and you want to upgrade to Series6 CPU s. To install the OSIMP 4.1 C for Series6, log in as root and issue the following command:
To install OSIMP 4.1 C with no change in architecture, log in as root and issue the command:
reinst_sys begins by reading the current letdfstab file to determine the disks at-tached to your system (mounted disks are also probed).
After examining all attached disks, reinst_sys presents the first menu, the Standard Filesystem Definition menu.
The root, swap, and usr partitions are required and must be defined before going to the next menu. The swap will be defined as the current swap area, and may be re-defined if you wish. The root and usr areas need to be re-defined from the currently available disk partitions that are highlighted in the Standard Filesystem Definition menu. For a disk partition to be available for use in reinst_sys, it must not be cur-rently mounted, and it must not have an entry in the letdfstab file.
Example:
Currently, the root(1) filesystem is on sdOa, swap is on sdOb, and the lusr filesys-tern is on sdOg. Available partitions are highlighted. If the necessary partitions are not available, exit reinst_sys. A partition may not be available because it is mount-ed or an entry exists for it in the letdfstab file. Also, it may not be available be-cause it does not exist, or it is not large enough, in which case you will need to run partition(8) to repartition the disk as needed.
Use the following steps to assign the root (I) filesystem to sd2a, the lusr filesystem to sd2g, and the /var filesystem to sd2d (rather than using the default of Ivar being a subdirectory of the root filesystem). Leaving swap on the disk may be desirable.
The steps for changing /var are optional. This makes use of partition d, thus using 9.5 MB of disk space that is not used when the default disk partition is used with the standard file system definition.
In Figure 58, the notation "(required)" appears next to the root(l), swap and lusr filesystems. These filesystems must be defined; however, they may be placed on any sufficiently large available partition of any disk.
Installing OSIMP 4.1 C on a server using reinsCsys 197
Figure 58. Sample Standard Filesystem Definition Menu To modify the root (I) filesystem, enter the number 1.
The root menu will be highlighted, and the system will request a disk partition. As-sign it to sd2a.
To modify the lusr filesystem, enter the number 3.
The usr menu will be highlighted, and the system will request a disk partition. As-sign it to sd2g.
To modify the Ivar filesystem, enter the number 4.
198 Installing OSIMP 4.1 C on a server using reinsCsys
The var menu will be highlighted, and the system will request a disk partition. As-sign it to sd2d.
The new arrangement is displayed as shown in Figure 59.
Figure 59. Modified Standard Filesystem Definition Menu
Once all changes for the standard filesystems have been made, enter continue to proceed to the Installation Media Identification menu.
Installation Media Identification Menu
The Installation Media Identification menu describes which media type (tape, CD-ROM, or network directory) will be used during the installation. Figure 60 shows the Installation Media Identification menu.
Installing from a Tape Drive
Installing from a local tape drive requires that the Installation media type be set to Tape, the tape drive field be set to either stO or stl (the only supported tape drives) and that Tape host be set to localhost.
Installing OS/MP 4.1 C on a server using reinst_sys 199
Figure 60. Installation Media Identification Menu - Local Tapehost Installing From a Remote Tape
Installation media type must be set to Tape.
Tape drive should be the base name of the tape drive on the tapehost, either stO or stl.
The Local Internet address is the address of the system being installed. If the de-fault value is not correct, make sure that the client name corresponding to the cor-rect address appears in the tape host's I.rhosts file. Check letc/hosts or the NIS/YP hosts map as appropriate.
The broadcast mask should not be changed unless your network uses a non-stan-dard mask. Such a mask is used when a network is sub-netted (i.e., a Class B net-work is treated as several Class C netnet-works). A leading 'Ox' is necessary if entering the mask as a hexadecimal number. A leading '0' is needed for octal numbers. If neither prefix is given, the value is assumed to be in decimal.
Tape host must be set to the name of the system with the tape (rootbeer in this example), which is used to determine the tape host's Internet address.
Figure 61 shows the Installation Media Identification Menu of a system that is set up to install from a remote tape using tape device stO (SCSI address 4).
When the details of the tape drive have been entered correctly, enter continue.
You will be presented with the Package Selection Menu.
200 Installing OSIMP 4.1 C on a server using reinsCsys
Figure 61. Installation Media Identification Menu - Remote Tapehost Local CD-ROM Installation
Installing from a local CD-ROM drive requires that the Installation media type be set to CD-ROM, the CD drive field be set to / dev / srO, and the CD host field be set to localhost.
Figure 62 shows the Installation Media Menu with the CD-ROM parameters set to install from CD-ROM.
Network and remote CD-ROM Installations Installation media type must be set to Network.
Installation directory should be the full path name of the location of the installa-tion area, OR the full path of the CD-ROM mount point, on the network host. For example, if the remote CD-ROM is mounted on / cdrom, then the installation path is simply / cdrom.
The Local Internet address is the address of the system being installed. If the de-fault value is not correct, make sure that the client name corresponding to the cor-rect address appears in the tape host's I.rhosts file. Check letc/hosts or the NISIYP hosts map as appropriate.
The broadcast mask should not be changed unless your network uses a non-stan-dard mask. Such a mask is used when a network is sub-netted (i.e., a Class B net-work is treated as several Class C netnet-works). A leading 'Ox' is necessary if entering the mask as a hexadecimal number. A leading '0' is needed for octal numbers. If neither prefix is given, the value is assumed to be in decimal.