Explanation/Reference:
Explanation:
Image Packaging System (IPS) is a new network based package management system included in Oracle Solaris 11. It provides a framework for complete software lifecycle management such as installation, upgrade and removal of software packages. IPS also enables you to create your own software packages, create and manage package repositories, and mirror existing package repositories.
Oracle Solaris software is distributed in IPS packages. IPS packages are stored in IPS package repositories, which are populated by IPS publishers.
E: The following command displays property information about the local repository.
$ pkgrepo get -s /export/repoSolaris11
SECTION PROPERTY VALUE publisher prefix solaris repository description This\ repository\ serves\ a\ copy\ of\ the\ Oracle\ Solaris\ 11\ Build\ 175b\ Package\ Repository.
repository name Oracle\ Solaris\ 11\ Build\ 175b\ Package\ Repository
repository version 4
The value of the publisher prefix specifies that solaris is to be used in the following cases:
When more than one publisher's packages are present and no publisher is specified in the package name in the pkg command
When packages are published to the repository and no publisher is specified.

Explanation/Reference:
Explanation:
A: Solaris uses a UID (User ID) to identify each user account. The UID is a unique number assigned to each user. It is usually assigned by the operating system when the account is created.
B: In Solaris the account name can include any alphanumeric string (and . _ -). The maximum length is 8 characters.

The $HOME/.profile file is an initialization file that is executed after the /etc/profile when logging in to the Bourne or Korn shell. The file contains user preferences for variable settings. If the ENV variable is set to .kshrc, the
.kshrc file executes every time a new shell begins execution. The $HOME/.profile is copied from the /etc/skel/ local.profile file by the Administration Tool when creating a new account.
Note: /etc/skel/local.profile
Per-system configuration file for
sh/ksh/ksh93/bash login sessions,
installed for new users

A: If the network is setup to perform automated installations,you can perform a text installation over the network by setting up an install service on the network and selecting a text installation when the client system boots.
B: After a fresh install of Solaris 11 express,only the console mode is activated.
To add Gnome,simply do :
$ sudo pkg install slim_install
This will install additional packages that are not installed by default.
D: The text installer advantages over the GUI installer include:
* In addition to modifying partitions,the text installer enables you to create and modify VTOC slices within the Solaris partition.
F: How do I upgrade my Solaris 10 or lower systems to Solaris 11?
Unfortunately,you CAN'T. There is no direct upgrade installer or other tool that will allow you to upgrade from earlier releases of Solaris to Solaris 11. This is primarily due to the vast changes in the packaging mechanism in Solaris 10.

On POSIX-compliant platforms,SIGTERM is the signal sent to a process to request its termination. The symbolic constant for SIGTERM is defined in the header file signal.h. Symbolic signal names are used because signal numbers can vary across platforms,however on the vast majority of systems,SIGTERM is signal #15.
SIGTERM is the default signal sent to a process by the kill or killall commands. It causes the termination of a process,but unlike the SIGKILL signal,it can be caught and interpreted (or ignored) by the process. Therefore,SIGTERM is akin to asking a process to terminate nicely,allowing cleanup and closure of files. For this reason,on many Unix systems during shutdown,init issues SIGTERM to all processes that are not essential to powering off,waits a few seconds,and then issues SIGKILL to forcibly terminate any such processes that remain.