btcreate - Builds a bootable Standalone System (SAS) kernel on tape
/usr/sys/bin/btcreate [-a addlist_file] [-f] [-k config_file] [-m mfs | disk_partition] [-s fslist_file] [-t tape_device]
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, 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 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
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.
To execute, the btcreate utility requires 156000 blocks (512 bytes per block) of disk space in the /usr directory.
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, rz2e) where the miniroot 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.
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 reside. 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:
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_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.
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 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.
The btcreate utility returns zero (0) on success and a number greater than zero (0) on error.
The following examples demonstrate several methods of invoking the btcreate utility. In the following example, the btcreate utility is invoked 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 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 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 required 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/local/bin/backup_file
Provides a log of the btcreate process Specifies the customized shell script used to perform system administrative tasks on the restored system image
Utilities: df(1), btextract(8), disklabel(8), doconfig(8), dump(8), newfs(8), mkfdmn(8), mkfset(8), pmerge(8), vdump(8) delim off