Pass the Oracle Oracle Solaris 1z0-580 Questions and answers with CertsForce

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.

There are no upgrade methods or tools available to transition from Oracle Solaris 10 to Oracle Solaris 11. You cannot use an installer to upgrade from Oracle Solaris 10 to Oracle Solaris 11.

Oracle Solaris 11 Transition Tools and Features

Note:

*There are no upgrade methods or tools available to transition from Oracle Solaris 10 to Oracle Solaris 11. You cannot use an installer to upgrade from Oracle Solaris 10 to Oracle Solaris 11.

/JumpStart Migration Utility (js2ai)

Used to convert Oracle Solaris 10 JumpStart rules and profiles to a format that is compatible with AI manifest entries.

/ZFS shadow migration feature

Used to migrate data from an existing file system to a new file system.

/Oracle Solaris 11 support for Oracle Solaris 10 zones

Used to migrate your Oracle Solaris 10 application environments to an Oracle Solaris 11 system.

/NFS file sharing and pool migration

Used to access shared files from an Oracle Solaris 10 system on an Oracle Solaris 11 system.

Used to import a ZFS storage pool from an Oracle Solaris 10 system into an Oracle Solaris 11 system.

The beadm create command has the following options, where BeName specifies the name of the boot environment to be created.

Syntax: beadm create [-a] [-d description] [-e non-activeBeName | BeName@snapshot] [-o property=value]...[-p zpool] BeName

-a – Activate the newly created boot environment upon creation. The default is to not activate the newly created boot environment.

A:dedicated-cpu Resource

The dedicated-cpu resource specifies that a subset of the system's processors should be dedicated to a non-global zone while it is running. When the zone boots, the system will dynamically create a temporary pool for use while the zone is running.

C:s the global administrator in the global zone, you can import raw and block devices into a non-global zone. After the devices are imported, the zone administrator has access to the disk. The zone administrator can then create a new file system on the disk and perform one of the following actions:

Mount the file system manually

Place the file system in /etc/vfstab so that it will be mounted on zone boot

D, E:Booting a zone places the zone in the running state. A zone can be booted from the ready state or from the installed state. A zone in the installed state that is booted transparently transitions through the ready state to the running state. Zone login is allowed for zones in the running state.

Incorrect:

Not F: Sys_time not related to booting a zone.

Note:

*sendmail

*Enabling Access to Remote Clients

On an unmodified system, access to sendmail by remote clients is enabled and disabled through the service management facility (see smf(5)). In particular, remote access is determined by the value of the local_only SMF property:

svc:/network/smtp:sendmail/config/local_only = true

A setting of true, as above, disallows remote access; false allows remote access. The default value is true.

The following example shows the sequence of SMF commands used to enable sendmail to allow access to remote systems:

# svccfg -s svc:/network/smtp:sendmail setprop config/local_only = false

# svcadm refresh svc:/network/smtp:sendmail

# svcadm restart svc:/network/smtp:sendmail

To patch a Solaris system or install a command you use pkg command.

TFTP Error or System Hangs After GATEWAY Message

The DHCP server provides an IP address and a location of the initial boot program as part of the DHCP response.

If the boot program does not exist, then the AI client boot cannot proceed. The following message is displayed:

Intel(R) Boot Agent PXE Base Code (PXE-2.1 build 0.86)

Copyright(C) 1997-2007, Intel Corporation

CLIENT MAC ADDR 00 14 4F 29 04 12 GUID FF2000008 FFFF FFFF FFFF 7BDA264F1400

CLIENT IP: 10.6.68.29 MASK: 255.255.255.0 DHCP IP: 10.6.68.49

GATEWAY: 10.6.68.1

TFTP.

PXE-T02: Access Violation

PXE-E3C: TFTP Error - Access violation

PXE-MOF: Exiting Intel Boot Agent

Boot Load Failed

If the AI client starts downloading the boot_archive, but then fails with the error, “Boot load failed,” that indicates that the client DHCP information is configured incorrectly.

Rebooting with command: boot net:dhcp - install

Boot device: /pci@7c0/pci@0/network@4:dhcp File and args:

1000 Mbps FDX Link up

HTTP: Bad Response: 500 Internal Server Error

Evaluating:

Boot load failed

This error could happen if another DHCP server is responding to the client. Check the DHCP configuration for this client. If the configuration appears to be correct, determine whether there is another DHCP server in the subnet.

A snapshot is a read-only point-in-time copy of a file system. The copy-on-write design

of ZFS makes them essentially “free” - They are space efficient and instantaneous, providing an invaluable part of backup strategies and synchronizing data between systems.

Incorrect:

Incorrect:

NotA:A ZFS vdev (aka "virtual device") is either:

a single disk, or

two or more disks that are mirrored, or

a group of disks that are organized using RAID-Z.

There are also special kinds of vdevs like hot-spares, ZIL or cache devices, etc.

Not D:

Clones are writeable snapshots, ideal for storing many private

copies of shared data for operations such as data migration, test

and development, or backup.

Use the pkg revert command to restore files to their as-delivered condition.