DOCSLIB.ORG

AROS User Manual

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
AROS User Manual AROS User Manual 2 - AROS USER MANUAL AROS PUBLIC LICENSE (APL) You may obtain a copy of the License at http://www.aros.org/license.html DISCLAIMER OF WARRANTY. COVERED CODE IS PROVIDED UNDER THIS LICENSE ON AN —AS IS“ BASIS, WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, WITHOUT LIMITATION, WARRANTIES THAT THE COVERED CODE IS FREE OF DEFECTS, MERCHANTABLE, FIT FOR A PARTICULAR PURPOSE OR NON-INFRINGING. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE COVERED CODE IS WITH YOU. SHOULD ANY COVERED CODE PROVE DEFECTIVE IN ANY RESPECT, YOU (NOT THE INITIAL DEVELOPER OR ANY OTHER CONTRIBUTOR) ASSUME THE COST OF ANY NECESSARY SERVICING, REPAIR OR CORRECTION. THIS DISCLAIMER OF WARRANTY CONSTITUTES AN ESSENTIAL PART OF THIS LICENSE. NO USE OF ANY COVERED CODE IS AUTHORIZED HEREUNDER EXCEPT UNDER THIS DISCLAIMER. LIMITATION OF LIABILITY. UNDER NO CIRCUMSTANCES AND UNDER NO LEGAL THEORY, WHETHER TORT (INCLUDING NEGLIGENCE), CONTRACT, OR OTHERWISE, SHALL YOU, THE INITIAL DEVELOPER, ANY OTHER CONTRIBUTOR, OR ANY DISTRIBUTOR OF COVERED CODE, OR ANY SUPPLIER OF ANY OF SUCH PARTIES, BE LIABLE TO ANY PERSON FOR ANY INDIRECT, SPECIAL, INCIDENTAL, OR CONSEQUENTIAL DAMAGES OF ANY CHARACTER INCLUDING, WITHOUT LIMITATION, DAMAGES FOR LOSS OF GOODWILL, WORK STOPPAGE, COMPUTER FAILURE OR MALFUNCTION, OR ANY AND ALL OTHER COMMERCIAL DAMAGES OR LOSSES, EVEN IF SUCH PARTY SHALL HAVE BEEN INFORMED OF THE POSSIBILITY OF SUCH DAMAGES. THIS LIMITATION OF LIABILITY SHALL NOT APPLY TO LIABILITY FOR DEATH OR PERSONAL INJURY RESULTING FROM SUCH PARTY'S NEGLIGENCE TO THE EXTENT APPLICABLE LAW PROHIBITS SUCH LIMITATION. SOME JURISDICTIONS DO NOT ALLOW THE EXCLUSION OR LIMITATION OF INCIDENTAL OR CONSEQUENTIAL DAMAGES, SO THIS EXCLUSION AND LIMITATION MAY NOT APPLY TO YOU. COPYRIGHT AND TRADEMARKS. Copyright © 1995-2007, The AROS Development Team. All rights reserved. The AROS Kitty mascot is © 2003 by Eric schwartz The image used in the cover is © 2005 by Damir Sijakovic. Amiga® is a trademark of Amiga Inc. All other trademarks belong to their respective owners. This manual was produced using a variety of resources and documentation available in www.aros.org and other AROS resource sites by João Ralha. Original AROS USER documentation was written by Stefan Rieken, Matt Parsons, Adam Chodorowski, Sergey Mineychev. AROS USER MANUAL - 3 TABLE OF CONTENTS WELCOME...........................................................................................................5 DOCUMENTATION CONVENTIONS ............................................................................5 OTHER USEFUL OR REFERENCE DOCUMENTATION........................................................6 INTRODUCTION ............................................................................. 7 WHAT‘S AROS?..................................................................................................7 GOALS ...............................................................................................................7 HISTORY ............................................................................................................7 REQUIREMENTS ...................................................................................................8 WARNING.........................................................................................................10 CHAPTER 1: AROS BASICS........................................................... 11 AROS ZUNE GUI BASICS ...................................................................................11 AROS BASIC HANDLING .....................................................................................15 Booting / Rebooting..........................................................................................15 Wandering around ............................................................................................16 CHAPTER 2: FILE MANAGEMENT ................................................. 18 DISK DEVICES...................................................................................................18 PATHS............................................................................................................19 FILES AND DRAWER......................................................................................19 FILE SYSTEMS ...................................................................................................20 ORGANIZING YOUR DATA.....................................................................................20 PREPARING A VOLUME........................................................................................20 Creating a drawer.............................................................................................21 Deleting files/drawers........................................................................................22 CHAPTER 3: AROS PROGRAMS .................................................... 25 AROS SYSTEM PROGRAMS ..................................................................................25 TOOLS DRAWER.................................................................................................26 Commodities.....................................................................................................27 DEVS AND STORAGE.......................................................................................28 Datatypes.........................................................................................................29 Dosdrivers........................................................................................................29 Drivers.............................................................................................................29 Keymaps..........................................................................................................30 MIDI ................................................................................................................30 Networks..........................................................................................................30 Printers............................................................................................................30 SYSTEM DIRECTORY ...........................................................................................31 UTILITIES DRAWER............................................................................................33 Clock................................................................................................................33 Installer............................................................................................................33 More................................................................................................................33 Multiview..........................................................................................................34 Snoopy.............................................................................................................34 WBSTARTUP DRAWER........................................................................................34 Tool types........................................................................................................34 CHAPTER 4: CUSTOMISING AROS............................................... 36 SETTING THE TIME AND DATE..............................................................................36 SETTING UP THE LOCALE.....................................................................................37 SETTING UP THE INPUT .......................................................................................38 4 - AROS USER MANUAL SETTING WANDERER LOOK AND USE.....................................................................38 Icontrol............................................................................................................ 39 Wanderer......................................................................................................... 39 FONT............................................................................................................... 41 Reqtools prefs.................................................................................................. 41 SETTING UP THE SOUND.....................................................................................42 SETTING UP INPUT/OUTPUT DEVICES ...................................................................42 Trackdisk prefs................................................................................................. 42 Serial Prefs....................................................................................................... 43 CHAPTER 5: EXTRA APPLICATIONS............................................. 44 APPENDIX I œ FONT SUPPORT..................................................... 51 Bitmap fonts..................................................................................................... 51 Free-type fonts................................................................................................. 51 APPENDIX II œ BOOT OPTIONS ................................................... 53 GRUB SUPPORT ........................................................................ 53 HOW DOES IT WORK?.........................................................................................53 AROS Specific GRUB support ............................................................................. 54 APPENDIX IV œ TROUBLE SHOOTING.......................................... 55 KNOWN PROBLEMATIC AND HARDWARE, OR THE
Load more

Recommended publications
  • MAGIC Summoning: Towards Automatic Suggesting and Testing of Gestures with Low Probability of False Positives During Use
    JournalofMachineLearningResearch14(2013)209-242 Submitted 10/11; Revised 6/12; Published 1/13 MAGIC Summoning: Towards Automatic Suggesting and Testing of Gestures With Low Probability of False Positives During Use Daniel Kyu Hwa Kohlsdorf [email protected] Thad E. Starner [email protected] GVU & School of Interactive Computing Georgia Institute of Technology Atlanta, GA 30332 Editors: Isabelle Guyon and Vassilis Athitsos Abstract Gestures for interfaces should be short, pleasing, intuitive, and easily recognized by a computer. However, it is a challenge for interface designers to create gestures easily distinguishable from users’ normal movements. Our tool MAGIC Summoning addresses this problem. Given a specific platform and task, we gather a large database of unlabeled sensor data captured in the environments in which the system will be used (an “Everyday Gesture Library” or EGL). The EGL is quantized and indexed via multi-dimensional Symbolic Aggregate approXimation (SAX) to enable quick searching. MAGIC exploits the SAX representation of the EGL to suggest gestures with a low likelihood of false triggering. Suggested gestures are ordered according to brevity and simplicity, freeing the interface designer to focus on the user experience. Once a gesture is selected, MAGIC can output synthetic examples of the gesture to train a chosen classifier (for example, with a hidden Markov model). If the interface designer suggests his own gesture and provides several examples, MAGIC estimates how accurately that gesture can be recognized and estimates its false positive rate by comparing it against the natural movements in the EGL. We demonstrate MAGIC’s effectiveness in gesture selection and helpfulness in creating accurate gesture recognizers.
    [Show full text]
  • Amigan Software
    tali ► an Amiga Februar y 97 Issue No 3 Gaz te rip $3 Who said that there are no Amiga dealers left? Hardware Amiga A1200 HD, Amiga A4000 Cobra 33 68030 33, Mhz Cobra 33+ with 68882, Cobra 40 68EC030 40 Mhz, Cobra40+ with 68882, Ferret SCSI card for Cobra 1202 32 bit rami- clock, 1202+ with 16 or 33 Mhz 68882, Squirrel SCSI, Surf Squirrel SCSI plus RS@232, 2 Mb PCMCIA Ram A1200/A600, Spitfire SCSI A2000/3000/4000, Rapidfire SCSI + RAM A2000, Wildfire A2000 68060+ram+SCSI F/W+network, Megachip, 2Mb chip ram A500/A2000, Securekey Security card for A2000/3000/4000, Picasso Graphics cards, SCSI and IDE Hard drives. Accessories Green Mouse -320 DPI with pad, Hypermouse I1 400 DPI with pad, Pen mouse - super small, Joysticks, from Quickshot and Rocfire, GI 105 hand- scanner with touchup 4 and OCR Jr, Colourburst colour hand scanner with ADPRO loader & OCR Jr, Master 3A 880 K External Floppy drives, Rocgen Plus genlock, Electronic Design Genlocks and TBC, Neriki Genlocks Syquest EzDrives, External SCSI Cases with A500/A600/A1200 power lead included & CD, or hard drive option, A1200 3.5 IDE Kits, Monitor adaptors, ROM Switches, Air Freight Magazines with CD. Plus Much more Available. Software Over 70 titles in stock including games, productivity, CD rom titles, and Utilities, all at competative prices. Servicing We have a fully equiped workshop, and our techs have a total of over 50 Man years of experience as technicians in the computer industry. We do repairs and upgrades including specialist work. The Complete Amiga specialist.
    [Show full text]
  • Calendrical Calculations: Third Edition
    Notes and Errata for Calendrical Calculations: Third Edition Nachum Dershowitz and Edward M. Reingold Cambridge University Press, 2008 4:00am, July 24, 2013 Do I contradict myself ? Very well then I contradict myself. (I am large, I contain multitudes.) —Walt Whitman: Song of Myself All those complaints that they mutter about. are on account of many places I have corrected. The Creator knows that in most cases I was misled by following. others whom I will spare the embarrassment of mention. But even were I at fault, I do not claim that I reached my ultimate perfection from the outset, nor that I never erred. Just the opposite, I always retract anything the contrary of which becomes clear to me, whether in my writings or my nature. —Maimonides: Letter to his student Joseph ben Yehuda (circa 1190), Iggerot HaRambam, I. Shilat, Maaliyot, Maaleh Adumim, 1987, volume 1, page 295 [in Judeo-Arabic] Cuiusvis hominis est errare; nullius nisi insipientis in errore perseverare. [Any man can make a mistake; only a fool keeps making the same one.] —Attributed to Marcus Tullius Cicero If you find errors not given below or can suggest improvements to the book, please send us the details (email to [email protected] or hard copy to Edward M. Reingold, Department of Computer Science, Illinois Institute of Technology, 10 West 31st Street, Suite 236, Chicago, IL 60616-3729 U.S.A.). If you have occasion to refer to errors below in corresponding with the authors, please refer to the item by page and line numbers in the book, not by item number.
    [Show full text]
  • Amigaos 3.2 FAQ 47.1 (09.04.2021) English
    $VER: AmigaOS 3.2 FAQ 47.1 (09.04.2021) English Please note: This file contains a list of frequently asked questions along with answers, sorted by topics. Before trying to contact support, please read through this FAQ to determine whether or not it answers your question(s). Whilst this FAQ is focused on AmigaOS 3.2, it contains information regarding previous AmigaOS versions. Index of topics covered in this FAQ: 1. Installation 1.1 * What are the minimum hardware requirements for AmigaOS 3.2? 1.2 * Why won't AmigaOS 3.2 boot with 512 KB of RAM? 1.3 * Ok, I get it; 512 KB is not enough anymore, but can I get my way with less than 2 MB of RAM? 1.4 * How can I verify whether I correctly installed AmigaOS 3.2? 1.5 * Do you have any tips that can help me with 3.2 using my current hardware and software combination? 1.6 * The Help subsystem fails, it seems it is not available anymore. What happened? 1.7 * What are GlowIcons? Should I choose to install them? 1.8 * How can I verify the integrity of my AmigaOS 3.2 CD-ROM? 1.9 * My Greek/Russian/Polish/Turkish fonts are not being properly displayed. How can I fix this? 1.10 * When I boot from my AmigaOS 3.2 CD-ROM, I am being welcomed to the "AmigaOS Preinstallation Environment". What does this mean? 1.11 * What is the optimal ADF images/floppy disk ordering for a full AmigaOS 3.2 installation? 1.12 * LoadModule fails for some unknown reason when trying to update my ROM modules.
    [Show full text]
  • Metadefender Core V4.12.2
    MetaDefender Core v4.12.2 © 2018 OPSWAT, Inc. All rights reserved. OPSWAT®, MetadefenderTM and the OPSWAT logo are trademarks of OPSWAT, Inc. All other trademarks, trade names, service marks, service names, and images mentioned and/or used herein belong to their respective owners. Table of Contents About This Guide 13 Key Features of Metadefender Core 14 1. Quick Start with Metadefender Core 15 1.1. Installation 15 Operating system invariant initial steps 15 Basic setup 16 1.1.1. Configuration wizard 16 1.2. License Activation 21 1.3. Scan Files with Metadefender Core 21 2. Installing or Upgrading Metadefender Core 22 2.1. Recommended System Requirements 22 System Requirements For Server 22 Browser Requirements for the Metadefender Core Management Console 24 2.2. Installing Metadefender 25 Installation 25 Installation notes 25 2.2.1. Installing Metadefender Core using command line 26 2.2.2. Installing Metadefender Core using the Install Wizard 27 2.3. Upgrading MetaDefender Core 27 Upgrading from MetaDefender Core 3.x 27 Upgrading from MetaDefender Core 4.x 28 2.4. Metadefender Core Licensing 28 2.4.1. Activating Metadefender Licenses 28 2.4.2. Checking Your Metadefender Core License 35 2.5. Performance and Load Estimation 36 What to know before reading the results: Some factors that affect performance 36 How test results are calculated 37 Test Reports 37 Performance Report - Multi-Scanning On Linux 37 Performance Report - Multi-Scanning On Windows 41 2.6. Special installation options 46 Use RAMDISK for the tempdirectory 46 3. Configuring Metadefender Core 50 3.1. Management Console 50 3.2.
    [Show full text]
  • Converted from Amigaguide by Drbong/HOL Team
    PHOENIX FIGHTERS Manual (1.5) What is Phoenix Fighters? System Requirements Installation Controls Game Modes Game Details Fighter Ships Weapons and Equipment Hints and Tips Credits Contact Bitwise Contact Alive Mediasoft (C)1999 Bitwise / Alive Mediasoft Ltd. WHAT IS PHOENIX FIGHTERS? Phoenix Fighters is a "gravity" game in the style of the classics like Gravity Force and Thrust. There have many games in this genre in the past and we have played them all - we feel that we have taken the best bits of them all and compiled them in one great game! You are one of the elite Phoenix Fighters pilots and are required to do all kinds of dangerous missions; Destroy enemies, make investigations, navigate narrow passes, prove your ship handling skills, carry reactors... You will receive rewards from completed missions which can used to buy new ships or update your old ones. SYSTEM REQUIREMENTS An Amiga computer with minimum of 1MB RAM and KS1.3. PAL display mode. Supports hard disk and takes advantage of extra RAM and faster processors. INSTALLATION The installation of Phoenix Fighters is done using the standard installer utility. Double click the install icon on the CD/disk1 and follow the instructions. If dos.library v36 or greater is present there is no need of any assigns. For earlier ROM's an assign will be needed if the game is started from workbench icon or if it's started in a shell from a directory other than the directory containing the files (like "pf/phoenixfighters"). As assigns, both "PhoenixFighters:" and "PF:" will be searched.
    [Show full text]
  • An Introduction to Morphos
    An Introduction to MorphOS Updated to include features to version 1.4.5 May 14, 2005 MorphOS 1.4 This presentation gives an overview of MorphOS and the features that are present in the MorphOS 1.4 shipping product. For a fully comprehensive list please see the "Full Features list" which can be found at: www.PegasosPPC.com Why MorphOS? Modern Operating Systems are powerful, flexible and stable tools. For the most part, if you know how to look after them, they do their job reasonably well. But, they are just tools to do a job. They've lost their spark, they're boring. A long time ago computers were fun, it is this background that MorphOS came from and this is what MorphOS is for, making computers fun again. What is MorphOS? MorphOS is a fully featured desktop Operating System for PowerPC CPUs. It is small, highly responsive and has very low hardware requirements. The overall structure of MorphOS is based on a new modern kernel called Quark and a structure divided into a series of "boxes". This system allows different OS APIs to be used along side one another but isolates them so one cannot compromise the other. To make sure there is plenty of software to begin with the majority of development to date has been based on the A- BOX. In the future the more advanced Q-Box shall be added. Compatibility The A-Box is an entire PowerPC native OS layer which includes source and binary compatibility with software for the Commodore A500 / A1200 etc.
    [Show full text]
  • Understanding and Mitigating the Security Risks of Apple Zeroconf
    2016 IEEE Symposium on Security and Privacy Staying Secure and Unprepared: Understanding and Mitigating the Security Risks of Apple ZeroConf Xiaolong Bai*,1, Luyi Xing*,2, Nan Zhang2, XiaoFeng Wang2, Xiaojing Liao3, Tongxin Li4, Shi-Min Hu1 1TNList, Tsinghua University, Beijing, 2Indiana University Bloomington, 3Georgia Institute of Technology, 4Peking University [email protected], {luyixing, nz3, xw7}@indiana.edu, [email protected], [email protected], [email protected] Abstract—With the popularity of today’s usability-oriented tend to build their systems in a “plug-and-play” fashion, designs, dubbed Zero Configuration or ZeroConf, unclear are using techniques dubbed zero-configuration (ZeroConf ). For the security implications of these automatic service discovery, example, the AirDrop service on iPhone, once activated, “plug-and-play” techniques. In this paper, we report the first systematic study on this issue, focusing on the security features automatically detects another Apple device nearby running of the systems related to Apple, the major proponent of the service to transfer documents. Such ZeroConf services ZeroConf techniques. Our research brings to light a disturb- are characterized by automatic IP selection, host name ing lack of security consideration in these systems’ designs: resolving and target service discovery. Prominent examples major ZeroConf frameworks on the Apple platforms, includ- include Apple’s Bonjour [3], and the Link-Local Multicast ing the Core Bluetooth Framework, Multipeer Connectivity and
    [Show full text]
  • A Directory Structure for TEX Files TUG Working Group on a TEX Directory Structure (TWG-TDS) Version 1.1 June 23, 2004
    A Directory Structure for TEX Files TUG Working Group on a TEX Directory Structure (TWG-TDS) version 1.1 June 23, 2004 Copyright c 1994, 1995, 1996, 1997, 1998, 1999, 2003, 2004 TEX Users Group. Permission to use, copy, and distribute this document without modification for any purpose and without fee is hereby granted, provided that this notice appears in all copies. It is provided “as is” without expressed or implied warranty. Permission is granted to copy and distribute modified versions of this document under the condi- tions for verbatim copying, provided that the modifications are clearly marked and the document is not represented as the official one. This document is available on any CTAN host (see Appendix D). Please send questions or suggestions by email to [email protected]. We welcome all comments. This is version 1.1. Contents 1 Introduction 2 1.1 History . 2 1.2 The role of the TDS ................................... 2 1.3 Conventions . 3 2 General 3 2.1 Subdirectory searching . 3 2.2 Rooting the tree . 4 2.3 Local additions . 4 2.4 Duplicate filenames . 5 3 Top-level directories 5 3.1 Macros . 6 3.2 Fonts............................................ 8 3.3 Non-font METAFONT files................................ 10 3.4 METAPOST ........................................ 10 3.5 BIBTEX .......................................... 11 3.6 Scripts . 11 3.7 Documentation . 12 4 Summary 13 4.1 Documentation tree summary . 14 A Unspecified pieces 15 A.1 Portable filenames . 15 B Implementation issues 16 B.1 Adoption of the TDS ................................... 16 B.2 More on subdirectory searching . 17 B.3 Example implementation-specific trees .
    [Show full text]
  • Solution 6: Drag and Drop 169
    06_0132344815_ch06.qxd 10/16/07 11:41 AM Page 167 SolutionSolution 1: Drag and Drop 167 6 Drag and Drop The ultimate in user interactivity, drag and drop is taken for granted in desktop appli- cations but is a litmus test of sorts for web applications: If you can easily implement drag and drop with your web application framework, then you know you’ve got something special. Until now, drag and drop for web applications has, for the most part, been limited to specialized JavaScript frameworks such as Script.aculo.us and Rico.1 No more. With the advent of GWT, we have drag-and-drop capabilities in a Java-based web applica- tion framework. Although GWT does not explicitly support drag and drop (drag and drop is an anticipated feature in the future), it provides us with all the necessary ingre- dients to make our own drag-and-drop module. In this solution, we explore drag-and-drop implementation with GWT. We implement drag and drop in a module of its own so that you can easily incorporate drag and drop into your applications. Stuff You’re Going to Learn This solution explores the following aspects of GWT: • Implementing composite widgets with the Composite class (page 174) • Removing widgets from panels (page 169) • Changing cursors for widgets with CSS styles (page 200) • Implementing a GWT module (page 182) • Adding multiple listeners to a widget (page 186) • Using the AbsolutePanel class to place widgets by pixel location (page 211) • Capturing and releasing events for a specific widget (page 191) • Using an event preview to inhibit browser reactions to events (page 196) 1 See http://www.script.aculo.us and http://openrico.org for more information about Script.aculo.us and Rico, respectively.
    [Show full text]
  • Cooper ( Interaction Design
    Cooper ( Interaction Design Inspiration The Myth of Metaphor Cooper books by Alan Cooper, Chairman & Founder Articles June 1995 Newsletter Originally Published in Visual Basic Programmer's Journal Concept projects Book reviews Software designers often speak of "finding the right metaphor" upon which to base their interface design. They imagine that rendering their user interface in images of familiar objects from the real world will provide a pipeline to automatic learning by their users. So they render their user interface as an office filled with desks, file cabinets, telephones and address books, or as a pad of paper or a street of buildings in the hope of creating a program with breakthrough ease-of- learning. And if you search for that magic metaphor, you will be in august company. Some of the best and brightest designers in the interface world put metaphor selection as one of their first and most important tasks. But by searching for that magic metaphor you will be making one of the biggest mistakes in user interface design. Searching for that guiding metaphor is like searching for the correct steam engine to power your airplane, or searching for a good dinosaur on which to ride to work. I think basing a user interface design on a metaphor is not only unhelpful but can often be quite harmful. The idea that good user interface design is based on metaphors is one of the most insidious of the many myths that permeate the software community. Metaphors offer a tiny boost in learnability to first time users at http://www.cooper.com/articles/art_myth_of_metaphor.htm (1 of 8) [1/16/2002 2:21:34 PM] Cooper ( Interaction Design tremendous cost.
    [Show full text]
  • UC Santa Cruz UC Santa Cruz Electronic Theses and Dissertations
    UC Santa Cruz UC Santa Cruz Electronic Theses and Dissertations Title Efficient Bug Prediction and Fix Suggestions Permalink https://escholarship.org/uc/item/47x1t79s Author Shivaji, Shivkumar Publication Date 2013 Peer reviewed|Thesis/dissertation eScholarship.org Powered by the California Digital Library University of California UNIVERSITY OF CALIFORNIA SANTA CRUZ EFFICIENT BUG PREDICTION AND FIX SUGGESTIONS A dissertation submitted in partial satisfaction of the requirements for the degree of DOCTOR OF PHILOSOPHY in COMPUTER SCIENCE by Shivkumar Shivaji March 2013 The Dissertation of Shivkumar Shivaji is approved: Professor Jim Whitehead, Chair Professor Jose Renau Professor Cormac Flanagan Tyrus Miller Vice Provost and Dean of Graduate Studies Copyright c by Shivkumar Shivaji 2013 Table of Contents List of Figures vi List of Tables vii Abstract viii Acknowledgments x Dedication xi 1 Introduction 1 1.1 Motivation . .1 1.2 Bug Prediction Workflow . .9 1.3 Bug Prognosticator . 10 1.4 Fix Suggester . 11 1.5 Human Feedback . 11 1.6 Contributions and Research Questions . 12 2 Related Work 15 2.1 Defect Prediction . 15 2.1.1 Totally Ordered Program Units . 16 2.1.2 Partially Ordered Program Units . 18 2.1.3 Prediction on a Given Software Unit . 19 2.2 Predictions of Bug Introducing Activities . 20 2.3 Predictions of Bug Characteristics . 21 2.4 Feature Selection . 24 2.5 Fix Suggestion . 25 2.5.1 Static Analysis Techniques . 25 2.5.2 Fix Content Prediction without Static Analysis . 26 2.6 Human Feedback . 28 iii 3 Change Classification 30 3.1 Workflow . 30 3.2 Finding Buggy and Clean Changes .
    [Show full text]