Making a New Configuration

This subsection walks you through the procedure for making a new system configuration. If your system includes server(s) and client(s), you probably want to go through this procedure twice, making one kernel for the 5erver machine (in5tall it in / vmun;z), and one kernel for all the clients (install it in / pub/ vmuniz).

1. Choose a name for your configuration of the system; here, SYSjlAME. Note that - by con-vention - the name should be in all uppercase letters.

2. Change directory to the

/'11'/

conI directory, and create the configuration file and the direc-tory in which the new system will be built. In this example, we assume that you will make a copy of the GENERIC file provided with this release, and edit the copy to create your new configuration file. Another (perhaps easier) method is to copy one of the stripped-down files in

/'11'/

conI and edit it, XY100, for example, makes a good starting point for a Model

Installing UNIX for the First Time Sun 100/150 Installation Manual (which are, generally, parameters global to all kernel images specified in the configuration file), and lines which specify devices 'attached' to the system. We have indicated both classes of lines as follows:

• General system description lines are tagged "**mandatory**". These lines must be included in your system configuration file, either exactly as they stand or, if commentary indicates variables, with the variables adjusted to fit your system.

• Device description lines are given and explained. Often, we also refer you to the manual entry which covers the device in question. When you edit the GENERIC file, you should include only the lines which describe your system's devices. Remember that if you are creating a kernel for several clients, the configuration file must include the entire set of devices used by all the machines.

*

the "swap generic" clause in the "config" line below. Ir you customize the identifier to SYS_NAME, you must either include an "options GENERIC" line or speciry at least the device where your root file system lives in place or "swap generic". For exa.mple, the "config" line ror a standard Sun 100U might read: "config vmunix root on xy".

Finally, ir SYS_NAME contains both alpha and numeric characters (as in XYI00, ror exa.mple), you must enclose the name in double quotes or you will get a syntax error when you run /etc/config ("XYI00").

,"Mandatory •• Number and "dst" are variable,

, .. Mandatory •• Number may vary. For most systems, "2" is the proper value ror max users. See the section Genertd Sllltem Delcn'ption Linel, below, ror inrormation.,

f •• Mandatory.. INET means include Internet codef fOptional; include only with pseudo-device sysacct.

Controls inclusion or code to do process accounting - see 4ut(2} and 4cct{5}.,

fPseudo-tty's. Needed ror network or window system.' fBerknet line discipline ror high speed tty input - see bk(4)., ,Include only with SYSACCT options clause, above.' f •• Mandatory •• Internet code - see inet(4}.,

IARP code. Must include ir using Ethernet - see 4rp(4).' f"Mandatory •• Sortwa.re loop ba.ck network device driver;

must include ir INET - see 10 (4).,

,Network disk. Needed ir server or diskless - see nd{4}.,

,Window system. Number indicates max windows. Must include dtop, below, ,Max Screens ('desktops'); required ror window system.,

,Max Mice; required ror window system - see ml {4}., kb3 ,Max Sun keyboards; required ir using any Sun keyboard;

omit ir using serial terminal ror console.' ingres IIngres lock device* fIst Xylogics controller - see Z1J(4}., '2nd Xylogics controller,

fIst disk on 1st Xylogics controllerf f2nd disk on 1st Xylogics controller, fIst disk on 2nd Xylogics controller,

Revision H of 12 March 1984 4-33

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

12nd disk on 2nd Xylogics controller, ,1st SCSI controller,

,1st disk on 1st SCSI controller, '2nd disk on 1st SCSI controller, ,SCSI tape'

ropeO at mbO esr Oxee0800 priority 1 , .. Mandatory .. Raster Op chip - see ropc(4).' skyO at mbO esr Ox2000 priority 2 ,Sky Floating Point board.'

zsO at mbO csr Oxeec800 flags 3 priority 2 ,CPU ports - see z,(4).fa

!sl at mbO csr OxeecOOO flags 3 priority 2 ,Sun-2 Video Board ports;

required it using Sun-2 keyboard and mouse.'

!s2 at mbO csr Ox80800 flags 3 priority 2 ,1st SCSI Board ports.,

fist 3COM Ethernet Controller - see ec(4)' f2nd 3COM Ethernet Controller,

,1st TAPEMASTER tape controller - see tm(4).' '2nd TAPEMASTER tape controller,

'1st 1/2" tape drive on 1st controller., '1st 1/2" tape drive on 2nd controller., '1st 1/4" tape drive - see sr(4).'

'1st Systech Centronics/Versatec Board - see t7pc(4s).' f2nd Systech Centronics/V ersatec Board. f

fParallel input. Only used on Sun Models 100U and 150U, tor keyboard and mouse.

Not needed it using terminal tor console.'

The following configuration XYI00 is a stripped down version of the GENERIC system for a system with only a single local peripheral: a Xylogics controller supporting one disk drive.

It's a good example of a standard configuration file:

*

Workltation Kernel, in the Tutorial, section of this manual.

4. When you ha.'ve finished editing SYS_NAME, run config2:

#=

lete/eooBs SYS_NAME

s.

Now change directory to the new configuration directory, •• / SYS_NAME, and make the new system:

2 Note that ir the "ident" field (system name) in your configuration file contains any digits,

/ete/eoAM

prints: "config: Line 5: syntax error" at this point. You may ignore the error message.

Revision H of 12 March 1984 4-35

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

#:

^{cd •• / SYS_NAME}

#:

make depend

( lots of out put . . . ignore the error message³

1

#:

make

[ lots of out put )

The make depend command creates the dependency tree for all system source files.

6. Now you can install the new system and try it out.

#:

mv /vmunlx /vmunlx.ors

#:

cp vmunlx /vmunix

:/1= /etc/halt

The 'liltem goe, through the holt ,equence, then . the monitor di'ploll' it, prompt} ot which point IIOU

con boot the 'Illtem in ,ingle-u,er ,tote

>

^b vmunlx-8

The 'lI"em boot, up in 'ingle u,er "ote} ond then IIOU con try thing' out

7. If the system appears to work, all is well. If the new kernel doesn't seem to be functioning properly, boot /vmuniz.org, move it back to /tJmuniz, and go about fixing your new kernel:

*

^/etc/halt

>

b vmunlx.org -II

:/1= mv /vmunix /vmunlx.oopa

*

mv /vmunlx.orl /vmunlx

*

^AD [Brings the system up multi-user)

You can now continue with the next phase of installation -

*

loading the manuals, demos, and games directories - or, it you do not wish to include this material in your system, with the

Net-work Configurotion section in the S"ltem Set-up ond Operotion chapter. The subsections immediately below give background information for configuring the kernel.

4.3.12.~. Configuration Directory Layout

~

The system as shipped contains the essential source and object files in the / 'II' directory. The / 'II' directory contains several subdirectories that in turn contain the object code modules required to build different parts

ot

the system. The subdirectories in

I'll'

^are:

OBI Contains the kernel object code plus the header files describing the number

ot

devices of each type.

conI Contains the files describing the configuration of the system and what files are required to build the new system. Also contains a README file describing how to make a new kernel. Finally, contains the GENERIC system configuration file a The 'make depend' may 3enerate a spurioufl error messase like • •. /sun/locore.s: no such file or

directory' at this point, which yoq may safely isnore.

h your specific system configuration file; procedures are given above.

Header files containing definitions and data structures.

Machine-dependent routines for the Sun system - this is a symbolic link to the the system has another file of this type.

Contains a list of the files required to build the basic kernel.

file,.,un Contains a description of the files required to build the specific Sun system. You add the names of new driver modules in here when adding drivers to the kernel.

/ etcl config should be run from the conI subdirectory of the system source or object files.

/ dcl config assumes that there is already a directory .. / SlIltem_Name created, and it places all its output files in there. The output of / dcl config consists of a number of files:

iocon/·c makefile

Contains a description of I/O devices attached to the system.

For building the system.

Heatler File, A set or header files which contain the number of various devices that will be compiled into the systel1i.

After running / dcl config, you must then change directory to the directory in which the new makefile was created, and use make to create the dependency tree for the new system.

/ etcl config remind~ you of this when it completes:

*

^cd

^it./

Sydem_Name

Dans le document Workstation Manual (Page 71-77)