Solaris is a Unix-based operating system introduced by Sun Microsystems in 1992 as the successor to SunOS.

Solaris is known for its scalability, especially on SPARC systems, as well for being the
origin for many innovative features such as DTrace and ZFS. Solaris supports SPARC-based and x86-based workstations and servers from Sun and other vendors, with efforts underway to port to additional platforms.

Solaris is certified against the Single Unix Specification. Although it was historically
developed as proprietary software, it is supported on systems manufactured by all major server vendors, and the majority of its codebase is now open source software via the OpenSolaris project.

• History

In 1987, AT&T and Sun announced that they were collaborating on a project to merge the most popular Unix variants on the market at that time: BSD, System V, and Xenix. This would become Unix System V Release 4 (SVR4).

On September 4, 1991, Sun announced that it would replace its existing BSD-derived Unix, SunOS 4, with one based on SVR4. This was identified internally as SunOS 5, but a new marketing name was introduced at the same time: Solaris 2.[4] While SunOS 4.1.x micro releases were retroactively named Solaris 1 by Sun, the Solaris name is almost exclusively used to refer to the SVR4-derived SunOS 5.0 and later.

The justification for this new "overbrand" was that it encompassed not only SunOS, but also he OpenWindows graphical user interface and Open Network Computing (ONC) functionality. The SunOS minor version is included in the Solaris release number; for example, Solaris 2.4 incorporated SunOS 5.4. After Solaris 2.6, Sun dropped the "2." from the number, so Solaris 7 incorporates SunOS 5.7, and the latest release SunOS 5.10 forms the core of Solaris 10.

• Supported architectures

Solaris uses a common code base for the platforms it supports: SPARC and i86pc (which includes both x86 and x86-64).Solaris has a reputation for being well-suited to symmetric multiprocessing, supporting a large number of CPUs. It has historically been tightly integrated with Sun's SPARC hardware (including support for 64-bit SPARC applications since Solaris 7), with which it is marketed as a combined package. This has often led to more reliable systems, but at a cost premium over commodity PC hardware. However, it has also supported x86 systems since Solaris 2.1 and the latest version, Solaris 10, includes support for 64-bit x86 applications, allowing Sun to capitalize on the availability of commodity 64-bit CPUs based on the x86-64 architecture. Sun has heavily marketed Solaris for use with both its own "x64" workstations and servers based on AMD Opteron and Intel Xeon processors, as well as x86 systems manufactured by companies such as Dell, Hewlett-Packard, and IBM. As of 2007, the following vendors support Solaris for their x86 server systems:

    * Dell - will "test, certify, and optimize Solaris and OpenSolaris on its rack and blade

servers and offer them as one of several choices in the overall Dell software menu"[8]
    * IBM - also distributes Solaris and Solaris Subscriptions for select x86-based IBM

System x servers and BladeCenter servers
    * Intel
    * Hewlett-Packard
    * Fujitsu Siemens

• UFS - Unix File System

The Unix file system (UFS) is a file system used by many Unix and Unix-like operating systems. It is also called the Berkeley Fast File System, the BSD Fast File System or FFS. It is a distant descendant of the original filesystem used by Version 7 Unix.

•  Design

 UFS volume is composed of the following parts:
a few blocks at the beginning of the partition reserved for boot blocks (which must be initialized separately from the filesystem)
a superblock, containing a magic number identifying this as a UFS filesystem, and some other vital numbers describing this filesystem's geometry and statistics and behavioral tuning parameters
a collection of cylinder groups. Each cylinder group has the following components:
a backup copy of the superblock
a cylinder group header, with statistics, free lists, etc, about this cylinder group, similar to those in the superblock
a number of inodes, each containing file attributes
a number of data blocks
Inodes are numbered sequentially. The first several inodes are reserved for historical reasons, followed by the inode for the root directory.
Directory files contain only the list of filenames in the directory and the inode associated with each file. All file metadata is kept in the inode.

• History and evolution

Early versions of Unix used filesystems referred to simply as FS. FS only included the boot block, superblock, a clump of inodes, and the data blocks. This worked well for the small disks early Unixes were designed for, but as technology advanced and disks got larger, moving the head back and forth between the clump of inodes and the data blocks they referred to caused thrashing. BSD optimized this in FFS (Fast File System) by inventing cylinder groups, breaking the disk up into smaller chunks, each with its own inode clump and data blocks.

The intent of BSD FFS is to try to localize associated data blocks and metadata in the same cylinder group, and ideally, all of the contents of a directory (both data and metadata for all the files) in the same or nearby cylinder group, thus reducing fragmentation caused by scattering a directory's contents over a whole disk.
Some of the performance parameters in the superblock included number of tracks and sectors, disk rotation speed, head speed, and alignment of the sectors between tracks. In a fully optimized system, the head could be moved between close tracks to read scattered sectors from alternating tracks while waiting for the platter to spin around.

As disks grew larger and larger, sector level optimization became obsolete (especially with disks that used linear sector numbering and variable sectors per track). With larger disks and larger files, fragmented reads became more of a problem. To combat this, BSD originally increased the filesystem block size from one sector to 1k in 4.0BSD, and, in FFS, increased the filesystem block size from 1k to 8k. This has several effects. The chances of a file's sectors being contiguous is much greater. The amount of overhead to list the file's blocks is reduced. The number of blocks representable in a fixed bit width block number is increased (allowing for larger disks).

With larger block sizes, disks with many small files would waste a lot of space, so BSD added block level fragmentation[1] (also called block suballocation, tail merging or tail packing), where the last partial block of data from several files may be stored in a single "fragment" block instead of multiple mostly empty blocks (Allen 2005).

•  Implementations

Vendors of some commercial Unix systems, such as SunOS/Solaris, System V Release 4, HP-UX, and Tru64 UNIX, have adopted UFS. Most of them adapted UFS to their own uses, adding proprietary extensions that may not be recognized by other vendors' versions of Unix. Surprisingly, many have continued to use the original block size and data field widths as the original UFS, so some degree of (read) compatibility remains across platforms. Compatibility between implementations as a whole is spotty at best and should be researched before using it across multiple platforms where shared data is a primary intent.

As of Solaris 7, Sun Microsystems included UFS Logging, which brought filesystem journaling to UFS. Solaris UFS also has extensions for large files and large disks and other features.

In 4.4BSD and BSD Unix systems derived from it, such as FreeBSD, NetBSD, OpenBSD, and DragonFlyBSD, the implementation of UFS1 and UFS2 is split into two layers — an upper layer that provides the directory structure and supports metadata (permissions, ownership, etc.) in the inode structure, and lower layers that provide data containers implemented as inodes. This was done to support both the traditional FFS and the LFS log-structured file system with common code for common functions. The upper layer is called "UFS", and the lower layers are called "FFS" and "LFS". In some of those systems, the term "FFS" is used for the combination of the FFS lower layer and the UFS upper layer, and the term "LFS" is used for the combination of the LFS lower layer and the UFS upper layer.

Kirk McKusick extended the FreeBSD FFS and UFS layers to support a new variant, called UFS2, which adds 64-bit block pointers (allowing volumes to grow up to 8 zettabytes), variable-sized blocks (similar to extents), extended flag fields, additional 'birthtime' stamps, extended attribute support and POSIX1.e ACLs. UFS2 became the default UFS version starting with FreeBSD 5.0. FreeBSD also introduced soft updates and the ability to make file system snapshots for both UFS1 and UFS2. These have since been ported to NetBSD. OpenBSD has supported soft updates since version 2.9  and UFS2 since version 4.2 . Since FreeBSD 7.0, UFS also fully supports filesystem journaling using gjournal mechanism.

Linux includes a UFS implementation for binary compatibility at the read level with other Unixes, but since there is no standard implementation for the vendor extensions to UFS, Linux does not have full support for writing to UFS. The native Linux ext2 filesystem is inspired by UFS. (In fact, in some 4.4BSD-derived systems, the UFS layer can use an ext2 layer as a container layer, just as it can use FFS and LFS.)
NeXTStep, which was BSD-derived, also used a version of UFS. In Apple's Mac OS X, it is available as an alternative to HFS+, their proprietary filesystem. However, as of Mac OS X v10.5, one cannot install Mac OS X "Leopard" on a UFS-formatted volume. In addition, one cannot upgrade older versions of Mac OS X installed on UFS-formatted volumes to Leopard; upgrading requires reformatting the startup volume.