mksas(8)mksas(8)NAMEmksas - Builds a network-bootable Standalone System (SAS) kernel
SYNOPSIS
/usr/sys/bin/mksas [-a addfile_list] [-C] [-c config_file] [-h] [-m
disk_partition |mfs] [-O output_directory] [-r free_space] [-s
source_path] [-S service_file] [-t disk_tmp_space] [-V]
OPTIONS
The mksas utility builds a Standalone System (SAS) kernel capable of
booting across a network. Such a kernel might be used on a remote disk‐
less system. To run the mksas utility, specify at least the following
options: In command mode you need only specify the following minimum
options: The -c option, specifying a configuration file in
/usr/sys/conf. The -m option, specifying mfs or a disk partition. In
interactive mode you need specify only the mksas command.
The command options are as follows: Specifies a list of additional
files to include in the target network-bootable kernel.
The mksas utility automatically selects the minimum set of files
required to build a kernel that will boot to single user mode.
This set of files is known as the miniroot file system. Use the
-a option to include files you want in the target kernel. For
example, the default miniroot includes the ed line editing util‐
ity, but does not include the vi screen editor. If you want the
vi editor as a user option in your network-bootable kernel, you
must add it and its dependencies, for example, libcurses.so, to
the addfile_list.
The addfile_list argument specifies an absolute path name (such
as /usr/tmp/addfile_list) to a text file containing the files
that you want to add. Entries in the addfile_list specify one
file on every line. Refer to the DESCRIPTION section for a
description of the syntax.
If any entries in the addfile_list are illegal, or point to
missing files and links an error message is displayed when you
run the mksas utility. After such an error the mksas utility
exits without building a target kernel. The error message pro‐
vides information on which file or link caused the error,
enabling you to debug your addfile_list.
Each file that you add to the addfile_list increases the size of
the target network-bootable kernel. When you have created your
addfile_list, use the -C option to verify the size of the target
kernel. Specifies which kernel configuration file the mksas
utility uses during the build. By default, configuration files
are located in the /usr/sys/conf directory. The kernel configu‐
ration file defines the run time behavior and is used to build
the network-bootable kernel. Enables you to calculate the space
used by the miniroot file system contained in the network-
bootable kernel. When you specify the -C option, the mksas
utility does not automatically build a kernel. It processes
all the files listed in your addfile_list and the default mini‐
root entries, and verifies the entries to ensure that they are
correct. It then calculates the size of the miniroot, which is
displayed in megabytes as follows: The estimated size of the
miniroot is NNN MB Displays the command usage help for the mksas
command. Specifies how the mksas utility must build the mini‐
root file system. The options are as follows: mfs - This option
uses the mfs utility to build the miniroot files system in vir‐
tual memory. Use this option only if you have sufficient virtual
memory available. For example: # /usr/sys/bin/mksas -m mfs
disk_partition - This option calls the newfs utility to build
the miniroot file system on disk. For example: #
/usr/sys/bin/mksas -m dsk0e
Enables you to specify an output location where the SAS kernels
are put. Specifies the amount of free space to reserve in the
target network-bootable kernel for use at run time. Replace N
with an integer indicating the free space to reserve in the
miniroot, in megabytes or in kilobytes
For example, if you want to reserve 10 megabytes of free space
in the target kernel, specify this option as follows: #
/usr/sys/bin/mksas -r 10M # /usr/sys/bin/mksas -r 100K Specify a
different source path for the files listed in the addfile_list
(see the -a option). By default, the source path is the root
directory (/). The specified source path is then prefixed to
the entries in your addfile_list. You might use this option to
specify source files from a different source tree.
For example the following command option instructs the mksas
utility to use the directory /sas_build as a source: #
/usr/sys/bin/mksas -s /sas_build
Suppose your addfile_list file contained an entry for
/usr/ucb/vi and you specify the directory /sas_build as a
source. The mksas utility attempts to find the file named
/sas_build/usr/ucb/vi instead. Enables you to create a tar file
for debugging purposes containing the following: The disk-
bootable standalone kernel. A tar file containing the file sys‐
tem image. The log file, /var/adm/mksas.date.log. By default
the tar file is named /usr/sys/bin/mksas.date.tar For example,
mksas.0112041155.tar. The addfile_list file that you specified.
No debugging is performed during this operation, it only gathers
the requisite files into a convenient package for future analy‐
sis. Specifies the location of temporary workspace. By default,
the mksas utility creates temporary files in the /usr file sys‐
tem.
In the following example, the temporary files are created at
/mnt/mksas_tmp: # /usr/sys/bin/mksas -t /mnt/mksas_tmp Displays
the version information for the mksas command.
DESCRIPTION
Use the mksas utility to build a network-bootable Standalone System
(SAS) kernel. Only specific system configurations and types of proces‐
sor can support network booting.
The network-bootable kernel has a built-in memory file system (mfs),
which contains the minimum commands, files, and directories needed to
boot a system to the desired run level. This minimal set of files is
referred to as the miniroot file system. The default entries taken by
mksas only allow you to boot to single user mode. You must have supe‐
ruser privileges to use the mksas utility.
To prepare to create a network-bootable kernel using the mksas utility,
gather the following information and resources: The name of a kernel
configuration file in the /usr/sys/conf directory. The file system to
use to create the miniroot. Your options are as follows: On disk -
Identify an available disk partition (for example, dsk2e). You can use
the diskconfig to examine disk partitions and identify a free parti‐
tion. In virtual memory - If you have adequate virtual memory, you can
specify a memory file system (mfs). If you choose mfs, the mksas util‐
ity mounts the memory file system on /var/tmp/mfsmnt$$. To hold the mfs
image before merging it into the kernel, the mksas utility creates
another memory file system and mounts it on /var/adm/procprod. An
addfile_list - This is a text file listing any additional files that
you want to include in the network-bootable kernel. Each line in the
file must obey the following syntax rules, with each field separated by
a tab character or a space: c (copylist) - Specifies a source and des‐
tination path to a binary or a data file . This enables you to copy
individual source files to specific destinations in the miniroot. c
source destination
The source and destination are defined as follows: The source
field specifies the path to a file that exists on the current
system, such as /usr/ucb/vi. The destination field specifies
the path to the file on the target network-bootable kernel, such
as /usr/maint_tools/vi. For example:
c /etc/.new..svc.conf /etc/svc.conf
Copylist entries in the addfile_list must not specify a path
that has two consecutive slashes (//). You can only specify reg‐
ular files and directories. Pipes, symbolic links, and block
devices are not allowed. d (directory) - Specifies the directo‐
ries to be created in the miniroot. For example: d /etc h -
Specifies a hard link. For example: h /sbin/tar /sbin/pax
Which means that /sbin/pax is a hard link to /sbin/tar. s -
Specifies a soft (symbolic) link. s /usr/bin /bin
Which means that /bin is a soft link to /usr/bin.
See the EXAMPLES section for an example of an addfile_list.
To create the network-bootable kernel, the mksas utility copies the
/usr/sys/conf/SYSTEM_NAME configuration file to /usr/sys/conf/SYS‐
TEM_NAME.BOOTABLE and modifies the configuration file as follows:
config vmunix root on md pseudo-device memd 38000
These modifications indicate that a memory file system of 38000
512-byte blocks is configured.
After modifying the configuration file, the mksas utility does the fol‐
lowing: Builds a kernel using the modified configuration file. Popu‐
lates the miniroot file system. Merges the miniroot file system with
the new kernel. Writes the network boot information (sboot) on the
merged kernel. The mksas utility creates two versions of the stand‐
alone kernel as follows: A network-bootable kernel, mksas.kernel. A
disk-bootable kernel, kernel.mksas.
Both kernels are saved in the current working directory.
Both kernels use the following files from the /usr/lib/sabt/etc direc‐
tory: inittab - The system initialization file to boot to single-user
mode. fstab - The file system mount commands. profile - The root
account profile.
When you invoke mksas, all messages and errors are automatically logged
to the /var/adm/mksas.date.log file. The date is specified in the for‐
mat year:month:day:hour:minute. For example,
/var/adm/mksas.200110111746.log.
DEFAULT FILES
If you do not specify an addfile_list, only the following files are
included in the miniroot: The following default entries are included in
the miniroot: /shlib /shlib /dev/MAKEDEV /dev /etc/disktab
/etc/disktab /etc/.new..passwd /etc/passwd /etc/group /etc/group
/etc/protocols /etc/protocols /etc/services /etc/services /etc/svc.conf
/etc/svc.conf /etc/sia/.new..matrix.conf /etc/sia/.new..matrix.conf
/etc/sia/matrix.conf /etc/sia/matrix.conf /etc/sia/siainitgood
/etc/sia/siainitgood /etc/magic /etc /etc/securettys /etc /etc/ddr.db
/etc /etc/ddr.dbase /etc /etc/gen_databases /etc /etc/sysconfigtab /etc
/sbin/chmod /sbin /sbin/chown /sbin /sbin/umount /sbin /sbin/sync
/sbin /sbin/cp /sbin /sbin/ps /sbin /sbin/dd /sbin /sbin/ed /sbin
/sbin/ls /sbin /sbin/ln /sbin /sbin/expr /sbin /sbin/grep /sbin
/sbin/init /sbin /sbin/disklabel /sbin /sbin/fsck /sbin /sbin/mkdir
/sbin /sbin/mknod /sbin /sbin/mount /sbin /sbin/mount_mfs /sbin
/sbin/mv /sbin /sbin/newfs /sbin /sbin/rm /sbin /sbin/sh /sbin
/sbin/stty /sbin /sbin/halt /sbin /sbin/df /sbin /sbin/shutdown /sbin
/sbin/cat /sbin /sbin/sleep /sbin /sbin/date /sbin /sbin/tee /sbin
/sbin/sysconfig /sbin /sbin/ddr_config /sbin /sbin/reboot /sbin
/sbin/dsfmgr /sbin /sbin/loader /sbin /sbin/hostname /sbin
/sbin/ifconfig /sbin /sbin/stty /sbin/STTY /sbin/dn_setup /sbin
/sbin/kill /sbin /usr/share/sysman/bin/ksmconfig /sbin /usr/sbin/lmf
/sbin /usr/lib/sabt/etc/profile /.profile /usr/lib/sabt/etc/fstab /etc
/usr/lib/sabt/etc/inittab /etc The following default directories are
created: /cluster/members/member0 /etc /etc/sia /mnt /sbin /tmp /shlib
/var/tmp /usr/tmp
The following hard and soft links are created: HARD LINKS sbin/newfs
sbin/mfs
SOFT LINKS usr/bin bin
RETURN VALUES
Success. An error occurred.
RESTRICTIONS
The following restrictions apply: The maximum size of the network-
bootable kernel is limited to 90MB. This size limit is imposed by the
console firmware. The maximum size of the miniroot is limited to 75MB.
The mksas utility expects a custom kernel (/vmunix), to be on the host.
MESSAGES
You can use the mksas utility in either command or interactive mode.
The following program listing provides a typical interactive session.
You have started mksas as follows :
/usr/sys/bin/mksas
SELECTING A KERNEL CONFIGURATION FILE
The kernel configuration file, located in the /usr/sys/conf directory,
defines the run-time behavior of the kernel. The mksas utility uses
this file to build the SAS kernel. You must specify which kernel con‐
figuration file to use.
Enter the name of the kernel configuration file [CTG004]:
The configuration file is CTG004
CONFIGURATION FILE. OK ----------------------
VERIFYING DEVICE ----------------
SELECTING MFS FILE SYSTEM OPTION
You can build the miniroot file system on a memory file system(mfs) to
save space on disk. A mfs file system is a UFS file system in virtual
memory.
Answer yes if you want to create the miniroot file system in memory.
Answer no if you want to create the miniroot file system on disk.
Do you want to use a MFS file system? (y/n) [Y]:
USING MEMORY FILESYSTEM
DEVICE OK ---------
Only default entries will be taken into the miniroot
Processing inventories to be added to the miniroot
--------------------------------------------------
Entry no: 1 -> /shlib /shlib Entry no: 2 -> /dev/MAKEDEV /dev Entry
no: 3 -> /etc/disktab /etc/disktab . . < list of files truncated> .
Entry no: 66 -> /var/adm/lmf/LURT /var/adm/lmf/LURT
The estimated size of the miniroot is 13.6 MB
---------------------------------------------
Building vmunix...
Moving the new kernel to /
Creating memory resident file system to populate miniroot
Populating miniroot Copying /shlib Copying /mdec Copying /dev/MAKEDEV .
. <list of files truncated> . Copying /var/adm/lmf/LURT Creating
Hardlinks in the miniroot Linking sbin/mfs to sbin/newfs Creating
Softlinks in the miniroot Linking bin to usr/bin Creating device files
in the miniroot Creating symbol table information for kloadsrv Procprod
in progress... Getting copy of kernel... Merging file system into
kernel... Merging sboot into kernel... pmerge sboot into kernel...
performing dd... 1+0 records in 1+0 records out performing cat...
deleting /usr/sys/bin/vmunix.boot.241281... Moving /usr/sys/bin/vmu‐
nix.tmp.241281 to //mksas.kernel smoothsync_age: reconfigured Unmount‐
ing the filesystem on /var/tmp/procprod
mksas have built the SAS kernel successfully
SAS kernel can be found at / ----------------------------
# ls -l mksas.kernel -rwxr-xr-x 1 root system 21585264 Jan 11
14:11 mksas.kernel
The following messages are displayed during a kernel build session.
COMMAND PROMPTS
In an interactive session the following prompts are displayed: SELECT‐
ING MFS FILE SYSTEM OPTION You can build the miniroot file system on a
memory file system (mfs) to save space on disk. A mfs file system is a
UFS file system in virtual memory. Answer yes if you want to create
the miniroot file system in memory. Answer no if you want to create
the miniroot file system on disk.
Do you want to use a MFS file system? (y/n)
Enter y (yes) or n (no). If you answer no, the mksas utility
prompts you to enter a disk partition. SELECTING A DISK PARTI‐
TION You must specify the disk partition where the miniroot file
system is to reside. The minimum size required is estimated_size
blocks (512 bytes per block).
Enter the disk partition (for example, dsk2e)
Enter the name of a disk partition in the format dskNx. Use the
diskconfig command to identify available disk partitions. The
mksas utility the prompts you to enter an optional alternate
source. Do you want to enter the alternate source (y/n):
Enter y (yes) or n (no ). If yes, then the mksas utility prompts
you to enter a path name to the alternate source. Do you want
to enter an inventory file (y/n):
Enter y (yes) or n (no). If yes, then the mksas utility prompts
you to supply a path name to the inventory file. Do you want to
enter the free space required (y/n):
Enter y (yes) or n (no). If yes, then the mksas utility prompts
you to supply a figure for the free space in megabytes or kilo‐
bytes, such as 10M or 100K SELECTING A KERNEL CONFIGURATION FILE
/usr/sys/conf directory, defines the run-time behavior of the
kernel. The mksas utility uses this file to build the SAS ker‐
nel. You must specify which kernel configuration file to use.
Enter the name of the kernel configuration file:
Enter the name of a kernel configuration file that exists in the
/usr/sys/conf directory.
INFORMATIONAL MESSAGES
The following informational messages might be displayed during a ses‐
sion: You must specify a disk partition before proceeding.
Description: A build requires a disk partition as temporary work
space
Action: Specify a valid disk partition such as dsk10e. Direc‐
tory temp_dir does not exist, creating
Description: The temporary workspace directory you specified
using the -t option does not exist.
Action: The mksas utility automatically creates the directory
path. /usr/sys and temp_dir are in the same filesystem.
Description: The temporary directory that you specified is
located in /usr. The mksas utility ignores the -t option.
Action: Specify an alternate workspace that is located in a file
system other than the /usr file system. Only default entries
will be taken into the miniroot
Description: The mksas utility is not processing an addfile_list
because you did not specify the -a option.
Action: Only the default miniroot files are included in the
built kernel. The estimated size of the miniroot is nnn MB
Description: This is an informational message displayed by
mksas. If you specify the -C option, mksas waits for a confirma‐
tion after displaying the message.
Action: Enter y (yes) to proceed with the build or n (no) to
exit. Making an archive of path/miniroot.image.tar path/ker‐
nel.mksas /var/adm/mksas.log and addfile_list
Description:This message informs you that mksas is creating an
archive of the mentioned files for debugging.
ERROR AND WARNING MESSAGES
The following error or warning messages might be displayed during a
session: Specify a partition of the disk. Not the whole disk.
Problem: You specified a disk basename, such as dsk10 instead of
a specific disk partition, such as dsk10b.
Action: Repeat the command or session using a disk partition
name. If you want to specify a whole disk, you must ensure that
it is labeled as having an active c partition. Then, enter the
disk partition name as dskNc. Error: The inventory file speci‐
fied does not exist or is not a regular file Problem: The
addfile_list that you specified using the -a option was not
found or is not usable.
Action: Verify the location and integrity of the file and repeat
the command. You are prompted again for the addfile_list.
Invalid input config_file Problem: The kernel configuration file
that you specified using the -c option does not exist or is not
usable.
Action: Verify the location and integrity of the configuration
file and repeat the command. A configuration file specified
exists in directory, but is not readable by current process.
Problem: The kernel configuration file that you specified using
the -c option was found but is not usable.
Action: Verify the integrity of the configuration file and
repeat the command. Unable to copy config_file to /usr/sys/conf
Problem: The mksas utility was unable to copy the configuration
file that you specified (using the -c option) from its current
location to the /usr/sys/conf directory. Not enough space in
location [Needed : required_space] <==> [Available : avail‐
able_space] Problem: You specified temporary work space using
the -t option, but the space is insufficient for the build.
Action: Specify an alternate location for temporary work space.
Unable to create temp_directory Problem: You specified temporary
work space using the -t option, but the mksas utility is unable
to create a directory at the location.
Action: Verify that the location exists and check the protection
of the top level directory. Please mount /proc with: mount -t
procfs /proc /proc command and rerun mksas utility. Exiting
mksas...
Problem: You used the -m option to specify that the build should
use a memory file system (mfs). This option requires that the
/proc file system is mounted.
Action: Use the following command to mount the /proc file sys‐
tem: # mount -t procfs /proc
Then repeat the mksas command. WARNING: About to copy the same
dir over another
Problem: This is an informational message. It warns you that
your addfile_list specifies that one directory is copied over
another.
Action: No action is required unless this was not your intent.
Modify you inventory file if required and repeat the kernel
build. Warning Entry no: N Duplicated entry. The directory or
filename in the second field is already given earlier.
Problem: Your addfile_list contains duplicate source files that
are copied to a common destination. For example, if there are
two password files, /etc/passwd and /tmp/passwd and both files
have a common destination, such as /etc.
Action: This is a warning message and no action is necessary.
However, if it was not your intent that the two sources should
be copied to the common destination, update your addfile_list
and repeat the build. Error Entry no: N Directory path for
dir_or_file does not exist. Ignoring the entry Problem: A file
or directory specified in your addfile_list was not found. The
entry is ignored and the kernel build proceeds.
Action: Verify the location and integrity of the source file or
directory and update your addfile_list then rebuild the kernel.
Incorrect entry, path to ???? does not exist Problem: A desti‐
nation directory file specified in your addfile_list does not
exist. The entry is ignored and the kernel build proceeds.
Action: Verify the location and integrity of the directory and
update your addfile_list then rebuild the kernel. Error Entry
no: N has more than 2 fields.
Problem: You specified more than two fields for either a c, h,
or an s entry in your addfile_list.
Action: Correct the addfile_list entry and restart Error Entry
no: N Field1 does not exist
Problem: The source entry in the addfile_list of a type c does
not exist.
Action: Remove the line from the addfile_list or specify a valid
source file. Error Entry no: N Entry can only be a regular file
or a directory
Problem: An entry in the addfile_list specifies a path that is
not a regular file or directory.
Action: Verify the path to the file and either correct it or
remove the entry from the addfile_list. Entries cannot be pipes,
symbolic links, or block devices. Error Entry no: N two consec‐
utive slashes not valid in COPYLIST filenames
Problem: An entry in the addfile_list specifies a path that has
two consecutive slashes (//). This is not permitted in the syn‐
tax for addfile_list entries of type c (copylist).
Action: Verify the path to the file and either correct it or
remove the entry from the addfile_list. Error Entry no: N must
be absolute filename
Problem: You specified a relative (logical) path to a file in
your addfile_list, such as
Action: Edit your addfile_list to replace any relative (../)
path names with absolute path names (/dir/subdir/file). Error
Entry: N Invalid entry, Path for file does not exist
Problem: In an addfile_list c entry, the path in the destination
field does not exist.
Action: Create a d entry in your addfile_list to add the path to
the directory list. Error: Source is not a directory
Problem:A path name that you specified with the -s option is not
a directory or does not exist.
Action: Verify that the source directory exists and is usable.
Confirm the protection level and run the command again. Unable
to unmount and remove procprod_mount
Problem: This message occurs only during the cleanup operation
after a failed build. The session was unable to unmount and
remove the temporary memory file system (mfs) space at
/var/adm/procprod.
Action:Unmount the file system manually. string is invalid.
Problem: The text string that you specified as a disk partition
is invalid, possible because you made a typographical error.
Action: Specify the correct text string for a disk partition,
such as dsk45g. Partition size is not sufficient
Problem: The disk partition that you specified is of insuffi‐
cient size for the build.
Action: Specify a larger partition. Use the diskconfig command
to check partition sizes. Unable to create a UFS filesystem on
disk_partition
Problem: There is a problem with the disk partition that you
specified with the -m option. The partition is available, but
the mksas utility was unable to create a file system on the par‐
tition.
Action: Verify the disk partition and check it for errors. Disk
in use by an AdvFs domain
Disk is in use by an LSM volume
Disk in use by an UFS filesystem
Disk in use as a swap device
Problem:The partition specified is already in use.
Action: Use the diskconfig command to check available partitions
and verify that they are not already in use as a file system or
swap space. Choose a partition that is not in use. Note that
the partition does not need to contain a valid file system.
partition is not a valid disk partition.
Problem: The disk partition specified is not valid.
Action: Ensure that the string that you entered has a disk base‐
name and partition specifier, such as dsk34b. device is not a
block device
Problem: The device that you specified is not a block device,
which is a disk device capable of storing a random-access file
system. Such devices are addressed via device special files in
the /dev/disk directory.
Action: Do not specify tape or read-only devices such as CD-ROM
readers. Do not specify raw devices, which are addressed via
device special files in the /dev/rdisk directory. Error: Unable
to copy file_or_directory to /mount_point/path
Problem: The mksas utility failed to copy a source file to its
target destination. The utility prints the reason for the fail‐
ure and exits.
Action: Check the error message and correct the reason for the
failure. Error: Unable to create Softlink. Path for file does
not exist in the miniroot
Problem: The mksas utility was unable to create a soft link as
the path for the link does not exist. The utility exits and
cleans up.
Action: Verify the link specified in the addfile_list and ensure
the path to the link exists. Unable to create symbol table file
to start kloadsrv
Problem: This is a command failure and must be escalated via
your technical support organization. Unable to archive the
miniroot
Problem: You specified the -s option to create an archive but
the mksas command was unable to create the archive.
Action: Verify that there is sufficient space for the archive in
the working directory using the df command. mfs of
mount_procprod failed
Problem: This is a command failure and must be escalated via
your technical support organization. procprod failed
Problem: This is a command failure and must be escalated via
your technical support organization. KERNEL has not been built
successfully
Problem: The source kernel could not be built. This is a com‐
mand failure and must be escalated via your technical support
organization. unable to move new_kernel to ???
Problem: The kernel was successfully built, but the mksas ses‐
sion was unable to relocate it to its temporary destination. The
kernel build fails.
Action: Verify that there is sufficient space in the current
working directory. fsmrg failed...
Problem: The mksas session was unable to merge the miniroot file
system with the new kernel. This is a command failure and must
be escalated via your technical support organization. unable to
copy temp_kernel to path/kernel.mksas
Problem:The kernel was successfully built, but the mksas session
was unable to relocate it to its final destination. The kernel
build fails.
Action: Verify that there is sufficient space in the current
working directory. pmerge failed...
Problem: The mksas session was unable to merge sboot into the
new kernel. This is a command failure and must be escalated via
your technical support organization. dd failed...
Problem: A file system copy failed. This is a command failure
and must be escalated via your technical support organization.
Error: Attempt to build SAS was unsuccessful
Problem: The network-bootable kernel could not be built. This is
a command failure and must be escalated via your technical sup‐
port organization. Interrupt received by mksasOne of these trap
condition occurred. (HUP,TERM,QUIT,KILL) Exiting mksas...
Problem: The mksas process was killed by an interrupt or kill
signal such as HUP. This event occurs when the process is
killed by an event other than typing [Ctrl-C].
Action: As the kill signal might be generated by any one of a
number of events, you should restart the build. If the process
is killed again, it might be due to a lack of system resources.
Check the event logs and use the Event Manager to look for
likely causes. mksas process has been terminated by the user
Problem: This message is displayed when you intentionally kill
the mksas by typing [Ctrl-C]. Failed to make an archive of the
kernel and the miniroot
Problem: You specified the -S (service) option, but the command
fails to complete and no tar file is created. This is a command
failure and must be escalated via your technical support organi‐
zation.
EXAMPLES
The following is an example of an addfile_list, specified using the -a
option. This example file is truncated for ease of reference: DIRECTO‐
RYLIST
d /cluster/members/member0/etc d /var/cluster/members/member0/evm d
/var/cluster/members/member0/adm d /var/cluster/members/mem‐
ber0/adm/syslog.dated
COPYLIST
c /sbin/init.d /sbin c /tcb /tcb c /usr/tcb /usr c
/sbin/who /sbin
HARDLINKS
etc/sia/matrix.conf etc/sia/bsd_matrix.conf usr/bin/grep
usr/bin/egrep usr/bin/egrep usr/bin/fgrep
SOFTLINKS
s /shlib usr/shlib s ../init.d/enlogin sbin/rc0.d/K00enlogin s
../init.d/audit sbin/rc0.d/K08audit s /sbin/mv usr/sbin/mv s
../cluster/members/member0/evm/evmlog /var/evm/evmlog In the
following example, the mksas utility is invoked without any options
placing you in interactive mode. The mksas utility prompts you for all
information needed to build the network-bootable kernel: #
/usr/sys/bin/mksas In the following example, the mksas utility is
invoked with the minimum command line options: # /usr/sys/bin/mksas -c
BBC03 -m mfs In the following example, all options are specified caus‐
ing the mksas utility to build a network-bootable kernel in non-inter‐
active mode. You are not prompted for additional information: #
/usr/sys/bin/mksas -c BBC04 -a /usr/sys/bin/user_file \
-f 20M -k myconfig -m dsk0h -s /sasbuild -t /mnt/mksastmp
FILES
Provides a log of the mksas process, including command dialogs and any
error or informational messages. This log file is automatically
included in the tar file produced when the -S option is specified. The
addfile_list argument specifies an absolute path name (such as
/usr/tmp/addfile_list) to a text file containing the files that you
want to add. A tar file output when you specify the -S (debug) option.
The configuration file that you specify. If you do not specify a file,
you are prompted to supply one. The device special file name for the
disk partition that you want to use for the build. You only need to
specify the actual device name and partition, such as dsk12h. The net‐
work-bootable kernel, located in the current working directory. The
disk-bootable kernel, located in the current working directory. The
directory from which the fstab, inittab, and profile files are copied
when the disk-bootable kernel is created. The boot binary which is
merged into the network-bootable version of the kernel.
SEE ALSO
Commands: btcreate(8), diskconfig(8), fstab(4), mfs(8)newfs(8)mksas(8)
