DOCSLIB.ORG

Kulkarni [email protected] Rackspace, the University of Texas at Austin

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Kulkarni Devdattakulkarni@Gmail.Com Rackspace, the University of Texas at Austin Provenance Issues in Platform-as-a-Service Model of Cloud Computing Devdatta Kulkarni [email protected] Rackspace, The University of Texas at Austin Abstract manages complete life-cycle of an application. In or- der for application developers to gain confidence into the In this paper we present provenance issues that arise in platform and to gain insights into application construc- building Platform-as-a-Service (PaaS) model of cloud tion process, it is important that the platform collects computing. The issues are related to designing, build- different kinds of provenance information and makes it ing, and deploying of the platform itself, and those re- available to application developers. Additionally, prove- lated to building and deploying applications on the plat- nance information about the platform itself is useful for form. These include, tracking of commands for success- the platform developers and platform operators towards ful software installations, tracking of inter-service de- correct design and operation of the platform. pendencies, tracking of configuration parameters for dif- In this paper we identify different kinds of provenance ferent services, and tracking of application related arti- information that need to be collected within a PaaS to facts. We identify the provenance information to address provide better insights into the workings of the plat- these issues and propose mechanisms to track it. form and the applications that it deploys (Section 2). We also propose mechanisms to collect this informa- 1 Introduction tion (Section 3). We realized the importance of some of these through our experience of building Solum, which is Platform-as-a-Service (PaaS) model of cloud computing an application life-cycle management system for Open- simplifies deployment of applications to a cloud infras- Stack [6]. Application developers use declarative speci- tructure. Application developers use a declarative model fication model to specify application’s build and runtime for specifying their application’s source code and re- requirements to Solum. Solum builds and deploys the quirements to the platform. The platform builds and de- application by creating Docker containers [7] with the ploys the application by provisioning the required infras- application code, hence forth referred as docker contain- tructure resources. There are several such PaaS systems ers, and deploying them on OpenStack infrastructure. in existence today, such as Heroku [1], Google App En- gine [2], OpenShift [3], Solum [4]. 2 Provenance Issues Provenance has emerged as one of the key requirement in building modern systems that support properties such 2.1 Platform development as auditability and data lineage tracking [5]. In our view provenance is all the information about an entity that can While developing Solum, we frequently followed a pat- help towards understanding how that entity got to a par- tern of trial and exploration when it came to using new ticular state. For instance, when a software is success- softwares and tools, such as the docker registry [8], fully installed on a Ubuntu host, all the packages that which we use for storing application’s docker containers. had to be installed towards that are part of that software’s The typical pattern that we followed was as follows. We provenance. Another example is that of a service which referred to several on-line documents, we installed dif- depends on other services for its correct functioning. The ferent softwares and packages, changed file permissions dependency information, such as the versions of the de- if required, changed directories, compiled/built certain pendent services, are part of that service’s provenance. packages, and so on until we were successful. In a PaaS system, the need to track provenance infor- At the end when the required software/package was mation is especially important given that the platform installed successfully, we wanted to consolidate the ex- act steps that we could follow if we had to install that ters for other services matter, for Solum to function cor- software on a different host in the future. However, at rectly in the devstack environment, following variables this point we generally faced a problem. From the entire need to be set in Nova’s [15] configuration file: sched- shell command history, it was difficult to find out only uler default filter, memory, compute driver. We propose those commands which were essential towards success- in subsection 3.3 how we can use provenance of config- ful installation of that software. We felt that we needed uration parameters towards enabling choosing of appro- an automated way which, given a list of commands, will priate configuration parameters of dependent services for find out the exact commands that are necessary and suffi- the purpose of design and development of Solum. cient for installing that software. Essentially, we needed the provenance for software installs (subsection 3.1). 2.4 Application provenance We observe that the trial and exploration pattern is not unique to design and development of Solum. It is quite Within Solum, application construction and deploy- general and can be seen to be followed by developers in ment information includes, commit hash of application’s trying to install any new software. source code deployed by the platform, test and run com- mands used in building particular version of the appli- 2.2 Platform building cation, version of docker used to build the application runtime environment, and versions of dependent services Solum depends on other OpenStack services such as used. All this information is part of the application con- Keystone [9], Glance [10], Heat [11], Barbican [12], struction and deployment provenance. Tempest [13]. Often times these services change their requirements, or undergo a refactoring change, which 3 Provenance Mechanisms causes Solum to break. For example, recently the tem- pest functional testing library re-factored its code to 3.1 Command list provenance move its REST module from its package to a separate li- brary. This caused all the functional tests in Solum to In order to find the provenance for successfully installing stop working as the import path of the REST module a software we need to consider the list of commands within Solum’s functional tests was no longer correct. that eventually led to a successful installation. An en- Such a breakage results in wasted developer productiv- tire history of user’s shell interactions contains differ- ity. It also leads to wasted resources in terms of testing ent kinds of commands, such as package installation failures and backups on the OpenStack’s continuous inte- commands (apt-get install), navigational commands (cd, gration servers (CI servers). The problem is exacerbated pushd, popd), listing/viewing commands (ls, less, more), if a service has had several commits. For developers of editor commands (opening files in vi, emacs), service a service like Solum, it is currently very tedious to find start up commands (service docker start), and so on. Be- out which commit in the dependent service broke their low we propose a method which, given a list of com- build. We felt that the severity of this issue could be re- mands and the name of the software to install, prunes duced if could have information about the last commit the command list to the essential commands required for of the dependent service that worked for Solum. Then installing the software. the problem would be constrained to finding the culprit The main issues that need to be addressed in design- commit between the last known working commit and the ing this method are: (a) detecting where to start and stop latest commit. Essentially, we needed to maintain prove- in user’s command history, and (b) determining whether nance information related to inter-service dependencies the candidate list of commands is complete. To address (subsection 3.2). the issue of where to start and stop in a long execution history we define the notion of an anchor point (ap) 2.3 Platform deployment command. Example of an anchor point command on Ubuntu is apt-get update. The reason this command can Each OpenStack service has large number of configura- be treated as an anchor point is because in our experi- tion parameters. It is hard for developers of a service like ence, updating packages on the host is a typical usage Solum, which depends on other services, to know the pa- pattern when trying to install new software on Ubuntu rameters from dependent services that are critical to the hosts. The anchor point commands may also be speci- operation of their service. We have faced this issue sev- fied by users. Moreover, instead of considering the entire eral times in the devstack [14] setup of OpenStack, which command history to build the candidate list, we can use supports running all the OpenStack services within a sin- the last command that led to successfully starting up of gle VM, typically for the purpose of design and devel- the service as another anchor point. Lets call this as the opment. As an example of how configuration parame- last successful command (lsc). To address the issue of 2 how to find out whether the candidate list of commands fore this commit. Below we propose two approaches that is complete, we propose that we need to try out that com- can help with this process. mand list in an automated manner in a contained envi- ronment. Our idea for this is to build a docker container 3.2.1 Dependent services’ commits tracking consisting of the list of candidate commands and check it with a verification script provided by the application One way to find the commit(s) to pin to is to maintain developer which checks whether that software was cor- provenance information about Solum that includes the rectly installed on the container or not.
Load more

Recommended publications
  • Extended Picodos Reference Manual
    Extended PicoDOS® Reference Manual SCHOOL OF OCEANOGRAPHY and APPLIED PHYSICS LABORATORY UNIVERSITY OF WASHINGTON v66.06 July 2009 Chapter 1 Introduction and Conventions 1.1 Introduction This manual is a reference to extensions to the PicoDOS® operating system command set implemented in the Seaglider operating code. PicoDOS® is a registered trademark of Persistor Instruments, Inc., Bourne MA, USA. The version number of this document coincides with the version of the main Seaglider operating code in which these extensions exist. These extensions either make new functions available from the PicoDOS® prompt, or extend the capabilities of existing functions. Commands are only available through the Seaglider operating code, which intercepts and interprets the commands, passing them to PicoDOS® as appropriate. While in this mode, the Seaglider code passes any command not explicitly recognized as an extended PicoDOS® command on to PicoDOS® itself for execution. Limited error reporting exists in this case. The extensions are accessible at the PicoDOS® prompt available from the main menu when connected directly to a Seaglider (exceptions as noted below), or by uploading the pdoscmds.bat file when the Seaglider is operating autonomously. In the former case, the Seaglider code displays a standard PicoDOS® prompt (picoDOS>) with an extra ' >', as follows. picoDOS>> In the latter case, results of the extended PicoDOS® commands are captured to a file and transferred to the Seaglider basestation (in compressed form, named sg0055pz.000, using "0055" as a placeholder for dive number, and "000" for increment number) following execution of the commands. The basestation renames this file per the p1230055.000.pdos convention.
    [Show full text]
  • Digital Backend Software Command Set – Ver
    DBE Memo#12.1 Mark 5 Memo #090.1 MASSACHUSETTS INSTITUTE OF TECHNOLOGY HAYSTACK OBSERVATORY WESTFORD, MASSACHUSETTS 01886 5 June, 2012 Telephone: 781-981-5951 Fax: 781-981-0590 TO: Distribution FROM: Chester Ruszczyk, Mikael Taveniku SUBJECT: Digital Backend Software Command Set – Ver. 1.2 1. Introduction This document describes the command set that the program to be used as the primary software interface on the second generation VLBI digital backends must support. This program will be the command and control interface for the embedded device. The name of the application is rdbe_server, for DBE command and control server daemon, where RDBE refers to the ROACH Digital Backend. The standard method of communication with the application will be via a TCP connection to port 5000 via the standard 10/100/1000 Mbps Ethernet interface. Multiple simultaneously connections, up to a maximum supplied by a command line argument, are allowed, with commands and queries being executed in the order received, regardless of their origin. The VSI-S specification defines the syntax of communication into and out of the RDBE. 2. Notes on RDBE Command Set Note the following with respect to the command set: 1. All of the commands/queries expect the VSI-S communications protocol and command/response syntax. 2. Commands/queries are case insensitive. RDBE COMMAND SET – Ver.1.2 1 3. VSI-S Command, Query and Response Syntax The following explanation of the VSI-S syntax may be useful in understanding the structure of commands, queries, and their respective responses. This explanation has been lifted directly from the VSI-S specification.
    [Show full text]
  • The Linux Command Line
    The Linux Command Line Second Internet Edition William E. Shotts, Jr. A LinuxCommand.org Book Copyright ©2008-2013, William E. Shotts, Jr. This work is licensed under the Creative Commons Attribution-Noncommercial-No De- rivative Works 3.0 United States License. To view a copy of this license, visit the link above or send a letter to Creative Commons, 171 Second Street, Suite 300, San Fran- cisco, California, 94105, USA. Linux® is the registered trademark of Linus Torvalds. All other trademarks belong to their respective owners. This book is part of the LinuxCommand.org project, a site for Linux education and advo- cacy devoted to helping users of legacy operating systems migrate into the future. You may contact the LinuxCommand.org project at http://linuxcommand.org. This book is also available in printed form, published by No Starch Press and may be purchased wherever fine books are sold. No Starch Press also offers this book in elec- tronic formats for most popular e-readers: http://nostarch.com/tlcl.htm Release History Version Date Description 13.07 July 6, 2013 Second Internet Edition. 09.12 December 14, 2009 First Internet Edition. 09.11 November 19, 2009 Fourth draft with almost all reviewer feedback incorporated and edited through chapter 37. 09.10 October 3, 2009 Third draft with revised table formatting, partial application of reviewers feedback and edited through chapter 18. 09.08 August 12, 2009 Second draft incorporating the first editing pass. 09.07 July 18, 2009 Completed first draft. Table of Contents Introduction....................................................................................................xvi
    [Show full text]
  • The Steps for Updating the 2488
    The Steps for Updating the 2488 Updating the 2488 is a unidirectional upgrade. You will not be able to downgrade to the previous version. Before proceeding, backup your data to CD or to your computer. Step 1: Burn your Disc Image. For Roxio Easy CD Creator 1) Open Roxio Easy CD Creator. 2) Select CREATE DATA CD from the menu. 3) Under FILE, select CREATE CD FROM IMAGE… 4) In the Files of Type window, choose “ISO IMAGE FILES (*.iso)” 5) Browse to the location of the downloaded image file. 6) Select the file “2488vxxx.iso "(version of the file you are updating to) and click OPEN. For Nero 1) Go to Recorder from the top menu and select “BURN IMAGE”. 2) Browse to the location of the downloaded image file. 3) Select the file “2488vxxx.iso“ and hit OPEN. 4) At the Burn Compilation Window, select BURN. For Mac OSX Panther 1) Go to your Disk Utility located in Hard Disk/Applications/Utilities. 2) From the Image menu at the top of the screen, select BURN. 3) Browse to the location of the downloaded image file. 4) Select the file “2488vxxx.iso “ and hit OPEN. For Mac OSX Jaguar 1) Go to your Disk Copy located in Hard Disk/Applications/Utilities. 2) Under the File Menu at the top of the page select “BURN IMAGE”. For Toast Titanium 6 1) Open Toast and select COPY from the Main Menu. 2) Click on IMAGE FILE. 3) Drag the downloaded 2488vxxx.iso file into Toast. 4) Click on the RED BUTTON at the bottom right of the window.
    [Show full text]
  • Database Administration - System Management User's Guide
    Oracle® Communications EAGLE Database Administration - System Management User's Guide Release 46.7 E97336 Revision 1 December 2018 Oracle Communications EAGLE Database Administration - System Management User's Guide, Release 46.7 E97336 Revision 1 Copyright © 1993, 2018, Oracle and/or its affiliates. All rights reserved. This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited. The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing. If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, then the following notice is applicable: U.S. GOVERNMENT END USERS: Oracle programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, delivered to U.S. Government end users are "commercial computer software" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, shall be subject to license terms and license restrictions applicable to the programs.
    [Show full text]
  • Introduction: DOS (Disk Operating System) Is an Oldest Type of Operating System
    DOS (Disk Operating System) 1 Introduction: DOS (Disk Operating System) is an oldest type of Operating System. Disk Operating System is abbreviated as DOS. DOS is a CUI type of Operating System. In computer science, a generic term describing any operating system is system software which is loaded from disk devices when the system is started or rebooted. DOS is a single-tasking, single-user operating system with a command-line interface. DOS acts on commands. Because DOS is ready to perform when given proper command hence, it is also known as Command Prompt. Commands are certain words of English language or short form of English words. The meaning of these word or short form is already known to DOS. Since, DOS recognized these words and hence acts accordingly. These words and short forms of the English words are better known as commands. Internal Command:-Those commands which are already stored in the “Command.Com” file of DOS are known as internal commands. For example, CLS, VOL, TIME, DATE, COPY etc External Command:-Those commands which are not included in the command.com file of DOS rather included in other files of DOS are known as external commands. It is formatted according to programme. For example, TREE, FORMAT, MODE etc Some Internal Commands:- 1. CLS To clear the screen. \>cls 2. DIR To view the directory and files C:\>Dir 3. DATE To View and change the date C:\>Date Current date is: 01-01-2008 Enter new date (mm/dd/yy):21-03-2009 4. TIME To view and change the time.
    [Show full text]
  • EPSON RC+ 5.0 (Ver.5.4) User's Guide Rev.3 I
    EPSON RC+ 5.0 Ver.5.4 User's Guide Project Management and Development Rev.3 EM11ZS2266F EPSON RC+ 5.0 (Ver.5.4) User's Guide 5.0 (Ver.5.4) User's Guide EPSON RC+ and Project Management Development Rev.3 EPSON RC+ 5.0 (Ver.5.4) User's Guide Rev.3 Copyright © 2011 SEIKO EPSON CORPORATION. All rights reserved. EPSON RC+ 5.0 (Ver.5.4) User's Guide Rev.3 i FOREWORD Thank you for purchasing our robot products. This manual contains the information necessary for the correct use of the Manipulator. Please carefully read this manual and other related manuals before installing the robot system. Keep this manual handy for easy access at all times. WARRANTY The robot and its optional parts are shipped to our customers only after being subjected to the strictest quality controls, tests, and inspections to certify its compliance with our high performance standards. Product malfunctions resulting from normal handling or operation will be repaired free of charge during the normal warranty period. (Please ask your Regional Sales Office for warranty period information.) However, customers will be charged for repairs in the following cases (even if they occur during the warranty period): 1. Damage or malfunction caused by improper use which is not described in the manual, or careless use. 2. Malfunctions caused by customers’ unauthorized disassembly. 3. Damage due to improper adjustments or unauthorized repair attempts. 4. Damage caused by natural disasters such as earthquake, flood, etc. Warnings, Cautions, Usage: 1. If the robot or associated equipment is used outside of the usage conditions and product specifications described in the manuals, this warranty is void.
    [Show full text]
  • MS-DOS Microsoft Disk Operating System
    emeronbEnßm MS-DOS Microsoft Disk Operating System 1-esckþIepþIm kñúgEpñkenH eyIgelIkykmkEtEpñkRKwHmYycMnUYn énRbB½n§tMeNIrkar edIm,IgayRsYl kñúgkar EsVgyl; MS-DOS nig eRbIR)as;bBa¢a rbs; . EtmunnwgsikSaeTAelIRbB½n§tMeNIrkar Gñk (Commad) DOS MS-DOS RtUvEsVgyl;eGay)anc,as;GMBIGVI ehAfa nig kñúg sin . File, Directory Directory Structure Windows - KWCasMnMuénÉksarEdlpÞúkenAelIépÞ rbs; ehIyvamaneQµaHtMNag nig File Media Disk TItaMgc,as;las;mYy . GacCakmµviFI Éksar b¤ File (Program), (Document) Collection of Data . .doc icon Extension Filename - KWCaTU b¤ CaftsMrab;pÞúkral; eTAtamRbePT gayRsYlcMnaM nig Directory or Folder Files EbgEck ehIyenAkñúg mYyGacmanftsMrab;pÞúkral; CaeRcInteTot ehAfa Directory Files Subdirectory or . Subfolder eTAkan; Path File POD.EXE 2-RbB½n§tMeNIrkarsMrab; IBM-PC kñúgEpñkenHeyIgnwgsikSa Cak;EsþgGMBI EdlCaRbePTkmµviFImYycMa)ac; CaTIbMput sMrab;RbePT DOS IBM-PC bc©úb,nñenH . mann½yfaenAmanRbB½n§tMeNIrkarepSg²CaeRcIneTot dUcCa sMrab;RbePT System Macintosh nigmanRbB½n§tMeNIrkar . UNIX,Windows ... RbB½n§tMeNIrkar KWCaRbB½n§kmµviFImYy eRbIsMrab;RtYtBinitüéntMeNIrkar RKb;RKgkarEbkEck (Operating System) nig eRbIR)as;épñkepSg² énma:sIundUcCa ryHeBlcaM)ac;sMrab; kareRbIR)as;én nwgk¾dUcCa CPU Memory bNþal]bkrN¾xageRkAepSg²eTot . 3- KWCaGVI DOS ? mkBIBaküfa mann½yfaCa RbB½n§tMeNIrkarrukrk nig eFVIkarelI DOS DISK OPERATING SYSTEM Disk (Harddisk or . vaCaRbB½n§RKb;RKg RKb;RKgÉksarenAelI dUcCakarcMlg lubnig karbegáIt Diskette) Disk Space Disk erobcMbegáIt b¤ .l. cUlGñkRsm½yemIlfaebIKµan RbB½n§tMeNIrkar Diectorys, Partition Track
    [Show full text]
  • SPEL+ Language Reference (Ver.4.2) Rev.3 I
    EPSON RC+ Ver.4.2 SPEL+ Language Reference Rev.3 EM086S1715F EPSON RC+ Ver.4.2 SPEL + Language Reference Rev.3 EPSON RC+ Ver.4.2 + SPEL Language Reference Rev.3 Copyright © 2007-2008 SEIKO EPSON CORPORATION. All rights reserved. SPEL+ Language Reference (Ver.4.2) Rev.3 i FOREWORD Thank you for purchasing our robot products. This manual contains the information necessary for the correct use of the EPSON RC+ software. Please carefully read this manual and other related manuals when using this software. Keep this manual in a handy location for easy access at all times. WARRANTY The robot and its optional parts are shipped to our customers only after being subjected to the strictest quality controls, tests and inspections to certify its compliance with our high performance standards. Product malfunctions resulting from normal handling or operation will be repaired free of charge during the normal warranty period. (Please ask your Regional Sales Office for warranty period information.) However, customers will be charged for repairs in the following cases (even if they occur during the warranty period): 1. Damage or malfunction caused by improper use which is not described in the manual, or careless use. 2. Malfunctions caused by customers’ unauthorized disassembly. 3. Damage due to improper adjustments or unauthorized repair attempts. 4. Damage caused by natural disasters such as earthquake, flood, etc. Warnings, Cautions, Usage: 1. If the robot or associated equipment is used outside of the usage conditions and product specifications described in the manuals, this warranty is void. 2. If you do not follow the WARNINGS and CAUTIONS in this manual, we cannot be responsible for any malfunction or accident, even if the result is injury or death.
    [Show full text]
  • Command Line Interface User's Guide for NEC Expressupdate [PDF]
    NEC ESMPRO Manager Ver.6 User's Guide Command Line Interface for NEC ExpressUpdate Chapter1 About Command Line Interface Chapter2 XML interface Chapter3 Component management Chapter4 Group management Chapter5 ExpressUpdate Chapter6 Log management Chapter7 Troubleshooting Chapter8 Terminology Chapter9 Appendix E6.53-01-STD © NEC Corporation 2021 Contents Contents ............................................................................................................................................................. 1 Trademarks ........................................................................................................................................................ 3 About This Document ....................................................................................................................................... 4 Chapter1 About Command Line Interface ................................................................................................... 5 1.1 Overview .......................................................................................................................................... 5 1.2 System Requirements ....................................................................................................................... 5 1.3 Configuring examples ....................................................................................................................... 6 1.4 Using the command line ..................................................................................................................
    [Show full text]
  • MCQ Questions from MS
    Multiple Choice Questions This PDF file is complementary study material of http://mcqsets.com for 5. Which command divides the surface of the blank the candidates of computer jobs examination. Please visit MCQ Sets for MCQ collections, Online Quiz, Class Notes, Old Question Papers & Model disk into sectors and assign a unique address to Question Sets. You are encouraged to send me the MCQ questions each one through http://mcqsets.com/contact/ or mail me at [email protected] a. Ver b. Format 1. In MS-Dos 6.22, which part identifies the c. Fat product uniquely? d. Chkdsk a. MS Correct Answer: b. Format b. DOS Explanation: Ver is used to display the version number of c. Ms-DOS DOS in use. Fat command does not exist and Chkdsk is to d. 6.22 check disk errors and fix it. Thus dividing surface into sectors is done by Format command. Correct Answer: d. 6.22 Explanation: MS stands for Microsoft, DOS is the name of operating system Disk Operating System, 6.22 is the version 6. Each time you turn on your computer, it will check number that identifies the product. on the control file a. Command.com, io.sys 2. In Ms-Dos what command you will use to display b. Command.com, date.com, dir.com system date? c. Command.com, io.sys, msdos.sys a. Date command d. Chkdsk.exe b. Ver command Correct Answer: c. command.com, io.sys, msdos.sys c. Disk command Explanation: command.com, io.sys and msdos.sys are the d.
    [Show full text]
  • Tutorial De Linux Comandos Básicos
    Tutorial de Linux Extraído de http://es.tldp.org/Tutoriales/CURSOLINUX/curso_linux/curso_linux.html Comandos básicos Los comandos son esencialmente los mismos que cualquier sistema UNIX. En la tablas que se presentan a continuación se tiene la lista de comandos mas frecuentes. Comando/Sintaxis Descripción Ejemplos cat fich1 [...fichN] Concatena y muestra un archivos cat /etc/passwd archivos cat dict1 dict2 dict cd [dir] Cambia de directorio cd /tmp chmod permisos fich Cambia los permisos de un archivo chmod +x miscript chown usuario:grupo Cambia el dueño un archivo chown nobody miscript fich cp fich1...fichN dir Copia archivos cp foo foo.backup Encuentra diferencia entre diff [-e]arch1 arch2 diff foo.c newfoo.c archivos du [-sabr] fich Reporta el tamaño del directorio du -s /home/ file arch Muestra el tipo de un archivo file arc_desconocido find . -name ``.bak'' – find dir test acción Encuentra archivos. print grep [-cilnv] expr Busca patrones en archivos grep mike /etc/passwd archivos head -count fich Muestra el inicio de un archivo head prog1.c mkdir dir Crea un directorio. mkdir temp Mueve un archivo(s) a un mv fich1 ...fichN dir mv a.out prog1 directorio mv fich1 fich2 Renombra un archivo. mv .c prog_dir Visualiza página a página un less / more fich(s) more muy_largo.c archivo. less acepta comandos vi. less muy_largo.c Crea un acceso directo a un ln -s /users/mike/.profile ln [-s] fich acceso archivo . ls Lista el contenido del directorio ls -l /usr/bin Muestra la ruta del directorio pwd Pwd actual rm fich Borra un fichero.
    [Show full text]