Museum

Home

Lab Overview

Retrotechnology Articles

Online Manuals

⇒ mboot(1a) — NEWS-os 5.0.1

Media Vault

Software Library

Restoration Projects

Artifacts Sought

Related Articles

system(4)

master(4)



mboot(1M)        SYSTEM ADMINISTRATION COMMANDS         mboot(1M)



NAME
     mboot - configure bootable kernel

SYNOPSIS
     /etc/mboot [ -v ] [ -x ] [ -m master ] [ -s  system[.suffix]
     ] [ -b directory ]

DESCRIPTION
     The mboot command is used to help configure a bootable  UNIX
     kernel.  Master files in the directory master contain confi-
     guration information which is used to create master.c in the
     master  directory.   The  mboot  command also creates a file
     called objlist[.suffix] in the boot directory which contains
     a  list  of the objects needed to be linked into the kernel.
     When the file master.c is compiled, it can  then  be  linked
     with kernel.o and all the objects listed in objlist[.suffix]
     to achieve a fully resolved and bootable UNIX kernel.

     If a module in master is specified in the  system  file  via
     "INCLUDE:",  that  module  will  be included in the bootable
     kernel.  For all included modules, mboot searches  the  boot
     directory  for an object file with the same name as the file
     in master, but with a ".o" or ".a" appended.  If found, this
     object is included when building the bootable kernel.

     For every module in the system file specified via "VECTOR:",
     mboot  takes  actions  to  determine  if  a  hardware device
     corresponding to the specified  module  exists.   Generally,
     the  action  is  a  memory  read at a specified base, of the
     specified size.  If the read succeeds, the device is assumed
     to  exist, and its module will also be included in the boot-
     able kernel.

     To create the new bootable object file, the applicable  mas-
     ter  files  are  read  and  the configuration information is
     extracted and compiled.  The output of this  compilation  is
     then linked with all included object files.

     Master files that are  specified  in  the  system  file  via
     "EXCLUDE:" are also examined; stubs are created for routines
     specified in the excluded master files that are not found in
     the included objects.

     The options are:

     -m master      This option specifies the directory  contain-
                    ing the master files to be used for the boot-
                    able kernel.  The default master directory is
                    $ROOT/etc/master.d.

     -s system      This option specifies the name of the  system
                    file.     The    default   system   file   is



                                                                1





mboot(1M)        SYSTEM ADMINISTRATION COMMANDS         mboot(1M)



                    $ROOT/etc/system.

     -b directory   This option  specifies  the  directory  where
                    object  files  are  to be found.  The default
                    directory is $ROOT/boot.

     -v             This option makes mboot  slightly  more  ver-
                    bose.

     -x             This option  displays  debugging  information
                    and  produces  a  configuration summary about
                    the devices and modules included in the  ker-
                    nel.

EXAMPLE
      ../mboot -v -x -m ../master.d -s ./system.single -b ../boo-
     tarea

     This starts a mboot command (mboot is from the .. directory)
     which  reads system.single from the current directory as the
     system file, uses ../master.d as the master  directory,  and
     uses  ../bootarea  as  the  boot directory.  A master.c file
     will be  produced  in  the  ../master.d  directory  and  the
     objlist.single  will  be generated in the ../bootarea direc-
     tory.

SEE ALSO
     system(4), master(4)



























                                                                2



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