SSA - how to create state database replica

#metabd –a –f c0t0d0s1

SSA - How to see the state databases replica.

A) # metabd

SSA - what are raid0,raid1 and raid5

Q) what are raid0,raid1 and raid5


A) Raid 0 is concatenation or stripping
Concatenation means writing data in disk one after another
Stripping means writing data of 32kbs interlease value in to disk

Raid 1 – mirroring that means writing data on two disk parallely or duplicatiung the data on two disk.

Raid 5 – stipping with parity the data of 2 disk is duplicated in the third disk with parity information

SSA - How to configure newly attached hardware like hardsik network card.

# devfsadm

Or drvconfig

SSA - How to set environment variable in NVRAM

# nvalias /pci---/rarp – to set scsi for booting of client

# nvalias net dhcp – to boot from dhcp

# nvunalias net – remove the alias

SSA - How to check the check the clock devices from OBP

Ok>netwatch-clock

SSA - How do you check your loop back or network devices from Open boot prom

ok> test net

SSA - How to see the physical disk connected to the system from Open Boot Command OBP

ok>probe-scsi

SSA - How to see all the informations of the hardware related from bootprom (OBP)

# banner


or

# prtconf

SSA - How do you set a default boot device from the boot prom

# setenv boot-device disk
Boot-device=disk
# reset - To make the changes.

SSA - How to see the default boot device from the boot prom or OBP

ok> prtenv boot-device

SSA How to see which kernel version and artitecture used by the system.

# isainfo -v :- To see kernal version and 32 bit or 64 bit system and artictect

SSA How to make processor 3 online when you have more then 4 processor and processor 3 is offline?

# psrinfo –v:- To see the status of all processors

# psrinfo –a 3 online :- To make processor 3 online

SSA How to make processor 4 number offline when you have more then 4 processors.

# psrinfo –V :- To check the status and then

# psradm –f 4 offline - To make processor number 4 offline

SSA How to change processor operation status in solaris

# psradm –a –n :- To set all processor available on the system to online

# psradm –f 2 3 :- To make processor 2 and 3 offline, if you have multiple processors

How do you set a deafaulr boot device from the boot prom

# setenv boot-device disk
Boot-device=disk
# reset - To make the changes.


Tags : solaris interview questions and answers

2203 How to see the physical disk connected to the system from Open Boot Command OBP

ok>probe-scsi

2203 How to see all the informations of the hardware related from bootprom(OBP)

# banner

or

# prtconf

2203 How do you check your loop back or network devices from Open boot prom

ok> test net

Big Admin - Solaris Tips and Tricks

I had to use the following tips time to time so I am posting them here to save me the time to look for them again (and avoid the possibility of the original sites going off-line).

1. Set up your /etc/hosts file.

It should look something like this:

127.0.0.1       localhost
192.168.0.150   solaris-box-1 solaris-box-1.yourdomain.com loghost

Make sure the second line has the correct IP address, hostname, and FQDN. The first line is the loopback entry. Along with #5, Solaris will know its name and IP address.

2. Create or edit /etc/nodename

Contains the hostname of the computer (same as hostname.hme0).

# cat nodename
solaris-box-1

3. Create or edit /etc/defaultrouter

Surprisingly enough, this file contains the IP address of your default router (or gateway). When you reboot and the network initialization scripts run, it will add a default route to the IP address in this file.

# cat defaultrouter
192.168.0.1

Now it knows about it's own network parameters and it's time to get it to use DNS. The next steps will tell it to use other nameservers. If you want to set up a nameserver on the local machine, see the man page for named.

4. Edit /etc/nsswitch.conf

If you haven't edited this file before, it should look suspiciously like like this:

passwd:     files
group:      files
hosts:      files
networks:   files
protocols:  files
rpc:        files
ethers:     files
netmasks:   files
bootparams: files
publickey:  files
# At present there isn't a 'files' backend for netgroup;  the system will
#   figure it out pretty quickly, and won't use netgroups at all.
netgroup:   files
automount:  files
aliases:    files
services:   files
sendmailvars:   files

Add the word 'dns' after 'files' on the 'hosts' line:

passwd:     files
group:      files
hosts:      files dns
networks:   files
protocols:  files
rpc:        files
ethers:     files
netmasks:   files
bootparams: files
publickey:  files
# At present there isn't a 'files' backend for netgroup;  the system will
#   figure it out pretty quickly, and won't use netgroups at all.
netgroup:   files
automount:  files
aliases:    files
services:   files
sendmailvars:   files

Now it knows to query a nameserver when looking up a name. Next we have to tell it what nameservers to use:

5. Create or edit /etc/resolv.conf

Here you tell it three things:

1. What domain we're in
2. Specify any additional search domains
3. What the nameservers are (it will use them in the order you put them in the file)

When you're done it should look something like this:

# cat resolv.conf
domain yourdomain.com
search yourdomain.com
search client1.com
nameserver 192.168.0.9
nameserver 192.168.0.11

For more information, see the man page for resolv.conf.

6. Edit /etc/hostname.hme0

This file should contain the hostname of your machine, without the domain name. So, if the FQDN (Fully Qualified Domain Name = hostname + domain name) is solaris-box-1.yourdomain.com, the file should look like this:

# cat hostname.hme0
solaris-box-1

This assumes that your Ethernet adatper is hme0, the default device name for the first Ethernet adapter.

7. Reboot

# sync;sync;sync
# reboot

8. Change IPs

UNIX Shell:      All Primary shells (sh,ksh,csh)
Function:    Use ifconfig to change your IP address immediately. Edit your /etc/hosts file to change it permanently.
Syntax:    Immediate change: ifconfig interface new IPaddress subnet mask

Permanent change: vi /etc/hosts
 interface   Specifies the network interface, e.g. hme0 for 100 Mbps or le0 for 10 Mbps.
 new IPaddress   Specifies the new IP address that you want to assign the computer.
 subnet mask   Specifies the subnet mask for your local network.

File Name:   hosts    Directory:    /etc    Type:   External
 ifconfig hme0 192.168.1.250 255.255.255.0     Sets the IP address to 192.168.1.250 on interface hme0.
 ifconfig le0 192.168.1.250 255.255.255.0     Sets the IP address to 192.168.1.250 on interface le0

9. Recover ROOT password

You need to have physical access to the machine's console.

Note the root partition;

Solaris uses

* /dev/dsk/c0t0d0s0 on the Ultra5/10 and Blade 100
* /dev/dsk/c0t1d0s0 for Blade 1000.

Press the STOP and A keys simultaneously, or, on an ASCII terminal or emulator, send a ) to halt the operating system, if it's running.

Boot single-user from CD-ROM (boot cdrom -s) or network install/jumpstart server (boot net -s). For CD media use the CD-ROM labeled "Installation". I prom pssword is set you need to know it

Mount the root partition on "/a". "/a" is an empty mount point that exists at this stage of the installation procedure. For example:

#mount /dev/dsk/c0t0d0s0 /a

If the mount command fails and since "/a" always exists, then you either typed in the wrong device, OR the system is seeing the root partition as something else.

Do a "ls /tmp/dev/dsk" and see what is there. "c0t6" things are the CD-ROM, what is left is what one needs to try. On a Blade 1000/2000, choose /dev/dsk/c1t1d0s0, and execute: #mount /dev/dsk/c1t1d0s0 /a

Set your terminal type so you can use a full-screen editor, such as vi. You can skip this step if you know how to use "ex" or "vi" from open mode.

* If you're on a sun console, type "TERM=sun; export TERM";
* If you are using an ascii terminal or terminal emulator on a PC for your console, set TERM to the terminal type for example: TERM=vt100; export TERM.

Edit the passwd file, /a/etc/shadow (or perhaps in older versions, /etc/passwd) and remove the encrypted password entry for root.

Type: "cd /; then "umount /a"

Reboot as normal in single-user mode ("boot -s"). The root account will not have a password. Give it a new one using the passwd command. PROM passwords: Naturally, you may not want anyone with physical access to the machine to be able to do the above to erase the root password. Suns have a security password mechanism in the PROM which can be set (this is turned off by default). The man page for the eeprom command describes this feature.

If security-mode is set to "command", the machine only be booted without the prom password from the default device (i.e. booting from CD-ROM or install server will require the prom password). Changing the root password in this case requires moving the default device (e.g. the boot disk) to a different SCSI target (or equivalent), and replacing it with a similarly bootable device for which the root password is known. If security-mode is set to full, the machine cannot be booted without the prom password, even from the default device; defeating this requires replacing the NVRAM on the motherboard. "Full" security has its drawbacks -- if, during normal operations, the machine is power-cycled (e.g. by a power outage) or halted (e.g. by STOP-A), it cannot reboot without the intervention of someone who knows the prom password.

10. Others (and repeated)

"I've almost just reinstalled Solaris to get the network settings fixed!" Ya, sometimes you can get alittle confused and irritated. Whether it's a new Linux distro, or diffrent UNIX OS, everyone puts their network configuration in diffrent places and learning each systems setup can be a pita. So, what if you don't even wanna bother learning all the network configuration stuff and what files does what... what if you could just re-run the networking configuration and have it all sorted out? You can! Solaris has a nifty command that can reset the base networking and configuration to a clean system: "sys-unconfig". If you buy a pre-installed system from Sun or a VAR, what they will generally do is install Solaris, customize the install as needbe and then run "sys-unconfig" before putting the system in the box and shipping it out. The command will scratch the networking configuration (most of it anyway), the root password, time zone, etc. Once sys-unconfig finished cleaning out the files it will immediately halt the system (shut it down). Next time you boot the system it will prompt you for all the networking information, time zone, locale and a new root password. This is the "quick-no-hassle" reconfiguration method. Generally we do not recommend this as ideal, but it will do the trick. If you plan on selling a pre-installed system or you are moving your system to a new network where all the info is changing, this is the command to use. Just use it carefully.

"I know root shouldn't login remotely, but I really want too!" Logging into a system via telnet, ftp, or ssh is just bad... very bad. However, some times people think they need to do this or they simply don't care about security. If you really wanna drop your pants like this, edit: /etc/default/login. In this file, you'll see a line for CONSOLE. To allow root to log in via telnet or ftp just comment out this line and your done. To allow root login via SSH you need to edit a diffrent file: /etc/ssh/sshd_config. Change the value of PermitRootLogin from "no" to "yes" and restart SSH via "svcadm restart ssh". The SSH configuration file is just the same as Linux since Solaris uses OpenSSH. Please note, that allowing root to log in remotely is a massive security risk and needlessly stupid, don't do this unless you absolutely must.

"How do I set and make the default gateway persistant across reboots?" The default gateway is easy to configure, just put the IP address of the default gateway in /etc/defaultrouter. If this file doesn't exist just create it and add the IP. The IP address of the gateway should be the ONLY thing in this file, nothing else. Typically you should just use echo, like this: "echo 10.0.0.255 > /etc/defaultrouter". Once you've changed the file you can restart the physical network interfaces to make the changes effective without a reboot ("svcadm restart physical").

How do I set or change my IP address? Setting and changing IP addresses on Solaris is a snap. Just add the IP and hostname that you wish to use to /etc/hosts. Then put the hostname (by itself) in teh /etc/hostname.(interface) file. Then just restart the physical networking via SMF ("svcadm restart phsyical") and your done! Example: "echo '10.0.0.25 solarisrox' >> /etc/hosts; echo 'solarisrox' > /etc/hostname.hme0" assuming that hme0 was the interface you wanted to use. Don't worry about this changing the hostname for the whole workstation, the hostname for the system is kept in /etc/nodename. You can add the default gateway as we discussed just above. If you need to specify a non-standard subnet netmask you can add it to /etc/netmasks. You can have as many subnet masks in the /etc/netmasks file as you like, one per line, just follow the instructions at the top of the file.

How do I configure DHCP? DHCP is pretty easy to configure, just create 2 empty files: /etc/hostname.(interface) and /etc/dhcp.(interface). If you are using HME0 you could do this: "echo "" > /etc/hostname.hme0 > /etc/dhcp.hme0". You might want to wipe out information that might conflict like the /etc/defaultrouter file if you created one. Once you've got these two empty files ready just restart the physical network to make the changes effective without a reboot ("svcadm restart physical"). If you want to customize the properties of the DHCP agent you can check out the " System Administration Guide: IP Services" manual. Remember that DHCP settings take acouple seconds to be retrieved from the server so if you reset the physical interfaces as mentioned above and you notice that nothing happened, just wait a couple seconds (30 secs is the default timeout).

I can't figure out what the network interface is called! Linux sort of makes network interface naming easy because typically interfaces are named "eth0", "eth1", so on and so forth. In Solaris, however, the name of the interface is decided by the interface driver. For instance, the onboard ethernet of a Sun Ultra workstation uses the HME (Happy Meal Ethernet, also more boringly called Hundred Meg Ethernet) driver and so the first instance is "hme0". You can look at the device mappings to driver names using "prtconf -D". In general, Solaris will find your network device and try to configure it so generally just checking "ifconfig -a" is enough to find it.

My l337 workstations network device isn't frickin' support!?! Sadly there are lots of networking devices that aren't officially supported (right now anyway, OpenSolaris hopes to change this). Thankfully there are tons of really kool Solaris developers that have been creating open source drivers! Check out these free NIC drivers by Masayuki Murayama! Grok google for drivers, you just might find your l337 gear really does have drivers avalible, they just aren't in Solaris right now.

There ya go.. some quick Solaris networking tips. As always, check out docs.sun.com's Solaris10 manuals for help and details.

Resetting the SYSTEM user password

OpenVMS

(Re) boot the system with:

b -fl 0,1 dka0

(Replace DKA0 with whatever is appropriate for your installation)

At the SYSBOOT console:

SYSBOOT> SET/STARTUP OPA0:
SYSBOOT> SET WINDOW_SYSTEM 0
SYSBOOT> SET WRITESYSPARAMS 0
SYSBOOT> CONTINUE

$ SPAWN
$ @SYS$SYSTEM:STARTUP
$ SET DEFAULT SYS$SYSTEM:
$ RUN SYS$SYSTEM:AUTHORIZE
UAF> MODIFY SYSTEM /PASSWORD=newpass
UAF> EXIT
$

disable all logins? - How to

Some servers are meant to only serve few specific ports and in this case, server administrator should disable the normal login process. In my case, I wanted to have alerts when someone tries to even login to this server and I configured /etc/hosts.deny file to send alerts to me. This is good for at least Solaris OS.

# cat /etc/hosts.deny
ALL:    ALL: /usr/ucb/finger -l @%h 2>&1 | /bin/mailx -s

"Someone is knocking at `hostname`" unixgeek@somecompany.co

ps (Process list) command in Solaris - Long format

the complete process COMMAND while showing the output of ps. Generally, I use default ps (i.e. /bin/ps) but sometime, the output it shows is not complete. To get rid of this problem, I now started using "/usr/ucb/ps". This command, along with necessary switches, shows complete COMMAND.

$ /usr/ucb/ps -wwxaa
  PID TT       S  TIME COMMAND
    0 ?        T  0:20 sched
    1 ?        S  0:01 /etc/init -
    2 ?        S  0:00 pageout
    3 ?        S 1502:02 fsflush
   49 ?        S  0:00 /usr/lib/sysevent/syseventd
   51 ?        S  0:00 /usr/lib/sysevent/syseventconfd
15323 ?        S  1:04 /usr/local/bin/.

ZFS file system

In particular, the revised version of the page contains some basic reference information on ZFS structure internals, as well as links to papers that can be used to walk the internal data structures of a ZFS file system:

ZFS
On-Disk Data Walk in the OpenSolaris Developer Conference Proceedings.

Solaris Cluster

new Sun Cluster page to the site.

history of sloaris | solaris history

UNIX is plural. It is not one operating system but, many implementations of an idea that originated in 1965. As a system administrator, you need to understand the history of the UNIX operating system where it came from, how it was built, and where it is now. Understanding the various versions of UNIX and its origins makes it clear why UNIX became known as a somewhat hostile operating system. For example, UNIX was not developed by a single company with a large marketing organization driving the user interface. (In other words, it did not follow the development path of, say, Microsoft Windows.) On the other hand, UNIX was not invented by hackers who were fooling around; it grew out of strong academic roots. The primary contributors to UNIX were highly educated mathematicians and computer scientists employed by what many people feel is the world’s premier industrial research center, Bell Laboratories. Although knowledgeable and experienced in their own right, these developers maintained professional contacts with researchers in academia, leading to an exchange of ideas that proved beneficial for both sides. Understanding the symbiotic relationship between UNIX and the academic community means understanding the background of the system’s inventors and the history of interactions between universities and Bell Laboratories.

HOW IT ALL BEGAN
It all began at Bell Labs, the research lab of AT&T, one of the largest and most powerful companies of our time. Ironically, AT&T was not interested in developing and selling computers or operating systems. In fact, the U.S. Department of Justice did not allow AT&T to sell software. However, AT&T’s existing systems, made up of people and paper, were in danger of being overwhelmed in the boom of the 1960s. By the 1970s, the phone business was in jeopardy. Out of desperation and need, Ken Thompson of AT&T set out to develop what no computer company was ready to provide a multiuser, multiprocessing operating system to be used in-house for its own information processing department. Specifically, the goal was an operating system to support several programmers simultaneously in a more hospitable environment. What follows is an account of major dates and events in the development cycle of the UNIX operating system.

1965–1969
In 1965, Bell Labs joined with MIT and General Electric in a cooperative development of Multics, a multiuser interactive operating system running on a GE 645 mainframe computer. However, unhappy with the progress in the development of a system that was experiencing many delays and high costs, Bell Labs dropped out of the development of Multics in 1969.
In 1969, Ken Thompson, exposed to Multics at Bell Labs, met up with Dennis Ritchie, who provided a Digital Equipment Corporation PDP-7 minicomputer to continue the development of an operating system capable of supporting a team of programmers in a research environment. After they created a prototype, Thompson returned to Bell Labs to propose the use of this new operating system as a document preparation tool in the Bell Labs patent department. The new operating system was named UNIX to distinguish it from the complexity of Multics. Efforts to develop UNIX continued, and UNIX became operational at Bell Labs in 1971.
The first version of UNIX was written in assembly language on a PDP-11/20. It included the file system, fork, roff, and ed. It was used as a text-processing tool for the preparation of patents.

1970–1972
During the early 1970s, UNIX began to gain popularity throughout Bell Labs, and as word of the new operating system spread, universities embraced it. However, although UNIX was viewed favorably by the academic and high-tech sectors, it was with skepticism by the business community. In a move to heighten the popularity of UNIX, AT&T began to license the UNIX source code to universities at a minimal cost. AT&T gave many licensees the software code and manuals, but didn’t provide technical support. By the late 1970s, 70% of all colleges and universities had UNIX. Computer science graduates were using it, even modifying the code to make it more robust. UNIX was written in assembly language and ran primarily on DEC hardware—first on the PDP-7, and then the PDP-11/40, the 11/45, and finally the 11/70, on which it gained wide popularity.

1973–1979
This period became the most significant in the development of UNIX. Ritchie and Thompson had developed the C programming language between 1969 and 1973, and now rewrote the UNIX kernel in the highlevel C language. The operating system could be compiled to run on different computers. Within months, UNIX could be ported to new hardware. Modifications to the operating system were easy. Again, Thompson resonated with members of the academic community who were already using UNIX in many of their system design courses. UNIX, written in a general-purpose language featuring modern commands, began to take off in the areas of word processing and programming.
By this point, UNIX was at version 6. This was the first release of UNIX to be picked up by a commercial firm, Whitesmiths, Inc., which created a commercial copy of version 6 called Idris.
In 1975, Thompson visited Berkeley while on sabbatical, and installed version 6 on a PDP-11/70. It was at this time that two graduate students, Bill Joy and Chuck Haley, got involved with version 6 and later played an important role in the development of the UNIX system at Berkeley. The first project they worked on was the development of the UNIX ex editor.
Joy and Haley began to take interest in the internal operations of UNIX—specifically, the kernel. Joy put together a distribution of UNIX called the Berkeley Software Distribution (BSD). He included enhancements such as the C shell (a C-like interface to UNIX) and the vi editor. 1BSd was released in 1975. By the second release of BSD in 1978, Joy had added virtual memory support, which allowed programs to run even if they required more physical memory than was available at the time. This second edition of BSD had a strong influence on the release of Bell Labs’ version 7 of UNIX, which was released in 1979 and was the last of the “clean” versions of UNIX (produced solely by Bell Labs). Version 7 gave rise to a number of UNIX ports to other platforms, and for the first time, both industry and academia supplied enhancements, which were incorporated into future releases.
In the late 1970s, the United States Department of Defense’s Advanced Research Projects Agency (DARPA) decided to base its universal computing environment on Berkeley’s version of UNIX. In the 4.1 release of BSD, DARPA provided some important performance tune-ups. The fast file system, which provided a way to improve the file system’s performance and prevent file fragmentation, was added in release 4.2.

1982–1983
AT&T formally released a beta version of UNIX to the commercial sector in 1982. In 1983, AT&T released the first true production version of UNIX, naming it System III (Systems I and II never existed). Although it was based on version 7 of UNIX, and thus included some BSD utilities, the release of System III did not include the vi editor or the C shell. Instead, AT&T included the programmer’s workbench.
With the release of System III, AT&T saw a future in UNIX, and soon released System V. (System IV was never seen outside of AT&T.) System V included the editor, curses (the screen-oriented software libraries), and the init program, which was used to start up processes at UNIX boot-up.
In the early 1980s, Joy left Berkeley with a master’s degree in electrical engineering, and became cofounder of Sun Microsystems (Sun stands for Stanford University Network). Sun’s implementation of BSD was called SunOS. Sun extended the networking tools of the operating system to include the Networked File System (NFS), which was to become an industry standard. Sun also did some of the early work in developing windowing software for UNIX. SunOS was first released in 1983.
With workstation products now offered by Sun, UNIX began to gain acceptance in the high-tech arena, especially in computer-aided design and computer-aided engineering (CAD/CAE) environments. The early 1980s saw CAD/CAE become popular. Additional workstation vendors, such as HP and Apollo, began to exploit CAD/CAE capabilities and performance gains over the popular personal computers of the time. These UNIX workstations could outperform PCs and, with UNIX as an operating system, could provide a multiuser environment.
In other business computing environments, however, UNIX was still considered a hostile environment, and did not pose a threat to the mainframes of the time. UNIX had yet to define itself as a user-friendly, triedand-tested operating system. However, it was gaining ground in the areas of multitasking and networking. More important, UNIX was being touted as the operating system that provided portability between different hardware architectures, and as a consequence, software developers were getting excited about UNIX. In theory, a program written in C for UNIX would be portable to any hardware platform running the UNIX operating system.

1984–1987
In 1984, AT&T released System V, release 2, and in 1987, release 3. Release 2 introduced the terminal capability database termcap file, named terminfo, which provided support for various CRT terminals connected to the UNIX system. Other changes included the addition of Streams and Remote File Systems.

1988–1992
In 1988, AT&T shocked the UNIX community by purchasing a percentage of Sun Microsystems, already a leader in the industry. Other hardware vendors saw this as an unfair advantage for Sun, so they quickly formed a consortium group called the Open Software Foundation (OSF). Together, they raised millions of dollars to develop a new UNIX standard to compete against Sun’s.
In a counterstrike, AT&T, Sun, Data General, and Unisys joined forces to start their own organization to fight OSF. This consortium of companies, called UNIX International (UI), was formed to oversee the development of System V standards. OSF and UI turned out to be the two major competing commercial standards for UNIX.
By the late 1980s, AT&T concluded that UNIX was a distraction from the company’s focus on producing hardware. As a result, AT&T formed the UNIX Software LAB (USL), ultimately purchased by Novell in 1992.
In 1992, at the summer UseNIX conference, Berkeley announced it would conclude its development activities at version 4.4 of BSD. Several people who were involved with BSD formed smaller companies to try to continue the development of BSD, but without Berkeley and ARPA, it was not the same.
In the 1990s, BSD and System V dominated the industry, with several vendors providing their versions of one of the two operating systems. Soon UNIX, an operating system meant to provide portability of applications between multiple hardware platforms, was getting out of control. Applications were not portable between UNIX System V, release 3, and BSD. To create even more confusion, hardware vendors were enhancing their versions of BSD and System V.

1993
Sun announced that SunOS, release 4.1.4, would be its last release of an operating system based on BSD. Sun saw the writing on the wall and moved to System V, release 4, which they named Solaris. System V, release 4 (SRV4) was a merger of System V and BSD, incorporating the important features found in SunOS.
As more hardware vendors, such as Sun, began to enter the picture, a proliferation of UNIX versions emerged. Although these hardware vendors had to purchase the source code from AT&T and port UNIX to their hardware platforms, AT&T’s policy toward licensing the UNIX brand name allowed nearly any hardware vendor willing to pay for a license to pick up UNIX.
Because UNIX was a trademark, hardware vendors had to give their operating systems a unique name. Here are a few of the more popular versions of UNIX that have survived over the years:

• SCO UNIX. SCO Open Desktop and SCO Open Server from the Santa Cruz Operation for the Intel platform. Based on System V.
• SunOS. Sun’s early operating system and the best-known BSD operating system.
• Solaris. Sun’s SRV4 implementation, also referred to as SunOS 5.x.
• HP-UX. Hewlett-Packard’s version of UNIX. HP-UX 9.x was System V, release 3, and HP-UX 11i is based on the System V, release 4 OS.
• Digital UNIX. Digital Equipment’s version of OSF/1.
• IRIX. The Silicon Graphics version of UNIX. Early versions were BSD-based; version 6 was System V, release 4.
• AIX. IBM’s System V-based UNIX.Linux. A free UNIX operating system for the INTEL platform; it was quickly gaining a hold in the UNIX community. Versions of Linux became available on Sun, HP, and IBM systems.

With the uncontrolled proliferation of UNIX versions, standards became a major issue. In 1993, Sun announced that it was moving to System V in an effort to promote standards in the UNIX community. With two major flavors of UNIX, standards could not become a reality. Without standards, UNIX would never be taken seriously as a business computing system. Thus, Sun developed BSD, but provided its users with System V, release 4, shrink-wrapped directly from AT&T. In addition, any applications developed by Sun to be added onto UNIX were to be SRV4-compliant. Sun challenged its competitors to provide true portability for the user community.
The GraphicalUser Interface (GUI) was the next wave in the development of the UNIX operating system. As each hardware vendor tried to outdo the others, ease of use became an issue. Again, in this area especially, standards were important. Applications that were to be portable needed a GUI standard. Therefore, Sun and
AT&T started promoting OPEN LOOK, which they jointly developed. Their goal was to create a consistent look and feel for all flavors of UNIX; unfortunately, OSF had its own GUI called OSF/MOTIF. Thus, round two of the fight for standards began, with MOTIF beating out OPEN LOOK.
MOTIF was based on a GUI developed at MIT named the X Window System, which allowed a user sitting at one machine to run programs on a remote machine while still interacting with the program locally. X was, in effect, one way for different systems to interface with each other. X allowed a program run on one computer to display its output on another computer, even when the other computer was of a different operating system and hardware architecture. The program displayed its output on the local machine, and accepted keyboard and mouse input from the local machine, but it executed on the CPU of the remote machine.
The local machine was typically a workstation or terminal called a dedicated X terminal, and was built specifically to run the X Window System. The remote machine might be a minicomputer or server, a mainframe, or even a supercomputer. In some cases, the local machine and the remote machine might, in fact, be the same. In summary, X was a distributed, intelligent, device-independent, operating-system-independent windowing system.
As stated earlier, MOTIF beat OPEN LOOK in the standards war. Sun conceded, and started to provide a package that contained both OPEN LOOK and MOTIF—called the Common Desktop Environment (CDE)—as standard equipment beginning with Solaris 2.5.1.

2001 AND BEYOND
Today, many hardware vendors have buried the hatchet and, for the sake of users, are moving their implementations of UNIX to be SRV4-compliant. SVR4 will clearly be the dominant flavor of UNIX across most major platforms. As all vendors begin to implement SVR4 along with the CDE or GNOME interface, users will begin to see a more consistent implementation of UNIX. In addition, software providers can be ssured that applications written to be SVR4-compliant will be portable across many hardware platforms.
Look for the GNOME desktop around mid-2002 with the release of Solaris 9. This new desktop will eventually replace CDE, and will be much better than CDE in terms of usability, visual design, and core features. Most major UNIX vendors will be moving toward GNOME.
Linux will still be a major player. Now that most of the major UNIX vendors including Sun, HP, and IBM have embraced it, Linux will not go away.

Solaris
No other flavor of UNIX is more popular or has enjoyed a wider user base and cultural following than Sun Microsystems’ Solaris. Since it was founded in 1982, Sun Microsystems’ focus has been on UNIX, and it appears to have no intention of moving away from the UNIX operating system. Sun’s user base has strong loyalty to the company, as well as to the operating system. Sun’s most recent version is Solaris 8, based on System V, release 4. The Solaris operating system is available for the SPARC architecture, Sun’s own processor, and the Intel platform.

MILESTONES IN THE DEVELOPMENT OF SOLARIS

1965 Bell Laboratories joins with MIT and General Electric to develop Multics.

1970 Ken Thompson and Dennis Ritchie develop UNIX.

1971 The B-language version of the operating system runs on a PDP-11.

1973 UNIX is rewritten in the C language.

1974 Thompson and Ritchie publish a paper and generate enthusiasm in the academic community. Berkeley starts the BSD program.

1975 The first licensed version of BSD UNIX is released.

1979 Bill Joy introduces “Berkeley Enhancements” as BSD 4.1.

1982 AT&T first markets UNIX. Sun Microsystems is founded.

1983 Sun Microsystems introduces SunOS.

1984 About 100,000 UNIX sites exist worldwide.

1988 AT&T and Sun start work on SVR4, a unified version of UNIX.

1988 OSF and UI are formed.

1989 AT&T releases System V, release 4.

1990 OSF releases OSF/1.

1992 Sun introduces Solaris, which is based on System V, release 4. SunOS, which is based on BSDF UNIX, will be phased out.

1993 Novell buys UNIX from AT&T.

1994 Solaris 2.4 is available.

1995 Santa Cruz Operation buys UNIXware from Novell. SCO and HP announce a relationship to develop a 64-bit version of UNIX. Solaris 2.5 is available.

1997 Solaris 2.6 is available.

1998 Solaris 7 is available.

2000 Solaris 8 is available.

2001 Solaris 9 in Beta testing Q3.