Manual Page Result
0
Command: btcreate | Section: 8 | Source: Digital UNIX | File: btcreate.8.gz
btcreate(8) System Manager's Manual btcreate(8)
NAME
btcreate - Builds a bootable Standalone System (SAS) kernel on tape
SYNOPSIS
/usr/sys/bin/btcreate [-a addlist_file] [-f] [-k config_file] [-m mfs |
disk_partition] [-s fslist_file] [-t tape_device]
FLAGS
The btcreate utility builds a bootable Standalone System (SAS) kernel
on UFS and AdvFS file systems only. It supports non-interactive and
interactive modes. To run this utility in non-interactive mode, spec-
ify at least the -f, -k, -m, -s, and -t flags on the command line. To
run this utility in interactive mode, invoke the utility without any
flags or a subset of the above flags; you are then prompted for all or
any missing information.
Causes the btcreate utility to back up the files and directories speci-
fied in the addlist_file to the miniroot file system. The miniroot
file system is the minimum file system required to build the SAS ker-
nel. If you are using the btcreate utility in non-interactive mode,
you must create this file before invoking the utility. The ad-
dlist_file name should be absolute pathname, such as
/usr/lib/sabt/etc/addlist
The addlist_file consists of one line for each entry. Each en-
try has two fields separated by a space or tab.
The first field specifies the absolute pathname of the file or
directory on the currently running system. If the file is not
found, the btcreate utility exits. The second field specifies
the absolute pathname of the file or directory on the miniroot
file system.
A sample addlist_file follows: /sbin/kill /sbin /usr/lo-
cal/bin/mydir /usr/local/bin/mydir /.kshrc /.kshrc /sbin/sort
/sbin/sort If the total size of all files and directories ex-
ceeds the size limit of 360KB on the miniroot file system, the
btcreate utility exits. Forces the newfs utility to create the
miniroot file system without verifying whether or not a file
system exists on the partition. This flag also forces btcreate
to be completely non-interactive, whether you select mfs or disk
partition for the -m option. Causes the btcreate utility to use
the specified kernel configuration file located in the
/usr/sys/conf directory. The kernel configuration file defines
the run-time behavior of the kernel and is used to build the SAS
kernel. Causes the btcreate utility to create the miniroot file
system on a memory file system (mfs) using the mfs utility or on
the specified disk partition (for example, rz0h) using the newfs
utility. The miniroot file system is the minimum file system
required to build the SAS kernel.
A memory file system (mfs) is a UFS file system which resides in
virtual memory. By creating the miniroot file system in virtual
memory, you can save disk space. The mfs utility uses 30720
(15MB) of memory using swap space as the special device. The
btcreate command mounts the memory file system on /var/tmp/mf-
smnt$$. If you use the mfs flag, the btcreate utility creates
another memory file system that is 17.45MB which is mounted on
the /var/tmp/procprod directory.
If you have sufficient disk space, use the -m flag with the
disk_partition variable to create the miniroot file system on
disk. Causes the btcreate utility to back up the file systems
specified in fslist_file to tape. If you are using the btcreate
utility in non-interactive mode, you must create this file be-
fore invoking the utility. The fslist_file should be an ab-
solute pathname, such as: /usr/lib/sabt/etc/fslist
The fslist_file consists of one line for each file system you
want to back up. Each line contains three fields separated by a
space as follows:
devname mountpoint type
In the previous example: Specifies the name of the disk device
where the file system resides. For example, /dev/rz0a and
root_domain#root, are valid device names for UFS and AdvFS re-
spectively. Specifies where the file system is mounted. For
example, the mount point may be root (/). Specifies the type of
file system. Valid entries are ufs for the UNIX File System or
advfs for the Advanced File System. Causes the btcreate utility
to use the tape device specified (for example, nrmt0h).
DESCRIPTION
Use the btcreate utility to build a bootable Standalone System (SAS)
kernel on tape. The SAS kernel has a built-in memory file system (mfs),
which contains the minimum commands, files, and directories needed to
restore the system image. This is referred to as the miniroot file
system. The btcreate utility supports UFS and AdvFS file systems only.
You must have superuser privileges to use this utility. After creating
the SAS kernel, you can install the customized operating system using
the btextract utility. See the btextract reference page for more in-
formation.
Note
To execute, the btcreate utility requires 156000 blocks
(512 bytes per block) of disk space in the /usr direc-
tory.
To prepare for a btcreate session, have the following information
available: Name of the configuration file in the /usr/sys/conf direc-
tory. Name of the disk partition (for example, rz2e) where the mini-
root file system is to reside. Minimum size needed on the disk is
30720 blocks (512 bytes per block). This disk partition should not be
mounted when btcreate is executed.
Note
The btcreate utility invokes the newfs utility to create the
partition. If you do not specify the -f flag, the newfs utility
asks you to confirm overwriting the partition. If you specify
the -f flag, the newfs utility overwrites this partition without
prompting you for confirmation. Name of the tape device, for
example nrmt0h, where the SAS kernel and file systems are to re-
side. Device name, mount point, and type of each file system
(UFS or AdvFS) that you want to back up to the tape device. The
following shows valid UFS and AdvFS entries:
UFS:
/dev/rz1a / ufs
/dev/rz1g /usr ufs
AdvFS:
root_domain#root / advfs
usr_domain#usr /usr advfs If you do not specify the -s
flag, the btcreate utility displays a list of file systems to
help you with your selection. If you specify the -s flag, you
must create the file before starting the btcreate utility. See
the -s flag for more information.
Note
Do not select swap partitions for file system
backups.
An addlist_file, if you specify the -a flag, which includes
files or directories on the miniroot file system. See the -a
flag for more information. An fslist_file, if you specify the
-s flag, which specifies the file systems to back up. See the
-s flag for more information. A /usr/lib/sabt/sbin/custom_in-
stall.sh script, if you want to customize the restored system
image. Both interactive and non-interactive users must create
this file before invoking the btcreate utility. The file must
be written in the Bourne shell language (sh1) as it is the only
shell provided on the miniroot file system.
The btcreate utility copies the custom_install.sh file on to
tape and places it in the sbin directory on the miniroot file
system. The btextract utility invokes the custom_install.sh
script before exiting.
To create the SAS kernel, the btcreate utility copies the
/usr/sys/conf/YOUR_SYSTEM_NAME configuration file to
/usr/sys/conf/YOUR_SYSTEM_NAME.BOOTABLE and modifies it as follows:
config vmunix root on md pseudo-device memd 30720 These
modifications indicate that a memory file system of 30720 is being con-
figured. The memory file system and the disk partition where the mini-
root file system reside are equivalent in size.
After modifying the configuration file, the btcreate utility executes
the doconfig command and moves the bootable kernel, /usr/sys/YOUR_SYS-
TEM_NAME.BOOTABLE/vmunix to the /usr/sys/bin directory.
RETURN VALUES
The btcreate utility returns zero (0) on success and a number greater
than zero (0) on error.
EXAMPLES
The following examples demonstrate several methods of invoking the bt-
create utility. In the following example, the btcreate utility is in-
voked without any flags placing you in interactive mode. The btcreate
utility prompts you for all information needed to build the SAS kernel.
# /usr/sys/bin/btcreate In the following example, all flags are speci-
fied causing the btcreate utility to build the SAS kernel in non-inter-
active mode. That is, the SAS kernel is built without prompting you
for information. # /usr/sys/bin/btcreate -a /usr/lib/sabt/etc/ad-
dlist_file -f \ -k YOUR_SYSTEM_NAME -m mfs -t nrmt0h \ -s
/usr/lib/sabt/etc/fslist_file In the following example, the -a flag is
excluded from the command line. The btcreate utility assumes you are
not adding files or directories. The SAS kernel is built without
prompting you for information as you specified the minimum flags re-
quired to run in non-interactive mode. # /usr/sys/bin/btcreate -f -k
GOOFY -m mfs -t nrmt0h \ -s /usr/local/bin/backup_file In the following
example, the -k flag is excluded from the command line. The btcreate
utility places you in interactive mode and prompts you for any options
that you did not specify. # /usr/sys/bin/btcreate -a
/usr/sys/bin/user_file -f \ -m rz0h -t nrmt0h -s /usr/lo-
cal/bin/backup_file
FILES
Provides a log of the btcreate process Specifies the customized shell
script used to perform system administrative tasks on the restored sys-
tem image
RELATED INFORMATION
Utilities: df(8), btextract(8), disklabel(8), doconfig(8), dump(8),
newfs(8), mkfdmn(8), mkfset(8), pmerge(8), vdump(8) delim off
btcreate(8)