Unix/linux System Management Technical Manual Read (v)

2016.8.19 17:20-17:50

HP-UX is based on System V and are tied to Hewlett-Packard ' s hardware platforms. It ' s closer to the ancestral source tree than either Solaris or AIX, but HP have kept pace with developments in the OS worl D and have added a variety of its own enhancements. Now that HP have begun supporting Linux as well, the future of HPUX was somewhat less clear.

HP- UX is based on system V and is used only for HP hardware platforms. It is closer to the source than Solaris and Aix on the UNIX genealogy, but HP has followed the development of the operating system and added various enhancements to HP-UX. Now HP is also starting to support Linux, and the future of HP-UX is a bit unclear.

IBM ' s AIX started as a variant of Berkeley ' s 4.2BSD, but as of version 4 in 1994, most parts of the system migrated to Sys TEM V. At the this point, AIX have drifted rather far from both origins.

IBM's AIX started out as a variant of the Berkeley 4.2BSD, but by the 4th edition of 1994, most of the operating system migrated to System V. The distance between Aix and the previous two source systems is now quite remote.

In general, we had the impression that AIX had enjoyed less cross-pollination from other systems than most UNIX variants. It also seems to has fallen under the svengali-like influence of some of IBM ' s mainframe and as/400 operating systems, F Rom which it inherits conventions such as the Object Data Manager (see page 432), the use of the configuration commands rather than configuration files, and the SMIT administrative interface. Over time, one might charitably say, it had grown to is more and more like itself.

In general , we have an impression of Aix that there is little communication between AIX and other systems compared to most UNIX variants. Aix also seems to have been affected by some of the bad effects of IBM's mainframe and AS/400 operating systems, which have inherited a tradition like ODM, using configuration commands instead of configuration files, and Smit management interfaces. As time goes by, people may be kind enough to say that Aix has become more and more like itself.

IBM has been pursuing a interestingly os-agnostic approach to marketing their hardware for the very last decade. IBM continues to develop and promote AIX, but it's also engaged in partnerships with Red Hat and Novell to ensure the IR respective Linux distributions run smoothly on IBM hardware. It'll be interesting the approach plays out in the years ahead.

for most of the past 10 years, it's interesting that IBM has been trying to keep an uncertain attitude to operating system choices for marketing its own hardware devices. IBM continues to develop and promote AIX, but it also forms a partnership with Red Hat and Novell to ensure that both Linux distributions run smoothly on IBM hardware. It is also interesting to observe how this will work in the coming years.

1.6 System-specific Administration TOOLS

Modern systems include a variety of visually oriented tools and control panels (such as SUSE ' s YaST2 and IBM's SMIT) that Help you configure or administer selected aspects of the system. These tools is useful, especially for novice administrators, but they also tend to be relatively incomplete reflections O f the underlying software. They make many administrative tasks easier and most fall short of being authoritative.

1.6 System-specific management tools

within the modern operating system, there are a variety of visual tools and control panels (such as SuSE's YaST2 and IBM Smit) that help users configure or manage selected system functions. These tools are very useful, especially for novice administrators, but they also tend to not completely reflect the actual operation of the underlying software. They make management easier, but most become less authoritative.

In this book, we cover the underlying mechanisms that the visual tools manipulate rather than the tools themselves, for SE Veral reasons. For one, the visual tools tend to is proprietary (or at least, system-specific). They introduce variation into processes so may actually is quite consistent among systems at a lower level. Second, we believe that it's important for administrators to a accurate understanding of how their systems work. When the system breaks, the visual tools is often not helpful in tracking and fixing problems. Finally, the manual configuration is often faster, the more flexible, the more reliable, and the easier to script.

in this book, for the following reasons, we introduce the underlying mechanism of the visualizer invocation, not the tool itself. The first visualization tool tends to be proprietary (or at least tends to be unique to the system). They bring variables to the configuration process, and these processes may actually be quite consistent at a lower level between the various systems. Second, we believe it is important for system administrators to know exactly how their systems work. When a system fails, the visualizer is often not helpful for identifying and correcting the problem. Finally, manual configuration is often better, faster, more flexible, more reliable, and easier to implement with scripting.

This article is from the "Zhao Dongwei blog" blog, make sure to keep this source http://zhaodongwei.blog.51cto.com/4233742/1840387

Unix/linux System Management Technical Manual Read (v)