What is the syntax for the JumpStart client’s profile file that uses this archive to install the new sys
You are creating a profile on your JumpStart server to install a new system and are using a Flash archive to provide the necessary software. The Flash archive is called /export/nb.flar and is shared on the network from the server grendel, which has the IP address 194.168.85.106. What is the syntax for the JumpStart client’s profile file that uses this archive to install the new system?
What is the archive argument?
Given the following command:
flarcreate -n archive -R / -e flash flash
What is the archive argument?
Which two are required by the flarcreate command?
You are creating a Flash archive of your existing system, which is to be used to install other systems on the network in your organization.
Which two are required by the flarcreate command? (Choose two.)
What is a requirement for using the Flash installation feature?
You have a large number of systems in your organization which are currently running either Solaris 2.6 OS or Solaris 7 OS. You also have a mix of both x86 and SPARC system hardware architectures. You need to ensure that all of these systems are running Solaris 10 OS. You are considering using the Flash installation feature to achieve this. What is a requirement for using the Flash installation feature?
What is a requirement for using the Flash installation feature?
You have a large number of systems in your organization that are currently running either Solaris 2.6 OS or Solaris 7 OS. You need to ensure that all of these systems are running Solaris 10 OS. You are considering using the Flash installation feature to achieve this. What is a requirement for using the Flash installation feature?
Which three methods can you use to make the Flash archives available across the network?
You are using the Flash installation feature to install a number of Solaris systems in your organization. Which three methods can you use to make the Flash archives available across the network? (Choose three.)
What JumpStart configuration technique must you use to disable power management during a JumpStart installatio
You are preparing to install several UltraSPARC machines that will function as servers using JumpStart. Since these machines are servers, you want to disable the power management feature of Solaris 10 OS during installation. What JumpStart configuration technique must you use to disable power management during a JumpStart installation?
Which additional lines are needed to complete the installation?
You receive a new UltraSPARC machine with two internal disk drives. You want to install the machine using JumpStart, and you want to mirror the root, /usr, and /var file systems as part of the installation. The beginning of the profile looks like this:
install_type initial_install
cluster SUNWCall
partitioning explicit
filesys c0t0d0s1 512 swap
filesys c0t0d0s7 free /export/home
filesys c0t1d0s7 free
Which additional lines are needed to complete the installation?
What is the cause of this problem?
You believe that you have a correctly configured boot server on the local network for the SPARC system currently being installed. Your JumpStart configuration is based on files only and does NOT use a naming service at any stage.
Upon running the following command:
boot net -install
the client displays the following output:
Boot device: /pci@1f,0/pci@1,1/network@c,1 File and args: – install 38600 panic – boot: Could not mount filesystem.
Program terminated
ok
What is the cause of this problem?
Which statement is true about the function of this line?
The rules.ok file on your JumpStart server contains the following line:
hostname client1 backup_root client_config set_root_passwd
Which statement is true about the function of this line?