DOCSLIB.ORG

Linux-Server – Das Umfassende Handbuch 1.156 Seiten, Gebunden, 3

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Linux-Server – Das Umfassende Handbuch 1.156 Seiten, Gebunden, 3 Wissen, wie’s geht. Leseprobe Dieses Buch ist wie ein Schweizer Taschenmesser für den Linux-Admin: Für jede Herausforderung hat es eine Lösung. In dieser Leseprobe finden Sie alles Wichtige zum Bootloader GRUP, und Sie machen sich mit dem Paketmanagement vertraut. Außerdem können Sie einen Blick in das vollständige Inhalts- und Stichwortverzeichnis des Buches werfen. »Bootvorgang« »Paketmanagement« Inhalt Index Die Autoren Leseprobe weiterempfehlen Dirk Deimeke, Stefan Kania, Charly Kühnast, Daniel van Soest, Peer Heinlein Linux-Server – Das umfassende Handbuch 1.156 Seiten, gebunden, 3. Auflage 2014 49,90 Euro, ISBN 978-3-8362-3020-9 www.galileo-press.de/3685 Kapitel 2 2 Bootvorgang Der Startvorgang eines Linux-Systems ist die Basis dafür, überhaupt etwas mit dem System anfangen zu können. Wir geben einen Einblick in den Bootloader, die initiale Ramdisk und den Start mittels init-Skripten. Ein kurzer Blick auf »eventgesteuertes Starten« mittels »upstart« und »systemd« rundet dieses Kapitel ab. 2.1 Einführung Mit dem Bootloader wird das Betriebssystem gestartet. Nachdem das BIOS den mehr oder weniger ausführlichen Systemcheck durchgeführt hat, werden die Bootmedien in der Rei- henfolge der Präferenzen abgearbeitet. Wenn es zur Festplatte kommt, werden die ersten 512 Byte der Festplatte ausgewertet; in die- sen ist der Master Boot Record (MBR) zu finden. Von den 512 Byte sind die ersten 446 für den Bootloader reserviert. In diesem begrenzten Bereich lassen sich keine großen Programme unterbringen, daher wird der Bereich dafür genutzt, Code von anderer Stelle nachzuladen. Der frühere Linux Loader (LILO) ist heute kaum nach verbreitet, daher beschränken wir uns im Weiteren auf den Grand Unified Bootloader (GRUB) und die Weiterentwicklung GRUB 2. 2.2 Der Bootloader GRUB Man unterscheidet bei GRUB drei Stages. Die Hauptaufgabe der ersten Stufe – Stage 1 –liegt darin, die zweite Stufe – Stage 1.5 – zu laden. In dieser Stufe liegen die notwendigen Treiber zum Ansprechen des Dateisystems. Stage 1.5 fällt unterschiedlich aus, je nachdem welches Dateisystem verwendet wird. Zu finden ist diese ebenfalls sehr kleine Stufe zwischen dem Master Boot Record (MBR) und der ersten Partition. Bei der Installation von GRUB werden die benötigten Treiber festgestellt und entsprechend installiert. Sobald der Dateisystemtreiber verfügbar ist, kann mit dem »eigentlichen« Bootloader be- gonnen werden. Nach Laden dieser dritten Stufe – Stage 2 – wird von allen verwendeten Dis- tributionen ein Menü angezeigt, mit dem sie das zu startende Betriebssystem oder spezielle Optionen starten können, häufig ist eine Option zum Speichertesten oder ein failsafe-Modus auswählbar. Wenn Sie keine Option auswählen, wird das Standardbetriebssystem gestartet. 63 Deimeke/Heinlein/Kania/Kühnast/van Soest – Das Linux-Administrationshandbuch – Dritte Auflage – Sommer 2014 Galileo Press, ISBN: 978-3-8362-3020-9 Layout: gp.cls, Version 3.5.016 (27th June, 2014), (C) Dr. Daniel Lauer, Bonn Mit TEX bearbeitet am 12. September 2014, 10:47 Uhr Umlaut-Check: äöüÄÖÜ. Ligaturen: fl fi S. 63 Einstellungen: ohne Marginalien – ohne Seitenrand – mit Taben – mit Kapitel-Intro – extra breit – Zoom auf 100.0% Aktuelle Quelldatei: bootvorgang/bootvorgang , Aktueller Job: administration 2 Bootvorgang 2.2 Der Bootloader GRUB 2.2.1 Installation Check if this is correct or not. If any of the lines is incorrect, fix it and re-run the script 'grub-install'. 2 Die Installationsroutinen der Betriebssysteme installieren den Bootloader GRUB automa- (hd0) /dev/sda tisch vor Abschluss aller Installationsarbeiten. Im Normalfall müssen Sie keine Hand anle- Listing 2.2 Installation des »GRUB« auf älteren Systemen gen, es sei denn, Sie wollen spezielle Optionen setzen, einen Bootloader reparieren oder eine (defekte) Festplatte ersetzen. Statt des Skripts grub-install lässt sich die Arbeit auch direkt mit der GRUB-Shell ausführen. Der Standardweg, den Bootloader zu installieren, ist, grub-install zu verwenden. Dieses Sie wird mit grub aufgerufen und bietet eine große Anzahl an Kommandos, um GRUB auf Skript fasst die Befehle, die notwendig sind, einen Bootloader zu installieren, auf einfache Art vielfältige Weise zu konfigurieren. und Weise zusammen. Die Befehle müssten ansonsten manuell in der GRUB-Shell ausgeführt Wie Sie in Listing 2.1 gesehen haben, ließe sich der Befehl setup mit den notwendigen Pa- werden. Die Konfigurationsparameter werden in der Datei /etc/grub.conf gesucht. rametern auch von Hand ausführen. Alternativ dazu besteht aber auch die Möglichkeit, die Je nach Distribution werden leicht unterschiedliche Werkzeuge verwendet. Listing 2.1 zeigt Schritte kleiner zu wählen und mit root festzulegen, auf welcher Partition des Verzeichnis die Installation in SUSE Linux Enterprise Server (SLES) 11, openSUSE setzt in aktuellen Ver- boot liegt. Der Befehl setup schließlich schreibt die Informationen in den MBR. sionen auf GRUB 2. Um es dem Administrator nicht zu leicht zu machen, unterscheidet sich die zu verwendende sles:~ # grub-install Schreibweise von der sonst in Linux üblichen, was aber kein böser Wille ist. Zum Zeitpunkt GNU GRUB version 0.97 (640K lower / 3072K upper memory) des Systemstarts gibt es noch keine Verbindung zu den unter /dev beschriebenen Geräten und zu denen, die beim Starten des Systems gefunden wurden. So wird aus /dev/sda der [ Minimal BASH-like line editing is supported. For the first word, TAB Parameter (hd0), der die erste Festplatte im System meint. Weiterhin wird die erste Partition lists possible command completions. Anywhere else TAB lists the possible der ersten Festplatte nicht mit /dev/sda1 beschrieben, sondern mit (hd0,0). completions of a device/filename. ] grub> setup --stage2=/boot/grub/stage2 --force-lba (hd0,0) (hd0,0) In Listing 2.3 finden Sie ein Beispiel für die Arbeit mit der GRUB-Shell. Checking if "/boot/grub/stage1" exists... yes Bitte beachten Sie, dass die Zählung bei 0 beginnt und nicht bei 1, ebenfalls muss /boot sich Checking if "/boot/grub/stage2" exists... yes nicht zwangsläufig auf der gleichen Partition wie das root-Dateisystem unter / befinden. Checking if "/boot/grub/e2fs_stage1_5" exists... yes Running "embed /boot/grub/e2fs_stage1_5 (hd0,0)"... failed (this is not fatal) Viele Distributionen legen /boot auf eine eigene Partition mit dem Dateisystem ext2. Running "embed /boot/grub/e2fs_stage1_5 (hd0,0)"... failed (this is not fatal) sles:~ # grub Running "install --force-lba --stage2=/boot/grub/stage2 /boot/grub/stage1 (hd0,0) \ /boot/grub/stage2 p /boot/grub/menu.lst "... succeeded GNU GRUB version 0.97 (640K lower / 3072K upper memory) Done. grub> quit [ Minimal BASH-like line editing is supported. For the first word, TAB Listing 2.1 Installation des »GRUB« in SLES11 lists possible command completions. Anywhere else TAB lists the possible completions of a device/filename. ] Es müssen keine weiteren Eingaben vorgenommen werden, mit grub-install läuft der Rest automatisch. grub> root (hd0,0) Filesystem type is ext2fs, partition type 0x83 Bei älteren Linux-Distributionen benötigt grub-install das Device (die Festplatte), auf die der GRUB geschrieben werden soll, als Parameter, beispielsweise wie in Listing 2.2 gezeigt: grub> setup (hd0) root@debian:~# grub-install /dev/sda Checking if "/boot/grub/stage1" exists... yes Searching for GRUB installation directory ... found: /boot/grub Checking if "/boot/grub/stage2" exists... yes Installation finished. No error reported. Checking if "/boot/grub/e2fs_stage1_5" exists... yes This is the contents of the device map /boot/grub/device.map. Running "embed /boot/grub/e2fs_stage1_5 (hd0)"... 17 sectors are embedded. 64 65 Deimeke/Heinlein/Kania/Kühnast/van Soest – Das Linux-Administrationshandbuch – Dritte Auflage – Sommer 2014 Galileo Press, ISBN: 978-3-8362-3020-9 Deimeke/Heinlein/Kania/Kühnast/van Soest – Das Linux-Administrationshandbuch – Dritte Auflage – Sommer 2014 Galileo Press, ISBN: 978-3-8362-3020-9 Layout: gp.cls, Version 3.5.016 (27th June, 2014), (C) Dr. Daniel Lauer, Bonn Mit TEX bearbeitet am 12. September 2014, 10:47 Uhr Umlaut-Check: äöüÄÖÜ. Ligaturen: fl fi Layout: gp.cls, Version 3.5.016 (27th June, 2014), (C) Dr. Daniel Lauer, Bonn Mit TEX bearbeitet am 12. September 2014, 10:47 Uhr Umlaut-Check: äöüÄÖÜ. Ligaturen: fl fi S. 64 Einstellungen: ohne Marginalien – ohne Seitenrand – mit Taben – mit Kapitel-Intro – extra breit – Zoom auf 100.0% S. 65 Einstellungen: ohne Marginalien – ohne Seitenrand – mit Taben – mit Kapitel-Intro – extra breit – Zoom auf 100.0% Aktuelle Quelldatei: bootvorgang/bootvorgang , Aktueller Job: administration Aktuelle Quelldatei: bootvorgang/bootvorgang , Aktueller Job: administration 2 Bootvorgang 2.2 Der Bootloader GRUB succeeded root (hd0,0) Running "install /boot/grub/stage1 (hd0) (hd0)1+17 p (hd0,0)/boot/grub/stage2 \ kernel /vmlinuz-3.0.76-0.11-default root=/dev/system/root showopts ide=nodma \ 2 /boot/grub/menu.lst"... succeeded apm=off noresume edd=off powersaved=off nohz=off highres=off \ Done. processor.max_cstate=1 nomodeset x11failsafe initrd /initrd-3.0.76-0.11-default grub> quit Listing 2.3 »GRUB-Shell« auf SLES11 ###Don't change this comment - YaST2 identifier: Original name: floppy### title Floppy In der Datei /boot/grub/device.map finden sich die Informationen über Devices, auf die der rootnoverify (fd0) GRUB geschrieben werden kann, sie sieht wie in Listing 2.4 gezeigt aus. Sollten die Informa- chainloader +1 tionen veraltet oder falsch sein, können Sie die Datei bearbeiten oder löschen. Falls sie nicht Listing 2.5 Die Datei »/etc/grub/menu.lst«
Load more

Recommended publications
  • Creating Rpms Guide
    CREATING RPMS (Student version) v1.0 Featuring 36 pages of lecture and a 48 page lab exercise This docu m e n t serves two purpose s: 1. Representative sample to allow evaluation of our courseware manuals 2. Make available high quality RPM documentation to Linux administrators A bout this m aterial : The blue background you see simulates the custom paper that all Guru Labs course w are is printed on. This student version does not contain the instructor notes and teaching tips present in the instructor version. For more information on all the features of our unique layout, see: http://ww w . g urulabs.co m /courseware/course w are_layout.php For more freely available Guru Labs content (and the latest version of this file), see: http://www.gurulabs.co m/goodies/ This sample validated on: Red Hat Enterprise Linux 4 & Fedora Core v3 SUSE Linux Enterprise Server 9 & SUSE Linux Professional 9.2 About Guru Labs: Guru Labs is a Linux training company started in 199 9 by Linux experts to produce the best Linux training and course w are available. For a complete list, visit our website at: http://www.gurulabs.co m/ This work is copyrighted Guru Labs, L.C. 2005 and is licensed under the Creative Common s Attribution- NonCom mer cial- NoDerivs License. To view a copy of this license, visit http://creativecom m o n s.org/licenses/by- nc- nd/2.0/ or send a letter to Creative Commons, 559 Nathan Abbott Way, Stanford, California 943 0 5, USA. Guru Labs 801 N 500 W Ste 202 Bountiful, UT 84010 Ph: 801-298-5227 WWW.GURULABS.COM Objectives: • Understand
    [Show full text]
  • Redesigning Src2pkg, a Linux Package Creation Toolkit
    Redesigning src2pkg, a Linux package creation toolkit Timothy Goya December 4, 2009 Senior Project COMPUTER SCIENCE DEPARTMENT California Polytechnic State University San Luis Obispo 2009 1 Contents 1 Introduction 3 2 Background 4 2.1 GNU Coding Standards . 4 2.2 CheckInstall . 4 2.3 src2pkg 1.x . 4 3 Description 5 3.1 Flexibility and coupling . 5 3.2 A simple example script . 5 3.3 Other interesting functions . 6 3.4 Modules . 6 3.4.1 Build systems . 6 3.4.2 Sandboxing methods . 7 3.4.3 Package formats . 7 4 Evaluation 7 5 Really Cool Bash Features 8 5.1 /dev/tcp . 8 5.2 Manipulating Binary . 9 5.3 Localization . 9 6 Conclusions 9 2 Acknowledgments Many thanks to Dr. Phillip Nico for his saintly patience and understanding during his time as my senior project advisor. Special thanks to Gilbert Ashley, the author of src2pkg, for his approval and support throughout this redesign. Thanks to Piete Sartain for adminstrating the src2pkg wiki and Drew Ames for the writing much of the great documentation on the src2pkg wiki. I would also like to thank Dr. Alexander Dekhtyar for acting as my advisor for my rst senior project idea. Abstract Package managers ease installation and removal of applications. How- ever, as the name indicates, in order for a package manager to be useful, they need packages created from upstream sources to manage. This is the purpose of src2pkg, a toolkit written in Bash shell script which automates many package creation tasks. src2pkg, however, suers from major de- sign aws that cripple its ability to package some exotic upstream sources.
    [Show full text]
  • Checkinstall
    LinuxFocus article number 360 http://linuxfocus.org CheckInstall by Mario M. Knopf (homepage) About the author: Mario enjoys working with Linux, networks Abstract: and security related topics. Checkinstall is utility to automatically build RPM/Debian or Slackware packages from tar.gz source pages. This makes it possible to do a "clean" installation and de−installation of almost any source code tar.gz package. Translated to English _________________ _________________ _________________ by: Mario M. Knopf (homepage) Introduction It often happens that the program which one certainly would like to test, is only available as tar.gz source code (no rpm or Debian package available). In such a case, you download the source package, unpack it and compile it manually. So far, so good. However, what happens if you like to delete the program? The Makefile contains only in very few cases an appropriate routine to uninstall the program. Of course there is the possibility of installing the program into a temporary directory and write down all of the files which were created or modified by the installation for a later removing. But this procedure is painful and very extensive, if programs are frequently compiled from the sources. The tool CheckInstall [1] written by Felipe Eduardo Sánchez Díaz Durán solves this problem. As a rule, you compile and install a GNU Autoconf compliant program under use of the widely known command sequence ./configure && make && make install. The configure shell script attempts to guess correct values for various system−dependent variables, which are used later during the compilation. It checks whether all requirements for compilation are fulfilled and uses those values to create a Makefile in each directory of the package.
    [Show full text]
  • System Administration
    System Administration Application Management Application Management ● A common task for a system administrator is the installation, updating and removal of software. Several ideas exist to make that an easier job Application Management ● Most linux distributions have some sort of package manager, which allows for easier installation, removal and updating of software. ● They also typically have some sort of dependency checking, allowing administrators to know about dependencies between packages, and (with some package managers) to handle automatically those dependancies ./configure; make; make install ● The traditional approach to UNIX application installation ● Application is shipped in a "tarball" file ● The tarball file is unpacked with the tar command, then make is used to compile and install the application Tarball Demonstration ● Download the sample tarball from the website ● Execute the following commands: tar -xzvf magicrescue-1.1.5.tar.gz cd magicrescue-1.1.5 ./configure make su make install Tarball Limitations ● How do I uninstall this package? Sometimes there©s a make uninstall ● What packages are installed on my system? ● How do I keep those packages up to date? The RedHat Package Manager ● RPM is the default package manager for Red Hat Linux systems. ● It deals with .rpm files, which contain the actual programs as well as various bits of meta- information about the package: what it is, where it came from, version information and info about package dependencies. RPM Commands ● rpm -ivh <filename(s)> Installs (-i) packages. The -vh causes rpm to be verbose about what it is doing and to print hash marks (#) as it is installing packages ● rpm -Uvh <filename(s)> Updates (-U) packages.
    [Show full text]
  • Checkinstall
    LinuxFocus article number 360 http://linuxfocus.org CheckInstall par Mario M. Knopf (homepage) Résumé: L´auteur: Checkinstall est un utilitaire qui génère automatiquement des paquets RPM, Debian Mario apprécie de ou Slackware à partir de sources en tar.gz. Ce qui permet une installation « propre » travailler avec Linux, et la désinstallation de quasi n'importe quel code source en tar.gz. les réseaux et tout sujet relatif à la sécurité. _________________ _________________ _________________ Introduction Il arrive fréquemment que des programmes que l'on désire tester n'existent qu'au format tar.gz sans être disponibles au format RPM ou Debian. Dans un tel cas, vous téléchargez le paquet (package) source, vous le décompactez et le compilez manuellement. Jusque là, c'est tout bon. Oui, mais que faire si vous voulez supprimer ce programme ? Le fichier Makefile peut contenir une routine appropriée pour désinstaller le programme mais ce n'est pas systématique. Bien sûr, il reste la possibilité d'installer le programme dans un répertoire temporaire et d'inscrire tous les fichiers qui ont été créés ou modifiés par l'installation et ce en prévision d'une suppression ultérieure. Mais convenons que cette procédure est plutôt pénible et astreignante surtout si des programmes sont fréquemment compilés à partir des sources. CheckInstall [1] écrit par Felipe Eduardo Sánchez Díaz Durán résoud ce problème. Il est de règle de compiler et d'installer un programme répondant au standard GNU Autoconf en utilisant la séquence bien connue de commandes ./configure && make && make install. Le script shell configure tente de deviner les valeurs correctes de différentes variables dépendantes du système, qui seront utilisées après, au cours de la compilation.
    [Show full text]
  • Ubuntu:Precise Ubuntu 12.04 LTS (Precise Pangolin)
    Ubuntu:Precise - http://ubuntuguide.org/index.php?title=Ubuntu:Precise&prin... Ubuntu:Precise From Ubuntu 12.04 LTS (Precise Pangolin) Introduction On April 26, 2012, Ubuntu (http://www.ubuntu.com/) 12.04 LTS was released. It is codenamed Precise Pangolin and is the successor to Oneiric Ocelot 11.10 (http://ubuntuguide.org/wiki/Ubuntu_Oneiric) (Oneiric+1). Precise Pangolin is an LTS (Long Term Support) release. It will be supported with security updates for both the desktop and server versions until April 2017. Contents 1 Ubuntu 12.04 LTS (Precise Pangolin) 1.1 Introduction 1.2 General Notes 1.2.1 General Notes 1.3 Other versions 1.3.1 How to find out which version of Ubuntu you're using 1.3.2 How to find out which kernel you are using 1.3.3 Newer Versions of Ubuntu 1.3.4 Older Versions of Ubuntu 1.4 Other Resources 1.4.1 Ubuntu Resources 1.4.1.1 Unity Desktop 1.4.1.2 Gnome Project 1.4.1.3 Ubuntu Screenshots and Screencasts 1.4.1.4 New Applications Resources 1.4.2 Other *buntu guides and help manuals 2 Installing Ubuntu 2.1 Hardware requirements 2.2 Fresh Installation 2.3 Install a classic Gnome-appearing User Interface 2.4 Dual-Booting Windows and Ubuntu 1 of 212 05/24/2012 07:12 AM Ubuntu:Precise - http://ubuntuguide.org/index.php?title=Ubuntu:Precise&prin... 2.5 Installing multiple OS on a single computer 2.6 Use Startup Manager to change Grub settings 2.7 Dual-Booting Mac OS X and Ubuntu 2.7.1 Installing Mac OS X after Ubuntu 2.7.2 Installing Ubuntu after Mac OS X 2.7.3 Upgrading from older versions 2.7.4 Reinstalling applications after
    [Show full text]
  • Packages Used by Major Linux Distributions
    Packages used by major linux distributions Michael Kluge June 25, 2013 Michael Kluge Packages used by major linux distributions June 25, 2013 1 / 24 Meaning of different box colors /path/to/some/file Content of the file or just parts of it. Shell commands Can be executed on the shell. Green box definition Definitions or examples. Michael Kluge Packages used by major linux distributions June 25, 2013 2 / 24 Introduction Introduction Michael Kluge Packages used by major linux distributions June 25, 2013 3 / 24 Introduction What is a package? Opensuse package definition Packages are archives of files that include all the files making up a piece of software and, eventually, instructions on the way to make them work. http://en.opensuse.org/Package_management Debian FAQ definition Packages generally contain all of the files necessary to implement a set of related commands or features. http://www.debian.org/doc/manuals/debian-faq/ch-pkg_basics.en.html Michael Kluge Packages used by major linux distributions June 25, 2013 4 / 24 Introduction How to install a package without a package manager? I tarball is an gziped tar archive (tar.gz file) I normally contains source code and a makefile I but content is not standardized and may be different I common method before package management systems emerged unpack, configure, compile & install tar -xzf node-v10.12.tar.gz cd node-v10.12 ./configure make make install Michael Kluge Packages used by major linux distributions June 25, 2013 5 / 24 Introduction Pros & cons + source code can be modified by user + can be used
    [Show full text]
  • Master Your Package Management
    TUTORIAL PACKAGE MANAGEMENT LINUX 101: MASTER YOUR TUTORIAL PACKAGE MANAGEMENT SYSTEM apt-get, dpkg, yum, zypper… There are many ways to install MIKE SAUNDERS packages on your Linux box. Here’s everything you need to know. ackage management systems are both loved WHY DO THIS? and hated in the Linux world. On the one hand, • Understand how they provide efficient ways to install and packages work and what P exactly they provide remove software, with everything neatly bundled up. • Learn vital admin skills (Contrast this to Windows, where a setup.exe typically to manage packages scatters all sorts of stuff all over your hard drive and outside of the GUI registry, and running the “uninstaller” doesn’t get rid of • Discover how packaging everything. You can even find third-party “uninstall” systems work across other distros tools designed to clean up this hideous mess.) On the other hand, package management systems often make it difficult to get the latest hot new applications. You have to find the right repository for your distribution, and make sure dependencies are satisfied (usually this is automatic, but not always), Here’s the metadata for the Debian Vim package, obtained and so forth. And if you’re completely new to Linux, with the dpkg -I command. Note the highlighted line, you might find all of the terminology here baffling. So showing dependencies. in this tutorial we’ll explore the two main packaging systems used in GNU/Linux distributions, and provide list GTK as a dependency in its metadata. Package some advanced tips and tricks for long-time Linuxers systems normally handle dependencies as well.
    [Show full text]
  • Package Managment Package Managment
    2021/07/26 13:02 (UTC) 1/7 Package Managment Package Managment Many users decide to use Linux based Operating Systems because of the freedoms they enjoy, included in the list is the freedom to choose the right tool for the job. The Slackware package management schema is a model for displaying the choices that are available to the users. When maintaining a server or even a personal system a certain amount of control must be given to the administrator, the control and simplicity of Slackware package management is what may in fact make you want to try or continue to use Slackware. Brief Explanation of Slackware Packages In terms of security and accountability Slackware is excellent because it brings you software in the condition that the authors intended. What this means is that the Slackware community does not modify the source or add and remove functions from software beyond the author's design, unless a small patch is required to work on Slackware. All packages are built using the original source code in which only official patches are applied, the only modifications that are made for the packages are adding .desktop files (executables for windows managers) and running installed applications/scripts to update databases, font or icon caches to include the newly installed files. Other distributions such as debian and redhat choose to modify the original source code with their own revisions prior to distribution, this can add additional functionality but in some cases such as the debian OpenSSL packages it can result in exploits that only effect the specific distribution which can remain unseen for some time because the original authors (those who know the applications best) were not responsible for the changes or aware of the changes.
    [Show full text]
  • The Official Ubuntu Book, 7Th Edition.Pdf
    ptg8126969 Praise for Previous Editions of The Official Ubuntu Book “The Official Ubuntu Book is a great way to get you started with Ubuntu, giving you enough information to be productive without overloading you.” —John Stevenson, DZone book reviewer “OUB is one of the best books I’ve seen for beginners.” —Bill Blinn, TechByter Worldwide “This book is the perfect companion for users new to Linux and Ubuntu. It covers the basics in a concise and well-organized manner. General use is covered separately from troubleshooting and error-handling, making the book well-suited both for the beginner as well as the user that needs extended help.” —Thomas Petrucha, Austria Ubuntu User Group “I have recommended this book to several users who I instruct regularly on ptg8126969 the use of Ubuntu. All of them have been satisfied with their purchase and have even been able to use it to help them in their journey along the way.” —Chris Crisafulli, Ubuntu LoCo Council, Florida Local Community Team “This text demystifies a very powerful Linux operating system . In just a few weeks of having it, I’ve used it as a quick reference a half-dozen times, which saved me the time I would have spent scouring the Ubuntu forums online.” —Darren Frey, Member, Houston Local User Group This page intentionally left blank ptg8126969 The Official Ubuntu Book Seventh Edition ptg8126969 This page intentionally left blank ptg8126969 The Official Ubuntu Book Seventh Edition Matthew Helmke Amber Graner With Kyle Rankin, Benjamin Mako Hill, ptg8126969 and Jono Bacon Upper Saddle River, NJ • Boston • Indianapolis • San Francisco New York • Toronto • Montreal • London • Munich • Paris • Madrid Capetown • Sydney • Tokyo • Singapore • Mexico City Many of the designations used by manufacturers and sellers to distinguish their products are claimed as trademarks.
    [Show full text]
  • Installing Software Installing Software
    2021/07/26 19:08 (UTC) 1/3 Installing Software Installing Software Overview There are three basic ways to install software in Slackware: install a pre-build binary package, make your own package, or compile the sources and install the resulting binaries manually. If you need to compile a program from source code, making it into your own package is easy and useful. Here's how these methods work. Installing Pre-built Binary Packages To install a package you first need to get the package. Official packages can be found on the Slackware CD-ROM or the Slackware FTP/HTTP mirrors. The package browser can be found at http://packages.slackware.com/. Unofficial, community contributed binaries can be searched for at http://slackfind.net/ which indexes the most well-known community repositories and Slackware-compatible spin-offs like http://slacky.eu/ http://salixos.org/ and more. Usually a package file name ends with .tgz or .txz and looks something like “mozilla- firefox-14.0-x86_64-1.txz”. The more universal naming scheme is “PRGNAM-VERSION- ARCH-BUILD.txz” where ARCH denotes the architecture for which the package was built (examples are x86_64, i486. armv6l, armv7hl, noarch) and the BUILD number is not just used to mark incremental package updates but also allows community packagers to add their own build tag1) which makes them unique. Make sure you get the Slackware package built for the correct architecture and made for your version of Slackware! To install the package you need to change to the root user. Run either the command su - or sudo - i and enter your root password.
    [Show full text]
  • GNU Source Installer Version 0.5, 16 September 2005
    GNU Source Installer version 0.5, 16 September 2005 Claudio Fontana [email protected] Copyright c 2005 Claudio Fontana Published by the Free Software Foundation, 51 Franklin Street - Fifth Floor, Boston, MA 02110-1301, USA Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.2 or any later version published by the Free Software Foundation; with the Invariant Sections being “GNU General Public License” and “GNU Free Documentation License”, with no Front-Cover Texts, and with no Back-Cover Texts. A copy of the license is included in the section entitled “GNU Free Documentation License”. Chapter 1: Introduction for Beginners 1 1 Introduction for Beginners This is an introduction for real beginners of source installation. If you are already somewhat experienced with UNIX-like systems and GNU source code install procedures, you should skip this chapter, otherwise Welcome! sourceinstall will try to make configuration, compilation, installation and removal of source packages easier for you as a beginner. Instead of hiding information and operations from you, everything that happens will be available for you to see. This way, if you are interested you can hopefully understand basic concepts by just looking at the commands executed by this program in the information frame. Provided your system meets the requirements, and thus you manage to have a working installation of sourceinstall itself, you will be shortly able to install new software from its source code by surfing the web, identifying a Free Software you like, downloading its SOURCE package, and feeding it to GNU Source Installer.
    [Show full text]