DOCSLIB.ORG

Categorical Variable Consolidation Tables

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Categorical Variable Consolidation Tables CATEGORICAL VARIABLE CONSOLIDATION TABLES FlossMole Data Name Old number of codes New number of codes Table 1: Intended Audience 19 5 Table 2: FOSS Licenses 60 7 Table 3: Operating Systems 59 8 Table 4: Programming languages 73 8 Table 5: SF Project topics 243 19 Table 6: Project user interfaces 48 9 Table 7 DB Environment 33 3 Totals 535 59 Table 1: Intended Audience: Consolidated from 19 to 4 categories Rationale for this consolidation: Categories that had similar characteristics were grouped together. For example, Customer Service, Financial and Insurance, Healthcare Industry, Legal Industry, Manufacturing, Telecommunications Industry, Quality Engineers and Aerospace were grouped together under the new category “Business.” End Users/Desktop and Advanced End Users were grouped together under the new category “End Users.” Developers, Information Technology and System Administrators were grouped together under the new category “Computer Professionals.” Education, Religion, Science/Research and Other Audience were grouped under the new category “Other.” Categories containing large numbers of projects were generally left as individual categories. Perhaps Religion and Education should have be left as separate categories because of they contain a relatively large number of projects. Since Mike recommended we get the number of categories down to 50, I consolidated them into the “Other” category. What was done: I created a new table in sf merged called ‘categ_intend_aud_aug06’. This table is a duplicate of the ‘project_intended_audience01_aug_06’ table with the fields ‘new_code’ and ‘new_description’ added. I updated the new fields in the new table with the new codes and descriptions listed in the table below using a python script I (Bob English) wrote called add_categ_intend_aud.py. I added the fields ‘ia1’, ‘ia2’, ‘ia3’, ‘ia4’ and ‘ia5’ to the ‘statistical_analysis_0607 table (the flat file table). These fields correspond to the new codes (1-5) in the intended audience table below. I updated the ia fields with the new codes from the ‘categ_intend_aud_aug06’ table using five sql queries having the general form: UPDATE statistical_analysis_0607 s INNER JOIN categ_intend_aud_aug06 c ON s.proj_unixname = c.proj_unixname SET s.ia5 = 1 WHERE c.new_code = 5 The ‘ia’ fields are the Boolean data type and have a 1 value if the project lists the corresponding new code and a 0 value if it does not. Some projects list more than one code for intended audience. NOTE: 6,033 projects that exist in the project_intended_audience01_aug_06 table do not exist in the ‘statistical_analysis_0607’ table. Some projects are missing from the ‘statistical_analysis_0607’ table because they were deleted from Sourceforge.net or because we don’t have accurate data for them for various reasons. This defect in the data may impact the statistical analysis and adjustments may need to be made to compensate. New code New description num_projec code Old description ts 2 1 End Users End Users/Desktop 35483 3 2 Computer professionals Developers 41337 359 3 Business Customer Service 1586 360 4 Other Education 6108 3 Business Financial and Insurance 361 954 Industry 362 3 Business Healthcare Industry 733 363 2 Computer professionals Information Technology 7408 364 3 Business Legal Industry 286 365 3 Business Manufacturing 717 366 4 Other Religion 329 367 4 Other Science/Research 6292 3 Business Telecommunications 368 1810 Industry 4 2 Computer professionals System Administrators 15812 5 4 Other Other Audience 6816 536 1 End Users Advanced End Users 5658 537 3 Business Quality Engineers 638 569 5 Government/Non-Profit Government 314 599 3 Business Aerospace 129 5 Government/Non-Profit Non-Profit 618 532 Organizations Table 2: FOSS Licenses used by projects: Consolidated from 60 categories to 7 categories using OSI categories (http://www.opensource.org/licenses/category) . Rationale for this consolidation: The OSI model groups most licenses under the category “Widely used/strong communities.” Using this categorization would essentially test whether projects using widely used licenses have a higher project success rate than projects using specialty or other types of licenses. However, this categorization does not test our essential hypotheses about whether “business friendly” or “reciprocal” licenses produce a higher percentage of successful projects. What was done: Nothing. I’ll pick up book in my mailbox at Holdsworth on licenses and consider dividing by “restrictive,” “non-restrictive.” I’ll also plot licenses against our dependent variable in R and see if that sheds any light. Old New New description Old description num_projects code code 14 3 Other/Miscellaneous OSI-Approved Open Source 430 Widely used/strong 15 1 GNU General Public License (GPL) 54842 communities Widely used/strong 16 1 GNU Library or Lesser General Public License (LGPL) 9429 communities 17 3 Other/Miscellaneous Artistic License 1317 187 1 Widely used/strong BSD License 5968 communities Widely used/strong 188 1 MIT License 1616 communities 189 5 Non-reusable Python Software Foundation License 184 190 3 Other/Miscellaneous Qt Public License (QPL) 235 191 5 Non-reusable IBM Public License 98 Retired MITRE Collaborative Virtual Workspace License 192 7 2 (CVW) 193 5 Non-reusable Ricoh Source Code Public License 8 194 5 Non-reusable Python License (CNRI Python License) 138 195 3 Other/Miscellaneous zlib/libpng License 420 196 3 Other/Miscellaneous Other/Proprietary License 1259 197 3 Other/Miscellaneous Public Domain 2134 296 6 Superceded Apache Software License 1077 297 5 Non-reusable Vovida Software License 1.0 5 298 7 Retired Sun Industry Standards Source License (SISSL) 44 299 7 Retired Intel Open Source License 24 300 7 Retired Jabber Open Source License 45 301 5 Non-reusable Nokia Open Source License 13 302 5 Non-reusable Sleepycat License 23 303 5 Non-reusable Nethack General Public License 31 304 6 Superceded Mozilla Public License 1.0 (MPL) 246 Widely used/strong 305 1 Mozilla Public License 1.1 (MPL 1.1) 1114 communities 306 5 Non-reusable Apple Public Source License 64 Widely used/strong 307 1 Common Public License 763 communities 316 2 Special purpose Open Group Test Suite License 18 317 4 Redundant X.Net License 11 318 5 Non-reusable Sun Public License 97 319 6 Superceded Eiffel Forum License 7 320 5 Non-reusable W3C License 45 321 5 Non-reusable Motosoto License 1 322 5 Non-reusable Zope Public License 42 323 4 Redundant University of Illinois/NCSA Open Source License 44 324 4 Redundant Academic Free License (AFL) 565 325 4 Redundant Attribution Assurance License 29 388 3 Other/Miscellaneous Open Software License 557 389 5 Non-reusable Sybase Open Watcom Public License 1 390 5 Non-reusable OCLC Research Public License 2.0 1 391 5 Non-reusable WxWindows Library Licence 88 392 4 Redundant Eiffel Forum License V2.0 20 393 4 Redundant Historical Permission Notice and Disclaimer 25 395 5 Non-reusable RealNetworks Public Source License V1.0 2 396 5 Non-reusable Reciprocal Public License 34 397 5 Non-reusable Entessa Public License 2 398 6 Superceded Lucent Public License (Plan9) 2 399 5 Non-reusable PHP License 320 400 5 Non-reusable Frameworx Open License 6 Widely used/strong 401 1 Apache License V2.0 1119 communities 402 5 Non-reusable CUA Office Public License Version 1.0 2 403 5 Non-reusable EU DataGrid Software License 4 404 4 Redundant Fair License 31 405 4 Redundant Lucent Public License Version 1.02 4 Widely used/strong 406 1 Eclipse Public License 241 communities 407 2 Special purpose NASA Open Source Agreement 12 628 3 Other/Miscellaneous Adaptive Public License 26 629 2 Special purpose Educational Community License 69 Widely used/strong 630 1 Common Development and Distribution License 114 communities 631 5 Non-reusable Computer Associates Trusted Open Source License 3 Table 3: Operating Systems Projects are developed for: Consolidated 59 categories to 8 categories Rationale for this consolidation: Categories that had similar characteristics were grouped together. For example, the categories All 32-bit MS Windows (95/98/NT/2000/XP), 32-bit MS Windows (NT/2000/XP), WinXP, 32-bit MS Windows (95/98), Win2K, Microsoft Windows Server 2003, WinNT, WinME, Win98 and Microsoft Windows 3.x were all consolidated to the new category “Windows.” Categories containing large numbers of projects were generally left as individual categories. Categories containing small numbers of projects were consolidated to the new category “other.” . What was done: I created a new table in sf_merged named ‘categ_oper_sys_aug06’. This table is a duplicate of the ‘project_operating_system01_aug_06’ table with the fields ‘new_code’ and ‘new_description’ added. I updated the new fields in the new table with the new codes and descriptions listed in the table below using a python script I (Bob English) wrote called add_categ_oper_sys.py. I added the fields ‘os1’, ‘os2’, ‘os3’…, ‘os8’ to the ‘statistical_analysis_0607 table (the flat file table). These fields correspond to the new codes (1-8) in the operating system table below. I updated the os fields with the new codes from the ‘categ_oper_sys_aug06’ table. The new fields are the Boolean data type and have a 1 value if the project lists the corresponding new code and a 0 value if it does not. Some projects list more than one code. NOTE: 5,881 projects that exist in the project_operating_system01_aug_06 table do not exist in the ‘statistical_analysis_0607’ table. Some projects are missing from the ‘statistical_analysis_0607’ table because they were deleted from Sourceforge.net
Load more

Recommended publications
  • Exploration and Combat in Nethack
    EXPLORATION AND COMBAT IN NETHACK by Jonathan C. Campbell School of Computer Science McGill University, Montréal Monday, April 16, 2018 A THESIS SUBMITTED TO THE FACULTY OF GRADUATE STUDIES AND RESEARCH IN PARTIAL FULFILLMENT OF THE REQUIREMENTS FOR THE DEGREE OF MASTER OF SCIENCE Copyright ⃝c 2018 Jonathan C. Campbell Abstract Roguelike games share a common set of core game mechanics, each complex and in- volving randomization which can impede automation. In particular, exploration of levels of randomized layout is a critical and yet often repetitive mechanic, while monster combat typically involves careful, detailed strategy, also a challenge for automation. This thesis presents an approach for both exploration and combat systems in the prototypical rogue- like game, NetHack. For exploration we advance a design involving the use of occupancy maps from robotics and related works, aiming to minimize exploration time of a level by balancing area discovery with resource cost, as well as accounting for the existence of se- cret access points. Our combat strategy involves the use of deep Q-learning to selectively match player items and abilities to each opponent. Through extensive experimentation with both approaches on NetHack, we show that each outperforms simpler, baseline approaches. Results are also presented for a combined combat-exploration algorithm on a full NetHack level context. These results point towards better automation of such complex roguelike game environments, facilitating automated testing and design exploration. i Résumé Les jeux du genre roguelike partagent un ensemble commun de systèmes de jeu de base. Ces systèmes sont souvent complexes et impliquent une randomisation qui peut être un obstacle à l’automatisation.
    [Show full text]
  • The Elinks Manual the Elinks Manual Table of Contents Preface
    The ELinks Manual The ELinks Manual Table of Contents Preface.......................................................................................................................................................ix 1. Getting ELinks up and running...........................................................................................................1 1.1. Building and Installing ELinks...................................................................................................1 1.2. Requirements..............................................................................................................................1 1.3. Recommended Libraries and Programs......................................................................................1 1.4. Further reading............................................................................................................................2 1.5. Tips to obtain a very small static elinks binary...........................................................................2 1.6. ECMAScript support?!...............................................................................................................4 1.6.1. Ok, so how to get the ECMAScript support working?...................................................4 1.6.2. The ECMAScript support is buggy! Shall I blame Mozilla people?..............................6 1.6.3. Now, I would still like NJS or a new JS engine from scratch. .....................................6 1.7. Feature configuration file (features.conf).............................................................................7
    [Show full text]
  • Africa Centre of Excellence on Technology Enhanced Learning (ACETEL)
    CIT 215: INTRODUCTION TO PROGRAMMING LANGUAGE Africa Centre of Excellence on Technology Enhanced Learning (ACETEL) Course Guide 1 NATIONAL OPEN UNIVERSITY OF NIGERIA FACULTY OF SCIENCE COURSE CODE: CIT 215 COURSE TITLE: INTRODUCTION TO PROGRAMMING LANGUAGE 2 Introduction CIT 215 Introduction to Programming Languages is a three [3] credit unit course of twenty units. It deals with Introduction to Programming languages. Programming languages are not very different from spoken languages. Learning any language requires an understanding of the building blocks and the grammar that govern the construction of statements in that language. This book will serve as an introduction to programming languages, taking you through the history of programming languages. We will also learn about the various universal properties of all programming languages and identify distinct design features of each programming language. By the end of this book, you will have a deeper understanding of what a programming language is and the ability to recognize the properties of programming languages. You will also take overview of some programming languages such as to Basic, Fortran, Pascal, C++ , HTML and Visual Basic. Module 1 provides a foundation for the course. In this module we introduce the art of computer programming; explained computer programming languages, and introductory theory of algorithms. Also covered in the module are Flowcharting Techniques and structured programming Module 2: In this module, we provide introductions to the rudiments of BASIC and FORTRAN programming language. In this module we introduce BASIC Programming; explained more programming statements in BASIC, and introduce you to FORTRAN Language. Also covered in the module are FORTRAN Keywords and Library Functions.
    [Show full text]
  • In This Day of 3D Graphics, What Lets a Game Like ADOM Not Only Survive
    Ross Hensley STS 145 Case Study 3-18-02 Ancient Domains of Mystery and Rougelike Games The epic quest begins in the city of Terinyo. A Quake 3 deathmatch might begin with a player materializing in a complex, graphically intense 3D environment, grabbing a few powerups and weapons, and fragging another player with a shotgun. Instantly blown up by a rocket launcher, he quickly respawns. Elapsed time: 30 seconds. By contrast, a player’s first foray into the ASCII-illustrated world of Ancient Domains of Mystery (ADOM) would last a bit longer—but probably not by very much. After a complex process of character creation, the intrepid adventurer hesitantly ventures into a dark cave—only to walk into a fireball trap, killing her. But a perished ADOM character, represented by an “@” symbol, does not fare as well as one in Quake: Once killed, past saved games are erased. Instead, she joins what is no doubt a rapidly growing graveyard of failed characters. In a day when most games feature high-quality 3D graphics, intricate storylines, or both, how do games like ADOM not only survive but thrive, supporting a large and active community of fans? How can a game design seemingly premised on frustrating players through continual failure prove so successful—and so addictive? 2 The Development of the Roguelike Sub-Genre ADOM is a recent—and especially popular—example of a sub-genre of Role Playing Games (RPGs). Games of this sort are typically called “Roguelike,” after the founding game of the sub-genre, Rogue. Inspired by text adventure games like Adventure, two students at UC Santa Cruz, Michael Toy and Glenn Whichman, decided to create a graphical dungeon-delving adventure, using ASCII characters to illustrate the dungeon environments.
    [Show full text]
  • Openbsd Gaming Resource
    OPENBSD GAMING RESOURCE A continually updated resource for playing video games on OpenBSD. Mr. Satterly Updated August 7, 2021 P11U17A3B8 III Title: OpenBSD Gaming Resource Author: Mr. Satterly Publisher: Mr. Satterly Date: Updated August 7, 2021 Copyright: Creative Commons Zero 1.0 Universal Email: [email protected] Website: https://MrSatterly.com/ Contents 1 Introduction1 2 Ways to play the games2 2.1 Base system........................ 2 2.2 Ports/Editors........................ 3 2.3 Ports/Emulators...................... 3 Arcade emulation..................... 4 Computer emulation................... 4 Game console emulation................. 4 Operating system emulation .............. 7 2.4 Ports/Games........................ 8 Game engines....................... 8 Interactive fiction..................... 9 2.5 Ports/Math......................... 10 2.6 Ports/Net.......................... 10 2.7 Ports/Shells ........................ 12 2.8 Ports/WWW ........................ 12 3 Notable games 14 3.1 Free games ........................ 14 A-I.............................. 14 J-R.............................. 22 S-Z.............................. 26 3.2 Non-free games...................... 31 4 Getting the games 33 4.1 Games............................ 33 5 Former ways to play games 37 6 What next? 38 Appendices 39 A Clones, models, and variants 39 Index 51 IV 1 Introduction I use this document to help organize my thoughts, files, and links on how to play games on OpenBSD. It helps me to remember what I have gone through while finding new games. The biggest reason to read or at least skim this document is because how can you search for something you do not know exists? I will show you ways to play games, what free and non-free games are available, and give links to help you get started on downloading them.
    [Show full text]
  • Linux Games Page 1 of 7
    Linux Games Page 1 of 7 Linux Games INTRODUCTION such as the number of players and the size of the map, then you start the game. Once the game is running clients may Hello. My name is Andrew Howlett. I've been using Linux join the game. Clients connect to the game using TCP/IP, since 1997. In 2000 I cutover to Linux for all my projects, so it is very easy to play multi-player games over the except I dual-booted Windows to play games. I like to play Internet. Like many Free games, clients are available for computer games. About a year ago I stopped dual booting. many platforms, including Windows, Amiga and Now I play computer games under Linux. The games I Macintosh. So there are lots of players out there. If you play can be divided into four groups: Free Games, native don't want to play against other humans, then Freeciv linux commercial games, Windows Emulated games, and includes some nasty AIs. Win4Lin enabled games. This presentation will demonstrate games from each of these four groups. BZFlag Platform BZFlag is a tank combat game along the same lines as the old BattleZone game. Like FreeCiv, BZFlag uses a client/ Before I get started, a little bit about my setup so you can server architecture over TCP/IP networks. Unlike FreeCiv, relate this to whatever you are running. This is a P3 900 the game contains no AIs – you must play this game MHz machine. It has a Crystal Sound 4600 sound card and against other humans (? entities ?) over the Internet.
    [Show full text]
  • Lisp: Final Thoughts
    20 Lisp: Final Thoughts Both Lisp and Prolog are based on formal mathematical models of computation: Prolog on logic and theorem proving, Lisp on the theory of recursive functions. This sets these languages apart from more traditional languages whose architecture is just an abstraction across the architecture of the underlying computing (von Neumann) hardware. By deriving their syntax and semantics from mathematical notations, Lisp and Prolog inherit both expressive power and clarity. Although Prolog, the newer of the two languages, has remained close to its theoretical roots, Lisp has been extended until it is no longer a purely functional programming language. The primary culprit for this diaspora was the Lisp community itself. The pure lisp core of the language is primarily an assembly language for building more complex data structures and search algorithms. Thus it was natural that each group of researchers or developers would “assemble” the Lisp environment that best suited their needs. After several decades of this the various dialects of Lisp were basically incompatible. The 1980s saw the desire to replace these multiple dialects with a core Common Lisp, which also included an object system, CLOS. Common Lisp is the Lisp language used in Part III. But the primary power of Lisp is the fact, as pointed out many times in Part III, that the data and commands of this language have a uniform structure. This supports the building of what we call meta-interpreters, or similarly, the use of meta-linguistic abstraction. This, simply put, is the ability of the program designer to build interpreters within Lisp (or Prolog) to interpret other suitably designed structures in the language.
    [Show full text]
  • MX Linux Benutzerhandbuch V
    MX Linux Benutzerhandbuch v. 20210327 manual AT mxlinux DOT org MX Linux Webseite MX Linux deutschsprachiges Forum Strg-F = Dieses Handbuch durchsuchen Pos1 / Home = Zum Anfang des Dokuments Translation: Sigi Vranšak – SpinBit Informatik Schaan, 27.03.2021 Tools: LibreOffice 7.0.4, deepl.com Rückmeldungen zu diesem deutschsprachigen Handbuch bitte an: [email protected] OpenPGP 51F0D5C53CF46E29 Titel des englischen Originals: MX Linux Users Manual v. 20200801 Inhalt 1 Einleitung.........................................................................................................................................7 1.1 Über MX Linux..........................................................................................................................7 1.2 Über dieses Handbuch.............................................................................................................7 1.3 Systemanforderungen..............................................................................................................8 1.4 Unterstützung und «Lebensdauer» (EOL, End Of Life)...........................................................8 1.5 Fehler, Probleme und Anfragen, Anträge.................................................................................9 1.6 Migration, Upgrade (Aktualisierung nächste Hauptversion)..................................................10 1.7 Unsere Standpunkte...............................................................................................................10 1.7.1 Systemd..........................................................................................................................10
    [Show full text]
  • Drscheme: a Pedagogic Programming Environment for Scheme
    DrScheme A Pedagogic Programming Environment for Scheme Rob ert Bruce Findler Cormac Flanagan Matthew Flatt Shriram Krishnamurthi and Matthias Felleisen Department of Computer Science Rice University Houston Texas Abstract Teaching intro ductory computing courses with Scheme el evates the intellectual level of the course and thus makes the sub ject more app ealing to students with scientic interests Unfortunatelythe p o or quality of the available programming environments negates many of the p edagogic advantages Toovercome this problem wehavedevel op ed DrScheme a comprehensive programming environmentforScheme It fully integrates a graphicsenriched editor a multilingua l parser that can pro cess a hierarchyofsyntactically restrictivevariants of Scheme a functional readevalprint lo op and an algebraical ly sensible printer The environment catches the typical syntactic mistakes of b eginners and pinp oints the exact source lo cation of runtime exceptions DrScheme also provides an algebraic stepp er a syntax checker and a static debugger The rst reduces Scheme programs including programs with assignment and control eects to values and eects The to ol is useful for explainin g the semantics of linguistic facilities and for studying the b ehavior of small programs The syntax c hecker annotates programs with fontandcolorchanges based on the syntactic structure of the pro gram It also draws arrows on demand that p oint from b ound to binding o ccurrences of identiers The static debugger roughly sp eaking pro vides a typ e inference system
    [Show full text]
  • 1. with Examples of Different Programming Languages Show How Programming Languages Are Organized Along the Given Rubrics: I
    AGBOOLA ABIOLA CSC302 17/SCI01/007 COMPUTER SCIENCE ASSIGNMENT ​ 1. With examples of different programming languages show how programming languages are organized along the given rubrics: i. Unstructured, structured, modular, object oriented, aspect oriented, activity oriented and event oriented programming requirement. ii. Based on domain requirements. iii. Based on requirements i and ii above. 2. Give brief preview of the evolution of programming languages in a chronological order. 3. Vividly distinguish between modular programming paradigm and object oriented programming paradigm. Answer 1i). UNSTRUCTURED LANGUAGE DEVELOPER DATE Assembly Language 1949 FORTRAN John Backus 1957 COBOL CODASYL, ANSI, ISO 1959 JOSS Cliff Shaw, RAND 1963 BASIC John G. Kemeny, Thomas E. Kurtz 1964 TELCOMP BBN 1965 MUMPS Neil Pappalardo 1966 FOCAL Richard Merrill, DEC 1968 STRUCTURED LANGUAGE DEVELOPER DATE ALGOL 58 Friedrich L. Bauer, and co. 1958 ALGOL 60 Backus, Bauer and co. 1960 ABC CWI 1980 Ada United States Department of Defence 1980 Accent R NIS 1980 Action! Optimized Systems Software 1983 Alef Phil Winterbottom 1992 DASL Sun Micro-systems Laboratories 1999-2003 MODULAR LANGUAGE DEVELOPER DATE ALGOL W Niklaus Wirth, Tony Hoare 1966 APL Larry Breed, Dick Lathwell and co. 1966 ALGOL 68 A. Van Wijngaarden and co. 1968 AMOS BASIC FranÇois Lionet anConstantin Stiropoulos 1990 Alice ML Saarland University 2000 Agda Ulf Norell;Catarina coquand(1.0) 2007 Arc Paul Graham, Robert Morris and co. 2008 Bosque Mark Marron 2019 OBJECT-ORIENTED LANGUAGE DEVELOPER DATE C* Thinking Machine 1987 Actor Charles Duff 1988 Aldor Thomas J. Watson Research Center 1990 Amiga E Wouter van Oortmerssen 1993 Action Script Macromedia 1998 BeanShell JCP 1999 AngelScript Andreas Jönsson 2003 Boo Rodrigo B.
    [Show full text]
  • Securing Debian HOWTO
    Securing Debian HOWTO Javier Fernández-Sanguino Peña <[email protected]> v1.92 6 noviembre 2001Tue Oct 23 00:59:57 CEST 2001 Abstract This document describes the process of securing and hardening the default Debian installation. It covers some of the common taks to setup a secure network environment using Debian GNU/Linux. Copyright Notice Copyright c 2001 Alexander Reelsen, Javier Fernández-Sanguino Peña Copyright c 2000 Alexander Reelsen however it is distributed under the terms of the GNU free documentation license. This document is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY. i Contents 1 Introduction 1 1.1 Download the HOWTO ................................... 1 1.2 Organizational Notes/Feedback ............................... 2 1.3 Prior knowledge ....................................... 2 1.4 Things that need to be written (TODO) ........................... 2 1.5 Changelog .......................................... 4 1.5.1 Version 1.92 .................................... 4 1.5.2 Version 1.91 .................................... 4 1.5.3 Version 1.9 ..................................... 4 1.5.4 Version 1.8 ..................................... 5 1.5.5 Version 1.7 ..................................... 5 1.5.6 Version 1.6 ..................................... 5 1.5.7 Version 1.5 ..................................... 6 1.5.8 Version 1.4 ..................................... 6 1.5.9 Version 1.3 ..................................... 6 1.5.10 Version 1.2 ..................................... 6 1.5.11 Version 1.1 ..................................... 6 1.5.12 Version 1.0 ..................................... 6 1.6 Credits ............................................ 7 2 Before you begin 9 2.1 What do you want this system for? ............................. 9 2.2 Be aware of general security problems ........................... 9 2.3 How does Debian handle security? ............................. 11 CONTENTS ii 3 Before and during the installation 13 3.1 Choose a BIOS password .................................
    [Show full text]
  • 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.
    [Show full text]