Solaris I am aware of

The boot process for SPARC platform involves 5 phases as shown in the diagram below. There is a slight difference in booting process of a SPARC based and x86/x64 based solaris operating system. Boot PROM phase 1. The boot PROM runs the power on self test (POST) to test the hardware. 2. The boot PROM displays the banner with below information – Model type – processor type – Memory – Ethernet address and host ID 3. Boot PROM reads the PROM variable boot-device to determine the boot device. 4. Boot PROM reads the primary boot program ( bootblk ) [sector 1 to 15] and executes it. Boot program phase 1.  bootblk  loads the secondary boot program  ufsboot  into memory. 2. ufsboot reads and loads the kernel. The kernel is composed of 2 parts : unix (platform specific kernel) genunix (platform independent kernel) 3. ufsboot combines these 2 kernel into one complete kernel and loads into memory. Kernel initialization phase 1. The kernel reads the configura...

How to check the Parent Zone (Global Zone) name of Non Global Zone from Non Global Zone ? As many Unix folks are discussing and believing that their is no way to find out the Parent Zone (Globle Zone, GZ) from Non Global Zone (NGZ). Folks there is a way, I will show you the complete steps how to find out the GZ name from NZG. It took many months for me to find out the way, but at last I got it. :-) This post is for all those Unix Champs who were asking the same que. on Linkedin.com , guys as committed below is the post. My Global Zone (Physical Server): =========================== yogesh-test#uname -a SunOS yogesh-test 5.10 Generic_144488-11 sun4u sparc SUNW,Sun-Fire-V245  —–> GZ (yogesh-test) yogesh-test#zoneadm list -cv ID NAME STATUS PATH BRAND IP 0 global running / native shared 1 yogesh-zone running /zones/yogesh-zone native shared   ——> NZG (yogesh-zone) My Non-Global Zone (Virtual Server): ============================== yogesh-test#zlogi...

First question in your mind is to identify the Non-Global Zone whether they Sparse or Whole Root Zone in real time. This post will help you to find those details in handy ways. Theoretically everyone having good knowledge about Sparse and Whole Root Zones. But in real time.....Please follow the Steps. Here We have 2 Non-Global zone, but we are not sure which one is Sparse or Whole Root Zones. Let we identify them. [root@unixrock ~]# zoneadm list -cv ID NAME STATUS PATH BRAND IP 0 global running / native shared 1 unixrockLZ running /export/zones/unixrockLZ native shared 2 unixrockLZ1 running /export/zones/unixrockLZ1 native shared [root@unixrock ~]# There is a Command called "pkgcond" allows you to determine the type of target being operated on (global zone, non-global zone). more details you can refer man Page of pkgcond. I'm executing the c...

Solaris zones enables a software partitioning of solaris 10 OS to support multiple independent, secure OS environments to run in the same OS. Each environment has separate process space, resource allocation and users. Zones are widely used in production environments as it is easy to setup and doesn’t require any special hardware like ldoms does. Zone types Global zone  – every installed OS acts like a global zone, which is present by default. All non-global zones can only be intalled, configured and administered from global zone. Non-global zone  – They share the functioning of the kernel booted under the global zone. All the software and other resources are inherited from the global zone. Whole Root zone (Big zone)  – It gets their own writable copy of all the file systems like /opt, /usr. It takes more disk space. Sparse root zone (Small zone)  – File systems like /opt, /usr are shared from global zone as loopback file-system (you only have a read-only access...

Booting a SPARC Based System If a system is turned off, turning it on starts the multiuser boot sequence. The following procedures show how to boot to different run levels from the  ok  PROM prompt. These procedures assume that the system has been cleanly shut down, unless stated otherwise. Use the  who -r  command to verify that the system is brought to the specified run level. For a description of run levels, see  Chapter 14, Managing Services (Overview) . How to Boot a System to Run Level 3 (Multiuser Level) Use this procedure to boot a system that is currently at run level 0 to run level 3. Boot the system to run level 3. ok boot The automatic boot procedure displays a series of startup messages, and brings the system to run level 3. For more information, see the  boot  ( 1M )  man page. Verify that the system has booted to run level 3. The login prompt is displayed when the boot process has finished successfully...