Path 2: Standard Server Configuration

Note that if you follow this path, you are constrained to put / pub on the first disk you configure.

This subsection provides an example of the ,etup interactive dialogue which is typical for a standard network server configuration. This path allows you to select the size of your public partition, and establish the size of a standard paging partition which is allotted to each client.

The remaining disk space is equally divided to make each client's file system subpartition.

In the example, what you might type in is shown in boldface type like this; whatever is sim-ply displayed on the monitor is shown in Roman type like this.

We invoke the ,etup program by typing the ,etup command. Setup begins by requesting global information:

*

^setup

Sun Microsystems Configuration System Global Information

1) network disk server 2) standalone

3) standalone with remote tape

Enter the number for your environment: 1

You have a network disk server system; is this correct! (y/n): y

Note that the ,etup program asks you to verify configuration information after each 'phase' of configuration is complete. It is extremely difficult to undo system configuration, so be careful with your responses: 'y' casts things in concrete, and 'n' allows you to start the phase over again. You can also type 'q' to any prompt to quit the ,etup program and return to the shell -this allows you to annihilate what you have done and start over, if you have to.

After determining your environment, ,etup gathers information about your disk configuration.

It determines the type of disk controller being used for installation, and asks you for device information:

You have booted off ofaXylogics disk controller

Enter the number of disks attached to the Xylogics controller: (1-2): 2 The Xylogics disk controller has 2 disk(s):

xyO xyl

Is this configuration correct! (y/n): y

For the remainder of the dialogue, ,etup will refer to your disk(s) by their UNIX device abbrevia-tions. Next, ,etup begins the partitioning process for the first-named disk. If your configuration includes more than one disk on a single controller, as in our example, ,etup will completely finish PJU"titioning the first disk and then turn to the second. If you have multiple controllers, you will be asked to repeat, this entire phase for each tontroller. Your configuration will be vali-dated after all disks have been partitioned. If errors are found at that time - for example, if all clients have not been allocated both file system and paging areas - you will be asked to edit your specified configuration until it is correct.

The partitioning phase of the dialogue with ,etup looks like this:

Disk Partition Information

Would you like to partition device xyO into "n" equal sized clients! (yIn): y Enter the pub partition size (nnnM or nnnK)

- minimum is 17408K - default is 20480K: 17M Partition size rounded to 17472K.

Enter the swap partition size (nnnM or nnnK) - minimum is 4096K

- default is 6144K: 8M Partition size rounded to 8288K.

Enter the number or clients on device xyO: (1-3): 2 Enter a client's name: adam

E~ter a client's name: eve

You are asked to declare partition sizes in K Bytes or M Bytes, and ,etup takes care of rounding your partitions to cylinder boundaries for performance reasons. You can always type

'RETURN' as a response to a sizing prompt to get the default partitioning.

This partitioning phase of the dialogue sets up a

I

pub partition of whatever size you select (if this is the first device being partitioned), allocates a standard paging area for each of your specified clients (again, you determine the size), and carves the remaining free disk space into equally sized user subpartitions for each of them.

This completes partItioning . for the first disk. If you have another controller, you are asked for its type, and the number of devices attached to it at this time, and are then asked to repeat the partitioning process for each disk. When all disks have been partitioned, ,etup asks for network information for each of your specified clients and your network server:

Revision H of 12 March 1984 4-19

Installing UNIX for the First Time Sun 100/150 Installation Manual

Network Information

Network numbers may be either class A, B or C Their formats are:

Class A: nnn (000

<=

ⁿⁿⁿ

<=

¹²⁷⁾

Class B: nnn.bl (128

<=

nnn

<=

191) Class C: nnn.b1.b2 (192

<=

nnn

<=

255) hI and b2 are one byte (0-255) quantites

Enter your network number (default is 192.9.200): <RETURN>

Your network number is 192.9.200; is this correct! (y/n): y

Enter the 6-byte hex adecimal ethernet address for each of the clients The correct form is xx:xx:xx:xx:xx:xx

Client adam: 8:0:20:0:14::78 Client eve: 8:0:20:0:8:14

The clients and their ethernet addresses are:

1) adam: 8:0:20:0:14:76 2) eve: 8:0:20:0:8:14

Are the ethernet addresses correct! (y / n): y

Do you want host numbers automatically assigned! (y/n): y Server Information

Enter the name of the server: IIUD

The server's hostname is:

sun

Is this correct! (y/n): y

Note that you use your network number, and your clients' hardware Ethernet addresses (esta-blished at the outset of the installation procedure) here. You may assign host numbers yourself, or have ,etup assign them automatically. For a discussion of network and host numbers, and clients' hexadecimal Ethernet addresses, see the earlier section, Determining Network In/orma·

tion.

The last phase of ,etup configuration requests information about your tape subsystem:

Tape Information

1) 1/4" SCSI tape (st) 2) 1/2" magnetic tape (mt) 3) 1/4" archive tape (ar)

Enter the numher for the type of tape: (1-3): 3

You have specified a 1/4" archive tape; is this correct? (y/n): 7

When this last phase has been completed, ,etup asks you whether you want to institute the configuration you have designed and, if you confirm, proceeds to edit several of the database files:

You have completed the configuration questions.

Continuing will destroy any existing files under /usr and any client partitions if you are a server.

Do you want to begin configuration! (y In): y Updating / etc /hosts

[ ... A few lines of configuration messages ... ]

If your distribution is on two 1/4-inch tape cartridges, letup will prompt you to change to the second cartridge about two minutes into its back-end routine. Insert the second tape and type 'RETURN' to continue the routine; it takes approximately 25 minutes to complete. When letup completes its back-end work, your shell prompt returns. You can then continue your installation by booting the full UNIX system, as described below.

Dans le document Workstation Manual (Page 58-61)