DOCSLIB.ORG

Modelsim SE User's Manual

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Modelsim SE User's Manual ModelSim® Advanced Verification and Debugging SE User’s Manual Version 6.0b Published: 15/Nov/04 UM-2 This document is for information and instruction purposes. Mentor Graphics reserves the right to make changes in specifications and other information contained in this publication without prior notice, and the reader should, in all cases, consult Mentor Graphics to determine whether any changes have been made. The terms and conditions governing the sale and licensing of Mentor Graphics products are set forth in written agreements between Mentor Graphics and its customers. No representation or other affirmation of fact contained in this publication shall be deemed to be a warranty or give rise to any liability of Mentor Graphics whatsoever. MENTOR GRAPHICS MAKES NO WARRANTY OF ANY KIND WITH REGARD TO THIS MATERIAL INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OR MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. MENTOR GRAPHICS SHALL NOT BE LIABLE FOR ANY INCIDENTAL, INDIRECT, SPECIAL, OR CONSEQUENTIAL DAMAGES WHATSOEVER (INCLUDING BUT NOT LIMITED TO LOST PROFITS) ARISING OUT OF OR RELATED TO THIS PUBLICATION OR THE INFORMATION CONTAINED IN IT, EVEN IF MENTOR GRAPHICS CORPORATION HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. RESTRICTED RIGHTS LEGEND 03/97 U.S. Government Restricted Rights. The SOFTWARE and documentation have been developed entirely at private expense and are commercial computer software provided with restricted rights. Use, duplication or disclosure by the U.S. Government or a U.S. Government subcontractor is subject to the restrictions set forth in the license agreement provided with the software pursuant to DFARS 227.7202-3(a) or as set forth in subparagraph (c)(1) and (2) of the Commercial Computer Software - Restricted Rights clause at FAR 52.227-19, as applicable. Contractor/manufacturer is: Mentor Graphics Corporation 8005 S.W. Boeckman Road, Wilsonville, Oregon 97070-7777. This is an unpublished work of Mentor Graphics Corporation. Contacting ModelSim Support Telephone: 503.685.0820 Toll-Free Telephone: 877-744-6699 Website: www.model.com Support: www.model.com/support ModelSim SE User’s Manual UM-3 Table of Contents 1 - Introduction (UM-21) ModelSim tool structure and verification flow . UM-22 ModelSim simulation task overview . UM-23 Basic steps for simulation . UM-24 Step 1 - Collecting Files and Mapping Libraries . UM-24 Step 2 - Compiling the design with vlog/vcom/sccom . UM-25 Step 3 - Loading the design for simulation . UM-26 Step 4 - Simulating the design . UM-26 Step 5- Debugging the design . UM-26 ModelSim modes of operation . UM-27 Command-line mode . UM-27 Batch mode . UM-28 ModelSim graphic interface overview . UM-29 Standards supported . UM-30 Assumptions . UM-30 Sections in this document . UM-31 What is an "object" . UM-34 Text conventions . UM-34 Where to find our documentation . UM-35 Download a free PDF reader with Search . UM-35 Technical support and updates . UM-36 2 - Projects (UM-37) Introduction . UM-38 What are projects? . UM-38 What are the benefits of projects? . UM-38 Project conversion between versions . UM-39 Getting started with projects . UM-40 Step 1 — Creating a new project . UM-40 Step 2 — Adding items to the project . UM-41 Step 3 — Compiling the files . UM-43 Step 4 — Simulating a design . UM-44 Other basic project operations . UM-44 The Project tab . UM-45 Sorting the list . UM-45 Changing compile order . UM-46 Auto-generating compile order . UM-46 Grouping files . UM-47 Creating a Simulation Configuration . UM-48 Optimization Configurations . UM-49 ModelSim SE User’s Manual UM-4 Table of Contents Organizing projects with folders . UM-50 Adding a folder . UM-50 Specifying file properties and project settings . UM-52 File compilation properties . UM-52 Project settings . UM-54 Accessing projects from the command line . UM-55 3 - Design libraries (UM-57) Design library overview . UM-58 Design unit information . UM-58 Working library versus resource libraries . UM-58 Archives . UM-59 Working with design libraries . UM-60 Creating a library . UM-60 Managing library contents . UM-61 Assigning a logical name to a design library . UM-62 Moving a library . UM-63 Setting up libraries for group use . UM-63 Specifying the resource libraries . UM-64 Verilog resource libraries . UM-64 VHDL resource libraries . UM-64 Predefined libraries . UM-64 Alternate IEEE libraries supplied . UM-65 Rebuilding supplied libraries . UM-65 Regenerating your design libraries . UM-66 Maintaining 32-bit and 64-bit versions in the same library . UM-66 Referencing source files with location maps . UM-67 Using location mapping . UM-67 Pathname syntax . UM-68 How location mapping works . UM-68 Mapping with Tcl variables . UM-68 Importing FPGA libraries . UM-69 Protecting source code using -nodebug . UM-70 4 - VHDL simulation (UM-71) Compiling VHDL files . UM-73 Creating a design library . UM-73 Invoking the VHDL compiler . UM-73 Dependency checking . UM-73 Range and index checking . UM-74 Subprogram inlining . UM-74 Differences between language versions . UM-75 Simulating VHDL designs . UM-78 Simulator resolution limit . UM-78 Default binding . UM-79 ModelSim SE User’s Manual UM-5 Delta delays . UM-80 Simulating with an elaboration file . UM-82 Overview . UM-82 Elaboration file flow . UM-82 Creating an elaboration file . UM-83 Loading an elaboration file . UM-83 Modifying stimulus . UM-84 Using with the PLI or FLI . UM-84 Syntax . UM-84 Example . UM-85 Checkpointing and restoring simulations . UM-86 Checkpoint file contents . UM-86 Controlling checkpoint file compression . UM-87 The difference between checkpoint/restore and restart . UM-87 Using macros with restart and checkpoint/restore . UM-87 Using the TextIO package . UM-88 Syntax for file declaration . UM-88 Using STD_INPUT and STD_OUTPUT within ModelSim . UM-89 TextIO implementation issues . UM-90 Writing strings and aggregates . UM-90 Reading and writing hexadecimal numbers . UM-91 Dangling pointers . UM-91 The ENDLINE function . UM-91 The ENDFILE function . UM-91 Using alternative input/output files . UM-92 Flushing the TEXTIO buffer . UM-92 Providing stimulus . UM-92 VITAL specification and source code . UM-93 VITAL packages . ..
Load more

Recommended publications
  • Prostep Ivip CPO Statement Template
    CPO Statement of Mentor Graphics For Questa SIM Date: 17 June, 2015 CPO Statement of Mentor Graphics Following the prerequisites of ProSTEP iViP’s Code of PLM Openness (CPO) IT vendors shall determine and provide a list of their relevant products and the degree of fulfillment as a “CPO Statement” (cf. CPO Chapter 2.8). This CPO Statement refers to: Product Name Questa SIM Product Version Version 10 Contact Ellie Burns [email protected] This CPO Statement was created and published by Mentor Graphics in form of a self-assessment with regard to the CPO. Publication Date of this CPO Statement: 17 June 2015 Content 1 Executive Summary ______________________________________________________________________________ 2 2 Details of Self-Assessment ________________________________________________________________________ 3 2.1 CPO Chapter 2.1: Interoperability ________________________________________________________________ 3 2.2 CPO Chapter 2.2: Infrastructure _________________________________________________________________ 4 2.3 CPO Chapter 2.5: Standards ____________________________________________________________________ 4 2.4 CPO Chapter 2.6: Architecture __________________________________________________________________ 5 2.5 CPO Chapter 2.7: Partnership ___________________________________________________________________ 6 2.5.1 Data Generated by Users ___________________________________________________________________ 6 2.5.2 Partnership Models _______________________________________________________________________ 6 2.5.3 Support of
    [Show full text]
  • Powerpoint Template
    Accellera Overview February 27, 2017 Lu Dai | Accellera Chairman Welcome Agenda . About Accellera . Current news . Technical activities . IEEE collaboration 2 © 2017 Accellera Systems Initiative, Inc. February 2017 Accellera Systems Initiative Our Mission To provide a platform in which the electronics industry can collaborate to innovate and deliver global standards that improve design and verification productivity for electronics products. 3 © 2017 Accellera Systems Initiative, Inc. February 2017 Broad Industry Support Corporate Members 4 © 2017 Accellera Systems Initiative, Inc. February 2017 Broad Industry Support Associate Members 5 © 2017 Accellera Systems Initiative, Inc. February 2017 Global Presence SystemC Evolution Day DVCon Europe DVCon U.S. SystemC Japan Design Automation Conference DVCon China Verification & ESL Forum DVCon India 6 © 2017 Accellera Systems Initiative, Inc. February 2017 Agenda . About Accellera . Current news . Technical activities . IEEE collaboration 7 © 2017 Accellera Systems Initiative, Inc. February 2017 Accellera News . Standards - IEEE Approves UVM 1.2 as IEEE 1800.2-2017 - Accellera relicenses SystemC reference implementation under Apache 2.0 . Outreach - First DVCon China to be held April 19, 2017 - Get IEEE free standards program extended 10 years/10 standards . Awards - Thomas Alsop receives 2017 Technical Excellence Award for his leadership of the UVM Working Group - Shrenik Mehta receives 2016 Accellera Leadership Award for his role as Accellera chair from 2005-2010 8 © 2017 Accellera Systems Initiative, Inc. February 2017 DVCon – Global Presence 29th Annual DVCon U.S. 4th Annual DVCon Europe www.dvcon-us.org 4th Annual DVCon India www.dvcon-europe.org 1st DVCon China www.dvcon-india.org www.dvcon-china.org 9 © 2017 Accellera Systems Initiative, Inc.
    [Show full text]
  • Co-Simulation Between Cλash and Traditional Hdls
    MASTER THESIS CO-SIMULATION BETWEEN CλASH AND TRADITIONAL HDLS Author: John Verheij Faculty of Electrical Engineering, Mathematics and Computer Science (EEMCS) Computer Architecture for Embedded Systems (CAES) Exam committee: Dr. Ir. C.P.R. Baaij Dr. Ir. J. Kuper Dr. Ir. J.F. Broenink Ir. E. Molenkamp August 19, 2016 Abstract CλaSH is a functional hardware description language (HDL) developed at the CAES group of the University of Twente. CλaSH borrows both the syntax and semantics from the general-purpose functional programming language Haskell, meaning that circuit de- signers can define their circuits with regular Haskell syntax. CλaSH contains a compiler for compiling circuits to traditional hardware description languages, like VHDL, Verilog, and SystemVerilog. Currently, compiling to traditional HDLs is one-way, meaning that CλaSH has no simulation options with the traditional HDLs. Co-simulation could be used to simulate designs which are defined in multiple lan- guages. With co-simulation it should be possible to use CλaSH as a verification language (test-bench) for traditional HDLs. Furthermore, circuits defined in traditional HDLs, can be used and simulated within CλaSH. In this thesis, research is done on the co-simulation of CλaSH and traditional HDLs. Traditional hardware description languages are standardized and include an interface to communicate with foreign languages. This interface can be used to include foreign func- tions, or to make verification and co-simulation possible. Because CλaSH also has possibilities to communicate with foreign languages, through Haskell foreign function interface (FFI), it is possible to set up co-simulation. The Verilog Procedural Interface (VPI), as defined in the IEEE 1364 standard, is used to set-up the communication and to control a Verilog simulator.
    [Show full text]
  • Development of Systemc Modules from HDL for System-On-Chip Applications
    University of Tennessee, Knoxville TRACE: Tennessee Research and Creative Exchange Masters Theses Graduate School 8-2004 Development of SystemC Modules from HDL for System-on-Chip Applications Siddhartha Devalapalli University of Tennessee - Knoxville Follow this and additional works at: https://trace.tennessee.edu/utk_gradthes Part of the Electrical and Computer Engineering Commons Recommended Citation Devalapalli, Siddhartha, "Development of SystemC Modules from HDL for System-on-Chip Applications. " Master's Thesis, University of Tennessee, 2004. https://trace.tennessee.edu/utk_gradthes/2119 This Thesis is brought to you for free and open access by the Graduate School at TRACE: Tennessee Research and Creative Exchange. It has been accepted for inclusion in Masters Theses by an authorized administrator of TRACE: Tennessee Research and Creative Exchange. For more information, please contact [email protected]. To the Graduate Council: I am submitting herewith a thesis written by Siddhartha Devalapalli entitled "Development of SystemC Modules from HDL for System-on-Chip Applications." I have examined the final electronic copy of this thesis for form and content and recommend that it be accepted in partial fulfillment of the equirr ements for the degree of Master of Science, with a major in Electrical Engineering. Dr. Donald W. Bouldin, Major Professor We have read this thesis and recommend its acceptance: Dr. Gregory D. Peterson, Dr. Chandra Tan Accepted for the Council: Carolyn R. Hodges Vice Provost and Dean of the Graduate School (Original signatures are on file with official studentecor r ds.) To the Graduate Council: I am submitting herewith a thesis written by Siddhartha Devalapalli entitled "Development of SystemC Modules from HDL for System-on-Chip Applications".
    [Show full text]
  • Ebook - Informations About Operating Systems Version: August 15, 2006 | Download
    eBook - Informations about Operating Systems Version: August 15, 2006 | Download: www.operating-system.org AIX Internet: AIX AmigaOS Internet: AmigaOS AtheOS Internet: AtheOS BeIA Internet: BeIA BeOS Internet: BeOS BSDi Internet: BSDi CP/M Internet: CP/M Darwin Internet: Darwin EPOC Internet: EPOC FreeBSD Internet: FreeBSD HP-UX Internet: HP-UX Hurd Internet: Hurd Inferno Internet: Inferno IRIX Internet: IRIX JavaOS Internet: JavaOS LFS Internet: LFS Linspire Internet: Linspire Linux Internet: Linux MacOS Internet: MacOS Minix Internet: Minix MorphOS Internet: MorphOS MS-DOS Internet: MS-DOS MVS Internet: MVS NetBSD Internet: NetBSD NetWare Internet: NetWare Newdeal Internet: Newdeal NEXTSTEP Internet: NEXTSTEP OpenBSD Internet: OpenBSD OS/2 Internet: OS/2 Further operating systems Internet: Further operating systems PalmOS Internet: PalmOS Plan9 Internet: Plan9 QNX Internet: QNX RiscOS Internet: RiscOS Solaris Internet: Solaris SuSE Linux Internet: SuSE Linux Unicos Internet: Unicos Unix Internet: Unix Unixware Internet: Unixware Windows 2000 Internet: Windows 2000 Windows 3.11 Internet: Windows 3.11 Windows 95 Internet: Windows 95 Windows 98 Internet: Windows 98 Windows CE Internet: Windows CE Windows Family Internet: Windows Family Windows ME Internet: Windows ME Seite 1 von 138 eBook - Informations about Operating Systems Version: August 15, 2006 | Download: www.operating-system.org Windows NT 3.1 Internet: Windows NT 3.1 Windows NT 4.0 Internet: Windows NT 4.0 Windows Server 2003 Internet: Windows Server 2003 Windows Vista Internet: Windows Vista Windows XP Internet: Windows XP Apple - Company Internet: Apple - Company AT&T - Company Internet: AT&T - Company Be Inc. - Company Internet: Be Inc. - Company BSD Family Internet: BSD Family Cray Inc.
    [Show full text]
  • An Introduction to the X Window System Introduction to X's Anatomy
    An Introduction to the X Window System Robert Lupton This is a limited and partisan introduction to ‘The X Window System’, which is widely but improperly known as X-windows, specifically to version 11 (‘X11’). The intention of the X-project has been to provide ‘tools not rules’, which allows their basic system to appear in a very large number of confusing guises. This document assumes that you are using the configuration that I set up at Peyton Hall † There are helpful manual entries under X and Xserver, as well as for individual utilities such as xterm. You may need to add /usr/princeton/X11/man to your MANPATH to read the X manpages. This is the first draft of this document, so I’d be very grateful for any comments or criticisms. Introduction to X’s Anatomy X consists of three parts: The server The part that knows about the hardware and how to draw lines and write characters. The Clients Such things as terminal emulators, dvi previewers, and clocks and The Window Manager A programme which handles negotiations between the different clients as they fight for screen space, colours, and sunlight. Another fundamental X-concept is that of resources, which is how X describes any- thing that a client might want to specify; common examples would be fonts, colours (both foreground and background), and position on the screen. Keys X can, and usually does, use a number of special keys. You are familiar with the way that <shift>a and <ctrl>a are different from a; in X this sensitivity extends to things like mouse buttons that you might not normally think of as case-sensitive.
    [Show full text]
  • Modelsim SE Tutorial T-3
    ModelSim® SE Tutorial Version 5.6d Published: 6/Aug/02 The world’s most popular HDL simulator T-2 ModelSim /VHDL, ModelSim /VLOG, ModelSim /LNL, and ModelSim /PLUS are produced by Model Technology™ Incorporated. Unauthorized copying, duplication, or other reproduction is prohibited without the written consent of Model Technology. The information in this manual is subject to change without notice and does not represent a commitment on the part of Model Technology. The program described in this manual is furnished under a license agreement and may not be used or copied except in accordance with the terms of the agreement. The online documentation provided with this product may be printed by the end-user. The number of copies that may be printed is limited to the number of licenses purchased. ModelSim is a registered trademark and ChaseX and TraceX are trademarks of Model Technology Incorporated. Model Technology is a trademark of Mentor Graphics Corporation. PostScript is a registered trademark of Adobe Systems Incorporated. UNIX is a registered trademark of AT&T in the USA and other countries. FLEXlm is a trademark of Globetrotter Software, Inc. IBM, AT, and PC are registered trademarks, AIX and RISC System/6000 are trademarks of International Business Machines Corporation. Windows, Microsoft, and MS-DOS are registered trademarks of Microsoft Corporation. OSF/Motif is a trademark of the Open Software Foundation, Inc. in the USA and other countries. SPARC is a registered trademark and SPARCstation is a trademark of SPARC International, Inc. Sun Microsystems is a registered trademark, and Sun, SunOS and OpenWindows are trademarks of Sun Microsystems, Inc.
    [Show full text]
  • Tms320c3x Workstation Emulator Installation Guide
    TMS320C3x Workstation Emulator Installation Guide 1994 Microprocessor Development Systems Printed in U.S.A., December 1994 2617676-9741 revision A TMS320C3x Workstation Emulator Installation Guide SPRU130 December 1994 Printed on Recycled Paper IMPORTANT NOTICE Texas Instruments (TI) reserves the right to make changes to its products or to discontinue any semiconductor product or service without notice, and advises its customers to obtain the latest version of relevant information to verify, before placing orders, that the information being relied on is current. TI warrants performance of its semiconductor products and related software to the specifications applicable at the time of sale in accordance with TI’s standard warranty. Testing and other quality control techniques are utilized to the extent TI deems necessary to support this warranty. Specific testing of all parameters of each device is not necessarily performed, except those mandated by government requirements. Certain applications using semiconductor products may involve potential risks of death, personal injury, or severe property or environmental damage (“Critical Applications”). TI SEMICONDUCTOR PRODUCTS ARE NOT DESIGNED, INTENDED, AUTHORIZED, OR WARRANTED TO BE SUITABLE FOR USE IN LIFE-SUPPORT APPLICATIONS, DEVICES OR SYSTEMS OR OTHER CRITICAL APPLICATIONS. Inclusion of TI products in such applications is understood to be fully at the risk of the customer. Use of TI products in such applications requires the written approval of an appropriate TI officer. Questions concerning potential risk applications should be directed to TI through a local SC sales offices. In order to minimize risks associated with the customer’s applications, adequate design and operating safeguards should be provided by the customer to minimize inherent or procedural hazards.
    [Show full text]
  • Installation Guide Meeting Maker
    Enterprise Scheduling & Calendaring Meeting Maker Installation Guide 010-MAN-0560 Copyright © 1999 by ON Technology Corporation. All rights reserved worldwide. Second Printing: June 1999 Information in this document is subject to change without notice and does not represent a commitment on the part of ON Technology. The software described in this document is furnished under a license agreement and may be used only in accordance with that agreement. This document has been provided pursuant to an agreement containing restrictions on its use. This document is also protected by federal copyright law. No part of this document may be reproduced or distributed, transcribed, stored in a retrieval system, translated into any spoken or computer language or transmitted in any form or by any means whatsoever without the prior written consent of: ON Technology Corporation One Cambridge Center Cambridge, MA 02142 USA Telephone: (617) 374 1400 Fax: (617) 374 1433 ON Technology makes no warranty, representation or promise not expressly set forth in this agreement. ON Technology disclaims and excludes any and all implied warranties of merchantability, title, or fitness for a particular purpose. ON Technology does not warrant that the software or documentation will satisfy your requirements or that the software and documentation are without defect or error or that the operation of the software will be uninterrupted. LIMITATION OF LIABILITY: ON Technology's aggregate liability, as well as that of the authors of programs sold by ON Technology, arising from or relating to this agreement or the software or documentation is limited to the total of all payments made by or for you for the license.
    [Show full text]
  • UNIVERSITY of CALIFORNIA RIVERSIDE Emulation of Systemc
    UNIVERSITY OF CALIFORNIA RIVERSIDE Emulation of SystemC Applications for Portable FPGA Binaries A Dissertation submitted in partial satisfaction of the requirements for the degree of Doctor of Philosophy in Computer Science by Scott Spencer Sirowy June 2010 Dissertation Committee: Dr. Frank Vahid, Chairperson Dr. Tony Givargis Dr. Sheldon X.-D. Tan Copyright by Scott Spencer Sirowy 2010 The Dissertation of Scott Spencer Sirowy is approved: Committee Chairperson University of California, Riverside ABSTRACT OF THE DISSERTATION Emulation of SystemC Applications for Portable FPGA Binaries by Scott Spencer Sirowy Doctor of Philosophy, Graduate Program in Computer Science University of California, Riverside, June 2010 Dr. Frank Vahid, Chairperson As FPGAs become more common in mainstream general-purpose computing platforms, capturing and distributing high-performance implementations of applications on FPGAs will become increasingly important. Even in the presence of C-based synthesis tools for FPGAs, designers continue to implement applications as circuits, due in large part to allow for capture of clever spatial, circuit-level implementation features leading to superior performance and efficiency. We demonstrate the feasibility of a spatial form of FPGA application capture that offers portability advantages for FPGA applications unseen with current FPGA binary formats. We demonstrate the portability of such a distribution by developing a fast on-chip emulation framework that performs transparent optimizations, allowing spatially-captured FPGA applications to immediately run on FPGA platforms without costly and hard-to-use synthesis/mapping tool flows, and sometimes faster than PC-based execution. We develop several dynamic and transparent optimization techniques, including just-in-time compilation , bytecode acceleration , and just-in-time synthesis that take advantage of a platform’s available resources, resulting in iv orders of magnitude performance improvement over normal emulation techniques and PC-based execution.
    [Show full text]
  • Installing Framemaker for UNIX®
    Adobe ® FrameMaker ® 7.0 Installing FrameMaker for UNIX® © 2002 Adobe Systems Incorporated and its licensors. All rights reserved. Installing Adobe FrameMaker for UNIX This manual, as well as the software described in it, is furnished under license and may be used or copied only in accordance with the terms of such license. The content of this manual is furnished for informational use only, is subject to change without notice, and should not be construed as a com- mitment by Adobe Systems Incorporated. Adobe Systems Incorporated assumes no responsibility or liability for any errors or inaccuracies that may appear in this book. Except as permitted by such license, no part of this publication may be reproduced, stored in a retrieval system, or transmitted, in any form or by any means, electronic, mechanical, recording, or otherwise, without the prior written permission of Adobe Systems Incorporated. Please remember that existing artwork or images that you may want to include in your project may be protected under copyright law. The unautho- rized incorporation of such material into your new work could be a violation of the rights of the copyright owner. Please be sure to obtain any per- mission required from the copyright owner. Any references to company names in sample templates are for demonstration purposes only and are not intended to refer to any actual organization. Adobe, the Adobe logo, Acrobat, Acrobat Reader, Adobe Type Manager, ATM, Display PostScript, Distiller, Exchange, FrameMaker, InstantView, Post- Script, and SuperATM are trademarks of Adobe Systems Incorporated. The following are copyrights of their respective companies or organizations: Portions reproduced with the permission of Apple Computer, Inc.
    [Show full text]
  • Administraci´On De Sistemas Unix
    ADMINISTRACION´ DE SISTEMAS UNIX Antonio Villal´onHuerta <[email protected]> Sergio Bayarri Gausi <[email protected]> Mayo, 2005 2 ´Indice General 1 Introducci´on:el superusuario 5 1.1 Conceptos b´asicospara administradores . 5 1.2 El entorno del superusuario . 5 1.3 El papel del administrador . 6 1.4 Comunicaci´oncon los usuarios. 7 2 Arranque y parada de m´aquina 11 2.1 Arranque del sistema . 11 2.2 Parada del sistema . 16 2.3 El int´erpretede ´ordenes . 16 3 Procesos 19 3.1 Conceptos b´asicos . 19 3.2 Actividades de los usuarios . 20 3.3 Control de procesos . 23 4 Sistemas de ficheros 27 4.1 Ficheros . 27 4.2 Sistemas de ficheros . 29 4.3 Creaci´one incorporaci´onde sistemas de ficheros . 30 4.4 Gesti´ondel espacio en disco . 31 4.5 Algunos sistemas de ficheros . 32 5 Tareas. Mantenimiento del sistema 35 5.1 Gesti´onde usuarios . 35 5.2 Automatizaci´onde tareas . 39 5.3 Actualizaci´one instalaci´onde paquetes software . 42 5.4 Copias de seguridad . 44 5.4.1 Consejos a considerar al realizar copias de seguridad . 45 5.4.2 Planificaci´onde un programa de copias de seguridad . 45 5.4.3 Realizaci´onde copias de seguridad y restauraci´onde archivos . 46 5.4.4 Ejemplo pr´actico:copia de seguridad del sistema . 51 5.4.5 Resumen . 52 5.5 Instalaci´onde la red . 52 5.5.1 Conceptos sobre redes . 52 5.5.2 Configuraci´onde la red . 55 5.5.3 Configuraci´onde servicios en Internet .
    [Show full text]