标签：读书
2016.8.19 17:20-17:50
HP-UX is based on System V and is tied to Hewlett-Packard’s hardware platforms. It’s closer to the ancestral source tree than either Solaris or AIX, but HP has kept pace with developments in the OS world and has added a variety of its own enhancements. Now that HP has begun supporting Linux as well, the future of HPUX is somewhat less clear.
HP-UX基于System V，并且只用于HP公司的硬件平台。在UNIX族谱上它比Solaris和AIX离源头更近，但是HP一直紧跟操作系统界的发展脚步，给HP-UX加入了各种各样的增强功能。现在HP也开始支持Linux了，HP-UX的未来有点儿不太清晰。
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 System V. At this point, AIX has drifted rather far from both origins.
IBM的AIX一开始是伯克利4.2BSD的一种变体，但是到1994年的第4版，这个操作系统的大部分都迁移到了System V上面。现在AIX和前面两种源头系统的距离都已经相当遥远了。
In general, we have the impression that AIX has enjoyed less cross-pollination from other systems than most UNIX variants. It also seems to have fallen under the Svengali-like influence of some of IBM’s mainframe and AS/400 operating systems, from which it inherits conventions such as the Object Data Manager (see page 432), the use of configuration commands rather than configuration files, and the SMIT administrative interface. Over time, one might charitably say, it has grown to be more and more like itself.
一般而言，我们对AIX的印象是，比起大多数UNIX变体来说，AIX和其他系统的交流很少。AIX也似乎受到了IBM的大型机和AS/400操作系统某些不好的影响，变得有点强人所难，它从后者那里继承了像ODM、使用配置命令而不是配置文件，以及SMIT管理界面等这样的传统。随着时间的推移，人们或许会厚道地说，AIX已经变得越来越像它自己了。
IBM has been pursuing an interestingly OS-agnostic approach to marketing its hardware for most of the last decade. IBM continues to develop and promote AIX, but it’s also engaged in partnerships with Red Hat and Novell to ensure that their respective Linux distributions run smoothly on IBM hardware. It will be interesting to see how this approach plays out in the years ahead.
在过去10年中的大多数时间里，IBM为营销自己的硬件设备，对操作系统选择一直力求保持一种不明朗的态度，这点显得很有意思。IBM继续开发和推广AIX，但是它也同Red Hat和Novell形成伙伴关系，确保这两家的Linux发行版本能够顺利地运行在IBM的硬件上。静观这样做法在未来几年会带来怎样的效果也挺有意思的。
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 are useful, especially for novice administrators, but they also tend to be relatively incomplete reflections of the underlying software. They make many administrative tasks easier, but most fall short of being authoritative.
1.6 特定于系统的管理工具
在现代的操作系统内，包含有各种各样可视化的工具和控制面板（比如SUSE的YaST2和IBM的SMIT），帮助用户配置或者管理选定的系统功能。这些工具非常有用，特别是对于管理员新手来说更是如此，但是它们也倾向于不能完整地体现下层软件的实际操作。它们让管理工作变得容易，但大多数又变得不那么权威。
In this book, we cover the underlying mechanisms that the visual tools manipulate rather than the tools themselves, for several reasons. For one, the visual tools tend to be proprietary (or at least, system-specific). They introduce variation into processes that may actually be quite consistent among systems at a lower level. Second, we believe that it’s important for administrators to have an accurate understanding of how their systems work. When the system breaks, the visual tools are often not helpful in tracking down and fixing problems. Finally, manual configuration is often faster, more flexible, more reliable, and easier to script.
在本书中，出于下面几个原因，我们要介绍可视化工具调用的底层机制，而不是工具本身。第一可视化工具趋于专有化（或者至少是趋于为系统所特有）。它们给配置过程带来了变数，而在各个系统之间，这些过程在较低层面实际上可能是相当一致的。第二，我们相信，对于系统管理员来说，准确了解他们的系统是如何工作，这点非常重要。当系统发生故障的时候，可视化工具通常对于确定并修正问题来说没有什么帮助。最后，手工配置往往更好、更快、更灵活、更可靠，而且更易于用脚本实现。
本文出自 “赵东伟的博客” 博客，请务必保留此出处http://zhaodongwei.blog.51cto.com/4233742/1840387
标签：读书
原文地址：http://zhaodongwei.blog.51cto.com/4233742/1840387
