|Home||Switchboard||Unix Administration||Red Hat||TCP/IP Networks||Neoliberalism||Toxic Managers|
May the source be with you, but remember the KISS principle ;-)
Bigger doesn't imply better. Bigger often is a sign of obesity, of lost control, of overcomplexity, of cancerous cells
|News||Open Boot||Solaris Run Levels||SMF||Startup Files|
|Serial Console on Solaris||ALOM||Boot Process||History||Humor||Etc|
The normal Unix boot process has these main phases:
Basic hardware detection (memory, disk, keyboard, mouse, and the
like) and executing the firmware system initialization program .
In Solaris this is called Boot PROM phase—After you turn on power
to the system, the PROM displays system identification information and
runs self-test diagnostics to verify the system's hardware and memory.
PROM chip contains Forth OpenBoot firmware, and it is executed
immediately after you turn on the system. The primary task of the OpenBoot
firmware is to boot the operating system either from a mass storage
device or from the network. OpenBoot contains a program called the
monitor that controls the operation of the system before the
kernel is available. When a system is turned on, the monitor runs a
power-on self-test (POST) that checks such things as the hardware and
memory on the system. If no errors are found, the automatic boot
process begins. OpenBoot contains a set of instructions that locate
and start up the system's boot program and eventually start up the Unix
Locating and running the initial boot program (IPL or bootloader)
from a predetermined location on the disk (MBR in PC). In Solaris the
primary boot program, called bootblk, is loaded from its location
on the boot device (usually disk) into memory.
Locating and starting the Unix kernel. The kernel image file to execute
may be determined automatically or via input to the bootloader. In Solaris
the bootblk program finds and executes the secondary boot program
(called ufsboot) from the Unix file system (UFS) and loads
it into memory. After the ufsboot program is loaded, the
ufsboot program loads the two-part kernel.
The kernel initializes itself and then performs final, high-level
hardware checks, loading device drivers and/or kernel modules as required.
In Solaris the kernel initializes itself and begins loading modules,
using ufsboot to read the files. When the kernel has loaded
enough modules to mount the root file system, it unmaps the ufsboot
program and continues, using its own resources.
The kernel starts the init process, which in turn starts system processes (daemons) and initializes all active subsystems. When everything is ready, the system begins accepting user logins. In Solaris kernel starts the Unix operating system, mounts the necessary file systems, and runs /sbin/init to bring the system to the initdefault state specified in /etc/inittab. The kernel creates a user process and starts the /sbin/init process, which starts other processes by reading the /etc/inittab file. The /sbin/init process starts the run control (rc) scripts, which execute a series of other scripts. These scripts (/sbin/rc*) check and mount file systems, start various processes, and perform system maintenance tasks.
Availability of svcs -a functionality cannot be legitimately sited as an advantage as it can be easily implemented with th4 old approach (as was done in Red Hat with services command).
I am not sure that conversion of init scripts to Perl cannot achieve the same functionality at lower cost.
The Service Management Facility is a new, unified model for services and service management that is included in the Solaris Operating System. SMF provides a deeper, more functional view into the processes managed during startup and shutdown of a Solaris system. In addition, processes managed through SMF can have dependencies and they are monitored to allow for restarts if a process fails or is improperly stopped.
SMF is a core part of the predictive self-healing technology available in the Solaris 10 OS, and it provides automatic recovery from software and hardware failures as well as administrative errors. In addition, SMF-managed services can be delegated to non-root users. Finally, SMF is a follow-on to the legacy method of starting and stopping services, though
/etc/rcscripts will continue to run when present for backward compatibility.
Deployment of services through SMF provides a much more consistent and robust environment. First, users can query the Solaris OS with a simple command (
svcs -a) to determine if a service is running, instead of attempting a connection and wondering if the connection will succeed. Additionally, critical services can be restarted automatically in the event of a problem, such as someone inadvertently killing a service, a bug causing a core dump, or other process failures occurring. Further, SMF provides detailed and common logging as well as robust error handling to prevent services from hanging after a system state change. Please see the man page for
smf(5) for more information.
After a typical software installation, there can be a half dozen or more processes that need to be started and stopped during system startup and shutdown. In addition, these processes may depend on each other and may need to be monitored and restarted if they fail. For each process, these are the logical steps that need to be done to incorporate these as services in SMF:
- Create a service manifest file.
- Create a methods script file to define the start, stop, and restart methods for the service.
- Validate and import the service manifest using
- Enable or start the service using
- Verify the service is running using
Using SAS processes as an example, we will create two services, one for the SAS Metadata Server (OMR) and one for the SAS Object Spawner. In this example, the Object Spawner cannot attempt to start before the OMR is started and should be stopped before the OMR is stopped.
Note If you change an NVRAM setting on a SPARC system and the system will no longer start up, it is possible to reset the NVRAM variables to their default settings by holding down the Stop and N keys simultaneously while the machine is powering up. When issuing this command, hold down Stop+N immediately after turning on the power to the SPARC system; keep these keys pressed for a few seconds or until you see the banner (if the display is available). This is a good technique to force a system's NVRAM variables to a known condition.
Solaris 10 has a new feature boot -m verbose which allows you to customize boot console output.
Miscellaneous Solaris notes
You too can understand<br> device numbers and mapping in Solaris ...
The following represents a summary of the boot process for a Solaris 2.x system on Sparc hardware.
Hardware Power ONmessage on a large Enterprise server, or a "'" or "," in the case of an older Ultra system. These indications will not be present on a monitor connected directly to the server.
diag-switch?parameter is set to
true, output from the POST (Power On Self Test) will be viewable on a serial terminal. The PROM
diag-levelparameter determines the extent of the POST tests. (See the Hardware Diagnostics page for more information on these settings.) If a serial terminal is not connected, a
prtdiag -vwill show the results of the POST once the system has booted. If a keyboard is connected, it will beep and the keyboard lights will flash during POST. If the POST fails, an error indication may be displayed following the failure.
diag-switch?is set, an
Entering OBPmessage will be seen on a serial terminal. The MMU (memory management unit) is enabled.
use-nvramrc?is set to
true, read the
NVRAMRC. This may contain information about boot devices, especially where the boot disk has been encapsulated with VxVM or DiskSuite.
ok>prompt, or by using
prtconfonce the system has been booted.
diag-levelare set, additional diagnostics will appear on the system console.
auto-boot?: If the
auto-boot?PROM parameter is set, the boot process will begin. Otherwise, the system will drop to the
ok>PROM monitor prompt, or (if
security-modeare set) the
The boot process will use the
boot-file PROM parameters unless
set. In this case, the boot process will use the
bootblkprimary boot program from the
diag-switch?is set). If the
bootblkis not present or needs to be regenerated, it can be installed by running the
installbootcommand after booting from a CDROM or the network. A copy of the
bootblkis available at
/platform/`arch -k`/ufsbootis run. This program loads the kernel core image files. If this file is corrupted or missing, a
bootblk: can't find the boot programor similar error message will be returned.
As part of the kernel loading process, the kernel banner is displayed to the screen. This includes the kernel version number (including patch level, if appropriate) and the copyright notice.
The kernel initializes itself and begins loading modules, reading
the files with the
ufsboot program until it has loaded
enough modules to mount the root filesystem itself. At that point,
ufsboot is unmapped and the kernel uses its own drivers.
If the system complains about not being able to write to the root filesystem,
it is stuck in this part of the boot process.
boot -a command singlesteps through this portion of the boot
process. This can be a useful diagnostic procedure if the kernel is
not loading properly.
/etc/systemfile is read by the kernel, and the system parameters are set.
The following types of customization are available in the
/etc/system file is edited, it is strongly recommended
that a copy of the working file be made to a well-known location. In
the event that the new
/etc/system file renders the system
unbootable, it might be possible to bring the system up with a
boot -a command that specifies the old file. If this has not
been done, the system may need to be booted from CD or network so that
the file can be mounted and edited.
schedprocess is sometimes called the "swapper."
initprocess reads the
/etc/default/initand follows the instructions in those files.
Some of the entries in the
/etc/rc#.ddirectories. They are run by the
/sbin/rc#scripts, each of which corresponds to a run level. Debugging can often be done on these scripts by adding
echolines to a script to print either a "I got this far" message or to print out the value of a problematic variable.
Google matched content
Groupthink : Two Party System as Polyarchy : Corruption of Regulators : Bureaucracies : Understanding Micromanagers and Control Freaks : Toxic Managers : Harvard Mafia : Diplomatic Communication : Surviving a Bad Performance Review : Insufficient Retirement Funds as Immanent Problem of Neoliberal Regime : PseudoScience : Who Rules America : Neoliberalism : The Iron Law of Oligarchy : Libertarian Philosophy
War and Peace : Skeptical Finance : John Kenneth Galbraith :Talleyrand : Oscar Wilde : Otto Von Bismarck : Keynes : George Carlin : Skeptics : Propaganda : SE quotes : Language Design and Programming Quotes : Random IT-related quotes : Somerset Maugham : Marcus Aurelius : Kurt Vonnegut : Eric Hoffer : Winston Churchill : Napoleon Bonaparte : Ambrose Bierce : Bernard Shaw : Mark Twain Quotes
Vol 25, No.12 (December, 2013) Rational Fools vs. Efficient Crooks The efficient markets hypothesis : Political Skeptic Bulletin, 2013 : Unemployment Bulletin, 2010 : Vol 23, No.10 (October, 2011) An observation about corporate security departments : Slightly Skeptical Euromaydan Chronicles, June 2014 : Greenspan legacy bulletin, 2008 : Vol 25, No.10 (October, 2013) Cryptolocker Trojan (Win32/Crilock.A) : Vol 25, No.08 (August, 2013) Cloud providers as intelligence collection hubs : Financial Humor Bulletin, 2010 : Inequality Bulletin, 2009 : Financial Humor Bulletin, 2008 : Copyleft Problems Bulletin, 2004 : Financial Humor Bulletin, 2011 : Energy Bulletin, 2010 : Malware Protection Bulletin, 2010 : Vol 26, No.1 (January, 2013) Object-Oriented Cult : Political Skeptic Bulletin, 2011 : Vol 23, No.11 (November, 2011) Softpanorama classification of sysadmin horror stories : Vol 25, No.05 (May, 2013) Corporate bullshit as a communication method : Vol 25, No.06 (June, 2013) A Note on the Relationship of Brooks Law and Conway Law
Fifty glorious years (1950-2000): the triumph of the US computer engineering : Donald Knuth : TAoCP and its Influence of Computer Science : Richard Stallman : Linus Torvalds : Larry Wall : John K. Ousterhout : CTSS : Multix OS Unix History : Unix shell history : VI editor : History of pipes concept : Solaris : MS DOS : Programming Languages History : PL/1 : Simula 67 : C : History of GCC development : Scripting Languages : Perl history : OS History : Mail : DNS : SSH : CPU Instruction Sets : SPARC systems 1987-2006 : Norton Commander : Norton Utilities : Norton Ghost : Frontpage history : Malware Defense History : GNU Screen : OSS early history
The Peter Principle : Parkinson Law : 1984 : The Mythical Man-Month : How to Solve It by George Polya : The Art of Computer Programming : The Elements of Programming Style : The Unix Hater’s Handbook : The Jargon file : The True Believer : Programming Pearls : The Good Soldier Svejk : The Power Elite
Most popular humor pages:
Manifest of the Softpanorama IT Slacker Society : Ten Commandments of the IT Slackers Society : Computer Humor Collection : BSD Logo Story : The Cuckoo's Egg : IT Slang : C++ Humor : ARE YOU A BBS ADDICT? : The Perl Purity Test : Object oriented programmers of all nations : Financial Humor : Financial Humor Bulletin, 2008 : Financial Humor Bulletin, 2010 : The Most Comprehensive Collection of Editor-related Humor : Programming Language Humor : Goldman Sachs related humor : Greenspan humor : C Humor : Scripting Humor : Real Programmers Humor : Web Humor : GPL-related Humor : OFM Humor : Politically Incorrect Humor : IDS Humor : "Linux Sucks" Humor : Russian Musical Humor : Best Russian Programmer Humor : Microsoft plans to buy Catholic Church : Richard Stallman Related Humor : Admin Humor : Perl-related Humor : Linus Torvalds Related humor : PseudoScience Related Humor : Networking Humor : Shell Humor : Financial Humor Bulletin, 2011 : Financial Humor Bulletin, 2012 : Financial Humor Bulletin, 2013 : Java Humor : Software Engineering Humor : Sun Solaris Related Humor : Education Humor : IBM Humor : Assembler-related Humor : VIM Humor : Computer Viruses Humor : Bright tomorrow is rescheduled to a day after tomorrow : Classic Computer Humor
The Last but not Least
Copyright © 1996-2018 by Dr. Nikolai Bezroukov. www.softpanorama.org was initially created as a service to the (now defunct) UN Sustainable Development Networking Programme (SDNP) in the author free time and without any remuneration. This document is an industrial compilation designed and created exclusively for educational use and is distributed under the Softpanorama Content License. Original materials copyright belong to respective owners. Quotes are made for educational purposes only in compliance with the fair use doctrine.
FAIR USE NOTICE This site contains copyrighted material the use of which has not always been specifically authorized by the copyright owner. We are making such material available to advance understanding of computer science, IT technology, economic, scientific, and social issues. We believe this constitutes a 'fair use' of any such copyrighted material as provided by section 107 of the US Copyright Law according to which such material can be distributed without profit exclusively for research and educational purposes.
This is a Spartan WHYFF (We Help You For Free) site written by people for whom English is not a native language. Grammar and spelling errors should be expected. The site contain some broken links as it develops like a living tree...
|You can use PayPal to make a contribution, supporting development of this site and speed up access. In case softpanorama.org is down you can use the at softpanorama.info|
The statements, views and opinions presented on this web page are those of the author (or referenced source) and are not endorsed by, nor do they necessarily reflect, the opinions of the author present and former employers, SDNP or any other organization the author may be associated with. We do not warrant the correctness of the information provided or its fitness for any purpose.
Last modified: April 18, 2018