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:
Note that /unix is linked to /stand/unix, or whichever kernel was actually booted.
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.
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.)