DOCSLIB.ORG

CXFSTM 5 Administration Guide for SGI® Infinitestorage

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
CXFSTM 5 Administration Guide for SGI® Infinitestorage CXFSTM 5 Administration Guide for SGI® InfiniteStorage 007–4016–029 COPYRIGHT © 1999–2009 SGI. All rights reserved; provided portions may be copyright in third parties, as indicated elsewhere herein. No permission is granted to copy, distribute, or create derivative works from the contents of this electronic documentation in any manner, in whole or in part, without the prior written permission of SGI. The following copyright notice applies to the LZF algorithm: Copyright (c) 2000-2005 Marc Alexander Lehmann <[email protected]> Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: 1. Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer. 2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution. 3. The name of the author may not be used to endorse or promote products derived from this software without specific prior written permission. THIS SOFTWARE IS PROVIDED BY THE AUTHOR ‘‘AS IS’’ AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY,WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. LIMITED RIGHTS LEGEND The software described in this document is "commercial computer software" provided with restricted rights (except as to included open/free source) as specified in the FAR 52.227-19 and/or the DFAR 227.7202, or successive sections. Use beyond license provisions is a violation of worldwide intellectual property laws, treaties and conventions. This document is provided with limited rights as defined in 52.227-14. TRADEMARKS AND ATTRIBUTIONS SGI, Altix, the SGI cube, the SGI logo, IRIX, O2, Octane, Onyx, Onyx2, Origin, Silicon Graphics Prism, Silicon Graphics Tezro, and XFS are registered trademarks and CXFS, FDDIXPress, NUMAlink, Octane2, Performance Co-Pilot, Silicon Graphics Fuel, and SGI ProPack are trademarks of SGI in the United States and/or other countries worldwide. AIX and IBM are registered trademarks of IBM Corporation. Brocade is a trademark of Brocade Communication Systems, Inc. Digi is a trademark of Digi International, Inc. Java and Sun are registered trademarks and Solaris is a trademark of Sun Microsystems, Inc. Linux is a registered trademark of Linus Torvalds in several countries. Legato NetWorker is a registered trademark of Legato Systems, Inc. Mac OS is a registered trademark of Apple Computer, Inc. Netscape is a trademark of Netscape Communications Corporation. QLogic is a registered trademark of QLogic Corporation. Red Hat is a registered trademark and RPM is a trademark of Red Hat, Inc. UNIX is a registered trademark of The Open Group in the United States and other countries. VERITAS is a trademark of VERITAS Software Corporation. Microsoft, Windows, Windows NT, and Windows Vista are registered trademarks or trademarks of Microsoft Corporation. X/Open is a registered trademark of X/Open Company Ltd. All other trademarks mentioned herein are the property of their respective owners. New Features in This Guide Note: Be sure to read the release notes for the SGI InfiniteStorage Software Platform, your specific CXFS platforms, and the late-breaking caveats pages on Supportfolio to learn about any changes to the installation and configuration procedures. This version includes corrections and the following: • "Unmount Filesystems Before Adding or Deleting Server-Capable Administration Nodes" on page 51 • "Change the Brocade Password when Prompted" on page 70 • "Use a Time Synchronization Application" on page 81 • "Turn Off Local XVM on Linux Nodes if Unused" on page 81 • "Configuring SuSEfirewall2" on page 115 • "Dynamic Parameters for Debugging Purposes Only" on page 468 007–4016–029 iii Record of Revision Version Description 001 September 1999 Supports the CXFS 1.1 product in the IRIX 6.5.6f release. 002 October 1999 Supports the CXFS 1.1 product in the IRIX 6.5.6f release. 003 December 1999 Supports the CXFS product in the IRIX 6.5.7f release. 004 March 2000 Supports the CXFS product in the IRIX 6.5.8f release. 005 June 2000 Supports the CXFS product in the IRIX 6.5.9f release. 006 September 2000 Supports the CXFS product in the IRIX 6.5.10f release. 007 January 2001 Supports the CXFS product in the IRIX 6.5.11f release. 008 March 2001 Supports the CXFS product in the IRIX 6.5.12f release. 009 June 2001 Supports the CXFS product in the IRIX 6.5.13f release. 011 September 2001 Supports the CXFS product in the IRIX 6.5.14f release. (Note, there was no 010 version due to an internal numbering mechanism.) 012 December 2001 Supports the CXFS Version 2 product in IRIX 6.5.15f. 013 March 2002 Supports the CXFS Version 2 product in IRIX 6.5.16f. 007–4016–029 v Record of Revision 014 June 2002 Supports the CXFS Version 2 product in IRIX 6.5.17f. 015 September 2002 Supports the CXFS Version 2 product in IRIX 6.5.18f. 016 December 2002 Supports the CXFS Version 2 product in IRIX 6.5.19f. 017 March 2003 Supports the CXFS Version 2 product in IRIX 6.5.20f. 018 September 2003 Supports the CXFS 3.0 product in IRIX 6.5.22 and CXFS 3.0 for SGI Altix 3000 running SGI ProPack 2.3 for Linux. 019 December 2003 Supports the CXFS 3.1 product in IRIX 6.5.23 and CXFS 3.1 for SGI Altix 3000 running SGI ProPack 2.4 for Linux. 020 March 2004 Supports the CXFS 3.2 product in IRIX 6.5.24 and CXFS 3.2 for SGI Altix 3000 running SGI ProPack 3 for Linux. 021 November 2004 Supports the CXFS 3.2 product in IRIX 6.5.24 and CXFS 3.2 for SGI Altix 3000 running SGI ProPack 3 for Linux. 022 April 2005 Supports the CXFS 3.3 product 023 July 2005 Supports the CXFS 3.4 product 024 May 2006 Supports the CXFS 4.0 product 025 January 2007 Supports the CXFS 4.1 product vi 007–4016–029 CXFSTM 5 Administration Guide for SGI® InfiniteStorage 026 September 2007 Supports the CXFS 4.2 product 027 March 2008 Supports the CXFS 5.0 product 028 September 2008 Supports the CXFS 5.2 product 029 March 2009 Supports the CXFS 5.4 product in ISSP 1.6 007–4016–029 vii Contents About This Guide .....................xxxvii Related Publications . ...................xxxvii Obtaining Publications . ...................xxxix Conventions . ........................ xl Reader Comments ....................... xli 1. Introduction to CXFS . ................. 1 What is CXFS? ........................ 1 Comparison of XFS and CXFS ................... 3 Differences in Filesystem Mounting and Management . ......... 3 Supported XFS Features . ................... 4 When to Use CXFS . ................... 5 Performance Considerations ................... 6 Comparison of Network and CXFS Filesystems .............. 7 Network Filesystems . ................... 7 CXFS Filesystems . ................... 7 CXFS Features ....................... 8 CXFS Restrictions . ................... 9 Cluster Environment Concepts ................... 9 Metadata . ........................ 10 Node . ........................ 10 RAID . ........................ 10 LUN.......................... 10 Cluster . ........................ 11 Pool . ........................ 11 007–4016–029 ix Contents Node Types, Node Functions, and the Cluster Database . ......... 12 Membership ........................ 22 Private Network ....................... 22 Data Integrity Protection . ................... 24 CXFS Tiebreaker ....................... 24 Relocation . ........................ 25 Recovery . ........................ 25 CXFS Services ....................... 28 CXFS Interoperability With Other Products and Features . ......... 28 Data Migration Facility (DMF) .................. 29 Highly Available Services . ................... 29 GPT Labels Overview . ................... 30 Guaranteed-Rate I/O (GRIO) Version 2 Overview . ......... 30 Storage Management . ................... 31 Storage Backups Differences .................. 31 NFS Differences . ................... 31 Quotas Differences . ................... 32 Samba Differences . ................... 32 Volume Management with XVM .................. 33 XVM Failover Version 2 Overview . .............. 34 Hardware and Software Requirements for Server-Capable Administration Nodes . 34 CXFS Software Products Installed on Server-Capable Administration Nodes . 36 CXFS Tools . ........................ 37 Configuration Commands . ................... 37 CXFS GUI Overview . ................... 38 cxfs_admin Command-Line Configuration Tool Overview ........ 40 Cluster Administration Daemons .................. 41 CXFS Control Daemons . ................... 42 x 007–4016–029 CXFSTM 5 Administration Guide for SGI® InfiniteStorage Other Commonly Used Administrative Commands . ......... 42 2. Best Practices . ..................... 45 Configuration Best Practices . ................... 45 Fix Network Issues First . ................... 46 Save the Current Configuration Before Making Changes . ......... 46 Save the CXFS Configuration .................. 47 Save the XVM Configuration
Load more

Recommended publications
  • A Ballista Retrospective
    Software Robustness Testing A Ballista Retrospective Phil Koopman [email protected] http://ballista.org With contributions from: Dan Siewiorek, Kobey DeVale John DeVale, Kim Fernsler, Dave Guttendorf, Nathan Kropp, Jiantao Pan, Charles Shelton, Ying Shi Institute for Complex Engineered Systems Overview Introduction • APIs aren’t robust (and people act as if they don’t want them to be robust!) Top 4 Reasons people give for ignoring robustness improvement • “My API is already robust, especially for easy problems” (it’s probably not) • “Robustness is impractical” (it is practical) • “Robust code will be too slow” (it need not be) • “We already know how to do it, thank you very much” (perhaps they don’t) Conclusions • The big future problem for “near-stationary” robustness isn’t technology -- it is awareness & training 2 Ballista Software Testing Overview SPECIFIED INPUT RESPONSE BEHAVIOR SPACE SPACE ROBUST SHOULD VAL I D OPERATION WORK INPUTS MO DULE REPRODUCIBLE UNDEFINED UNDER FAILURE TEST SHOULD INVALID INPUTS UNREPRODUCIBLE RETURN FAILURE ERROR Abstracts testing to the API/Data type level • Most test cases are exceptional • Test cases based on best-practice SW testing methodology 3 Ballista: Test Generation (fine grain testing) Tests developed per data type/subtype; scalable via composition 4 Initial Results: Most APIs Weren’t Robust Unix & Windows systems had poor robustness scores: • 24% to 48% of intentionally exceptional Unix tests yielded non-robust results • Found simple “system killer” programs in Unix, Win 95/98/ME, and WinCE
    [Show full text]
  • Introduction to UNIX What Is UNIX? Why UNIX? Brief History of UNIX Early UNIX History UNIX Variants
    What is UNIX? A modern computer operating system Introduction to UNIX Operating system: “a program that acts as an intermediary between a user of the computer and the computer hardware” CS 2204 Software that manages your computer’s resources (files, programs, disks, network, …) Class meeting 1 e.g. Windows, MacOS Modern: features for stability, flexibility, multiple users and programs, configurability, etc. *Notes by Doug Bowman and other members of the CS faculty at Virginia Tech. Copyright 2001-2003. (C) Doug Bowman, Virginia Tech, 2001- 2 Why UNIX? Brief history of UNIX Used in many scientific and industrial settings Ken Thompson & Dennis Richie Huge number of free and well-written originally developed the earliest software programs versions of UNIX at Bell Labs for Open-source OS internal use in 1970s Internet servers and services run on UNIX Borrowed best ideas from other Oss Largely hardware-independent Meant for programmers and computer Based on standards experts Meant to run on “mini computers” (C) Doug Bowman, Virginia Tech, 2001- 3 (C) Doug Bowman, Virginia Tech, 2001- 4 Early UNIX History UNIX variants Thompson also rewrote the operating system Two main threads of development: in high level language of his own design Berkeley software distribution (BSD) which he called B. Unix System Laboratories System V Sun: SunOS, Solaris The B language lacked many features and Ritchie decided to design a successor to B GNU: Linux (many flavors) which he called C. SGI: Irix They then rewrote UNIX in the C FreeBSD programming language to aid in portability. Hewlett-Packard: HP-UX Apple: OS X (Darwin) … (C) Doug Bowman, Virginia Tech, 2001- 5 (C) Doug Bowman, Virginia Tech, 2001- 6 1 Layers in the UNIX System UNIX Structure User Interface The kernel is the core of the UNIX Library Interface Users system, controlling the system Standard Utility Programs hardware and performing various low- (shell, editors, compilers, etc.) System Interface calls User Mode level functions.
    [Show full text]
  • Absolute BSD—The Ultimate Guide to Freebsd Table of Contents Absolute BSD—The Ultimate Guide to Freebsd
    Absolute BSD—The Ultimate Guide to FreeBSD Table of Contents Absolute BSD—The Ultimate Guide to FreeBSD............................................................................1 Dedication..........................................................................................................................................3 Foreword............................................................................................................................................4 Introduction........................................................................................................................................5 What Is FreeBSD?...................................................................................................................5 How Did FreeBSD Get Here?..................................................................................................5 The BSD License: BSD Goes Public.......................................................................................6 The Birth of Modern FreeBSD.................................................................................................6 FreeBSD Development............................................................................................................7 Committers.........................................................................................................................7 Contributors........................................................................................................................8 Users..................................................................................................................................8
    [Show full text]
  • Introduction
    CS307 Operating Systems Introduction Fan Wu Department of Computer Science and Engineering Shanghai Jiao Tong University Spring 2020 Operating Systems Operating Systems 2 Operating Systems UNIX-family: BSD(Berkeley Software Distribution), System-V, GNU/Linux, MINIX, Nachos, OS X, iOS BSD-family: FreeBSD, NetBSD, OpenBSD System-V-family: AIX, HP-UX, IRIX, Solaris Linux-family: Red Hat, Debian, Ubuntu, Fedora, openSUSE, Linux Mint, Google's Android, WebOS, Meego MS-DOS, Microsoft Windows, Windows Mobile, Win-CE, WP8 AmigaOS Symbian, MeeGo Google Chrome OS OS/2 XrossMediaBar(XMB) for PS3, Orbis OS for PS4 Input Output System for Wii Tiny-OS, LynxOS, QNX, VxWorks Operating Systems 3 Four Components of a Computer System People, machines, other computers Application programs define the ways in which theSystem system programs resources are arecomputer used to software solve the computingdesigned to problems operate theof thecomputer users hardware and toControls provide and a platformcoordinates for runninguse of hardware application among programsvarious applications and users provides basic computing resources Operating Systems 4 Computer System Structure Hardware – provides basic computing resources CPU, memory, I/O devices Operating system – Controls and coordinates use of hardware among various applications and users System programs – are computer software designed to operate the computer hardware and to provide a platform for running application programs BIOS and device drivers Application programs – define the ways in
    [Show full text]
  • Google Announces Chrome OS, for Release Mid
    Google Announces Chrome OS, For Release Mid-... http://tech.slashdot.org/story/09/07/08/0953238/... Slashdot Stories Slash Boxes Comments Search Deals new SlashTV Jobs Newsletter Submit Login Join Slashdot81 Full 19 stories Abbreviated can be 0listened Hidden to in audio form via an RSS feed,/Sea as read by our own robotic overlord. Score: 5 4 3 2 Nickname: 1 0 -1Password: 989 More Login Public Terminal Nickname:Log In Forgot your password? Sign in with Password: Google Public Terminal Twitter Log In Forgot yourFacebook password? Close LinkedIn Close Close Stories Submissions Popular Blog Slashdot Build Ask Slashdot Book Reviews Games Idle YRO Technology Cloud Hardware Linux Management Mobile Science Security Storage 1 of 31 03/01/15 17:19 Google Announces Chrome OS, For Release Mid-... http://tech.slashdot.org/story/09/07/08/0953238/... Announcing: Slashdot Deals - Explore geek apps, games, gadgets and more. (what is this?) Close, and don't show me this again Google Announces Chrome OS, For Release Mid-2010 1089 Posted by timothy on Wednesday July 08, 2009 @07:14AM from the bring-on-the-shiny dept. Zaiff Urgulbunger writes "After years of speculation, Google has announced Google Chrome OS, which should be available mid-2010. Initially targeting netbooks, its main selling points are speed, simplicity and security — which kind of implies that the current No.1 OS doesn't deliver in these areas! The Chrome OS will run on both x86 and ARM architectures, uses a Linux kernel with a new windowing system. According to Google, 'For application developers, the web is the platform.
    [Show full text]
  • SDE 3.0.1 System Requirements
    SDE 3.0.1 System Requirements This PDF contains system requirements information, including hardware requirements, best performance configurations, and limitations, for SDE 3.0.1. Compaq/Digital Tru64 UNIX V4.0b o Oracle 8 (32 bit) Enterprise Server 7.3.3 o Oracle 8 (32 bit) Workgroup Server 7.3.3 Compaq/Digital Tru64 UNIX V4.0c o Oracle 8 (32 bit) Enterprise Server 7.3.3 o Oracle 8 (32 bit) Workgroup Server 7.3.3 Compaq/Digital Tru64 UNIX V4.0d o Oracle 8 (32 bit) Enterprise Server 7.3.3 o Oracle 8 (32 bit) Workgroup Server 7.3.3 HP HP-UX 10.20 (700 series, 8x7 series) o Oracle 8 (32 bit) Enterprise Server 7.3.3 o Oracle 8 (32 bit) Workgroup Server 7.3.3 o Sybase SQL Server 11.0.2 HP HP-UX 11.0 (700 series, 8x7 series) o Oracle 8 (32 bit) Enterprise Server 7.3.3 o Oracle 8 (32 bit) Workgroup Server 7.3.3 IBM AIX 4.1.5.0 o IBM DB2 Common Server 2.1.2 o IBM DB2 Universal Database (UDB) 5.0 o Oracle 8 (32 bit) Enterprise Server 7.3.3 o Oracle 8 (32 bit) Workgroup Server 7.3.3 o Sybase SQL Server 11.0.2 IBM AIX 4.2.1.0 o IBM DB2 Universal Database (UDB) 5.0 o Oracle 8 (32 bit) Enterprise Server 7.3.3 o Oracle 8 (32 bit) Workgroup Server 7.3.3 IBM AIX 4.3.0.0 o Oracle 8 (32 bit) Enterprise Server 7.3.3 o Oracle 8 (32 bit) Workgroup Server 7.3.3 PC-Intel Windows NT 4.0 o Microsoft SQL Server 6.5 o Oracle 8 (32 bit) Enterprise Server 7.3.3 o Oracle 8 (32 bit) Workgroup Server 7.3.3 SGI IRIX 6.2 o Oracle 8 (32 bit) Enterprise Server 7.3.3 o Oracle 8 (32 bit) Workgroup Server 7.3.3 o Sybase SQL Server 11.0.2 SGI IRIX 6.3 o Oracle 8 (32 bit) Enterprise
    [Show full text]
  • Porting IRIX® Applications to SGI® Altix® Platforms: SGI Propack™ for Linux®
    Porting IRIX® Applications to SGI® Altix® Platforms: SGI ProPack™ for Linux® 007-4674-001 CONTRIBUTORS WrittenbyStevenLevine Illustrated by Chrystie Danzer Production by Karen Jacobson Engineering contributions by George Pirocanac COPYRIGHT © 2004, Silicon Graphics, Inc. All rights reserved; provided portions may be copyright in third parties, as indicated elsewhere herein. No permission is granted to copy, distribute, or create derivative works from the contents of this electronic documentation in any manner, in whole or in part, without the prior written permission of Silicon Graphics, Inc. LIMITED RIGHTS LEGEND The software described in this document is “commercial computer software” provided with restricted rights (except as to included open/free source) as specified in the FAR 52.227-19 and/or the DFAR 227.7202, or successive sections. Use beyond license provisions is a violation of worldwide intellectual property laws, treaties and conventions. This document is provided with limited rights as defined in 52.227-14. TRADEMARKS AND ATTRIBUTIONS Silicon Graphics, SGI, the SGI logo, Altix, IRIX, Origin, Onyx, Onyx2, and XFS are registered trademarks and CaseVision, NUMAflex, NUMAlink, OpenMP, Performance Co-Pilot, ProDev, SGI Advanced Linux, SGI ProPack, SGIconsole, and SHMEM are trademarks of Silicon Graphics, Inc., in the United States and/or other countries worldwide. SGI Advanced Linux Environment 3.0 is based on Red Hat Enterprise Linux AS 3.0, but is not sponsored by or endorsed by Red Hat, Inc. in any way. Cray is a registered trademark of Cray, Inc. FLEXlm is a registered trademark of Macrovision Corporation. Java is a registered trademark of Sun Microsystems, Inc. in the United States and/or other countries.
    [Show full text]
  • IRIX® Admin System Configuration and Operation
    IRIX® Admin System Configuration and Operation 007-2859-017 COPYRIGHT © 1992-2001 Silicon Graphics, Inc. All rights reserved; provided portions may be copyright in third parties, as indicated elsewhere herein. No permission is granted to copy, distribute, or create derivative works from the contents of this electronic documentation in any manner, in whole or in part, without the prior written permission of Silicon Graphics, Inc. LIMITED RIGHTS LEGEND The electronic (software) version of this document was developed at private expense; if acquired under an agreement with the USA government or any contractor thereto, it is acquired as "commercial computer software" subject to the provisions of its applicable license agreement, as specified in (a) 48 CFR 12.212 of the FAR; or, if acquired for Department of Defense units, (b) 48 CFR 227-7202 of the DoD FAR Supplement; or sections succeeding thereto. Contractor/manufacturer is Silicon Graphics, Inc., 1600 Amphitheatre Pkwy 2E, Mountain View, CA 94043-1351. TRADEMARKS AND ATTRIBUTIONS Challenge, Indigo, IRIS, IRIX, Octane, and Onyx are registered trademarks and SGI, Crimson, Indigo2, IRIS FailSafe, IRIS InSight, IRIS WorkSpace, IRIX Networker, NUMAlink, Origin, Performance Co-Pilot, Power Challenge, Power Indigo2, Power Onyx, the SGI logo, and XFS are trademarks of Silicon Graphics, Inc. Indy is a registered trademark, used under license in the United States and owned by Silicon Graphics, Inc., in other countries worldwide. Centronics is a trademark of Centronics Data Computer Corporation. Cray is a registered trademark of Cray, Inc. Documenter’s Workbench is a trademark of Novell, Inc. FrameMaker, Illustrator, and PostScript are trademarks of Adobe Systems, Incorporated.
    [Show full text]
  • Low Overhead Real-Time Computing • General Purpose OS's Can Be
    Low Overhead Real-Time Computing • General Purpose OS’s can be highly unpredictable • Linux response times seen in the 100’s of milliseconds • Work around this by isolating from interrupts and other processes and kernel threads • Put as much functionality into user space as possible User Space Functionality • Memory map hardware and clocks, and handle interrupts in user space • Use shared memory for IPC • Memory map special kernel pages or use virtual system calls • Do uncontended locking with IRIX usyncs or Linux futuxes Mutex Protocol Performance Time to Acquire and Release Once (ns) 100000 14,219 10000 725 715 1000 254 260 100 10 1 None Non- Priority Priority Ceiling Priority Ceiling preemptive Inheritance - Same Priority - Higher Priority Mutex Protocol Overview - General Purpose OS’s are complicated and unpredictable - Good RT performance may be had by protecting cpu’s from outside interference - User level interfaces to common features further reduce latency and unpredictability - Summary: Lock out and avoid as much of the kernel as possible 10/1/2003 1 Methods of Blocking Interruptions - Restrict cpu’s to specific threads - Isolate cpu’s from TLB and cache invalidations - Direct hardware interrupts elsewhere - Turn off the timeshare scheduling interrupt - Ward off any remaining kernel background tasks 10/1/2003 2 Lock in User Space When Possible - IRIX? usyncs and Linux? futexes attempt to handle most locking actions with atomic primitives outside the kernel - Contended locks force accessors into the kernel to use wait queues -
    [Show full text]
  • Packaging for 11 Platforms with One Tool
    Packaging for 11 platforms with one tool Jens Rehsack 2013 Jens Rehsack () Packaging for 11 platforms with one tool 2013 1 / 6 everyone know that but packaging takes time can't use dpkg's from developers machine on CentOS production server dependencies don't compile on backend AIX machine Packaging improves . Packaging Why packaging? Packaging provides Information - always know what is installed Reliability - always know if things belong together Useful - easy deployment / rollout Jens Rehsack () Packaging for 11 platforms with one tool 2013 2 / 6 everyone know that but packaging takes time can't use dpkg's from developers machine on CentOS production server dependencies don't compile on backend AIX machine Packaging Why packaging? Packaging provides Information - always know what is installed Reliability - always know if things belong together Useful - easy deployment / rollout Packaging improves . Jens Rehsack () Packaging for 11 platforms with one tool 2013 2 / 6 but packaging takes time can't use dpkg's from developers machine on CentOS production server dependencies don't compile on backend AIX machine Packaging Why packaging? Packaging provides Information - always know what is installed Reliability - always know if things belong together Useful - easy deployment / rollout Packaging improves . everyone know that Jens Rehsack () Packaging for 11 platforms with one tool 2013 2 / 6 Packaging Why packaging? Packaging provides Information - always know what is installed Reliability - always know if things belong together Useful - easy
    [Show full text]
  • Introduction to Unix
    Introduction to Unix Class 1 * Notes adapted by Alexey Onufriev from previous work by other members of the CS faculty at Virginia Tech What is Unix? A modern computer operating system Operating System “a program that acts as an intermediary between a user of the computer and the computer hardware” Software that manages your computer’s resources (files, programs, disks, network) Examples: Windows, MacOSX, Solaris, BSD, Linux (e.g. Mandrake, Red Hat, Slackware, SUSE) Modern Stable, flexible, configurable, allows multiple users and programs (C) Alexey Onufriev and Virginia Tech CS and Physics Dept. 2 Why Learn Unix? Will make you a better computer scientist UNIX is a building block for many CS concepts Open source and stable (no viruses, worms, etc) Used in many scientific and industrial settings. Huge number of free and well-written software programs Excellent programming environment. Different paradigm. Roughly 65% of the world’s web servers are Linux/Unix machines running Apache. Prerequisite to many other CS courses to follow (Operating Systems, Numerical methods, etc. ) (C) Alexey Onufriev and Virginia Tech CS and Physics Dept. 3 Example: Unix Open Office (C) Alexey Onufriev and Virginia Tech CS and Physics Dept. 4 Brief History of Unix Ken Thompson and Dennis Ritchie originally developed the earliest versions of Unix at Bell Labs for internal use in the 1970s Simple and elegant Meant for programmers and experts Written in a high-level language instead of assembly language Small portion written in assembly language (kernel) Remaining code written in C on top of the kernel http://www.bell-labs.com/history/unix/ (C) Alexey Onufriev and Virginia Tech CS and Physics Dept.
    [Show full text]
  • Binary Compatibility on Netbsd
    Binary compatibility on NetBSD Emmanuel Dreyfus, july 2014 About me ● Emmanuel Dreyfus <[email protected]> ● IT manager at ESPCI ParisTech as daylight job ● NetBSD contributor since 2001 ● Milter-greylist since 2006 ● OpenLDAP, glusterFS, mod_auth_mellon... ● Le cahier de l'admin BSD, Eyrolles editions Binary compatibility ● Same CPU, different OS ● No emulation ● Kernel masquarade as target kernel ● Useful to run proprietary apps ● Almost native performances What do we need? ● Identifying foreign binaries ● System calls translation ● Signals translation ● Nothing more... ● … except if non Unix-like target Identifying aliens ● This happens inside execve(2) ● OS-specific dynamic linker? ● .interp ELF section (see next slide) ● objdump -s -j .interp /bin/ls ● NetBSD: /libexec/ld.elf_so ● Linux: /lib/ld-linux.so.2 ● Only for dynamic binaries Playing with objdump(1) $ objdump -h /bin/ls (...) Idx Name Size VMA LMA File off Algn 0 .interp 00000013 0000004001c8 0000004001c8 000001c8 2**0 CONTENTS, ALLOC, LOAD, READONLY, DATA 1 .note.netbsd.ident 018 0000004001dc 0000004001dc 000001dc 2**2 CONTENTS, ALLOC, LOAD, READONLY, DATA 2 .note.netbsd.pax 00014 0000004001f4 0000004001f4 000001f4 2**2 CONTENTS, ALLOC, LOAD, READONLY, DATA 3 .hash 0000019c 000000400208 000000400208 00000208 2**3 CONTENTS, ALLOC, LOAD, READONLY, DATA 4 .dynsym 00000600 0000004003a8 0000004003a8 000003a8 2**3 CONTENTS, ALLOC, LOAD, READONLY, DATA (…) $ objdump -s -j .interp /bin/ls (...) Contents of section .interp: 4001c8 2f6c6962 65786563 2f6c642e 656c665f /libexec/ld.elf_
    [Show full text]