Get 1z0-580 Dumps : Verified Oracle Solaris 11 Installation and Configuration Essentials

You can display information about snapshots, boot environments, and datasets that were created by the beadm command by using the beadm list subcommand. The beadm list command output also displays boot environments that are created by the pkg command.

Viewing Boot Environment Specifications

The values for the Active column are as follows:

• R – Active on reboot.
• N – Active now.
• NR – Active now and active on reboot.
• “-” – Inactive.
• “!” – Unbootable boot environments in a non-global zone are represented by an exclamation point.

The following example displays full information for the BE5 boot environment.

The Solaris 11 release in November 2011 only contains GNOME as a full desktop.

Incorrect:

Not A: The Common Desktop Environment (CDE) is a desktop environment for Unix and OpenVMS, based on the Motif widget toolkit. For a long period, it was the "classic" Unix desktop associated with commercial Unix workstations. After a long history as proprietary software, it was released as free software on 6 August 2012, under the GNU Lesser General Public License.

How to Use DTracein a Non-global Zone

• Use the zonecfg limitpriv property to add the dtrace_proc and dtrace_user privileges.

global# zonecfg -z my-zone

zonecfg:my-zone> set limitpriv="default,dtrace_proc,dtrace_user"

zonecfg:my-zone> exit

Note –

Depending on your requirements, you can add either privilege, or both privileges.

• Boot the zone.

• global# zoneadm -z my-zone boot

Log in to the zone.

global# zlogin my-zone

• Run the DTrace program.

my-zone# dtrace -l

Note:

*Oracle Solaris DTrace is a comprehensive, advanced tracing tool for troubleshooting systemic problems in real time.

*DTrace helps you understand a software system by enabling you to dynamically modify the operating system kernel and user processes to record additional data that you specify at locations of interest, called probes.

The Live Media provides administrators with an opportunity to explore the Oracle Solaris 11.1 environment without installing it on a system. The system boots off the media directly allowing administrators to start the installer should they choose to install it to a system.

Note:

*You have several alternatives for where to install Oracle Solaris 11:

Inside a virtual machine on top of your existing operating system

On the bare metal as a standalone operating system

On the bare metal alongside your existing operating system(s) (multiboot scenario)

How to Loopback Mount a File That Is Usually Not Visible in a Labeled Zone

This procedure enables a user in a specified labeled zone to view files that are not exported from the global zone by default.

• Halt the zone whose configuration you want to change.

# zoneadm -z zone-name halt

• Loopback mount a file or directory.

For example, enable ordinary users to view a file in the /etc directory.

# zonecfg -z zone-name

add filesystem

set special=/etc/filename

set directory=/etc/filename

set type=lofs

add options [ro,nodevices,nosetuid]

end

exit

Note - Certain files are not used by the system, so that loopback mounting them has no effect. For example, the /etc/dfs/dfstab file in a labeled zone is not checked by Trusted Extensions software. For more information, see Sharing Files From a Labeled Zone.

• Start the zone.

# zoneadm -z zone-name boot

Note:

*In this Solaris release, you create a ZFS file system share and publish the share as follows:

Create the file system share and define the NFS or SMB share properties by using the zfs share command.

*ZFS File Sharing Within a Non-Global Zone

In previous Solaris releases, you could not create and publish NFS or SMB shares in a Oracle Solaris non-global zone. In this Solaris release, you can create and publish NFS shares by using the zfs set share command and the legacy share command with a non-global zone.

*If a ZFS file system is mounted and available in a non-global zone, it can be shared in that zone.

*A file system can be shared in the global zone if it is not mounted in a non-global zone or is not shared to a non-global zone.

*If a ZFS file system's mountpoint property set to legacy, the file system can be shared by using the legacy share command.