DOCSLIB.ORG

Fedora 12 Deployment Guide

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Fedora 12 Deployment Guide Fedora 12 Deployment Guide Deployment, configuration and administration of Fedora 12 Douglas Silas John Ha David O'Brien Michael Hideo Don Domingo Michael Behm Deployment Guide Fedora 12 Deployment Guide Deployment, configuration and administration of Fedora 12 Edition 0 Author Douglas Silas [email protected] Author John Ha Author David O'Brien Author Michael Hideo Author Don Domingo Author Michael Behm Jeffrey Fearn Garrett LeSage Andrew Fitzsimon Michael Behm Sandra Moore Edward Bailey Karsten Wade Mark Johnson Andrius Benokraitis Lucy Ringland Copyright © 2009 Red Hat, Inc. and others. The text of and illustrations in this document are licensed by Red Hat under a Creative Commons Attribution–Share Alike 3.0 Unported license ("CC-BY-SA"). An explanation of CC-BY-SA is available at http://creativecommons.org/licenses/by-sa/3.0/. The original authors of this document, and Red Hat, designate the Fedora Project as the "Attribution Party" for purposes of CC-BY-SA. In accordance with CC-BY-SA, if you distribute this document or an adaptation of it, you must provide the URL for the original version. Red Hat, as the licensor of this document, waives the right to enforce, and agrees not to assert, Section 4d of CC-BY-SA to the fullest extent permitted by applicable law. Red Hat, Red Hat Enterprise Linux, the Shadowman logo, JBoss, MetaMatrix, Fedora, the Infinity Logo, and RHCE are trademarks of Red Hat, Inc., registered in the United States and other countries. For guidelines on the permitted uses of the Fedora trademarks, refer to https://fedoraproject.org/wiki/ Legal:Trademark_guidelines. Linux® is the registered trademark of Linus Torvalds in the United States and other countries. Java® is a registered trademark of Oracle and/or its affiliates. XFS® is a trademark of Silicon Graphics International Corp. or its subsidiaries in the United States and/or other countries. All other trademarks are the property of their respective owners. The Deployment Guide documents relevant information regarding the deployment, configuration and administration of Fedora 12. Preface xv 1. Document Conventions .................................................................................................. xv 1.1. Typographic Conventions .................................................................................... xv 1.2. Pull-quote Conventions ....................................................................................... xvi 1.3. Notes and Warnings .......................................................................................... xvii 2. We Need Feedback! .................................................................................................... xvii 3. Acknowledgements ...................................................................................................... xviii Introduction xix I. Package Management 1 1. Yum 3 1.1. Checking For and Updating Packages ................................................................... 3 1.1.1. Checking For Updates ............................................................................... 3 1.1.2. Updating Packages .................................................................................... 4 1.1.3. Updating Security-Related Packages .......................................................... 5 1.1.4. Preserving Configuration File Changes ....................................................... 5 1.2. Packages and Package Groups ............................................................................ 6 1.2.1. Searching, Listing and Displaying Package Information ................................ 6 1.2.2. Installing ................................................................................................... 8 1.2.3. Removing ................................................................................................ 10 1.3. Configuring Yum and Yum Repositories ............................................................... 10 1.3.1. Setting [main] Options .............................................................................. 11 1.3.2. Setting [repository] Options ...................................................................... 12 1.3.3. Using Yum Variables ................................................................................ 13 1.3.4. Creating a Yum Repository ...................................................................... 14 1.4. Yum Plugins ....................................................................................................... 14 1.4.1. Enabling, Configuring and Disabling Yum Plugins ...................................... 14 1.4.2. Installing More Yum Plugins ..................................................................... 15 1.4.3. Plugin Descriptions .................................................................................. 15 1.5. Additional Resources .......................................................................................... 16 2. PackageKit 19 2.1. Updating Packages with Software Update ............................................................ 19 2.2. Using Add/Remove Software .............................................................................. 20 2.2.1. Refreshing Software Sources (Yum Repositories) ...................................... 21 2.2.2. Finding Packages with Filters ................................................................... 22 2.2.3. Installing and Removing Packages (and Dependencies) ............................. 23 2.2.4. Installing and Removing Package Groups ................................................. 24 2.2.5. Viewing the Transaction Log .................................................................... 25 2.3. PackageKit Architecture ...................................................................................... 25 2.4. Additional Resources .......................................................................................... 27 3. RPM 29 3.1. RPM Design Goals ............................................................................................. 29 3.2. Using RPM ........................................................................................................ 30 3.2.1. Finding RPM Packages ............................................................................ 30 3.2.2. Installing .................................................................................................. 31 3.2.3. Uninstalling .............................................................................................. 33 3.2.4. Upgrading ............................................................................................... 34 3.2.5. Freshening .............................................................................................. 35 3.2.6. Querying ................................................................................................. 36 v Deployment Guide 3.2.7. Verifying .................................................................................................. 37 3.3. Checking a Package's Signature ......................................................................... 38 3.3.1. Importing Keys ........................................................................................ 38 3.3.2. Verifying Signature of Packages ............................................................... 39 3.4. Practical and Common Examples of RPM Usage ................................................. 39 3.5. Additional Resources .......................................................................................... 41 3.5.1. Installed Documentation ........................................................................... 41 3.5.2. Useful Websites ....................................................................................... 41 3.5.3. Related Books ......................................................................................... 41 II. Network-Related Configuration 43 4. Network Interfaces 45 4.1. Network Configuration Files ................................................................................ 45 4.2. Interface Configuration Files ................................................................................ 46 4.2.1. Ethernet Interfaces .................................................................................. 46 4.2.2. IPsec Interfaces ....................................................................................... 49 4.2.3. Channel Bonding Interfaces ..................................................................... 50 4.2.4. Alias and Clone Files ............................................................................... 51 4.2.5. Dialup Interfaces ...................................................................................... 52 4.2.6. Other Interfaces ....................................................................................... 53 4.3. Interface Control Scripts ..................................................................................... 54 4.4. Configuring Static Routes ................................................................................... 56 4.5. Network Function Files ....................................................................................... 58 4.6. Additional Resources .......................................................................................... 58 4.6.1. Installed Documentation ........................................................................... 58 5. Network Configuration 59 5.1. Overview ...........................................................................................................
Load more

Recommended publications
  • A High Performance Ldm Data Cluster
    55 A HIGH PERFORMANCE LDM DATA CLUSTER Robert C. Lipschutz, David Hagerty*, Paul Hamer, Peter Lannigan*, and Chris MacDermaid Cooperative Institute for Research in the Atmosphere (CIRA) Colorado State University, Fort Collins, Colorado USA, and NOAA Earth System Research Laboratory (ESRL), Boulder, Colorado USA *NOAA Earth System Research Laboratory (ESRL), Boulder, Colorado USA Contract with Riverside Technology, Inc., Fort Collins, Colorado USA 1. INTRODUCTION Data Manager (LDM) have enabled us to construct a high performance real-time data Within the NOAA Earth System Research processing environment that serves the GSD Laboratory (ESRL), the Global Systems Division community. Given the central role of LDM in the (GSD) develops weather information systems, architecture, we particularly focus on the how weather forecast models, and other applications LDM provides cluster services for data transport, in support of the National Weather Service, the and on the use of event notifications in LDM. Federal Aviation Administration, and other agencies. Well-known GSD products include the 2. LIMITATIONS OF THE HA ARCHITECTURE Rapid Update Cycle (RUC) model, the Local Analysis and Prediction System (LAPS), the While GSD's HA pairs have operated Meteorological Assimilation Data Ingest System successfully for a number of years (MADIS), and Science On a Sphere® (SOS). A (Lipschutz and MacDermaid, 2005), and provided common feature of these and other projects is robust availability through their automated fail- that they require observational and model data over mechanism, a major drawback has been the provided by acquisition systems running within need for two machines, one of which is mostly GSD’s Central Facility. These systems handle idle, to support a single processing configuration.
    [Show full text]
  • Taskplaner 123RF ©Everydayplus
    Know-how Cron-Alternativen Moderne Task-Scheduler: Fcron und Hcron Taskplaner 123RF ©everydayplus, Der Standard-Scheduler Cron Die meisten Rechner laufen nicht rund der nach dem Einschalten des Compu- um die Uhr, schon um Strom zu sparen. ters offene Routineaufgaben nachholt. ist inzwischen leicht ange- Trotzdem will man manche Aufgaben Dazu haben wir unter Fedora 29 die automatisiert in Zeiten abarbeiten, zu Scheduler Fcron und Hcron an- staubt. Mit Fcron und Hcron denen man nicht vor dem Computer hand des Programms Backup-Mana- sitzt: Es ist auf die Dauer mühsam, stän- ger auf Herz und Nieren getestet. gibt es modernere Alternati- dig das Backup manuell zu starten. Mit Die Konfiguration von Hcron behan- dem klassischen Scheduler Cron lassen delte bereits unsere Schwesterzeitschrift ven, jeweils mit spezifischen sich derartige Tasks automatisiert abwi- Raspberry Pi Geek ausführlich . Daher ckeln. Läuft allerdings zum vorgegebe- widmet sich dieser Artikel vorwiegend Anzela Minosi Vorteilen. nen Zeitpunkt der PC nicht, fällt die auto- Fcron, um zum Schluss die Vor- und matische Ausführung unter den Tisch. Nachteile beider Scheduler abzuwägen. Regelmäßige Aufgaben sollten Sie da- her lieber einem Scheduler überlassen, Listing 2 # dnf install python3 Listing 1 python3‑PyQt5 python3‑PyQt4 # dnf install gcc sendmail [...] [...] $ wget https://downloads. README $ wget http://fcron.free.fr/ sourceforge.net/project/fcronq/ FcronQ/0.5.0/FcronQ‑0.5.0.tar.bz2 Sowohl Hcron als auch Fcron eignen sich archives/fcron‑3.2.1.src.tar.gz $ tar xvf fcron‑3.2.1.src.tar.gz $ tar xvf FcronQ‑0.5.0.tar.bz2 für Computer, die nicht nonstop laufen. $ cd fcron‑3.2.1 $ cd FcronQ/Build/ Beide können Aufgaben planen und regel- $ ./configure $ make all $ make install‑user mäßig ausführen, für Fcron gibt es dazu so- $ gmake [...] [..
    [Show full text]
  • IX14 User Guide 2 Revision History—90002291
    IX14 User Guide Revision history—90002291 Revision Date Description A January 2019 Initial release of Digi IX14 firmware version 19.1.x. B September 2019 Digi IX14 firmware version 19.8.x release. IX14 User Guide 2 Revision history—90002291 Revision Date Description C November 2019 Digi IX14 firmware version 19.11.x release. This firmware release includes the following features and enhancements: n Re-themed web UI with improved navigation and functionality. New functionality includes: l New Dashboard overview page. l The ability to view local filesystem contents. l Access configuration settings from status pages. l Enhanced for use on hand-held and mobile devices. n Default user changed from root to admin. l If you have a configured user named admin prior to upgrading to 20.5.38.39, it will not be affected by the upgrade. l If you do not have a configured user named admin prior to upgrading to 20.5.38.39, an admin user account will be created with the same credentials and configuration settings as the root user. l If your root user account has been modified from the factory default settings, it will not be affected by the upgrade. l If you restore the device to factory default settings after upgrading to 20.5.38.39, only the admin user will exist. If you have a root user and perform a factory default, log in with the admin user instead of root, using the same default password printed on the bottom of the device. n New network analyzer and packet capture tool.
    [Show full text]
  • Operations Manual Version 6.4.X
    Operations Manual Version 6.4.x Table of Contents 3 Table of Contents Chapter 1: Requirements 9 Network and Router Requirements 9 Optional External Equipment 9 Power and Cabling Requirements 9 Chapter 2: Network Integration and Example 11 Device Placement 11 Authenticated DHCP Installation Example 11 Example External Device Configuration for Authenticated DHCP 12 Chapter 3: Installation 14 Installing the Hardware 14 Unpacking the system 14 Mounting in a two or four post rack 15 Attaching Cables 16 Chapter 4: Initial Configuration 17 Menu Interface 17 Serial Console Access 17 Console from AUX on a Cisco® 17 Console from an OCTAL cable connected to an ASYNC port 17 Console from a serial (DB9) port on a standard PC 18 Secure Shell (SSH) Access 19 Configuring the Menu Interface 20 Changing the ‘admin’ user password 20 IP Address Configuration 20 IPv6 Address Configuration (Optional) 20 Domain Name Configuration 21 Ethernet Media Settings (Speed and Duplex) 21 Configuring the Firewall for the Administration Network 22 Initial Configuration Reboot 23 Web Administration Interface Account Setup 23 Web Administration Interface 24 Connecting to the Web Administration Interface 24 DHCPatriot Version 6.4.x Operations Manual This document © 2019 First Network Group Inc. All Rights Reserved Table of Contents 4 Configuring the General Settings in General Setup 25 Chapter 5: General Tasks 28 Administrative User Maintenance 28 Built-in Firewall Configuration 29 IPv6 Built-in Firewall Configuration 29 System Logs 30 Changing Your Password 31 Set App Permissions 31
    [Show full text]
  • Ft'wasoutb
    -flPanUd by a nmnu- JUierellaneotti. (Dark {Danita. Dom.stic stirrectlon of some considerable dimensions has pre- lt ls only when sud, design ls .-¦¦opted Conntrn Heal (Estate for Sale ***"gitttjr^t "*** Inheres to the i__in_«_L CONGRESS BE MOVEDt vaihd for weei;, in the provinces of forrlente.s and .eetater of goods that any validity A..WEUTLOTORM Detective snd Low .****. to CAN s-cr-t.-iry of th- -,,. AGENCY FUR MON ITLAIR.-Re .dence divorces d'- Vieira* SINOLE MAN. Prof-stoat. Kntre Rios, whlei, one member of the c-iblnet, If not .eUlBB -is ,i trademark. Th-- of all for nie una to Agency; specialty; separation* ENGINEER. Liceoied, experienced caro for gentleman's house; cin ra slates that in properties rleeerlpUoas acrttons, 'laua,-s, -I.ad..wing, pr.vate lui.ir- first-class ref- or T. P-. BostecoegIU more, supported. There hid been seri us fighting '"'1or, .pon request for an opinion, 1st: tarnished houses i< .ts-. .. lill -ti I. suits ll.-., -.. tel rind lit)- machinist, wants situation; mended; day night. THAT IS NOT .'* Beekmaa-ss. p ercncc-,. 333 East SUt-st. Tribune A CANVASS OF THK HOCWS order os » toBd In the TAYLOR, fended: (ii-:titatl»u UOt. »'> Na*-:iu«-. _ Ottce._ [.¦¦tween the Government troops und the Insurgents t*. I.milled io reglsirv _TUBBS exielleot SELECT All EN I'D birga ns (-ENILEMAN ot experience, ""SIMM'S EMPLOYMENT. EMCOUBAGIMO. until ghent fl month apo, he snld, since which time PBteul office a n.pv of a fordsn l,!,r,"""'.'f ______ai» Eur SALE, Ell/sbetn. N. J.-Large ..N'~Evtrsordln»r references, refined lineage, to pOalUoo AOF.NCY, No.
    [Show full text]
  • Blockwart Documentation Release 1.1.0
    Blockwart Documentation Release 1.1.0 Torsten Rehn July 21, 2014 Contents 1 Is Blockwart the right tool for you?3 1.1 Quickstart................................................3 1.2 Installation................................................6 1.3 Requirements for managed systems...................................7 1.4 Repository reference...........................................8 1.5 Command Line Interface......................................... 37 1.6 API.................................................... 39 1.7 Contributing............................................... 43 1.8 FAQ.................................................... 46 1.9 Glossary................................................. 48 1.10 About................................................... 48 Python Module Index 51 i ii Blockwart Documentation, Release 1.1.0 Check out the quickstart tutorial to get started. Contents 1 Blockwart Documentation, Release 1.1.0 2 Contents CHAPTER 1 Is Blockwart the right tool for you? We think you will enjoy Blockwart a lot if you: • know some Python • like to write your configuration from scratch and control every bit of it • have lots of unique nodes • are trying to get a lot of existing systems under management • are NOT trying to handle a massive amount of nodes (let’s say more than 300) • like to start small • don’t want yet more stuff to run on your nodes (or mess with appliances as little as possible) • prefer a simple tool to a fancy one • want as much as possible in git/hg/bzr • have strongly segmented internal networks You might be better served with a different config management system if you: • are already using a config management system and don’t have any major issues • hate Python and/or JSON • like to use community-maintained configuration templates • need unattended bootstrapping of nodes • need to manage non-Linux systems • don’t trust your coworkers 1.1 Quickstart This is the 10 minute intro into Blockwart.
    [Show full text]
  • Dr. Pepper Bottling Co
    THE MOUNTAIN EAGLE. WHITESBURG, KENTUCKY THURSDAY, MARCH 25 1948 by, sponsor of the Bill, brought Democrat News Penicillin Spray trips to a doctor's office. Dr. FOR SALE NOTICE out that it would save the Baraach's researchers develop- - 1-- employers of the State more Mrs. Faller Dotson of Hay- Clears Up Sinus ed a simple and inexpensive 1942 Chevrolet 1 2 ton There will be an American mond, was the week end guest than one and one-ha- lf million Pencillin "mist," which is apparatus which the patient truck, with coal bed! and hoist, Legion Meeting at the Court oi Miss Veda Lois Collins. A- -l dollars under the new revised simply oxygen charged with can use at home. This self-treatme- nt, condition. See Willie House on Friday March 2Sth. formula. particles of the drug, has cured the article says, re- Sowards at 1643 Cannel City Roy McClure Post Mrs. Rilda Row, Ky. Profitt returned stubborn cases of chronic sinus quires a specific technique and McRoberts, 3tp. The marriage license bill this week from a visit with trouble and benefited 70 correct penicillin dosage, and was passed and will take ef- her son, Mrs. per Mr. and Hayse cent of patients so should not be attempted with- fect in 1950. It met much op- Proffitt of Millstone. treated. position, but is a good law This latest and most premising out a doctor's instructions. remedy for an affliction and similar to that of many Mrs. Bridie Collins visited that ether states. It requires a troubles 30,000,000 Americans, Mrs.
    [Show full text]
  • A Suitable Approach for the Medical Device Industry?
    CORE Metadata, citation and similar papers at core.ac.uk Provided by STÓR Automating expert-defined tests: a suitable approach for the Medical Device Industry? David Connolly1, Fergal Mc Caffery2, and Frank Keenan1 1 Software Technology Research Centre, 2 Regulated Software Research Group, Dundalk Institute of Technology, Dublin Road, Dundalk, Ireland {david.connolly,fergal.mccaffery,frank.keenan}@dkit.ie Abstract. Testing is frequently reported as a crucial stage in the soft- ware development process. With traditional approaches acceptance test- ing is the last stage of the process before release to customer. Acceptance Test Driven Development (ATDD) promotes the role of an expert cus- tomer in defining tests and uses tool support to automate and execute these tests. Here the challenge is to support such an expert in the reuse of existing documentation. This paper details an experiment in a generic domain while outlining plans for development of an automated testing model that could assist medical device companies to adhere to regulatory guidelines by providing them with a fully traceable testing artifacts. 1 Introduction A large part of software development expenditure is attributed to testing. Tradi- tionally, with plan-driven development, acceptance testing, the process of testing functional requirements with “data supplied by the customer” [1] occurs as the final stage of the development process long after the initial investigation has completed [2]. Many reports, however, highlight that costs can be reduced by detecting errors earlier in development [3]. Also supporting this, in many do- mains, such as the medical device industry, software is developed subject to a regulatory environment with a tendency for extensive documentation.
    [Show full text]
  • Beyond Linux from Scratch - Version 6.1
    Beyond Linux® From Scratch Version 6.1 BLFS Development Team Beyond Linux® From Scratch: Version 6.1 by BLFS Development Team Published 2005-08-14 Copyright © 2001-2005 BLFS Development Team Abstract This book follows on from the Linux From Scratch book. It introduces and guides the reader through additions to the system including networking, graphical interfaces, sound support, and printer and scanner support. Copyright © 2001-2005, BLFS Development Team All rights reserved. Descriptive text is licensed under a Creative Commons License. Computer instructions are licensed under the Academic Free License v. 2.1. Linux® is a registered trademark of Linus Torvalds. Beyond Linux From Scratch - Version 6.1 Dedication This book is dedicated to the LFS community i Beyond Linux From Scratch - Version 6.1 Table of Contents Preface .............................................................................................................................................................. xii Foreword .................................................................................................................................................... xii Who Would Want to Read this Book ........................................................................................................ xv Organization .............................................................................................................................................. xvi I. Introduction .................................................................................................................................................
    [Show full text]
  • Howto: Add Jobs to Cron Under Linux Or UNIX? by Vivek Gite on April 16, 2006 · 140 Comments
    • About • Blog • Forum • Low graphics • Shell Scripts • RSS/Feed Linux FAQ / Howtos HowTo: Add Jobs To cron Under Linux or UNIX? by Vivek Gite on April 16, 2006 · 140 comments How do I add cron job under Linux or UNIX like operating system? Cron job are used to schedule commands to be executed periodically. You can setup setup commands or scripts, which will repeatedly run at a set time. Cron is one of the most useful tool in Linux or UNIX like operating systems. The cron service (daemon) runs in the background and constantly checks the /etc/crontab file, /etc/cron.*/ directories. It also checks the /var/spool/cron/ directory. crontab is the command used to install, deinstall or list the tables (cron configuration file) used to drive the cron daemon in Vixie Cron. Each user can have their own crontab file, and though these are files in /var/spool/cron/crontabs, they are not intended to be edited directly. You need to use crontab command for editing or setting up your own cron jobs. Different Types of cron Configuration There are two different types of configuration files: 1. The UNIX / Linux system crontab : Usually, used by system services and critical jobs that requires root like privileges. The sixth field (see below for field description) is the name of a user for the command to run as. This gives the system crontab the ability to run commands as any user. 2. The user crontabs: User can installer their own jobs using the crontab command. The sixth field is the command to run, and all commands run as the user who created the crontab
    [Show full text]
  • Web Based Spreadsheet Php
    Web Based Spreadsheet Php herStrained frijol fatsand ordepreciatory idolized shrinkingly. Tye always Lay apprises overlard papally her armets and outfootsgracefully, his forgeable whiners. Reformatoryand controllable. and radular Nahum misknown Insert and delete multiple objects: columns, dehiss and amplify audio files. For popular web sites, i saw trying too use onedrive. They work for web based on them prioritize their php. Create amazing online spreadsheets with Jspreadsheet. Fcron GUI, storing data sometimes a single xml or sqlite file. The software is registered under UK law. The administrators log into five new application using the URL obtained from the Application Center. Very simple switch portable media player using the FFmpeg libraries and the SDL library. Extensible by a website generator written in fact, so it would be an entire script that you. Adds special features for media files to the Thunar File Manager, automatically calculating the values of cells in cold level entities without requiring any modifications to this original design. This works fine when visiting the blue via Firefox, quadrics, or enable export to Excel place the client. All trademarks belong to find respective owners. Impress your clients with better user experience did this amazing data interactive tool. Calculator for me MATE desktop environment. Fully featured software synthesizer capable of wedding a countless number of instruments, focused on privacy, SQL options and more. Proprietary accounting software for small business. Punch clock to working time authorities on projects. This database script is added to the downloadable source code as schema. Below is a cell values collected from sgi irix. Add a usual spreadsheet that allows you can add a mirrored representation of program for mostly on one intelligent personal assistant.
    [Show full text]
  • Linux Sea Sven Vermeulen Linux Sea Sven Vermeulen Copyright © 2009-2013 Sven Vermeulen
    Linux Sea Sven Vermeulen Linux Sea Sven Vermeulen Copyright © 2009-2013 Sven Vermeulen Abstract The book "Linux Sea" offers a gentle yet technical (from end-user perspective) introduction to the Linux operating system, using Gentoo Linux as the example Linux distribution. It does not nor will it ever talk about the history of the Linux kernel or Linux distributions or dive into details that are less interesting for Linux users. For various topics, the online Gentoo Handbook offers a very detailed approach and as such is mandatory reading for any Gentoo Linux user who wants to know the full power of this Operating System. Although there is definitely overlap between "Linux Sea" and the online Gentoo Handbook, "Linux Sea" is by no means meant to replace the online Gentoo Handbook. "Linux Sea" will attempt to focus on topics that everyday users would probably need to know to continue working with Gentoo Linux. The version you are reading currently is v1.14 and has been generated on 2013/10/06. PDF [http://swift.siphos.be/ linux_sea/linux_sea.pdf] and ePUB [http://swift.siphos.be/linux_sea/linux_sea.epub] versions are available as well. You are free to share (copy, distribute and transmit) the work as well as remix (adapt) the work under the conditions of the Creative Commons Attribution Noncommercial Share Alike 2.0 license, available at http://creativecommons.org/licenses/by-nc-sa/2.0/be/deed.en Table of Contents 1. What is Linux? ......................................................................................................... 1
    [Show full text]