Explanation/Reference:
Explanation:
Etherstubs are pseudo ethernet NICs which are managed by the system administrator. You can create VNICs over etherstubs instead of over physical links. VNICs over an etherstub become independent of the physical NICs in the system. With etherstubs, you can construct a private virtual network that is isolated both from the other virtual networks in the system and from the external network. For example, you want to create a network environment whose access is limited only to your company developers than to the network at large. Etherstubs can be used to create such an environment.
Note: Oracle Solaris 11 introduces a new and powerful network stack architecture which includes:
* Networking virtualization with virtual network interface cards (VNICs) and virtual switching (etherstubs)
* Tight integration with zones
* Network resource management - efficient and easy to manage integrated quality of service (QoS) to enforce bandwidth limit on VNICs and traffic flows

If the boot environment is unbootable,it is marked with an exclamation point (!) in the Active column in the beadm list output.
The beadm command restricts actions on unbootable boot environments as follows:
You cannot activate an unbootable boot environment. (B)
You cannot destroy a boot environment that is both unbootable and marked as active on reboot.
You cannot create a snapshot of an unbootable boot environment.
You cannot use an unbootable boot environment or boot environment snapshot with the -e option of beadm create.
You cannot rename an unbootable boot environment. (C)

Oracle Solaris provides predefined rights profiles. These profiles, listed in the /etc/security/prof_attr, can be assigned by the root role to any account. The root role is assigned all privileges and all authorizations, so can perform all tasks, just as root can when root is a user.
To perform administrative functions, you open a terminal and switch the user to root. In that terminal, you can then perform all administrative functions.
$ su - root
Password: Type root password
#
When you exit the shell, root capabilities are no longer in effect.

You can change an inactive boot environment into an active boot environment. Only one boot environment can be active at a time. The newly activated boot environment becomes the default environment upon reboot.
How to Activate an Existing Boot Environment
1. Use the following command to activate an existing, inactive boot environment:
beadm activate beName
beName is a variable for the name of the boot environment to be activated.
Note the following specifications.
beadm activate beName activates a boot environment by setting the bootable pool property, bootfs, to the value of the ROOT dataset of the boot environment that is being activated.
beadm activate sets the newly activated boot environment as the default in the menu.lst file.
2. Reboot.
The newly activated boot environment is now the default on the x86 GRUB menu or SPARC boot menu.

Explanation/Reference:
Explanation:
From the output exhibit we can deduce that the shell has id 15156.
It has spawned three subprocesses:
grep: id 15166
ps -aef 15165
The remaining 15163 must be the subshell (see note below).
This is the id of the process which should be terminated.