Starting and stopping the system

The stand slice

The bootable operating system unix is found in the stand slice. This slice has the boot filesystem (bfs) defined on it and contains all the bootable programs and data files used during the boot procedure. It can be identified, using the prtvtoc(1M) command, as the partition labeled V_STAND. The bfs defined on this partition is mounted by default as /stand.

The contents of /stand include the following:

This is the bootable operating system. When the boot program is loaded, it searches for and loads this program into memory and then passes control to it. Once the bootable operating system is running, various system daemons are started, and the system enters one of several system states, sometimes called ``init states.'' (See the description of /etc/inittab under ``Early initialization''.) You can boot from another operating system kernel using the interactive boot feature to redefine the KERNEL boot parameter: see boot(4) for details.

Note that /unix is linked to /stand/unix, or whichever kernel was actually booted.

Contains the old bootable operating system saved when a new kernel is built.

Contains boot parameter definitions.

Contains boot message parameter definitions.

Contains a graphical image of the bootstrap logo.

Contains the help message output by the BCP when you use the commands ? or help.

Contains a copy of the resource manager database.

Contains a copy of the old resource manager database, saved when a new kernel is built.

Contain the bootstrap loadable modules (BLMs).

In the delivered system, the stand slice contains a filesystem of type bfs; this boot filesystem is mounted as /stand by default.

The boot filesystem is a flat filesystem with only one directory. You can copy and move regular files to and from a boot filesystem, and use filesystem commands such as mount(1M), umount(2), and fsck(1M), but you cannot make directories or create other special files. We recommend you use this filesystem only for boot-related and configuration-related files.

If you want, you can use mkfs to create bfs-type filesystems on other disk partitions. (See ``Managing filesystem types'' and mkfs(1M) for more information.) Having multiple boot filesystems on one or more partitions is particularly useful in an operating system development environment.

CAUTION: You must define bfs-type filesystems only on hard disk partitions with a tag of stand. Do not make bfs-type filesystems on any other devices. Similarly, do not make a filesystem of any type other than bfs in a partition with a tag of stand. Doing so may render your computer unbootable. (See ``Managing filesystem types'', mkfs(1M), and prtvtoc(1M) for more information.)

The maximum size of a bfs filesystem is 128MB.

Although any disk can be made bootable, only one disk can be booted on powerup, and that is the default boot disk defined in non-volatile random-access memory (NVRAM). If you define multiple stand slices on the default boot disk, the one used during a reboot or powerup will be from the active partition.

The file /etc/vfstab contains the pathname of the stand slice to be mounted in single-user and multi-user states; it is used during configuration of a new operating system on powerup or reboot. This should always be the one defined on the lowest numbered partition on your default boot disk. The device name has the form /dev/dsk/c0b0t0d0sS, where S is the slice ID. (See intro(7) for details on device name notation.)

Next topic: Starting (rebooting) your system
Previous topic: Operations on the boot slice

© 2004 The SCO Group, Inc. All rights reserved.
UnixWare 7 Release 7.1.4 - 22 April 2004