If sysinstall is compiled with LOAD_CONFIG_FILE set in the environment (or in the Makefile) to some value, then that value will be used as the filename to automatically look for and load when sysinstall starts up and with no user interaction required. This option is aimed primarily at large sites who wish to create a single prototype install for multiple machines with largely identical configurations and/or installation options.
If sysinstall is run interactively, that is to say in the default manner, it will bring up a main menu which contains a "load config file" option. Selecting this option will prompt for the name of a script file which it then will attempt to load from a DOS or UFS formatted floppy.
Each command line argument is treated as a script directive when sysinstall is run in multi-user mode. Execution ends either by explicit request (e.g. calling the shutdown directive), upon reaching the end of the argument list or on error.
/usr/sbin/sysinstall _ftpPath=ftp://ziggy/pub/ mediaSetFTP configPackages
Would initialize sysinstall for FTP installation media (using the server ziggy) and then bring up the package installation editor, exiting when finished.
Select which routing daemon you wish to use, potentially loading any required 3rd-party routing daemons as necessary.
can be set to the name of the desired routing daemon, e.g. "routed" or "gated", otherwise it is prompted for.
Configure host as an NFS server.
Configure host as a user of the Network Time Protocol.
The flags to ntpdate(8), that is to say the name of the server to sync from.
Configure host to support PC NFS.
The name of the PCNFSD package to load if necessary (defaults to hard coded version).
Bring up the interactive package management menu.
Add users and/or groups to the system.
Invokes the disk partition (MBR) editor.
The disk geometry, as a cyls/heads/sectors formatted string. Default: no change to geometry.
Set to disk partitioning type or size, its value being free in order to use only remaining free space for .Fx , all to use the entire disk for .Fx but maintain a proper partition table, existing to use an existing .Fx partition (first found), exclusive to use the disk in "dangerously dedicated" mode or, finally, somenumber to allocate somenumber blocks of available free space to a new .Fx partition. Default: Interactive mode.
is set to one of boot to signify the installation of a boot manager, standard to signify installation of a "standard" non-boot MGR DOS MBR or none to indicate that no change to the boot manager is desired. Default: none.
If set, bring up the interactive disk partition editor.
Note: Nothing is actually written to disk by this function, an explicit call to diskPartitionWrite being required for that to happen.
Causes any pending MBR changes (typically from the diskPartitionEditor function) to be written out.
Invokes the disk label editor. This is a bit trickier from a script since you need to essentially label everything inside each .Fx (type 0xA5) partition created by the diskPartitionEditor function, and that requires knowing a few rules about how things are laid out. When creating a script to automatically allocate disk space and partition it up, it is suggested that you first perform the installation interactively at least once and take careful notes as to what the slice names will be, then and only then hardwiring them into the script.
For example, lets say you have a SCSI disk on which you have created a new .Fx partition in slice 2 (your DOS partition residing in slice 1). The slice name would be da0s2 for the whole .Fx partition ( da0s1 being your DOS primary partition). Now lets further assume that you have 500MB in this partition and you want to sub-partition that space into root, swap, var and usr file systems for .Fx . Your invocation of the diskLabelEditor function might involve setting the following variables:
"da0s2-1=ufs 40960 /"
A 20MB root file system (all sizes are in 512 byte blocks).
"da0s2-2=swap 131072 /"
A 64MB swap partition.
"da0s2-3=ufs 204800 /var"
A 100MB /var file system.
"da0s2-4=ufs 0 /usr 1"
With the balance of free space (around 316MB) going to the /usr file system and with soft-updates enabled (the argument following the mount point, if non-zero, means to set the soft updates flag).
One can also use the diskLabelEditor for mounting or erasing existing partitions as well as creating new ones. Using the previous example again, lets say that we also wanted to mount our DOS partition and make sure that an /etc/fstab entry is created for it in the new installation. Before calling the diskLabelEditor function, we simply add an additional line:
before the call. This tells the label editor that you want to mount the first slice on /dos_c and not to attempt to newfs it (not that sysinstall would attempt this for a DOS partition in any case, but it could just as easily be an existing UFS partition being named here and the 2nd field is non-optional).
You can also set the diskInteractive variable to request that the disk label editor use an interactive dialog to partition the disk instead of using variables to explicitly layout the disk as described above.
Note: No file system data is actually written to disk until an explicit call to diskLabelCommit is made.
Writes out all pending disklabel information and creates and/or mounts any file systems which have requests pending from the diskLabelEditor function.
Resets all selected distributions to the empty set (no distributions selected).
Allows the selection of a custom distribution set (e.g. not just one of the existing "canned" sets) with no user interaction.
List of distributions to load. Possible distribution values are:
Alias for mediaSetFTP using "active" FTP transfer mode.
Variables: Same as for mediaSetFTP.
Alias for mediaSetFTP using "passive" FTP transfer mode.
Variables: Same as for mediaSetFTP.
Alias for mediaSetFTP using an HTTP proxy.
Variables: See mediaSetFTP, plus
The proxy to use (host:port) (non-optional).
Select an existing UFS partition (mounted with the label editor) as the installation media.
full /path to directory containing the .Fx distribution you are interested in.
The name of the host being installed (non-optional).
The domain name of the host being installed (optional).
The default router for this host (non-optional).
Which host interface to use ( ed0 or ep0, for example. Non-optional).
If set, bring up the interactive network setup form even if all relevant configuration variables are already set (optional).
The IP address for the selected host interface (non-optional).
The netmask for the selected host interface (non-optional).
full hostname:/path specification for directory containing the .Fx distribution you are interested in.
The username to log in as on the ftp server site. Default: ftp
The password to use for this username on the ftp server site. Default: user@host
Can be used to set the verbosity of cpio extractions to low, medium or high.
Interactively get the user to specify some type of media.
Invoke the interactive options editor.
Try to fetch and add a package to the system (requires that a media type be set),
The name of the package to add, e.g. bash-1.14.7 or ncftp-2.4.2.
Invoke the interactive group editor.
Invoke the interactive user editor.
Stop the script and terminate sysinstall.
Execute an arbitrary command with system(3)
The name of the command to execute. When running from a boot floppy, very minimal expectations should be made as to what is available until/unless a relatively full system installation has just been done.
Configure a network device.
Variables: Same as for mediaSetFTP except that _ftpPath is not used.
A text file of properties, listed one per line, that describe the contents of the media in use. The syntax for each line is simply "property = value". Currently, only the following properties are recognized.
This property should be set to the .Fx version on the current media volume. For example, ""CD_VERSION = 5.3"".
This property should be set to the architecture of the contents on this volume. This property is normally only used with .Fx products that contain CDs for different architectures, to provide better error messages if users try to install Alpha packages on an i386 machine. For example, ""CD_MACHINE_ARCH = alpha"".
In a multi-volume collection (such as the .Fx 4-CD set), the ports/INDEX file on each disc should contain the full package index for the set. The last field of the INDEX file denotes which volume the package appears on, and the CD_VOLUME property here defines the volume ID of the current disc.
The package index file. Each package is listed on a separate line with additional meta-data such as the required dependencies. This index is generated by ""make index"" from the ports(7) collection. When multi-volume support is enabled, an additional field should be added to each line indicating which media volume contains the given package.
For information about building a full release of .Fx , please see release(7).