Museum

Home

Lab Overview

Retrotechnology Articles

Online Manuals

⇒ system(4) — NEWS-os 5.0.1

Media Vault

Software Library

Restoration Projects

Artifacts Sought

Related Articles

crash(1M)

mboot(1M)

master(4)



system(4)                 FILE FORMATS                  system(4)



NAME
     system - system configuration information file

DESCRIPTION
     This file is used by the mboot(1M) program to obtain  confi-
     guration information.  This file generally contains informa-
     tion used to determine if specified hardware exists, a  list
     of  software drivers to include in the load, and the assign-
     ment of system devices such as  pipedev  and  swapdev.   The
     system file is /usr/src/uts/sony/master.gen/system.<suffix>.
     This  file  is  typically  generated  by  a   shell   script
     (/usr/src/uts/sony/master.gen/sysgen.sh)  which parses vari-
     ous options, invokes the mboot program, and prepares  for  a
     master.gen.<suffix>.c file.  This master.gen.<suffix>.c file
     later gets compiled and linked to create a new bootable ker-
     nel.    The   system.<suffix>   file  is  derived  from  the
     sysgen.<suffix>  file.   It  is  preferable   to   use   the
     sysgen.<suffix>  as the real system file when using the pro-
     vided set of scripts and makefiles.  The syntactic rule  for
     the  sysgen.<suffix> is essentially the same as that for the
     system file.

     The syntax of the system file is given  below.   The  parser
     for  the  system  file  is  case  sensitive.  All upper case
     strings in the syntax below should be upper case in the sys-
     tem file as well.  Nonterminal symbols are enclosed in angle
     brackets < > while optional arguments are enclosed in square
     brackets  [ ].   Ellipses (...) indicate optional repetition
     of the argument for that line.

     The symbols in the syntax description below are  interpreted
     as follows:

     <fname>    ::=   master file name from master.d directory
     <device>   ::=   special device name | DEV(<major>,<minor>)
     <major>    ::=   <number>
     <minor>    ::=   <number>
     <number>   ::=   decimal, octal or hex literal

     The lines listed below may appear in any order.  Blank lines
     may be inserted at any point.  Comment lines must begin with
     an asterisk.  Entries for VECTOR, EXCLUDE  and  INCLUDE  are
     cumulative.   For all other entries, the last line to appear
     in the file is used-any earlier entries are ignored.

     VECTOR: module=<fname> [intr=<func>]
          [vector=<number>       ipl=<number>       unit=<number>
          base=<number>]
          [ probe=<number> [ probe_size=<number> ] ]
          Specifies hardware to conditionally load.  If  a  probe
          address  is  specified,  the  boot  program  will  read
          probe_size  bytes  (default  4)  to  determine  if  the



                                                                1





system(4)                 FILE FORMATS                  system(4)



          hardware  exists  for the module.  If so, the module is
          included.  If a probe address  is  not  specified,  the
          hardware  will  be assumed to exist.  The intr function
          specifies the name of the module's  interrupt  handler.
          If  it  is  not  specified,  the  prefix defined in the
          module's master file (see  master(4))  is  concatenated
          with  the  string  "intr",  and, if a routine with that
          name is found in the module's object (which resides  in
          the          boot          directory,         typically
          /usr/src/uts/sony/bootarea), it is used as  the  inter-
          rupt routine.

     EXCLUDE:  <fname> ...
          Specifies drivers to exclude from the load even if  the
          device is found via VECTOR information.

     INCLUDE:  <fname>[(<number>)] ...
          Specifies software drivers or loadable  modules  to  be
          included  in  the  configuration.  This is necessary to
          include  the  drivers  for  software  "devices".    The
          optional  <number> (parentheses required) specifies the
          number of  devices  to  be  controlled  by  the  driver
          (defaults  to 1).  This number corresponds to the buil-
          tin variable #CC which may be referred  to  by  expres-
          sions in Part two of the master file.

     ROOTDEV:  <device>
          Identifies the device containing the root file system.

     SWAPDEV:  <device> <number> <number>
          Identifies the device to be used as  swap  space.   The
          <device> in this case may be a special device file name
          or a regular file.  The <number>'s  correspond  to  the
          block number the swap space starts at and the number of
          swap blocks available.

     PIPEDEV:  <device>
          Identifies the device to be used for pipe space.

     DUMPDEV:  <device> <number> <number>
          Identifies the device to be used for kernel dumps.

     KERNEL: [ <fname> ] ...
          Specifies  the  module  containing  the  heart  of  the
          operating  system.   It  must  be present in the system
          file.

     LCOPTS:  <option string>

     LDOPTS:  <option string>
          Option strings given to cc(1) and  ld(1)  respectively,
          to  compile the master.gen.<suffix>.c file and link the



                                                                2





system(4)                 FILE FORMATS                  system(4)



          operating system.

FILES
     /usr/src/uts/sony/master.d/*
     /usr/src/uts/sony/master.gen/system.<suffix>
     /usr/src/uts/sony/master.gen/sysgen.<suffix>

SEE ALSO
     crash(1M), mboot(1M), master(4).














































                                                                3



Typewritten Software • bear@typewritten.org • Edmonds, WA 98026