Sponsored Content
Full Discussion: Solaris 10
Operating Systems Solaris Solaris 10 Post 51582 by nitrile on Monday 24th of May 2004 03:06:20 PM
Old 05-24-2004
This is an official list of changes from Sun:

===================================
Solaris 10 Beta Feature Summary:

Storage Technologies NFSv4 - The NFSv4 protocol is supported for both client and server, providing performance and functionality enhancements over NFSv3.

ZFS - (Zettabyte File System) A new storage system which replaces traditional file systems and volume managers in order to provide truly logical filesystems on top of any arrangement of storage devices.

Multipath I/O Boot - Allows booting from MPxIO controlled devices (such as T3 storage arrays).

Solaris Volume Manager - Further ease-of-use enhancements, such as a new tool for volume creation.

Multi-terabyte UFS/SVM System Management Consolidation and Virtualization Technologies Service Management Facility - An expanded mechanism for starting, managing, and monitoring long-running Solaris applications. Services started by this facility benefit from enhanced fault-tolerance, managability, and observability.

Solaris Zones - Zones are isolated, secure application environments hosted by the Solaris kernel. Zones provide improved server consolidation, allowing a single server to look like many.

Resource pools - A flexible configuration mechanism for partitioning of kernel resources among a set of workloads. Resource pools can be dynamically and automatically resized in accordance with system and application goals.

IP Quality of Service - Implements the IETF differentiated Service model enabling the definition of class of service for flows, users, projects, and a mapping to IEEE 802.1p user priorities.

Debugging, Tracing, and ObservabilityTechnologies KMDB (Kernel Modular Debugger) - A more flexible replacement for the existing kernel debugger (kadb), based on the mdb(1M)debugger.

Dtrace - A comprehensive and powerful new tracing facility, which allows dynamic instrumentation of kernel and user programs.

Networking Technologies IPMP Enhancements - Probe-based failure/repair detection is now optional, removing the need for IPMP test addresses and simplifying configuration. The set of drivers that support link up/down notifications has also been greatly extended.

IP Filter - IPFilter provides a stateful packet filter that can be used to provide Network Address Translation (NAT) or firewall services.

Wide Area Network Boot (WAN Boot) - Boot and install Solaris over http and/or https protocols; boot servers connected to the local subnet are not required.

Security Technologies Privilege-based security model - Fine grained control over the privileges with which a process runs. Provides the ability to limit privilege escalation attacks and further secures the system against hackers.

Encryption framework interfaces - A wide range of encryption algorithms are made available to user programs; hardware acceleration is automatically enabled when available.

Solaris x86-Based Platform Support Pentium IV Hyperthreading support SSE (Streaming SIMD Extensions) instruction support

Fault Management FMA - (Fault Management Administration) FMA provides a solution that monitors system behavoir and attempts to avoid downtiime by proactively self-healing a system in any way possible.
===================================

As you can see most of these changes are with an eye to enhance server and resource management/maximisation - Solaris is continuing to drift away from a workstation OS (though I'll doubtless continue to use it as such).

Some of the new features are pretty good. The zones model will let you run an entire server farm on one system, the overhead is very limited unlike e.g. with vmware yet still independent of the 'global' zone.

IPFilter..evolutionary, I already use this on Solaris 9 - saves me a step, if and when I upgrade my firewall.

On x86, the introduciton of SSE and hyperthreadting support is plenty overdue.

Dtrace, very interesting indeed though I've used it but little.

For me, Solaris 10 will not be major introduction but the new applications it will have are very interesting prospects.
 

4 More Discussions You Might Find Interesting

1. Solaris

application compiled on solaris 10 throwing error when executed on solaris 9

I have compiled my application on Solaris 10 with following description SunOS ldg1 5.10 Generic_138888-03 sun4v sparc SUNW,Sun-Blade-T6320 The compiler is Sun C++ 5.9 SunOS_sparc Patch 124863-01 2007/07/25 But when installing the application on Solaris 9 SunOS odcarch02 5.9... (2 Replies)
Discussion started by: ash_bit2k2
2 Replies

2. Solaris

Unable to login using ssh,telnet onto my solaris machine with solaris 10 installed

Hi, I am unable to login into my terminal hosting Solaris 10 and get the below error message "Server refused to allocate pty ld.so.1: sh: fatal: libc.so.1: open failed: No such file or directory " Is there anyways i can get into my machine and what kind of changes are required to be... (7 Replies)
Discussion started by: sankasu
7 Replies

3. Solaris

root disk mirroring in solaris volume manager for solaris 10

Need a procedure document to do "root disk mirroring in solaris volume manager for solaris 10". I hope some one will help me asap. I need to do it production environment. Let me know if you need any deatils on this. Thanks, Rama (1 Reply)
Discussion started by: ramareddi16
1 Replies

4. Solaris

Patching Procedure in Solaris 10 with sun cluster having Solaris zone

Hi Gurus I am not able to find the patching procedure for solaris 10 ( sol10 u11) to latest patchset with sun cluster having failover zones so that same I should follow. Take an instance, there are sol1 and sol2 nodes and having two failover zones like sozone1-rg and sozone2-rg and currently... (1 Reply)
Discussion started by: nick101
1 Replies
kadb(1M)                                                  System Administration Commands                                                  kadb(1M)

NAME
kadb - a kernel debugger SYNOPSIS
SPARC ok boot device_specifier kadb [-d] [boot-flags] x86 select (b)oot or (i)nterpreter: b kadb [-d] [boot-flags] DESCRIPTION
kadb, an interactive kernel debugger, has been replaced by kmdb(1). For backwards compatibility, the methods used to load kadb will be interpreted as requests to load kmdb(1). Unlike with the compatibility link from adb(1) to mdb(1), kmdb(1) will always load in its native user interface mode, regardless of the name used to load it. kmdb(1) is based on mdb(1), and thus shares mdb's user interface style and feature set. The mdb(1) man page describes the features and operation of mdb. The kmdb(1) man page describes the differences between mdb and kmdb. This man page describes the major changes and incom- patibilities between kadb and kmdb. Consult the Solaris Modular Debugger Guide for a detailed description of both mdb and kmdb. Major changes This section briefly lists the major differences between kadb and kmdb. It is not intended to be exhaustive. Debugger Loading and Unloading kmdb(1) may be loaded at boot, as with kadb. It may also be loaded after boot, thus allowing for kernel debugging and execution control without requiring a system reboot. If kmdb(1) is loaded after boot, it may be unloaded. mdb Feature Set The features introduced by mdb(1), including access to kernel type data, debugger commands (dcmds), debugger modules (dmods), and enhanced execution control facilities, are available under kmdb(1). Support for changing the representative CPU (:x) is available for both SPARC and x86. Furthermore, full execution-control facilities are available after the representative CPU has been changed. Significant Incompatibilities This section lists the significant features that have changed incompatibly between kadb and kmdb(1). It is not intended to be exhaustive. All kmdb(1) commands referenced here are fully described in the kmdb(1) man page. A description as well as examples can be found in the Solaris Modular Debugger Guide. Deferred Breakpoints The kadb-style "module#symbol:b" syntax is not supported under kmdb(1). Instead, use "::bp module`symbol". Watchpoints The ::wp dcmd is the preferred way to set watchpoint with kmdb. Various options are available to control the type of watchpoint set, including -p for physical watchpoints (SPARC only), and -i for I/O port watchpoints (x86 only). $l is not supported, therefore, the watchpoint size must be specified for each watchpoint created. Access to I/O Ports (x86 only) The commands used to access I/O ports under kadb have been replaced with the ::in and ::out dcmds. These two dcmds allow both read and write of all I/O port sizes supported by kadb. ATTRIBUTES
See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SUNWcar | +-----------------------------+-----------------------------+ SEE ALSO
adb(1), mdb(1), kmdb(1), attributes(5) Solaris Modular Debugger Guide SunOS 5.10 2 Jul 2004 kadb(1M)
All times are GMT -4. The time now is 07:50 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy