Skip Navigation Links | |
Exit Print View | |
Creating and Administering Oracle Solaris 11.1 Boot Environments Oracle Solaris 11.1 Information Library |
1. Introduction to Managing Boot Environments
3. Creating Boot Environments and Snapshots
4. Administering Boot Environments
Listing Existing Boot Environments and Snapshots
Viewing Boot Environment Specifications
Viewing Specifications in Machine-Parsable Output
Viewing Snapshot Specifications
Changing the Default Boot Environment
Mounting and Updating an Inactive Boot Environment
How to Mount and Update a Boot Environment
You can create additional private datasets for an existing boot environment by using the zfs command to create a dataset located hierarchically under the root dataset of the boot environment.
This new dataset will not be automatically cloned to existing, associated zone boot environments. Also, because the new dataset is under the root dataset of a boot environment, the new dataset will be private to that boot environment. The new dataset will not be a shared dataset.
Once this new dataset has been created under the root dataset, if you then clone that whole boot environment, the new dataset would be included in the new, cloned boot environment.
Note - When creating additional datasets for boot environments, the canmount ZFS property of the dataset must be set to noauto. The dataset's mountpoint is inherited from the boot environment's root dataset and hence should be mounted at /myfs when this boot environment is in use.
For example, to create a new, non-shared dataset mounted at /myfs for the boot environment, BE1:
# zfs create -o canmount=noauto rpool/ROOT/BE1/myfs
For further information, see the zfs(1M) man page.