DOCSLIB.ORG

IRIX® 6.5.16 Update Guide

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text

Load more

IRIX® 6.5.16 Update Guide 1600 Amphitheatre Pkwy. Mountain View, CA 94043-1351 Telephone (650) 960-1980 FAX (650) 961-0595 May 2002 Dear Valued Customer, SGI® is pleased to present the new IRIX® 6.5.16 maintenance and feature release. Starting with IRIX® 6.5, SGI created a new software upgrade strategy, which delivers both the maintenance (6.5.16m) and feature (6.5.16f) streams. This upgrade is part of a family of releases that periodically enhances IRIX 6.5. There are several benefits to this release strategy: it provides periodic fixes to IRIX, it assists in managing upgrades, and it supports all platforms. Additional information on this strategy and how it affects you is included in the updated Installation Instructions manual contained in this package. If you need assistance, please visit the Supportfolio™ Online Web site at http://support.sgi.com or contact your local support provider. In conjunction with the release of IRIX® 6.5.15, SGI added to the existing life cycle management categories the Limited Support Mode that customizes services we deliver to our users. This new support mode is targeted for open source products. We now offer eight (8) modes of 2 service for software supported by SGI : Active, Maintenance, Limited, Legacy, Courtesy, Divested, Retired, and Expired. Active Mode is our highest level of service. It applies to products that are being actively developed and maintained and are orderable through general distribution. Software fixes for all levels of problems can be expected. Maintenance Mode software is maintained and is still an important part of our product mix. No new functionality is added to products in this support mode. Functional fixes for severe problems are generally available. Products in this support mode category are still orderable through general distribution. Software usually stays in this category about 18 months before being moved to a mode of lesser support. Limited Mode is a restricted level of service developed mainly for products developed and maintained by open source organizations and that are distributed by SGI. Legacy Mode software generally runs on out-of-production operating system versions or system platforms that are no longer in active development or maintained. These products are usually distributed with limited availability. New support contracts may be offered and renewed. Services provided with Legacy Mode are limited to providing existing fixes and “workarounds” for reported problems. IRIX® 6.2, IRIX® 6.3, and IRIX® 6.4 operating system revisions are examples of major operating system releases that are supported in this category. 3 Courtesy Mode software is not officially part of the software support offerings. Courtesy mode software is not covered by software support contracts, and call center support is not available. An e-mail alias may be provided to facilitate customer communications and to address any technical questions. Response times will vary according to availability of resources. The e-mail alias may be terminated at any time without advance notice. IRIS Showcase™ and Cosmo Worlds™ are examples of products with Courtesy Mode support. Divested Mode software has been turned over to a third party who assumes all responsibility for support. SGI no longer distributes these products. Calls received at the SGI Call Center for support on divested products will be redirected to the applicable third party. CA Unicenter® TNG and Syntax TAS™ are examples of divested products. Retired Mode provides restricted support for older software products which are no longer generally distributed by SGI. This level of support has severe limitations on portability to new platforms. Availability of support at this level is limited to existing customers with whom we have existing contractual obligations. This is the final stage before a product is completely removed from the SGI product set. Expired Mode software products have reached the end of their useful life. These products are not supported or distributed in any form by SGI. Examples are: IRIX® 5.3, IRIXPro™, and Proconf. 4 The Web page at http://support.sgi.com/irix/news/index.html#swmodes contains a link to a Web page where the eight software support modes are described in more detail. This Web page also contains links to the latest customer letters, which provide a list of the various software products that have changed support modes. We thank you for your continued commitment to SGI. Terry Oberdank Vice President, Global Services SGI 5 Welcome to your SGI IRIX 6.5.16 update. This booklet contains: • A list of key features in IRIX 6.5.16 • A list of CDs contained in the IRIX 6.5.16 update kit • A guide to SGI Web sites 6 IRIX 6.5.16 Key New Features The following changes have been incorporated into the core IRIX 6.5.16 overlay CDs and the Applications CD. New Software Features - Feature Stream Only Filesystems • New option for XVM show command For the IRIX 6.5.16f release, the -extend option has been added to the XVM show command. Specifying this option will display additional information about physvols, slices, stripes and foreign disks than the show command alone. The XVM Volume Manager Administrator’s Guide and the XVM help screens have been updated with examples that use this option. • CXFS new features For IRIX 6.5.16f, CXFS features include the following: – Support for multiple operating system (multiOS) clients, such as Solaris nodes and Windows NT nodes. The CXFS GUI and cmgr(1M) command now allow you to specify the operating system for a given node. 7 – I/O fencing, which allows a problem node to be isolated from the storage area network (SAN) so that it cannot corrupt data in the shared CXFS filesystem; this is required for Solaris nodes and Windows NT nodes. A Brocade switch is required to support I/O fencing. – Support for a two-node CXFS cluster running with FailSafe and an L1 controller on Origin 300 and Origin 3200 systems. See the CXFS Software Installation and Administration Guide for more information. • CXFS upgrade: filesystem definitions The structure of the CXFS filesystem configuration was changed with the release of IRIX 6.5.13f. Backward compatibility with earlier versions is no longer maintained as of IRIX 6.5.14f, since all nodes in the cluster must be running the same or adjacent releases. – If you are upgrading from 6.5.13f to 6.5.14f or later, there is no further impact. – If you are upgrading from 6.5.12f or earlier, you must perform a one-time manual conversion of your CXFS filesystem definitions. See the CXFS Software Installation and Administration Guide for more information. • CXFS upgrade: cluster nodes For CXFS customers, if you install IRIX 6.5.16f including sysadm_base on a cluster node where the 6.5.13f or earlier version 8 of CXFS is installed, you will need to upgrade to the 6.5.16f version CXFS (sysadm_cxfs) and install 6.5.16f sysadm_cluster. System Performance and Tuning • New joblimitsign kernel tunable parameters group The IRIX 6.5.16 release adds the joblimitsign group of kernel tunables that can be used to specify that specific job limit resource accumulation and enforcement should be ignored by the kernel. Setting the kernel tunable value to 1 indicates the specific limit should be ignored. Setting the value to 0 will re-enable the limit for newly created jobs. The following kernel tunable parameters have been added: – jlimit_cpu_ign parameter The jlimit_cpu_ign parameter specifies that the accumulation and enforcement of CPU time limits for jobs should be ignored. – jlimit_data_ign parameter The jlimit_data_ign parameter specifies that the accumulation and enforcement of data memory limits for jobs should be ignored. – jlimit_nofile_ign parameter The jlimit_nofile_ign parameter specifies that the accumulation and enforcement of limits for the number of open files in jobs should be ignored. 9 – jlimit_numproc_ign parameter The jlimit_numproc_ign parameter specifies that the accumulation and enforcement of limits for the number of processes in jobs should be ignored. – jlimit_pmem_ign parameter The jlimit_pmem_ign parameter specifies that the accumulation and enforcement of physical memory limits for jobs should be ignored. – jlimit_pthread_ign parameter The jlimit_pthread_ign parameter specifies that the accumulation and enforcement of limits for the number of pthreads should be ignored. – jlimit_rss_ign parameter The jlimit_rss_ign parameter specifies that the accumulation and enforcement of resident set size (RSS) memory limits for jobs should be ignored. – jlimit_vmem_ign parameter The jlimit_vmem_ign parameter specifies that the accumulation and enforcement of virtual memory limits for jobs should be ignored. For more information on kernel tunable parameters, see the setjusage(2) entry in Appendix A in IRIX Admin: Resource Administration. 10 – New setjusage system call The setjusage system call is used to update resource usage for jobs in the kernel. The system call can only be used to update usage information if the limit accumulation and enforcement for the specified resource is being ignored. This function can be used by sites to implement a site-specific solution for resource accumulation and enforcement. Using this system call allows the various job limit status commands to display usage values as reported from the site-specific implementation. For more information, see the setjusage(2) man page and the setjusage(2) entry in Appendix A in IRIX Admin: Resource Administration. Comprehensive System Accounting (CSA) • Change to csa.conf file The IRIX 6.5.16 release removes the ACCT_FS parameter in the /etc/csa.conf file. The MIN_BLKS parameter now determines the minimum number of free 1K blocks needed on the file system on which the /var/adm/acct directory resides. The default is 2000. To ensure that the MIN_BLKS variable has been set correctly, check the value in the /etc/csa.conf configuration file. For more information, see Chapter 5, “Comprehensive System Accounting”, in IRIX Admin: Resource Administration.
Recommended publications
  • ROADS and BRIDGES: the UNSEEN LABOR BEHIND OUR DIGITAL INFRASTRUCTURE Preface

    ROADS and BRIDGES: the UNSEEN LABOR BEHIND OUR DIGITAL INFRASTRUCTURE Preface

    Roads and Bridges:The Unseen Labor Behind Our Digital Infrastructure WRITTEN BY Nadia Eghbal 2 Open up your phone. Your social media, your news, your medical records, your bank: they are all using free and public code. Contents 3 Table of Contents 4 Preface 58 Challenges Facing Digital Infrastructure 5 Foreword 59 Open source’s complicated relationship with money 8 Executive Summary 66 Why digital infrastructure support 11 Introduction problems are accelerating 77 The hidden costs of ignoring infrastructure 18 History and Background of Digital Infrastructure 89 Sustaining Digital Infrastructure 19 How software gets built 90 Business models for digital infrastructure 23 How not charging for software transformed society 97 Finding a sponsor or donor for an infrastructure project 29 A brief history of free and public software and the people who made it 106 Why is it so hard to fund these projects? 109 Institutional efforts to support digital infrastructure 37 How The Current System Works 38 What is digital infrastructure, and how 124 Opportunities Ahead does it get built? 125 Developing effective support strategies 46 How are digital infrastructure projects managed and supported? 127 Priming the landscape 136 The crossroads we face 53 Why do people keep contributing to these projects, when they’re not getting paid for it? 139 Appendix 140 Glossary 142 Acknowledgements ROADS AND BRIDGES: THE UNSEEN LABOR BEHIND OUR DIGITAL INFRASTRUCTURE Preface Our modern society—everything from hospitals to stock markets to newspapers to social media—runs on software. But take a closer look, and you’ll find that the tools we use to build software are buckling under demand.
  • An Automated Binary Security Update System for Freebsd

    An Automated Binary Security Update System for Freebsd

    An Automated Binary Security Update System for FreeBSD Colin Percival Computing Lab, Oxford University [email protected] Abstract that a large number of people find the task of applying security patches and rebuilding affected programs to be difficult and/or confusing. Given that releases are on av- With the present trend towards increased reliance upon erage several months – and several security holes – old computer systems, the provision and prompt application by the time they are installed, the possibility arises that of security patches is becoming vital. Developers of all a new user will find his system compromised before he operating systems must generally be applauded for their has a chance to bring it up to date. success in this area; systems administrators, however, are often found lacking. Furthermore, there are some circumstances where build- ing from source is undesirable. Some embedded sys- Anecdotal evidence suggests that for FreeBSD much of tems might lack sufficient disk space to store the entire the difficulty arises out of the need to recompile from the source and object trees; some system administrators re- source code after applying security patches. Many peo- move part or all of the build toolchain in an (arguably ple, after spending years using closed-source point-and- misguided) attempt to thwart any attempt to build a click operating systems, find the concept of recompiling rootkit; and the purveyors of application-specific ‘toast- software to be entirely foreign, and even veteran users ers’ might very likely wish to keep the complexity of of open source software are often less than prompt about building from source entirely hidden from their users.
  • IE 5.5 and Netscape 4.75 - Why Upgrade? ..Page 1

    IE 5.5 and Netscape 4.75 - Why Upgrade? ..Page 1

    In This Issue . IE 5.5 and Netscape 4.75 - Why Upgrade? ..page 1 WindowsME for Home Computing ..…..…..page 1 Critical Updates are Essential ……..……….page 1 Win 95/98 Web Browser Upgrade.…………page 2 Permanent LRC Stations…………...……….page 2 cc:Mail is Retiring ……..…………..………..page 2 The newsletter for IPFW computer users Information Technology Services October 2000 Courses & Resources…………….……….….page 2 IE 5.5 and Netscape for Home 4.75 - Why Upgrade? Computing Campus surfers should update their browsers to the Microsoft recently released its upgrade to Windows 98 latest versions of Netscape and Internet Explorer (IE). for home computing — Windows Millennium (WindowsMe). Windows users may do so by the following instructions on Follett's IPFW Bookstore is now offering the CD to students, page 2. Macintosh users may obtain the instructions for faculty, and staff as part of IU's licensing agreement with creating an alias for either or both programs from the Help Microsoft. Is the upgrade for you? Windows Millennium Desk (e-mail: [email protected]). includes: Very basic digital media editing tools Why upgrade? In general, obtaining the latest 4 IE 5.5 (also downloadable for Windows 98) version of your favorite browser helps ensure that you have 4 4 Media Player 7 (also downloadable for Windows 98) the most capable and secure browser for today's Web If you have no compelling need for the above features environment. Specifically, the newest and most significant or if you take the time to do wnload IE 5.5 and/or Media Player 7 features of each include: for Windows 98, you may want to skip this upgrade.
  • Znetlive SSL Compatible Applications, Platforms & Operating

    Znetlive SSL Compatible Applications, Platforms & Operating

    ZNetLive SSL Compatible Applications, Platforms & Operating Systems Certificate Authority Root Apple MAC OS 9.0+ (circa 2002), includes 10.5.X and 10.6.X Future proof at 2048 bit, embedded in all Microsoft Windows XP, Vista, 7 and 8 (all devices and browsers and capable of upgrading versions inc 32/64 bit) weak encryption to a strong one is the most reliable Certificate Authority Root-GlobalSign. It is very important to ensure a flawless interaction of your online solutions with Default API Support within Hosting Control customers making connection with your web Panels server, reading emails, trusting your e- Ubersmith documents or running your code. Every WHMCS standard machine that uses trust of Public Key Infrastructure (PKI), e.g. S/MIME, SSL/TLS, Document Signing and Code Signing, has GlobalSign’s Root Certification present in it. Email Clients (S/MIME) ZNetLive’s SSL Certificates authenticated by GlobalSign have 2048 bit strength throughout Mulberry Mail complete Digital Certificate portfolio and Microsoft Outlook 99+ comply with recommendations of National Microsoft Entourage (OS/X) Institute of Standards and Technology (NIST) Qualcomm Eudora 6.2+ according to which all cryptographic keys Mozilla Thunderbird 1.0+ should be 2048 bit strength from 2011 onwards. Mail.app Anything weaker than 2048 bit encryption is Lotus Notes (6+) considered insecure. Because of this, the Netscape Communicator 4.51+ Certification Authorities and Browsers insists The Bat that all the EV SSL Certificates should be 2048 Apple Mail bit encryption.
  • Netscape 6.2.3 Software for Solaris Operating Environment

    Netscape 6.2.3 Software for Solaris Operating Environment

    What’s New in Netscape 6.2 Netscape 6.2 builds on the successful release of Netscape 6.1 and allows you to do more online with power, efficiency and safety. New is this release are: Support for the latest operating systems ¨ BETTER INTEGRATION WITH WINDOWS XP q Netscape 6.2 is now only one click away within the Windows XP Start menu if you choose Netscape as your default browser and mail applications. Also, you can view the number of incoming email messages you have from your Windows XP login screen. ¨ FULL SUPPORT FOR MACINTOSH OS X Other enhancements Netscape 6.2 offers a more seamless experience between Netscape Mail and other applications on the Windows platform. For example, you can now easily send documents from within Microsoft Word, Excel or Power Point without leaving that application. Simply choose File, “Send To” to invoke the Netscape Mail client to send the document. What follows is a more comprehensive list of the enhancements delivered in Netscape 6.1 CONFIDENTIAL UNTIL AUGUST 8, 2001 Netscape 6.1 Highlights PR Contact: Catherine Corre – (650) 937-4046 CONFIDENTIAL UNTIL AUGUST 8, 2001 Netscape Communications Corporation ("Netscape") and its licensors retain all ownership rights to this document (the "Document"). Use of the Document is governed by applicable copyright law. Netscape may revise this Document from time to time without notice. THIS DOCUMENT IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. IN NO EVENT SHALL NETSCAPE BE LIABLE FOR INDIRECT, SPECIAL, INCIDENTAL, OR CONSEQUENTIAL DAMAGES OF ANY KIND ARISING FROM ANY ERROR IN THIS DOCUMENT, INCLUDING WITHOUT LIMITATION ANY LOSS OR INTERRUPTION OF BUSINESS, PROFITS, USE OR DATA.
  • Twenty Years of Berkeley Unix : from AT&T-Owned to Freely

    Twenty Years of Berkeley Unix : from AT&T-Owned to Freely

    Twenty Years of Berkeley Unix : From AT&T-Owned to Freely Redistributable Marshall Kirk McKusick Early History Ken Thompson and Dennis Ritchie presented the first Unix paper at the Symposium on Operating Systems Principles at Purdue University in November 1973. Professor Bob Fabry, of the University of California at Berkeley, was in attendance and immediately became interested in obtaining a copy of the system to experiment with at Berkeley. At the time, Berkeley had only large mainframe computer systems doing batch processing, so the first order of business was to get a PDP-11/45 suitable for running with the then-current Version 4 of Unix. The Computer Science Department at Berkeley, together with the Mathematics Department and the Statistics Department, were able to jointly purchase a PDP-11/45. In January 1974, a Version 4 tape was delivered and Unix was installed by graduate student Keith Standiford. Although Ken Thompson at Purdue was not involved in the installation at Berkeley as he had been for most systems up to that time, his expertise was soon needed to determine the cause of several strange system crashes. Because Berkeley had only a 300-baud acoustic-coupled modem without auto answer capability, Thompson would call Standiford in the machine room and have him insert the phone into the modem; in this way Thompson was able to remotely debug crash dumps from New Jersey. Many of the crashes were caused by the disk controller's inability to reliably do overlapped seeks, contrary to the documentation. Berkeley's 11/45 was among the first systems that Thompson had encountered that had two disks on the same controller! Thompson's remote debugging was the first example of the cooperation that sprang up between Berkeley and Bell Labs.
  • Spybot - Search & Destroy Can Detect and Remove Spyware of Different Kinds from Your Computer

    Spybot - Search & Destroy Can Detect and Remove Spyware of Different Kinds from Your Computer

    Description Spybot - Search & Destroy can detect and remove spyware of different kinds from your computer. Spyware is a relatively new kind of threat that common anti-virus applications do not cover yet. If you see new toolbars in your Internet Explorer that you didn't intentionally install, if your browser crashes, or if you browser start page has changed without your knowing, you most probably have spyware. But even if you don't see anything, you may be infected, because more and more spyware is emerging that is silently tracking your surfing behaviour to create a marketing profile of you that will be sold to advertisement companies. Spybot-S&D; is free, so there's no harm in trying to see if something snooped into your computer, too :) Spybot-S&D; can also clean usage tracks, an interesting function if you share your computer with other users and don't want them to see what you worked on. And for professional users, it allows to fix some registry inconsistencies and offers some extended reporting features. License Spybot-S&D; comes under the Dedication Public License. Requirements Microsoft Windows 95, 98, ME, NT, 2000 or XP (32 and 64 bit), 2003, Vista. Compatible with bootable PE disks (e.g. BartPE) and Wine. Minimum of 10 MB free hard disk space, more recommended for updates and backups. Usage We recommend that you continue by reading the tutorial next. © 2000-2008 Safer Networking Ltd. All rights reserved. I. Freeware First of all, the reasons why Spybot-S&D; is free: I.a. Dedication Spybot-S&D; is dedicated to the most wonderful girl on earth :) I.b.
  • Web Browser Set-Up Guide for New BARC

    Web Browser Set-Up Guide for New BARC

    Web Browser Set-up Guide for new BARC The new BARC system is web-based and is designed to work best with Netscape 4.79. Use the chart below to determine the appropriate set-up for your web browser to use new BARC. What type of computer do you use? What you will need to do in order to use the new BARC system… I am a Thin Client user. You do not need to do anything. The version of Netscape available to Thin Client users (version 4.75) will work with the new BARC system. I use a PC and the following statement about the Netscape web browser applies to my workstation…. I don’t have Netscape. Proceed to Section 2 of this document for instructions on how you can download and install Netscape 4.79. I only have Netscape 6.x or Netscape 7.x. Proceed to Section 2 of this document for instructions on how you can download and install Netscape 4.79. I currently have Netscape 4.79. You do not need to do anything. The new BARC system was designed to work best with the version of Netscape you have. I currently have Netscape 4.75 or Netscape 4.76. You do not need to do anything. Even though the new BARC system is designed to work best in Netscape 4.79, the application will work fine with Netscape 4.75 and Netscape 4.76. I have a version of Netscape 4, but it is not Proceed to Section 1 of this document Netscape 4.75, Netscape 4.76 or Netscape 4.79 and to uninstall the current version of I have an alternative web browser (such as Microsoft Netscape you have and then continue Internet Explorer, Netscape 6.x or Netscape 7.x) on to Section 2 to download and on my workstation.
  • Why Websites Can Change Without Warning

    Why Websites Can Change Without Warning

    Why Websites Can Change Without Warning WHY WOULD MY WEBSITE LOOK DIFFERENT WITHOUT NOTICE? HISTORY: Your website is a series of files & databases. Websites used to be “static” because ​ there were only a few ways to view them. Now we have a complex system, and telling your webmaster what device, operating system and browser is crucial, here’s why: TERMINOLOGY: You have a desktop or mobile “device”. Desktop computers and mobile ​ ​ ​ devices have “operating systems” which are software. To see your website, you’ll pull up a ​ ​ ​ ​ “browser” which is also software, to surf the Internet. Your website is a series of files that ​ ​ needs to be 100% compatible with all devices, operating systems and browsers. Your website is built on WordPress and gets a weekly check up (sometimes more often) to ​ ​ ​ see if any changes have occured. Your site could also be attacked with bad files, links, spam, comments and other annoying internet pests! Or other components will suddenly need updating which is nothing out of the ordinary. WHAT DOES IT LOOK LIKE IF SOMETHING HAS CHANGED? Any update to the following can make your website look differently: There are 85 operating ​ systems (OS) that can update (without warning). And any of the most popular roughly 7 ​ ​ ​ browsers also update regularly which can affect your site visually and other ways. (Lists below) ​ Now, with an OS or browser update, your site’s 18 website components likely will need ​ ​ updating too. Once website updates are implemented, there are currently about 21 mobile ​ devices, and 141 desktop devices that need to be viewed for compatibility.
  • Open Source Software Licenses: Perspectives of the End User and the Software Developer

    Open Source Software Licenses: Perspectives of the End User and the Software Developer

    White Paper: Open Source Software Licenses: Perspectives of the End User and the Software Developer By: Paul H. Arne Morris, Manning & Martin, L.L.P. Copyright © 2004 Morris, Manning & Martin, L.L.P. All rights reserved Table of Contents History of Open Source .........................................................................................................................2 Open Source Licenses Generally ..........................................................................................................3 Copyright Issues .........................................................................................................................3 Contract Considerations..............................................................................................................4 Limitation of Liability Clause.....................................................................................................5 Other Implied Warranties ...........................................................................................................6 UCITA ........................................................................................................................................6 Parties to License........................................................................................................................6 Specific Open Source Licenses..............................................................................................................7 GNU General Public License (GPL) ..........................................................................................7
  • Open Source Software: a History David Bretthauer University of Connecticut, Dave.Bretthauer@Uconn.Edu

    Open Source Software: a History David Bretthauer University of Connecticut, [email protected]

    University of Connecticut OpenCommons@UConn Published Works UConn Library 12-26-2001 Open Source Software: A History David Bretthauer University of Connecticut, [email protected] Follow this and additional works at: https://opencommons.uconn.edu/libr_pubs Part of the OS and Networks Commons Recommended Citation Bretthauer, David, "Open Source Software: A History" (2001). Published Works. 7. https://opencommons.uconn.edu/libr_pubs/7 Open Source Software: A History —page 1 Open Source Software: A History by David Bretthauer Network Services Librarian, University of Connecticut Open Source Software: A History —page 2 Abstract: In the 30 years from 1970 -2000, open source software began as an assumption without a name or a clear alternative. It has evolved into a s ophisticated movement which has produced some of the most stable and widely used software packages ever produced. This paper traces the evolution of three operating systems: GNU, BSD, and Linux, as well as the communities which have evolved with these syst ems and some of the commonly -used software packages developed using the open source model. It also discusses some of the major figures in open source software, and defines both “free software” and “open source software.” Open Source Software: A History —page 1 Since 1998, the open source softw are movement has become a revolution in software development. However, the “revolution” in this rapidly changing field can actually trace its roots back at least 30 years. Open source software represents a different model of software distribution that wi th which many are familiar. Typically in the PC era, computer software has been sold only as a finished product, otherwise called a “pre - compiled binary” which is installed on a user’s computer by copying files to appropriate directories or folders.
  • Building and Installing Software Packages for Linux Building and Installing Software Packages for Linux

    Building and Installing Software Packages for Linux Building and Installing Software Packages for Linux

    Building and Installing Software Packages for Linux Building and Installing Software Packages for Linux Table of Contents Building and Installing Software Packages for Linux.....................................................................................1 Mendel Cooper −−− http://personal.riverusers.com/~thegrendel/...........................................................1 1.Introduction...........................................................................................................................................1 2.Unpacking the Files..............................................................................................................................1 3.Using Make...........................................................................................................................................1 4.Prepackaged Binaries............................................................................................................................1 5.Termcap and Terminfo Issues...............................................................................................................1 6.Backward Compatibility With a.out Binaries.......................................................................................1 7.Troubleshooting....................................................................................................................................2 8.Final Steps.............................................................................................................................................2