Introduction to Unix for Programmers

Total Page:16

File Type:pdf, Size:1020Kb

Introduction to Unix for Programmers CS252 Introduction to Unix for Programmers April 24, 2020 CS252 Outline Spring 2020 1 Preamble Syllabus Policies Library Library Below are the modules that comprise the course content. Each module includes a mixture of lecture notes for you to read (required) and relevant textbook chapters (optional). Many of the lecture notes include “Try This” activities for you to perform while logged in to one of our Linux servers. Most modules include at least one assignment that you should attempt to complete before moving on. KEYS TO SUCCESS IN THIS COURSE: 1. READ THE SYLLABUS The syllabus lays out the basic course policies. It tells you what you need to do to earn a passing grade. It tells you when you need to have done that by. It tells you how to get in touch with me if you run into problems. 2. HAVE A SCHEDULE You have the freedom to schedule your own time in this course, but you DO need to set up a schedule. Don’t forget that this course exists and that you are registered for it. Don’t think you can repeatedly set it aside for weeks at a time and make up the time later. There are 14 assignments in the course. There are approximately 14 weeks in a Fall or Spring semester (12 in summer). You can easily figure out what kind of pace you should be setting if you want to complete this course. 3. IF YOU DON"T UNDERSTAND SOMETHING, ASK QUESTIONS In a web course, my role as Instructor changes from “lecturer” to “tutor”. You can ask questions in the course Forums. You can send me email. You can also contact me during office hours. You’ll find more information on these options in the syllabus and other documents on the Course Policies page. Some people are too shy to ask questions. Some are too proud to ask questions. My advice to both groups is to get over it! Part of being educated is knowing how to exploit your available information resources. In this course, I am one of those resources. 4. READ THE LECTURE NOTES. DO THE “TRY THIS” EXERCISES. As a general rule, everything you need to complete the assignments and final exam are contained in the lecture notes and are things that you will practice with in the “Try This” exercises. The listed textbook readings are optional. Hunting the internet for additional info is possible, but can often lead to more confusion than enlightenment, so you do that at your own risk. When you read, read attentively. When you do the Try This exercises, be observant to the results you are getting and make sure that you understand them. If you consistently find yourself starting the assignments thinking that you are prepared, then get stuck with no idea how to proceed, that’s a good sign that you were not really giving the lecture notes or Try This exercises enough attention. 1 Getting Started Objectives Upon completing this section, a student should… Be familiar with the course layout and policies. Understand the differences between local and remote command sessions text-mode and graphics mode sessions Have set up a CS network account. Be able to log in to a remote text-mode session on the CS Dept Linux machines. 1. Read: Welcome to CS 252 2. Read: CS 252 Syllabus - Spring 2020 3. Read: Communications 4. Why Unix? 5. Unix account setup 6. Peek: Preface, Ch 1 7. Logging In 8. See website for assignment. 2 The Basics: Working in Text Mode 2.1 Files and Directories Objectives Upon completing this section, a student should… Understand the hierarchical structure of a typical file system. Understand how paths identify the location of a file. Recognize the various ways to name their own home directory and those of other account holders. Understand the difference between relative and absolute paths. Write both absolute and relative paths to a desired file. Be able to issue basic commands for creating and listing directories, copying, moving, and viewing the contents of files. 1. Working in a Text-Based Interface 2. Peek: Ch 3 3. Taylor, ch 3, 4, 6 4. The Unix File System 5. Basic File Manipulation 6. See website for assignment. 7. Getting Help 2.2 The Elements of Unix Commands Objectives Upon completing this section, a student should be able to… Understand the common special characters available in the command shell. Use special characters to speed up and simplify the typing of commands. Use the three forms of quoting (single quotes, double quotes, and backslashes) to suppress special character actions. Be able to use wildcard patterns to describe lists of multiple files. 1. Typing Unix Commands 2. Patterns for File Names: Wildcards 3. Peek: Ch 4 4. Quoting Special Characters 5. See website for assignment. 2.3 Editing Files Objectives Upon completing this section, a student should be able to… Discuss the relative merits of the nano, emacs, and vim editors. Use at least two of those editors to create and modify text files. 1. Editing in Text Mode 2. Sobell, ch 6,7 3. See website for assignment. 2.4 Protection Objectives Upon completing this section, a student should be able to… Understand the Unix file permissions model. List the permissions being granted by a file. Change the permissions granted by a file. 1. Tansley, ch 1 2. File Protection 3. See website for assignment. 2.5 File Transfer Objectives Upon completing this section, a student should be able to… Identify the common protocols used to transfer files from one computer to another over a network. Understand the difference in ASCII text file format between Windows and other operating systems (Unix, Android, OS/X). Transform ASCII text files from Windows format to Unix and vice versa. Use SFTP to transfer files between their own PC and the CS Dept servers. 1. Peek: Ch 6 2. File Transfer 3. See website for assignment. 2.6 Regular Expressions Objectives Upon completing this section, a student should be able to… Write regular expression patterns to describe desired text during search operations. Use common commands for searching through the contents of files and for doing simple text replacements within a file. 1. Patterns for Text: Regular Expressions 2. Tansley, ch 7-8, 10 3. See website for assignment. 2.7 Modifying and Combining Commands Objectives Upon completing this section, a student should be able to… Use input redirection to send the contents of a file to the input of a command that is expecting standard (keyboard) input. Use output redirection to send the output of a command into a file rather than to the screen. Employ pipes to use the output of one command as the the input of another. Use the find and xargs commands to search for and operate on groups of files. 1. Peek: Ch 5 2. Venkateshmurthy, Ch. 4 3. Redirection and Pipes 4. Commands That Launch Other Commands 5. See website for assignment. 3 Program Development in Text-Mode 3.1 Compiling Objectives Upon completing this section, a student should be able to… Issue appropriate commands to compile simple C++, C, and Java programs. Issue the sequence of steps required to compile programs consisting multiple compilation units. Capture lengthy lists of error messages for later examination. 1. Compiling and Executing Programs 2. Dealing with Error Messages 3. See website for assignment. 3.2 Project Management (make) Objectives Upon completing this section, a student should be able to… Use the ’make` program to automate a series of project build steps. Write make files describing the automation of a typical programming project. 1. Project Management with Make 2. See website for assignment. 3. Compiling in Editors 4 Working in Graphics Mode 4.1 The X Window System Objectives Upon completing this section, a student should be able to… Launch a remote graphics-based session using a compressed X protocol (X2Go). Launch xterms and other X-based programs for operation from their own PC. Discuss the relative merits of the gedit, emacs, and vim editors in a graphics-mode session. 1. Peek: Ch 7 2. The X Window System 3. Editing under X 4. Troubleshooting X 5. See website for assignment. 4.2 Program Development: IDEs Objectives Upon completing this section, a student should be able to… Identify the components comprising a typical IDE. Employ the IDEs available on the CS Linux servers (emacs, Code::Blocks, and Eclipse) to create and compile C++ programs. 1. IDEs for Compiling under X 2. See website for assignment. 4.3 Debugging Objectives Upon completing this section, a student should be able to… Understand the value and basic operations of an automated debugger. Employ a debugger to step through code set breakpoints examine the values of program variables examine the call stack Perform each of the above operations in nemiver, Code::Blocks, and `Eclipse. 1. Debugging 2. Debugging under X 3. See website for assignment. 5 Scripting 5.1 Environment Variables Objectives Upon completing this section, a student should be able to… Understand how environment variables affect shell commands. Set and examine environment variables. Use backticks to capture command output in an environment variable. Understand the role of the PATH variable. 1. Tansley, ch 16-18, 20 2. Shore Are a Lot of Shells! 3. Shell and Environment Variables 4. Customizing Your Unix Environment 5.2 Shell Scripts Objectives Upon completing this section, a student should be able to… Understand the concept of a script. Write simple scripts. Use control-flow features of the scripting language to modify the order in which script commands are issued.
Recommended publications
  • Curriculum Vitae
    Vancouver, BC Canada +1.604.551.7988 KipWarner [email protected] Senior Software Engineer / Co-chairman OPMLWG 07 August 2021 *** WARNING: MANGLED TEXT COPY. DOWNLOAD PDF: www.thevertigo.com/getcv.php?fix Education 2007 Artificial Intelligence, BSc (Cognitive Systems: Computational Intelligence & Design) Department of Computer Science, University of British Columbia 2005 Associate of General Science Kwantlen Polytechnic University Professional Experience Jul 2015 - Cartesian Theatre, Vancouver, British Columbia Present Senior Software Engineer Techniques: Artificial intelligence, asymmetric cryptography, build automation, continuous integration testing, digital signal processing, machine learning, MapReduce, REST architecture, SIMD, and UNIX server daemon. Technologies: AltiVec / POWER Vector Media Extension; Apport; Assembly; AVX, Autopkgtest; Avahi / Apple’s Bonjour; Bash; C++17; CppUnit; cwrap (nss_wrapper); DBus; debhelper; GCC; GDB; Git; GNU Autotools; GNU/Linux; init.d; libav / FFmpeg; lsbinit; M4; OpenBMC; OpenSSL; Pistache; pkg-config; PortAudio; PostgreSQL; PPA; Python; QEMU; quilt; sbuild / pbuilder; setuptools; SQLite; STL; strace; systemd; Swagger; Umbrello; and Valgrind. Standards: Debian Configuration Management Specification; Debian Database Application Policy; Debian Policy Manual; Debian Python Policy; DEP-8; Filesystem Hierarchy Standard; freedesktop.org; GNU Coding Standards; IEEE 754; JSON; LSB; OpenAPI Specification; POSIX; RFC 4180; RSA; SQL; UNIX System V; UML; UPnP; and Zeroconf. Hardware: Ported to 64-bit PC
    [Show full text]
  • Indicators for Missing Maintainership in Collaborative Open Source Projects
    TECHNISCHE UNIVERSITÄT CAROLO-WILHELMINA ZU BRAUNSCHWEIG Studienarbeit Indicators for Missing Maintainership in Collaborative Open Source Projects Andre Klapper February 04, 2013 Institute of Software Engineering and Automotive Informatics Prof. Dr.-Ing. Ina Schaefer Supervisor: Michael Dukaczewski Affidavit Hereby I, Andre Klapper, declare that I wrote the present thesis without any assis- tance from third parties and without any sources than those indicated in the thesis itself. Braunschweig / Prague, February 04, 2013 Abstract The thesis provides an attempt to use freely accessible metadata in order to identify missing maintainership in free and open source software projects by querying various data sources and rating the gathered information. GNOME and Apache are used as case studies. License This work is licensed under a Creative Commons Attribution-ShareAlike 3.0 Unported (CC BY-SA 3.0) license. Keywords Maintenance, Activity, Open Source, Free Software, Metrics, Metadata, DOAP Contents List of Tablesx 1 Introduction1 1.1 Problem and Motivation.........................1 1.2 Objective.................................2 1.3 Outline...................................3 2 Theoretical Background4 2.1 Reasons for Inactivity..........................4 2.2 Problems Caused by Inactivity......................4 2.3 Ways to Pass Maintainership.......................5 3 Data Sources in Projects7 3.1 Identification and Accessibility......................7 3.2 Potential Sources and their Exploitability................7 3.2.1 Code Repositories.........................8 3.2.2 Mailing Lists...........................9 3.2.3 IRC Chat.............................9 3.2.4 Wikis............................... 10 3.2.5 Issue Tracking Systems...................... 11 3.2.6 Forums............................... 12 3.2.7 Releases.............................. 12 3.2.8 Patch Review........................... 13 3.2.9 Social Media............................ 13 3.2.10 Other Sources..........................
    [Show full text]
  • Pipenightdreams Osgcal-Doc Mumudvb Mpg123-Alsa Tbb
    pipenightdreams osgcal-doc mumudvb mpg123-alsa tbb-examples libgammu4-dbg gcc-4.1-doc snort-rules-default davical cutmp3 libevolution5.0-cil aspell-am python-gobject-doc openoffice.org-l10n-mn libc6-xen xserver-xorg trophy-data t38modem pioneers-console libnb-platform10-java libgtkglext1-ruby libboost-wave1.39-dev drgenius bfbtester libchromexvmcpro1 isdnutils-xtools ubuntuone-client openoffice.org2-math openoffice.org-l10n-lt lsb-cxx-ia32 kdeartwork-emoticons-kde4 wmpuzzle trafshow python-plplot lx-gdb link-monitor-applet libscm-dev liblog-agent-logger-perl libccrtp-doc libclass-throwable-perl kde-i18n-csb jack-jconv hamradio-menus coinor-libvol-doc msx-emulator bitbake nabi language-pack-gnome-zh libpaperg popularity-contest xracer-tools xfont-nexus opendrim-lmp-baseserver libvorbisfile-ruby liblinebreak-doc libgfcui-2.0-0c2a-dbg libblacs-mpi-dev dict-freedict-spa-eng blender-ogrexml aspell-da x11-apps openoffice.org-l10n-lv openoffice.org-l10n-nl pnmtopng libodbcinstq1 libhsqldb-java-doc libmono-addins-gui0.2-cil sg3-utils linux-backports-modules-alsa-2.6.31-19-generic yorick-yeti-gsl python-pymssql plasma-widget-cpuload mcpp gpsim-lcd cl-csv libhtml-clean-perl asterisk-dbg apt-dater-dbg libgnome-mag1-dev language-pack-gnome-yo python-crypto svn-autoreleasedeb sugar-terminal-activity mii-diag maria-doc libplexus-component-api-java-doc libhugs-hgl-bundled libchipcard-libgwenhywfar47-plugins libghc6-random-dev freefem3d ezmlm cakephp-scripts aspell-ar ara-byte not+sparc openoffice.org-l10n-nn linux-backports-modules-karmic-generic-pae
    [Show full text]
  • GNOME Annual Report 2008
    1 Table of Contents Foreword Letter from the Executive Director 4 A year in review GNOME in 2008 8 GNOME Mobile 16 Events and Community initiatives Interview with Willie Walker 20 GNOME around the world 24 GNOME Foundation Foundation Finances 30 List of all 2008 donors 33 2 Letter from Stormy Peters Stormy Peters is the GNOME Foundation Executive Director and has great experience in the industry and with the open source culture. Hello GNOME Lovers! seek them out and to invite them to come play. (Actually, I felt welcome from day -1, GNOME's goal is to bring free and open as I met a bunch of guys on the plane who source computing to everyone regardless of turned out to also be going to GUADEC. I ability. I consider myself extremely lucky to spent my first day in Copenhagen walking have joined the project as executive director around with some guys from Red Hat and of the GNOME Foundation. It's a pleasure Eazel trying to stay awake through jetlag. I and a privilege to work with thousands of pe- remember Havoc Pennington saying we just ople dedicated to making free had to stay awake until dinner software available for everyone The spirit and time.) on desktops and mobile plat- dedication of the forms. I don't think it's an GNOME community to One of the most common exaggeration to say that their goals of creating questions I get asked is GNOME technology is chan- a free and open source why did you take this job? ging the world for many from software ..
    [Show full text]
  • Omnet++ Installation Guide Version 4.6 Copyright © 2014 András Varga and Opensim Ltd
    OMNeT++ Installation Guide Version 4.6 Copyright © 2014 András Varga and OpenSim Ltd. Table of Contents 1. General Information ........................................................................................... 1 2. Windows ............................................................................................................. 2 3. Mac OS X ........................................................................................................... 6 4. Linux ................................................................................................................ 12 5. Ubuntu ............................................................................................................. 18 6. Fedora 18 ......................................................................................................... 22 7. Red Hat ............................................................................................................ 24 8. OpenSUSE ....................................................................................................... 26 9. Generic Unix .................................................................................................... 28 10. Build Options ................................................................................................. 35 iii Chapter 1. General Information 1.1. Introduction This document describes how to install OMNeT++ on various platforms. One chapter is dedicated to each operating system. 1.2. Supported Platforms OMNeT++ has been tested and is supported on the
    [Show full text]
  • CSE 303 Lecture 13A
    CSE 303 Lecture 13a Debugging C programs reading: Programming in C Ch. 13 slides created by Marty Stepp http://www.cs.washington.edu/303/ 1 gdb • gdb : GNU debugger. Helps you step through C programs. absolutely essential for fixing crashes and bad pointer code your program must have been compiled with the -g flag • usage: $ gdb program GNU gdb Fedora (6.8-23.fc9) Copyright (C) 2008 Free Software Foundation, Inc... (gdb) run parameters ... • redirecting input: $ gdb program (gdb) run parameters < inputfile 2 gdb commands command description run or r parameters run the program break or b place sets a breakpoint at the given place: - a function's name - a line number - a source file : line number print or p expression prints the given value / variable step or s advances by one line of code ("step into") next or n advances by one line of code ("step over") finish runs until end of function ("step out") continue or c resumes running program backtrace or bt display current function call stack quit or q exits gdb 3 A gdb session $ gdb intstack GNU gdb 5.2.1 Copyright 2002 Free Software Foundation, Inc. (gdb) b 34 Breakpoint 1 at 0x4010ea: file intstack.c, line 34. (gdb) r Starting program: /home/user/intstack Breakpoint 1, main () at intstack.c:34 34 Node* oldFront = stack; (gdb) p stack $1 = (Node *) 0x4619c0 (gdb) n 35 printf("%d\n", stack->data); (gdb) n 36 stack = stack->next; (gdb) n 37 free(oldFront); (gdb) p stack $4 = (Node *) 0x462856 (gdb) p oldFront $2 = (Node *) 0x4619c0 (gdb) p *oldFront $3 = {data = 10, next = 0x462856} (gdb) c Continuing.
    [Show full text]
  • GUADEC Schedule.Pdf
    1 Contents About the event ......................................................................................................................... 5 Map of the location............................................................................................................................................................. 5 Welcome to GUADEC!................................................................................................................. 6 The G !ME !pen Des"top Da#............................................................................................... $ Main t%ac" sche&ule................................................................................................................... ' We&nes&a# ('th )ul#.......................................................................................................................................................... ' Thurs&a# 29th )ul#............................................................................................................................................................... * +ri&a# ,-th )ul#.................................................................................................................................................................... 10 Abst%acts..................................................................................................................................... 1( G OME, the /eb. an& +ree&om................................................................................................................................
    [Show full text]
  • L'écosystème Du Libre
    L’écosystème du Libre: interactions entre projets amonts, distributions et utilisateurs - l’exemple de Debian et Ubuntu Lucas Nussbaum Rencontres Mondiales du Logiciel Libre 2009 Thème Développement Lucas Nussbaum L’écosystème du Libre 1 / 23 Le Logiciel Libre aujourd’hui Lucas Nussbaum L’écosystème du Libre 2 / 23 Le Logiciel Libre aujourd’hui Ubuntu Lucas Nussbaum L’écosystème du Libre 2 / 23 Objectifs de cette présentation Présenter les différents acteurs du développement de logiciels libres Expliquer les interactions entre ces acteurs En particulier : interactions autour de/entre Debian et Ubuntu Lucas Nussbaum L’écosystème du Libre 3 / 23 Les Utilisateurs Objectif : utiliser les logiciels pour produire quelque chose Besoins : Logiciels faciles d’accès et à utiliser Logiciels correspondant à leurs besoins Logiciels fonctionnant correctement Utilité pour la communauté : Remontée de problèmes ou de besoins supplémentaires Vie de la communauté : Support d’autres utilisateurs Buzz ... Lucas Nussbaum L’écosystème du Libre 4 / 23 Les distributions Tentent de fournir aux utilisateurs tous les logiciels correspondant à leurs besoins Standardisent : La manière d’accéder aux logiciels (paquets) La qualité des logiciels La manière de remonter des problèmes Principales tâches : Uniformisation de logiciels d’origines diverses Intégration Gestion de branches "stables" Lucas Nussbaum L’écosystème du Libre 5 / 23 Les projets amonts Développent réellement les logiciels Objectif : meilleur logiciel possible Dans sa branche de développement Grande diversité
    [Show full text]
  • ANNUAL REPORT 2010-2011 Table of Contents
    ANNUAL REPORT 2010-2011 Table of contents Foreword Letter from the GNOME Foundation Executive Director 4 GNOME 3 A review of the GNOME 3 Platform 5 The way to GNOME 3 and the future 7 Words about GNOME 3 8 Two years in review International events 9 Hackfests 11 Interview with the Thank You pants winners 13 GNOME Outreach Program for Women 15 Google Summer of Code 19 GNOME User Groups 21 Foundation development GNOME Foundation financial overview 22 GNOME Advisory Board 23 Friends of GNOME donors 25 3 Letter from the GNOME Foundation Executive Director The publication date of this biannual report is roughly one year from when I started as Executive Director of the GNOME Foundation. Most of the period it covers is before I joined, and a discussion of the accomplishments of this period needs a big acknowledgement and thank you to the folks that drove the organization during this time. In fact, it's because of the amazing work that you'll read about in this report that I knew it was the right decision to come and work for GNOME. During the first part of this time, Stormy Peters held the role of Executive Director and worked hard to steer the Foundation. I personally have learned a great deal from her and I think the organization benefited greatly from her dedication and hard work! The second­most significant period of time represented in this report was the ten month period after Stormy left the GNOME Foundation but before I was hired. During this time, all of the affairs and activities of the GNOME community and Foundation were steered by volunteers.
    [Show full text]
  • Herramientas Computacionales En Linux
    Herramientas Computacionales en Linux Antonio Carrillo Ledesma y Karla Ivonne González Rosas Facultad de Ciencias, UNAM http://academicos.fciencias.unam.mx/antoniocarrillo Una copia de este trabajo se puede descargar de la página: http://132.248.182.159/acl/hcl/ http://132.248.182.159/acl/Textos/ Con…namiento 2020, Versión 1.0 1 1El presente trabajo está licenciado bajo un esquema Creative Commons Atribución CompartirIgual (CC-BY-SA) 4.0 Internacional. Los textos que compo- nen el presente trabajo se publican bajo formas de licenciamiento que permiten la copia, la redistribución y la realización de obras derivadas siempre y cuando éstas se distribuyan bajo las mismas licencias libres y se cite la fuente. ¡Copiaeste libro! ... Compartir no es delito. Herramientas Computacionales en Linux Índice 1 Introducción 5 2 Sistemas Operativos 12 2.1 Windows .............................. 14 2.2 Mac OS .............................. 15 2.3 Android .............................. 17 2.4 Linux ............................... 20 2.5 Chrome OS y las Chromebook .................. 27 2.6 Otros ................................ 30 3 Trabajando con Debian GNU/Linux y sus Derivados 32 3.1 Sistema de Archivos y Estructura de Directorios ........ 32 3.2 Trabajando en Línea de Comandos ............... 37 3.3 Cómo buscar archivos ....................... 59 3.4 Monitorear el Desempeño .................... 66 3.5 Compresores y Descompresores de Archivos .......... 69 3.6 Copiar Archivos entre Equipos .................. 75 3.7 Interprete de Órdenes de Consola BASH ............ 78 3.8 Desde la Nube ........................... 86 4 Otras Herramientas en Línea de Comandos 91 4.1 Prompt de la Línea de Comandos ................ 91 4.2 Historia de Comados ....................... 96 4.3 Alias a Comandos ......................... 97 4.4 Ayuda de Comandos y Tipo de Archivos ...........
    [Show full text]
  • El Cómputo En Los Cursos De La Facultad De Ciencias, UNAM
    El Cómputo en los Cursos de la Facultad de Ciencias, UNAM Antonio Carrillo Ledesma y Karla Ivonne González Rosas Facultad de Ciencias, UNAM http://academicos.fciencias.unam.mx/antoniocarrillo Una copia de este trabajo se puede descargar de la página: https://sites.google.com/ciencias.unam.mx/acl/en-desarrollo Con…namiento 2020-2021, Versión 1.0 1 1El presente trabajo está licenciado bajo un esquema Creative Commons Atribución CompartirIgual (CC-BY-SA) 4.0 Internacional. Los textos que compo- nen el presente trabajo se publican bajo formas de licenciamiento que permiten la copia, la redistribución y la realización de obras derivadas siempre y cuando éstas se distribuyan bajo las mismas licencias libres y se cite la fuente. ¡Copiaeste libro! ... Compartir no es delito. El Cómputo en los Cursos de la Facultad de Ciencias, UNAM Índice 1 Introducción 7 1.1 Software Propietario y Libre ................... 7 1.1.1 Software Propietario ................... 8 1.1.2 Software Libre ....................... 9 1.2 El Cómputo en las Carreras de Ciencias ............ 11 1.2.1 Algunos Cursos que Usan Cómputo ........... 14 1.3 Paquetes de Cómputo de Uso Común .............. 17 1.3.1 Sistemas Operativos ................... 21 1.3.2 Paquetes de Cálculo Numérico .............. 21 1.3.3 Paquetes de Cálculo Simbólico .............. 22 1.3.4 Paquetes Estadísticos ................... 23 1.3.5 Paquetes O…máticos ................... 24 1.3.6 Lenguajes de Programación y Entornos de Desarrollo . 24 1.3.7 Otros Programas de Cómputo .............. 24 1.4 Sobre los Ejemplos de este Trabajo ............... 25 1.5 Agradecimientos .......................... 25 2 Sistemas Operativos 26 2.1 Windows .............................
    [Show full text]
  • Developer Switch Dreams Crafting the GNOME DX
    Developer Switch Dreams Crafting the GNOME DX Christian Hergert ([email protected]) GNOME is so much more than a desktop What is GNOME? ● Compositor (Mutter, Shell ● !ro"ect with stron# desi#n ethic ($%, Hi# ● 'ile Manager (Nautilus, Sushi ● Hardware ()stractions (*luetooth, Network, Disk, Media, !ower, +nput ● Graphics ,oolkits (Gtk+, Clutter, St ● Lan#uage Enablement (GO)"ect, !ython, JavaScript, 1ala, !erl, Mono What is GNOME? (Continued ● Content Storage and E2ctraction (Tracker, Gom ● !ersonal Data Management (E-D-S, Calendar, Notes, Tasks, ,odo ● (pplication Suite (Evolution, Gnumeric, GIMP, Gedit ● We) *rowser (Epiphan/, We)4itGtk) ● +!C (D3*us/kd)us, G1ariant, Gsettin#s ● Media 'ramework (GStreamer, pulseaudio, rygel ● ,ranslations (damned lies, #translator) ● (rtwork (backgrounds, icono#raph/ What is GNOME? (Continued ● Security (!olic/4it, lock screen, li)secret, seahorse, sand)o2in# ● Communications (Telepathy, 6arstream, empathy ● System Setup/Con7# (+nitial Setup, Control Center) ● 'ile 'ormats (li)2ml8, documents, "son, markdown, (SN9:, desktop ● Standards (wmspec, trash, mime, icons, thum)nail, sounds, recent 7les ● Documentation (yelp/mallard, #tk-doc, #uides5turorials What is GNOME? (Continued ● Developer Tools (#lade, #it#, #li), devhelp, #edit, an"uta, Nemiver, *uilder, *o2es, #he2, s/spro6, terminal, #tk-doc, yelp, d36eet, lookin# #lass, #parted, meld, mempro6, vala) GNOME is a massive achievement *ut there is an elephant in the GN$5room +t;s reall/ hard to contri)ute to 'ree So6tware So + did some research on wh/
    [Show full text]