 |
Index for
Section 8 |
|
 |
Alphabetical
listing for B |
|
 |
Bottom of
page |
|
btcreate(8)
NAME
btcreate - Builds a bootable Standalone System (SAS) kernel on tape
SYNOPSIS
/usr/sys/bin/btcreate [-a addlist_file[-d disk_tmp_space]] [-f] [-k
config_file] -mdisk_partition [-s fslist_file] [-t tape_device]
OPTIONS
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, specify at
least the -f, -k, -m, -s, -t, and -d options on the command line. To run
this utility in interactive mode, invoke the utility without any options or
a subset of the above options; you are then prompted for all or any missing
information.
-a addlist_file
Causes the btcreate utility to back up the files and directories
specified in the addlist_file to the miniroot file system. The
miniroot file system is the minimum file system required to build the
SAS kernel. If you are using the btcreate utility in non-interactive
mode, you must create this file before invoking the utility. The
addlist_file name should be absolute pathname, such as
/usr/lib/sabt/etc/addlist.
The addlist_file consists of one line for each entry. Each entry 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/local/bin/mydir /usr/local/bin/mydir
/.kshrc /.kshrc
/sbin/sort /sbin/sort
If the total size of all files and directories exceeds the size limit
of 360KB on the miniroot file system, the btcreate utility exits.
-d Enables you to specify the location of temporary workspace. If you do
not use this option, btcreate creates temporary files in the /usr
filesystem and requires up to 156000 blocks (512 bytes per block) of
disk space In the following example, the temporary files will be
created at /mnt/bt_tmp:
# ./btcreate -d /mnt/bt_tmp
-f Forces the newfs utility to create the miniroot file system without
verifying whether or not a file system exists on the partition. This
option also forces btcreate to be completely non-interactive, whether
you select mfs or disk partition for the -m option.
-k config_file
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.
-m mfs | disk_partition
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, dsk0h) 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/mfsmnt$$. If you use the mfs
option, 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 option with the
disk_partition variable to create the miniroot file system on disk.
-s fslist_file
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 before invoking the
utility. The fslist_file should be an absolute 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:
devname
Specifies the name of the disk device where the file system
resides. For example, /dev/disk/disk0a and root_domain#rootare
valid device names for UFS and AdvFS respectively.
mountpoint
Specifies where the file system is mounted. For example, the mount
point may be root (/).
type
Specifies the type of file system. Valid entries are ufs for the
UNIX File System or advfs for the Advanced File System.
-t tape_device
Causes the btcreate utility to use the tape device specified (for
example, tape0_d1).
-d Enables you to specify the location for temporary workspace. If you do
not use this option, btcreate creates temporary files in the /usr
filesystem which requires upto 156000 blocks (512 bytes per block) of
disk space, (for example, the temporary files will be created at
/mnt/bt_tmp:#./btcreate -d /mnt/bt_tmp).
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 information.
Note
To execute, the btcreate utility requires 156000 blocks (512 bytes per
block) of disk space in the /usr directory unless you use the -d
option to specify alternate temporary workspace.
To prepare for a btcreate session, have the following information
available:
· Name of the configuration file in the /usr/sys/conf directory.
· Name of the disk partition (for example, dsk2e) where the miniroot
file system is to reside. Minimum size needed on the disk is 38000
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 option, the newfs utility
asks you to confirm overwriting the partition. If you specify the -f
option, the newfs utility overwrites this partition without
prompting you for confirmation.
· Name of the tape device, for example tape0_d1, where the SAS kernel
and file systems are to reside.
· Device name, mount point, and type of each file system (UFS, AdvFS )
that you want to back up to the tape device. The following shows valid
UFS and AdvFS entries:
UFS:
/dev/disk/dsk1a / ufs
/dev/disk/dev/dsk1g /usr ufs
/dev/vol/rootdg/rootvol /ufs
AdvFS:
root_domain#root / advfs
usr_domain#usr /usr advfs
If you do not specify the -s option, the btcreate utility displays a
list of file systems to help you with your selection. If you specify
the -s option, you must create the file before starting the btcreate
utility. See the -s option for more information.
Note
Do not select swap partitions/volumes for file system backups.
· An addlist_file, if you specify the -a option, which includes files or
directories on the miniroot file system. See the -a option for more
information.
· An fslist_file, if you specify the -s option, which specifies the file
systems to back up. See the -s option for more information.
· A /usr/lib/sabt/sbin/custom_install.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 38000
These modifications indicate that a memory file system of 38000 is being
configured. The memory file system and the disk partition where the
miniroot 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_SYSTEM_NAME.BOOTABLE/vmunix to the /usr/sys/bin directory.
You also have the option to label disks using your own disklabel script.
If a customized disklabel script is not present, the btextract command will
label the disks in the usual manner. A customized disklabel script has
the following restrictions:
· It must be located in the /usr/lib/sabt/etc directory.
· It must be named custom_disklabel_file.
RETURN VALUES
0 (Zero)
Success.
>0 An error occurred.
EXAMPLES
The following examples demonstrate several methods of invoking the btcreate
utility.
1. In the following example, the btcreate utility is invoked without any
options placing you in interactive mode. The btcreate utility prompts
you for all information needed to build the SAS kernel.
# /usr/sys/bin/btcreate
2. In the following example, all options are specified causing the
btcreate utility to build the SAS kernel in non-interactive mode.
That is, the SAS kernel is built without prompting you for
information.
# /usr/sys/bin/btcreate -a /usr/lib/sabt/etc/addlist_file -f \
-k YOUR_SYSTEM_NAME -m mfs -t tape0_d1 -d /mnt/bt_tmp \
-s /usr/lib/sabt/etc/fslist_file
3. In the following example, the -a option 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 options required to run in
non-interactive mode.
# /usr/sys/bin/btcreate -f -k GOOFY -m mfs -t tape0_d1 \
-s /usr/local/bin/backup_file
4. In the following example, the -k option 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 dsk0h -t tape0_d1 -s /usr/local/bin/backup_file
FILES
/var/adm/btcreate.log
Provides a log of the btcreate process
/usr/lib/sabt/sbin/custom_install.sh
Specifies the customized shell script used to perform system
administrative tasks on the restored system image
/usr/lib/sabt/etc/custom_disklabel_file
A custom disklabel file read by btextract
RESTRICTIONS
· Only root, swap, usr and var partitions will be supported.
· Mirroring and/or stripping are not options for bootable tape
functionality.
SEE ALSO
Commands: df(1), btextract(8), disklabel(8), doconfig(8), dump(8),
newfs(8), mkfdmn(8), mkfset(8), pmerge(8), vdump(8)
|
Index for
Section 8 |
|
|
Alphabetical
listing for B |
|
 |
Top of
page |
|