DOCSLIB.ORG

PDF Copy of the CWM Installation Guide for Solaris 7, Release 11

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text

Load more

Cisco WAN Manager Installation Guide for Solaris 7 Release 11 July 2003 Corporate Headquarters Cisco Systems, Inc. 170 West Tasman Drive San Jose, CA 95134-1706 USA http://www.cisco.com Tel: 408 526-4000 800 553-NETS (6387) Fax: 408 526-4100 Customer Order Number: DOC-7813567= Text Part Number: 78-13567-01 THE SPECIFICATIONS AND INFORMATION REGARDING THE PRODUCTS IN THIS MANUAL ARE SUBJECT TO CHANGE WITHOUT NOTICE. ALL STATEMENTS, INFORMATION, AND RECOMMENDATIONS IN THIS MANUAL ARE BELIEVED TO BE ACCURATE BUT ARE PRESENTED WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED. USERS MUST TAKE FULL RESPONSIBILITY FOR THEIR APPLICATION OF ANY PRODUCTS. THE SOFTWARE LICENSE AND LIMITED WARRANTY FOR THE ACCOMPANYING PRODUCT ARE SET FORTH IN THE INFORMATION PACKET THAT SHIPPED WITH THE PRODUCT AND ARE INCORPORATED HEREIN BY THIS REFERENCE. IF YOU ARE UNABLE TO LOCATE THE SOFTWARE LICENSE OR LIMITED WARRANTY, CONTACT YOUR CISCO REPRESENTATIVE FOR A COPY. The Cisco implementation of TCP header compression is an adaptation of a program developed by the University of California, Berkeley (UCB) as part of UCB’s public domain version of the UNIX operating system. All rights reserved. Copyright © 1981, Regents of the University of California. NOTWITHSTANDING ANY OTHER WARRANTY HEREIN, ALL DOCUMENT FILES AND SOFTWARE OF THESE SUPPLIERS ARE PROVIDED “AS IS” WITH ALL FAULTS. CISCO AND THE ABOVE-NAMED SUPPLIERS DISCLAIM ALL WARRANTIES, EXPRESSED OR IMPLIED, INCLUDING, WITHOUT LIMITATION, THOSE OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT OR ARISING FROM A COURSE OF DEALING, USAGE, OR TRADE PRACTICE. IN NO EVENT SHALL CISCO OR ITS SUPPLIERS BE LIABLE FOR ANY INDIRECT, SPECIAL, CONSEQUENTIAL, OR INCIDENTAL DAMAGES, INCLUDING, WITHOUT LIMITATION, LOST PROFITS OR LOSS OR DAMAGE TO DATA ARISING OUT OF THE USE OR INABILITY TO USE THIS MANUAL, EVEN IF CISCO OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. CCIP, CCSP, the Cisco Arrow logo, the Cisco Powered Network mark, Cisco Unity, Follow Me Browsing, FormShare, and StackWise are trademarks of Cisco Systems, Inc.; Changing the Way We Work, Live, Play, and Learn, and iQuick Study are service marks of Cisco Systems, Inc.; and Aironet, ASIST, BPX, Catalyst, CCDA, CCDP, CCIE, CCNA, CCNP, Cisco, the Cisco Certified Internetwork Expert logo, Cisco IOS, the Cisco IOS logo, Cisco Press, Cisco Systems, Cisco Systems Capital, the Cisco Systems logo, Empowering the Internet Generation, Enterprise/Solver, EtherChannel, EtherSwitch, Fast Step, GigaStack, Internet Quotient, IOS, IP/TV, iQ Expertise, the iQ logo, iQ Net Readiness Scorecard, LightStream, MGX, MICA, the Networkers logo, Networking Academy, Network Registrar, Packet, PIX, Post-Routing, Pre-Routing, RateMUX, Registrar, ScriptShare, SlideCast, SMARTnet, StrataView Plus, Stratm, SwitchProbe, TeleRouter, The Fastest Way to Increase Your Internet Quotient, TransPath, and VCO are registered trademarks of Cisco Systems, Inc. and/or its affiliates in the U.S. and certain other countries. All other trademarks mentioned in this document or Web site are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (0304R) Cisco WAN Manager Installation Guide for Solaris 7, Release 11. Copyright © 2003 Cisco Systems, Inc. All rights reserved. CONTENTS About This Guide ix Objectives ix Audience ix Document Organization ix Related Documentation x Cisco WAN Manager Release 11 x Cisco MGX 8850 (PXM45) Multiservice Switch Release 3 xi Cisco MGX 8850 (PXM1E) Multiservice Switch Release 3 xii Cisco MGX 8950 Multiservice Switch Release 3 xiv SES PNNI Controller Release 3 xv Cisco MGX 8830 Multiservice Switch Release 3 xv Cisco WAN Switching Software Release 9.3 xvi Cisco MGX 8850 (PXM1) Edge Concentrator Switch Release 1 xvii Cisco MGX 8250 Edge Concentrator Switch Release 1 xviii Cisco MGX 8230 Edge Concentrator Switch Release 1 xix Document Conventions xx Obtaining Documentation xxi World Wide Web xxi Documentation CD-ROM xxi Ordering Documentation xxii Documentation Feedback xxii Obtaining Technical Assistance xxii Cisco.com xxii Technical Assistance Center xxiii CHAPTER 1 Introduction 1-1 CWM Configurations 1-2 Upgrade Limitations 1-3 CiscoView Guidelines 1-3 Installation or Upgrade Sequences 1-4 CHAPTER 2 Preparing for CWM Installation 2-1 CWM Server Prerequisite Checklist 2-1 CWM Server Workstation Requirements 2-2 Cisco WAN Manager Installation Guide for Solaris 7 Release 11, Part Number 78-13567-01 Rev. G0, October 2003 iii Contents Hardware Requirements 2-3 Software Requirements 2-3 CWM Standalone Statistics Collector 2-4 Hardware Requirements 2-4 Software Requirements 2-5 CWM Client System Requirements 2-5 Hardware Requirements 2-5 Software Requirements 2-5 Solaris Operating System 2.7 Installation 2-6 Preparing the Disk 2-6 Solaris 2.7 Initial Configuration 2-7 Disk Partitioning Requirements 2-9 Partitioning Two 9-GB Disks 2-9 Partitioning an 18-GB Disk 2-10 Installing Solaris on the Newly-Partitioned Disk 2-11 Installing Solaris 2.7 Patches 2-12 First Time Login to Solaris 2-12 CiscoView 5.4 Considerations 2-13 Installation of Netscape Communicator 2-13 HP OpenView 6.2 Installation 2-15 Obtaining HP OpenView Software 2-15 Installing HP OpenView Software 2-15 Setting Up CWM to HP OpenView Communication 2-15 Check the /etc/services File 2-16 Starting HP OpenView 2-16 Wingz Version 2.5.1 Installation 2-16 CHAPTER 3 Installing CWM Server Software 3-1 Installing CWM Software 3-1 Post Installation Tasks 3-14 First Time Login as User svplus 3-14 Checking the CWM Server File System 3-15 CHAPTER 4 Upgrading CWM Software 4-1 Upgrading to the Latest Release of CWM 11 Software from an Earlier 10 Release 4-1 Upgrading to the CWM 11 Software from Release 10.4 or 10.5.10 with Multiple CWM Gateways 4-14 Initial Conditions before Upgrade 4-14 Upgrade Procedure 4-15 Cisco WAN Manager Installation Guide for Solaris 7 iv Release 11, Part Number 78-13567-01 Rev. G0, October 2003 Contents Post Installation Tasks 4-17 First Time Login as User svplus 4-17 Checking the CWM Server File System 4-18 CHAPTER 5 CiscoView, Netscape, and the Java Plug-in 5-1 Installing the Java Plug-in 1.3.1 on Solaris 5-1 Uninstall of the Java Plug-in 5-2 Standalone Installation of CiscoView 5-2 Uninstall CiscoView 5-4 Uninstallation of Netscape Communicator 5-4 CHAPTER 6 Installing CWM SNMP Service Agent Software 6-1 Installing SNMP Service Agent Software 6-1 Configuration 6-7 Agent Configuration 6-7 Service Agent Configuration 6-7 CHAPTER 7 Installing CWM Client 7-1 Overview of CWM Client 7-1 Setting Up a Windows Based CWM Client 7-2 Hardware 7-2 Software 7-2 Web Browser 7-3 Installing Java Tools 7-4 Setting Up a Solaris Based CWM Client 7-7 Hardware 7-7 Software 7-7 Web Browser 7-8 Installing Java Tools 7-9 Installing Java Web Start 7-12 Launching CWM Client 7-13 Web Browser Method 7-13 Java Web Start Application Manager Method 7-14 Desktop Shortcut Method 7-15 CHAPTER 8 Installing Standalone Statistics Collection Manager Software 8-1 Installing CWM Statistics Collection Manager Standalone 8-2 First Time Login as User svplus 8-10 Cisco WAN Manager Installation Guide for Solaris 7 Release 11, Part Number 78-13567-01 Rev. G0, October 2003 v Contents CHAPTER 9 Upgrading Standalone Statistics Collection Manager Software 9-1 Upgrading CWM Statistics Collection Manager Standalone Software 9-2 Upgrading to the SCMSA 11 Software from Release 10.x with Multiple CWM Gateways 9-10 Initial Conditions before Upgrade 9-10 Upgrade Procedure 9-11 First Time Login as User svplus 9-12 CHAPTER 10 Configuration 10-1 Configuring Topology Discovery 10-1 Configuring AutoRoute Topology 10-1 Configuring PNNI Topology 10-2 Configuring Hybrid Topology 10-3 Configuring Standalone Nodes 10-3 Checking the CWM Workstation File System 10-4 Modifying the SNMP Community String 10-11 Modifying the svplus.conf File 10-11 Modifying the process.conf File 10-12 Setting Up the IP Address on an Cisco MGX 8850, Release 2 Switch 10-12 Setting Up ATM WAN Connections 10-13 Configuring the Switch 10-14 Configuring the Router 10-16 cnflan 10-18 cnfnwip 10-20 cnfstatmast 10-21 Configuring PNNI using CiscoView 10-22 Getting Started 10-22 PNNI Configuration 10-22 PNNI Configuration Categories 10-24 CHAPTER 11 Migration From Automatic Routing Management to PNNI Using Cisco WAN Manager 11-1 Migration Process Overview 11-1 Upgrade Cisco WAN Manager from 10.x to 11. 11-1 Preparing To Upgrade Cisco BPX Switch Software From 9.2.34 to 9.3.30 11-1 Gracefully Upgrading the BCC Card Pair on the BPX node 11-3 Gracefully Upgrading the Rest of the Cards on the BPX Node 11-3 Upgrading Existing Switch Software to 9.3.30 11-4 Upgrading the MGX 8850 from Release 2 to Release 2.1 Software 11-5 XPVC Creation Overview 11-6 Cisco WAN Manager Installation Guide for Solaris 7 vi Release 11, Part Number 78-13567-01 Rev. G0, October 2003 Contents XPVC as a Migration Connection 11-10 XPVC/XPVP Provisioning and Management 11-11 Connection Creation for XPVC/XPVPs 11-12 Creating an XPVC 11-12 XPVC Preferred Table Configurator 11-12 CWM-XPVC-CLI 11-13 Adding an XPVC 11-13 Deleting an XPVC 11-16 XPVC Provisioning via Service Agent 11-18 Location of ConnProxy Scripts 11-18 Displaying XPVC Status 11-25 Displaying Information on a Specified XPVC Segment 11-27 XPVC End-to-end Test Delay 11-29 APPENDIX A Statistics Collection Manager Configuration A-1 Description of Modules A-1 SCM Control Server A-2 SCM Collection Server A-2 SCM Parser Server A-2 SCM Installation Options A-2 ScmProxy A-4 Setting Up the SCM Configurations A-5 SCM Redundancy A-6 APPENDIX B IP Reachability B-1 Overview B-1 General Guidelines B-2 AutoRoute Networks B-2 PNNI Networks B-4 I NDEX Cisco WAN Manager Installation Guide for Solaris 7 Release 11, Part Number 78-13567-01 Rev.
Recommended publications
  • Release Notes for X11R6.8.2 the X.Orgfoundation the Xfree86 Project, Inc

    Release Notes for X11R6.8.2 the X.Orgfoundation the Xfree86 Project, Inc

    Release Notes for X11R6.8.2 The X.OrgFoundation The XFree86 Project, Inc. 9February 2005 Abstract These release notes contains information about features and their status in the X.Org Foundation X11R6.8.2 release. It is based on the XFree86 4.4RC2 RELNOTES docu- ment published by The XFree86™ Project, Inc. Thereare significant updates and dif- ferences in the X.Orgrelease as noted below. 1. Introduction to the X11R6.8.2 Release The release numbering is based on the original MIT X numbering system. X11refers to the ver- sion of the network protocol that the X Window system is based on: Version 11was first released in 1988 and has been stable for 15 years, with only upwardcompatible additions to the coreX protocol, a recordofstability envied in computing. Formal releases of X started with X version 9 from MIT;the first commercial X products werebased on X version 10. The MIT X Consortium and its successors, the X Consortium, the Open Group X Project Team, and the X.OrgGroup released versions X11R3 through X11R6.6, beforethe founding of the X.OrgFoundation. Therewill be futuremaintenance releases in the X11R6.8.x series. However,efforts arewell underway to split the X distribution into its modular components to allow for easier maintenance and independent updates. We expect a transitional period while both X11R6.8 releases arebeing fielded and the modular release completed and deployed while both will be available as different consumers of X technology have different constraints on deployment. Wehave not yet decided how the modular X releases will be numbered. We encourage you to submit bug fixes and enhancements to bugzilla.freedesktop.orgusing the xorgproduct, and discussions on this server take place on <[email protected]>.
  • An Introduction to the X Window System Introduction to X's Anatomy

    An Introduction to the X Window System Introduction to X's Anatomy

    An Introduction to the X Window System Robert Lupton This is a limited and partisan introduction to ‘The X Window System’, which is widely but improperly known as X-windows, specifically to version 11 (‘X11’). The intention of the X-project has been to provide ‘tools not rules’, which allows their basic system to appear in a very large number of confusing guises. This document assumes that you are using the configuration that I set up at Peyton Hall † There are helpful manual entries under X and Xserver, as well as for individual utilities such as xterm. You may need to add /usr/princeton/X11/man to your MANPATH to read the X manpages. This is the first draft of this document, so I’d be very grateful for any comments or criticisms. Introduction to X’s Anatomy X consists of three parts: The server The part that knows about the hardware and how to draw lines and write characters. The Clients Such things as terminal emulators, dvi previewers, and clocks and The Window Manager A programme which handles negotiations between the different clients as they fight for screen space, colours, and sunlight. Another fundamental X-concept is that of resources, which is how X describes any- thing that a client might want to specify; common examples would be fonts, colours (both foreground and background), and position on the screen. Keys X can, and usually does, use a number of special keys. You are familiar with the way that <shift>a and <ctrl>a are different from a; in X this sensitivity extends to things like mouse buttons that you might not normally think of as case-sensitive.
  • Oracle® Secure Global Desktop Platform Support and Release Notes for Release 4.7

    Oracle® Secure Global Desktop Platform Support and Release Notes for Release 4.7

    Oracle® Secure Global Desktop Platform Support and Release Notes for Release 4.7 E26357-02 November 2012 Oracle® Secure Global Desktop: Platform Support and Release Notes for Release 4.7 Copyright © 2012, Oracle and/or its affiliates. All rights reserved. Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners. Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Opteron, the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered trademark of The Open Group. This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited. The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing. If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, the following notice is applicable: U.S. GOVERNMENT END USERS: Oracle programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, delivered to U.S.
  • Qtile Documentation Release 0.15.1

    Qtile Documentation Release 0.15.1

    Qtile Documentation Release 0.15.1 Aldo Cortesi Apr 14, 2020 Contents 1 Getting started 1 1.1 Installing Qtile..............................................1 1.2 Configuration...............................................5 2 Commands and scripting 25 2.1 Commands API............................................. 25 2.2 Scripting................................................. 28 2.3 qshell................................................... 28 2.4 iqshell.................................................. 30 2.5 qtile-top.................................................. 31 2.6 qtile-run................................................. 31 2.7 qtile-cmd................................................. 31 2.8 dqtile-cmd................................................ 34 3 Getting involved 37 3.1 Contributing............................................... 37 3.2 Hacking on Qtile............................................. 38 4 Miscellaneous 43 4.1 Reference................................................. 43 4.2 Frequently Asked Questions....................................... 107 4.3 License.................................................. 108 Index 109 i ii CHAPTER 1 Getting started 1.1 Installing Qtile 1.1.1 Distro Guides Below are the preferred installation methods for specific distros. If you are running something else, please see In- stalling From Source. Installing on Arch Linux Stable versions of Qtile are currently packaged for Arch Linux. To install this package, run: pacman -S qtile Please see the ArchWiki for more information on
  • The Basis System Release 12.1

    The Basis System Release 12.1

    The Basis System Release 12.1 The Basis Development Team November 13, 2007 Lawrence Livermore National Laboratory Email: [email protected] COPYRIGHT NOTICE All files in the Basis system are Copyright 1994-2001, by the Regents of the University of California. All rights reserved. This work was produced at the University of California, Lawrence Livermore National Laboratory (UC LLNL) under contract no. W-7405-ENG-48 (Contract 48) between the U.S. Department of Energy (DOE) and The Regents of the University of California (University) for the operation of UC LLNL. Copyright is reserved to the University for purposes of controlled dissemination, commercialization through formal licensing, or other disposition under terms of Contract 48; DOE policies, regulations and orders; and U.S. statutes. The rights of the Federal Government are reserved under Contract 48 subject to the restrictions agreed upon by the DOE and University as allowed under DOE Acquisition Letter 88-1. DISCLAIMER This software was prepared as an account of work sponsored by an agency of the United States Government. Neither the United States Government nor the University of California nor any of their employees, makes any warranty, express or implied, or assumes any liability or responsibility for the accuracy, completeness, or usefulness of any information, apparatus, product, or process disclosed, or represents that its specific commercial products, process, or service by trade name, trademark, manufacturer, or otherwise, does not necessarily constitute or imply its endorsement, recommendation, or favoring by the United States Government or the University of California. The views and opinions of the authors expressed herein do not necessarily state or reflect those of the United States Government or the University of California, and shall not be used for advertising or product endorsement purposes.
  • MIT 150 | Project Athena - X Window System Users and Developers Conference, Day 1 [3/4] 1/14/1987

    MIT 150 | Project Athena - X Window System Users and Developers Conference, Day 1 [3/4] 1/14/1987

    MIT 150 | Project Athena - X Window System Users and Developers Conference, Day 1 [3/4] 1/14/1987 [MUSIC PLAYING] PALAY: My name is Andrew Palay I work at the Information Technology Center at Carnegie Mellon University. For those who don't know, the Information Technology Center is a joint project between Carnegie Mellon University and IBM. It also has some funding from the National Science Foundation. This talk is going to cover the Andrew toolkit. I'd like to begin this talk by providing a short example of what the toolkit's all about. In particular, how I made this slide. And actually some of the other slides. So I basically had the editor. In this case, I had typed in the text. And I selected a spot of the text and essentially asked to add a raster. This particular place, I added a raster. This object that we add into these will be referred to, and are referred to by the toolkit, as insets. The inset comes up as its default size, given that I've added nothing to it. I then request to read a known raster from the file, And this point, in this case the ITC logo. If you note, the actual inset itself hasn't increased in size to accommodate the raster image. The user has control over that size, can actually make it larger or smaller. Later in the talk, another slide you will see actually has a drawing. In this case, I selected areas that I wanted the drawing, actually created the drawing in place.
  • Proceedings of the FREENIX Track: 2002 USENIX Annual Technical Conference

    Proceedings of the FREENIX Track: 2002 USENIX Annual Technical Conference

    USENIX Association Proceedings of the FREENIX Track: 2002 USENIX Annual Technical Conference Monterey, California, USA June 10-15, 2002 THE ADVANCED COMPUTING SYSTEMS ASSOCIATION © 2002 by The USENIX Association All Rights Reserved For more information about the USENIX Association: Phone: 1 510 528 8649 FAX: 1 510 548 5738 Email: [email protected] WWW: http://www.usenix.org Rights to individual papers remain with the author or the author's employer. Permission is granted for noncommercial reproduction of the work for educational or research purposes. This copyright notice must be included in the reproduced paper. USENIX acknowledges all trademarks herein. XCL : An Xlib Compatibility Layer For XCB Jamey Sharp Bart Massey Computer Science Department Portland State University Portland, Oregon USA 97207–0751 fjamey,[email protected] Abstract 1 The X Window System The X Window System [SG86] is the de facto standard technology for UNIX applications wishing to provide a graphical user interface. The power and success of the X model is due in no small measure to its separation of The X Window System has provided the standard graph- hardware control from application logic with a stable, ical user interface for UNIX systems for more than 15 published client-server network protocol. In this model, years. One result is a large installed base of X applica- the hardware controller is considered the server, and in- tions written in C and C++. In almost all cases, these dividual applications and other components of a com- programs rely on the Xlib library to manage their inter- plete desktop environment are clients.
  • How To: X11 Forwarding

    How To: X11 Forwarding

    written by Nate Book, `14 on 12/08/2011 updated 12/09/2011 How To: X11 Forwarding or, how to get Matlab through SSH Introduction SSH allows you to remotely access the cycle computers to test code for C (gcc, make), Prolog (pl), and Scheme (racket). All of these are accessible via the command-line. If you’re on Windows, you are familiar with something simple like PuTTY. On Linux or Mac, a command like ssh name@host brings it up for you. It’s command-line only and you’re stuck wondering, is there something better? Is there some way to access the familiar Dr. Racket interface as opposed to just racket? Is there a way to get the graphical Matlab environment (typing matlab just gives an error about a missing display— this is correct since it doesn’t know about your display. You might as well ssh from a non-graphical OS for all it cares)? Yes! The trick is X11 Forwarding. Linux and X11 X11 is the 11th version of the X Windows Server (not related to Windows in any way), a protocol allowing window managers to display GUIs on many Linux distributions such as Fedora or Ubuntu. X11 is a server in that applications “connect” to it and send it abstracted GUI information. It also allows remote computers to do the same through, for example, SSH. To actually do this on any OS you need two things, OpenSSH and X.Org. The following sections detail this for common operating systems. Linux/Unix-based This is astoundingly easy to do on any distribution that comes with X Windows.
  • Aligning Intent and Behavior in Software Systems: How Programs Communicate & Their Distribution and Organization

    Aligning Intent and Behavior in Software Systems: How Programs Communicate & Their Distribution and Organization

    © 2020 William B. Dietz ALIGNING INTENT AND BEHAVIOR IN SOFTWARE SYSTEMS: HOW PROGRAMS COMMUNICATE & THEIR DISTRIBUTION AND ORGANIZATION BY WILLIAM B. DIETZ DISSERTATION Submitted in partial fulfillment of the requirements for the degree of Doctor of Philosophy in Computer Science in the Graduate College of the University of Illinois at Urbana-Champaign, 2020 Urbana, Illinois Doctoral Committee: Professor Vikram Adve, Chair Professor John Regehr, University of Utah Professor Tao Xie Assistant Professor Sasa Misailovic ABSTRACT Managing the overwhelming complexity of software is a fundamental challenge because complex- ity is the root cause of problems regarding software performance, size, and security. Complexity is what makes software hard to understand, and our ability to understand software in whole or in part is essential to being able to address these problems effectively. Attacking this overwhelming complexity is the fundamental challenge I seek to address by simplifying how we write, organize and think about programs. Within this dissertation I present a system of tools and a set of solutions for improving the nature of software by focusing on programmer’s desired outcome, i.e. their intent. At the program level, the conventional focus, it is impossible to identify complexity that, at the system level, is unnecessary. This “accidental complexity” includes everything from unused features to independent implementations of common algorithmic tasks. Software techniques driving innovation simultaneously increase the distance between what is intended by humans – developers, designers, and especially the users – and what the executing code does in practice. By preserving the declarative intent of the programmer, which is lost in the traditional process of compiling and linking and building software, it is easier to abstract away unnecessary details.
  • Computational Weld Mechanics (CWM) Framework for Exploring Parametric Design Space to Manage Weld Optimization

    Computational Weld Mechanics (CWM) Framework for Exploring Parametric Design Space to Manage Weld Optimization

    Computational Weld Mechanics (CWM) Framework for Exploring Parametric Design Space to Manage Weld Optimization by Mahyar Asadi A Dissertation submitted to the Faculty of Graduate Studies and Research in partial fulfilment of the requirements for the degree of Doctor of Philosophy Ottawa-Carleton Institute for Mechanical and Aerospace Engineering Department of Mechanical and Aerospace Engineering Carleton University Ottawa, Ontario, Canada April 2011 Library and Archives Bibliotheque et 1*1 Canada Archives Canada Published Heritage Direction du Branch Patrimoine de I'edition 395 Wellington Street 395, rue Wellington OttawaONK1A0N4 OttawaONK1A0N4 Canada Canada Your file Votre reference ISBN: 978-0-494-81543-4 Our file Notre reference ISBN: 978-0-494-81543-4 NOTICE: AVIS: The author has granted a non­ L'auteur a accorde une licence non exclusive exclusive license allowing Library and permettant a la Bibliotheque et Archives Archives Canada to reproduce, Canada de reproduire, publier, archiver, publish, archive, preserve, conserve, sauvegarder, conserver, transmettre au public communicate to the public by par telecommunication ou par I'lnternet, preter, telecommunication or on the Internet, distribuer et vendre des theses partout dans le loan, distribute and sell theses monde, a des fins commerciales ou autres, sur worldwide, for commercial or non­ support microforme, papier, electronique et/ou commercial purposes, in microform, autres formats. paper, electronic and/or any other formats. The author retains copyright L'auteur conserve la propriete du droit d'auteur ownership and moral rights in this et des droits moraux qui protege cette these. Ni thesis. Neither the thesis nor la these ni des extraits substantiels de celle-ci substantial extracts from it may be ne doivent etre imprimes ou autrement printed or otherwise reproduced reproduits sans son autorisation.
  • Free, Functional, and Secure

    Free, Functional, and Secure

    Free, Functional, and Secure Dante Catalfamo What is OpenBSD? Not Linux? ● Unix-like ● Similar layout ● Similar tools ● POSIX ● NOT the same History ● Originated at AT&T, who were unable to compete in the industry (1970s) ● Given to Universities for educational purposes ● Universities improved the code under the BSD license The License The license: ● Retain the copyright notice ● No warranty ● Don’t use the author's name to promote the product History Cont’d ● After 15 years, the partnership ended ● Almost the entire OS had been rewritten ● The university released the (now mostly BSD licensed) code for free History Cont’d ● AT&T launching Unix System Labories (USL) ● Sued UC Berkeley ● Berkeley fought back, claiming the code didn’t belong to AT&T ● 2 year lawsuit ● AT&T lost, and was found guilty of violating the BSD license History Cont’d ● BSD4.4-Lite released ● The only operating system ever released incomplete ● This became the base of FreeBSD and NetBSD, and eventually OpenBSD and MacOS History Cont’d ● Theo DeRaadt ○ Originally a NetBSD developer ○ Forked NetBSD into OpenBSD after disagreement the direction of the project *fork* Innovations W^X ● Pioneered by the OpenBSD project in 3.3 in 2002, strictly enforced in 6.0 ● Memory can either be write or execute, but but both (XOR) ● Similar to PaX Linux kernel extension (developed later) AnonCVS ● First project with a public source tree featuring version control (1995) ● Now an extremely popular model of software development anonymous anonymous anonymous anonymous anonymous IPSec ● First free operating system to implement an IPSec VPN stack Privilege Separation ● First implemented in 3.2 ● Split a program into processes performing different sub-functions ● Now used in almost all privileged programs in OpenBSD like httpd, bgpd, dhcpd, syslog, sndio, etc.
  • The Linux Gamers' HOWTO

    The Linux Gamers' HOWTO

    The Linux Gamers’ HOWTO Peter Jay Salzman Frédéric Delanoy Copyright © 2001, 2002 Peter Jay Salzman Copyright © 2003, 2004 Peter Jay SalzmanFrédéric Delanoy 2004-11-13 v.1.0.6 Abstract The same questions get asked repeatedly on Linux related mailing lists and news groups. Many of them arise because people don’t know as much as they should about how things "work" on Linux, at least, as far as games go. Gaming can be a tough pursuit; it requires knowledge from an incredibly vast range of topics from compilers to libraries to system administration to networking to XFree86 administration ... you get the picture. Every aspect of your computer plays a role in gaming. It’s a demanding topic, but this fact is shadowed by the primary goal of gaming: to have fun and blow off some steam. This document is a stepping stone to get the most common problems resolved and to give people the knowledge to begin thinking intelligently about what is going on with their games. Just as with anything else on Linux, you need to know a little more about what’s going on behind the scenes with your system to be able to keep your games healthy or to diagnose and fix them when they’re not. 1. Administra If you have ideas, corrections or questions relating to this HOWTO, please email me. By receiving feedback on this howto (even if I don’t have the time to answer), you make me feel like I’m doing something useful. In turn, it motivates me to write more and add to this document.