DOCSLIB.ORG

Dotfiles Documentation

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Dotfiles Documentation dotfiles Documentation Release 0.9.0 Wes Turner April 29, 2016 Contents 1 Dotfiles 1 1.1 Goals...................................................1 1.2 Installation................................................1 1.2.1 Requirements..........................................1 1.2.2 Install the dotfiles........................................1 1.2.3 Source the dotfiles.......................................2 1.2.4 Upgrade the dotfiles.......................................3 1.3 Quickstart................................................4 1.4 Further Dotfiles Resources........................................5 2 Usage 7 2.1 bootstrap_dotfiles.sh...........................................7 2.2 Makefile.................................................7 2.3 Readline.................................................7 2.4 Bash...................................................9 2.5 ZSH.................................................... 30 2.6 I3wm................................................... 31 2.7 Vim.................................................... 35 2.8 src/.................................................... 48 2.8.1 pgs................................................ 48 2.8.2 pyline.py............................................ 49 2.8.3 pyrpo.py............................................. 49 2.8.4 web.sh.............................................. 49 2.9 Scripts.................................................. 49 2.9.1 dotfiles............................................. 50 bootstrap_dotfiles.sh....................................... 50 2.9.2 venv............................................... 50 venv.py.............................................. 50 venv_relabel.sh.......................................... 50 venv_root_prefix.sh........................................ 50 venv.sh.............................................. 50 _ewrd.sh............................................. 50 _dotfileshelp.sh.......................................... 50 gitw................................................ 51 _grinwrd.sh............................................ 51 makew.............................................. 51 usrlog.sh............................................. 52 usrlog.py............................................. 52 i 2.9.3 git................................................ 52 .gitconfig............................................. 52 .gitignore_global......................................... 55 gittagstohgtags.sh......................................... 55 git-changelog.py......................................... 55 git-subrepo2submodule.sh.................................... 55 git-track-all-remotes.sh...................................... 56 git-upgrade-remote-to-ssh.sh................................... 56 2.9.4 hg................................................ 56 .hgrc............................................... 56 .hgignore_global......................................... 60 2.9.5 bashmarks_to_nerdtree.sh................................... 60 2.9.6 compare_installed.py...................................... 61 2.9.7 pulse.sh............................................. 61 2.9.8 setup_mathjax.py........................................ 61 2.9.9 setup_pandas_notebook_deb.sh................................ 61 2.9.10 setup_pandas_notebook.sh................................... 61 2.9.11 setup_scipy_deb.py....................................... 61 2.9.12 deb_deps.py........................................... 61 2.9.13 deb_search.py.......................................... 61 2.9.14 build_docs.py.......................................... 61 2.9.15 el................................................ 62 2.9.16 greppaths.py........................................... 62 2.9.17 lsof.py.............................................. 62 2.9.18 mactool.py........................................... 62 2.9.19 optimizepath.py......................................... 62 2.9.20 passwordstrength.py...................................... 62 2.9.21 pipls.py............................................. 63 2.9.22 pycut.py............................................. 63 2.9.23 py_index.py........................................... 63 2.9.24 pyren.py............................................. 63 2.9.25 whyquote.sh........................................... 63 2.9.26 xlck.sh.............................................. 63 3 Usage (dhelp) 65 3.1 scripts/_dotfileshelp.sh.......................................... 65 3.2 scripts/bootstrap_dotfiles.sh....................................... 66 3.3 etc/.inputrc................................................ 68 3.4 etc/bash/00-bashrc.before.sh....................................... 69 3.5 etc/bash/01-bashrc.lib.sh......................................... 72 3.6 etc/bash/02-bashrc.platform.sh...................................... 72 3.7 etc/bash/03-bashrc.darwin.sh...................................... 72 3.8 etc/bash/04-bashrc.TERM.sh...................................... 73 3.9 etc/bash/05-bashrc.dotfiles.sh...................................... 73 3.10 etc/bash/06-bashrc.completion.sh.................................... 74 3.11 etc/bash/07-bashrc.python.sh...................................... 74 3.12 etc/bash/07-bashrc.virtualenvwrapper.sh................................. 75 3.13 etc/bash/08-bashrc.conda.sh....................................... 75 3.14 etc/bash/08-bashrc.conda.sh.un~..................................... 76 3.15 etc/bash/08-bashrc.gcloud.sh....................................... 77 3.16 etc/bash/10-bashrc.venv.sh........................................ 78 3.17 etc/bash/11-bashrc.venv.pyramid.sh................................... 79 3.18 etc/bash/20-bashrc.editor.sh....................................... 79 3.19 etc/bash/29-bashrc.vimpagers.sh..................................... 80 ii 3.20 etc/bash/30-bashrc.usrlog.sh....................................... 80 3.21 etc/bash/30-bashrc.xlck.sh........................................ 80 3.22 etc/bash/40-bashrc.aliases.sh....................................... 81 3.23 etc/bash/42-bashrc.commands.sh.................................... 82 3.24 etc/bash/50-bashrc.bashmarks.sh.................................... 83 3.25 etc/bash/70-bashrc.repos.sh....................................... 83 3.26 etc/bash/99-bashrc.after.sh........................................ 85 3.27 etc/bash/_ewrd.sh............................................ 85 3.28 etc/bash/usrlog.sh............................................ 86 3.29 etc/bash/xlck.sh............................................. 89 3.30 etc/zsh/00-zshrc.before.sh........................................ 89 3.31 etc/zsh/01-zshrc.lib.sh.......................................... 90 3.32 etc/zsh/05-zshrc.bashrc.sh........................................ 90 3.33 etc/zsh/99-zshrc.after.sh......................................... 90 3.34 etc/i3/config............................................... 90 3.35 etc/vim/vimrc............................................... 94 3.36 etc/vim/vimrc.full.bundles.vimrc.................................... 100 3.37 etc/vim/vimrc.tinyvim.bundles.vimrc.................................. 106 4 venv 109 4.1 Working With Venv........................................... 109 4.1.1 CdAlias............................................. 110 4.1.2 venv.py............................................. 112 Python API............................................ 113 4.1.3 Example Venv Configuration.................................. 114 Shell Configuration........................................ 114 JSON Configuration....................................... 115 4.2 Other scripts with venv-style paths.................................... 117 5 usrlog 119 5.1 usrlog.sh................................................. 119 5.1.1 Installation........................................... 119 5.1.2 Features............................................. 119 usrlog venv integration...................................... 120 5.1.3 -usrlog.log format........................................ 121 -usrlog.log natural key...................................... 121 5.2 usrlog.py................................................. 121 5.3 Caveats.................................................. 122 5.4 Ideas................................................... 122 6 Dotfiles API 125 6.1 Subpackages............................................... 125 6.1.1 dotfiles.cli package....................................... 125 Submodules............................................ 125 dotfiles.cli.cli module....................................... 125 6.1.2 dotfiles.venv package...................................... 126 Objectives............................................. 126 Configuration........................................... 126 Submodules............................................ 127 dotfiles.venv.ipython_config module............................... 127 dotfiles.venv.ipython_magics module.............................. 141 dotfiles.venv.venv module.................................... 144 dotfiles.venv.venv_ipyconfig module............................... 158 dotfiles.venv.venv_ipymagics module.............................. 172 iii 7 Developing 175 7.1 Create a virtualenv with virtualenvwrapper............................... 175 7.2 Install this package............................................ 175 7.3 Test and build this package........................................ 175 8 Changelog 177 8.1 0.9.0................................................... 177 8.2 0.8.3................................................... 179 8.3 0.8.2..................................................
Load more

Recommended publications
  • Opengear User Manual 4.4.Pdf
    User Manual ACM5000 Remote Site Managers ACM5500 Management Gateways ACM7000 Resilience Gateways IM7200 & IM4200 Infrastructure Managers CM7100 Console Servers Revision 4.32 2019-4-10 Table of Contents Safety Please take care to follow the safety precautions below when installing and operating the console server: - Do not remove the metal covers. There are no operator serviceable components inside. Opening or removing the cover may expose you to dangerous voltage which may cause fire or electric shock. Refer all service to Opengear qualified personnel. - To avoid electric shock the power cord protective grounding conductor must be connected through to ground. - Always pull on the plug, not the cable, when disconnecting the power cord from the socket. Do not connect or disconnect the console server during an electrical storm. Also it is recommended you use a surge suppressor or UPS to protect the equipment from transients. FCC Warning Statement This device complies with Part 15 of the FCC rules. Operation of this device is subject to the following conditions: (1) This device may not cause harmful interference, and (2) this device must accept any interference that may cause undesired operation. Proper back-up systems and necessary safety devices should be utilized to protect against injury, death or property damage due to system failure. Such protection is the responsibility of the user. This console server device is not approved for use as a life-support or medical system. Any changes or modifications made to this console server device without the explicit approval or consent of Opengear will void Opengear of any liability or responsibility of injury or loss caused by any malfunction.
    [Show full text]
  • Sequence Listings Webinar Suzannah K. Sundby Carl Oppedahl
    Suzannah K. Sundby Canady + Lortz LLP Sequence Listings Webinar January 9, 2018 – Updated Version Carl Oppedahl Oppedahl Patent Law Firm LLC DISCLAIMER These materials and views expressed today reflect only the personal views of the author and do not necessarily represent the views of other members and clients of the author’s organizations. These materials are public information and have been prepared solely for educational purposes to contribute to the understanding of U.S. intellectual property law. While every attempt was made to ensure that these materials are accurate, errors or omissions may be contained therein, for which any liability is disclaimed. These materials and views are not a source of legal advice and do not establish any form of attorney-client relationship with the authors and their law firms. Why are some sequence errors not identified by Checker? Is “SEQ ID NO” required before sequences in Specifications? Do you recommend using the PatentIn Software? How do you correct sequence listing errors in PCTs? What about the new WIPO ST.26 Standard? Is Checker worthwhile? How can I easily edit sequence listings generated by others? Can I use other software to generate sequence listings? How do I file sequence listings using EFS-Web and ePCT? How long does it take the USPTO to review and approve? Any risk TYFNIL of using certain sequence descriptors? Help! IT locked down my computer… what do I do? Any sequence listing tips? Why Practitioners Should Know and Do Usually lack of time to send to outside vendors Last minute changes to applications (apps) containing sequences (seqs) Particularly, changes to claims Not hostage to staff/vendors, overtime, etc.
    [Show full text]
  • Prebrane Zo Stranky
    Manuál pre začiatočníkov a používateľov Microsoft Windows Galadriel 1.7.4 Manuál je primárne tvorený pre Ubuntu 7.04 Feisty Fawn. Dá sa však použiť aj pre Kubuntu, Xubuntu, Edubuntu, Ubuntu Studio a neoficiálne distribúcie založené na Ubuntu. Pokryté verzie: 7.10, 7.04, 6.10, 6.06 a 5.10 (čiastočne) Vypracoval Stanislav Hoferek (ICQ# 258126362) s komunitou ľudí na stránkach: linuxos.sk kubuntu.sk ubuntu.wz.cz debian.nfo.sk root.cz 1 Začíname! 5 Pracovné prostredie 9 Live CD 1.1 Postup pre začiatočníkov 5.1 Programové vybavenie 9.1 Vysvetlenie 1.2 Zoznámenie s manuálom 5.1.1 Prvé kroky v Ubuntu 9.2 Prístup k internetu 1.3 Zoznámenie s Ubuntu 5.1.2 Základné programy 9.3 Pripojenie pevných diskov 1.3.1 Ubuntu, teší ma! 5.1.3 Prídavné programy 9.4 Výhody a nevýhody Live CD 1.3.2 Čo tu nájdem? 5.2 Nastavenie jazyka 9.5 Live CD v prostredí Windows 1.3.3 Root 5.3 Multimédia 9.6 Ad-Aware pod Live CD 1.4. Užitočné informácie 5.3.1 Audio a Video Strana 48 1.4.1 Odkazy 5.3.2 Úprava fotografii 1.4.2 Slovníček 5.4 Kancelária 10 FAQ 1.4.3 Ako Linux funguje? 5.4.1 OpenOffice.org 10 FAQ 1.4.4 Spúšťanie programov 5.4.2 PDF z obrázku Strana 50 1.5 Licencia 5.4.3 Ostatné Strana 2 5.5 Hry 11 Tipy a triky 5.6 Estetika 11.1 Všeobecné rady 2 Linux a Windows 5.7 Zavádzanie systému 11.2 Pokročilé prispôsobenie systému 2.1 Porovnanie OS 5.7.1 Zavádzač 11.3 Spustenie pri štarte 2.2 Náhrada Windows Programov 5.7.2 Prihlasovacie okno 11.4 ALT+F2 2.3 Formáty 5.7.3 Automatické prihlásenie 11.5 Windows XP plocha 2.4 Rozdiely v ovládaní 5.8 Napaľovanie v Linuxe Strana 55 2.5 Spustenie programov pre Windows 5.9 Klávesové skratky 2.6 Disky 5.10 Gconf-editor 12 Konfigurácia 2.7 Klávesnica Strana 27 12.1 Nástroje na úpravu konfigurákov Strana 12 12.2 Najdôležitejšie konf.
    [Show full text]
  • BEA TUXEDO Reference Manual Section 5 - File Formats and Data Descriptions
    BEA TUXEDO Reference Manual Section 5 - File Formats and Data Descriptions BEA TUXEDO Release 6.5 Document Edition 6.5 February 1999 Copyright Copyright © 1999 BEA Systems, Inc. All Rights Reserved. Restricted Rights Legend This software and documentation is subject to and made available only pursuant to the terms of the BEA Systems License Agreement and may be used or copied only in accordance with the terms of that agreement. It is against the law to copy the software except as specifically allowed in the agreement. This document may not, in whole or in part, be copied photocopied, reproduced, translated, or reduced to any electronic medium or machine readable form without prior consent, in writing, from BEA Systems, Inc. Use, duplication or disclosure by the U.S. Government is subject to restrictions set forth in the BEA Systems License Agreement and in subparagraph (c)(1) of the Commercial Computer Software-Restricted Rights Clause at FAR 52.227-19; subparagraph (c)(1)(ii) of the Rights in Technical Data and Computer Software clause at DFARS 252.227-7013, subparagraph (d) of the Commercial Computer Software--Licensing clause at NASA FAR supplement 16-52.227-86; or their equivalent. Information in this document is subject to change without notice and does not represent a commitment on the part of BEA Systems. THE SOFTWARE AND DOCUMENTATION ARE PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND INCLUDING WITHOUT LIMITATION, ANY WARRANTY OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. FURTHER, BEA Systems DOES NOT WARRANT, GUARANTEE, OR MAKE ANY REPRESENTATIONS REGARDING THE USE, OR THE RESULTS OF THE USE, OF THE SOFTWARE OR WRITTEN MATERIAL IN TERMS OF CORRECTNESS, ACCURACY, RELIABILITY, OR OTHERWISE.
    [Show full text]
  • Brewer Mkiv Spectrophotometer
    BREWER MKII Spectrophotometer Operator's Manual BREWER MKIV SPECTROPHOTOMETER OPERATOR'S MANUAL OM-BA-C231 REV B, August 15, 1999 SCI-TEC Instruments Inc. 1503 Fletcher Road Saskatoon, Sask. , Canada S7M 5S5 Phone 306-934-0101 Fax 306-978-2339 Email: [email protected] Web site: www.sci-tec.com BREWER MKII Spectrophotometer Operator's Manual This Page is Intentionally left Blank TABLE OF CONTENTS 1 SYSTEM OVERVIEW..................................................................................................................................1 2 SYSTEM DESCRIPTION .............................................................................................................................3 2.1 SPECTROPHOTOMETER ......................................................................................................................4 2.2 SOLAR TRACKING..............................................................................................................................16 2.3 COMPUTER EQUIPMENT ...................................................................................................................17 3 BREWER SYSTEM SETUP........................................................................................................................19 3.1 SPECTROPHOTOMETER UNPACKING AND SETUP........................................................................21 3.2 TRIPOD UNPACKING AND SETUP ....................................................................................................21 3.3 AZIMUTH TRACKER UNPACKING AND SETUP..............................................................................21
    [Show full text]
  • The AWK Programming Language
    The Programming ~" ·. Language PolyAWK- The Toolbox Language· Auru:o V. AHo BRIAN W.I<ERNIGHAN PETER J. WEINBERGER TheAWK4 Programming~ Language TheAWI(. Programming~ Language ALFRED V. AHo BRIAN w. KERNIGHAN PETER J. WEINBERGER AT& T Bell Laboratories Murray Hill, New Jersey A ADDISON-WESLEY•• PUBLISHING COMPANY Reading, Massachusetts • Menlo Park, California • New York Don Mills, Ontario • Wokingham, England • Amsterdam • Bonn Sydney • Singapore • Tokyo • Madrid • Bogota Santiago • San Juan This book is in the Addison-Wesley Series in Computer Science Michael A. Harrison Consulting Editor Library of Congress Cataloging-in-Publication Data Aho, Alfred V. The AWK programming language. Includes index. I. AWK (Computer program language) I. Kernighan, Brian W. II. Weinberger, Peter J. III. Title. QA76.73.A95A35 1988 005.13'3 87-17566 ISBN 0-201-07981-X This book was typeset in Times Roman and Courier by the authors, using an Autologic APS-5 phototypesetter and a DEC VAX 8550 running the 9th Edition of the UNIX~ operating system. -~- ATs.T Copyright c 1988 by Bell Telephone Laboratories, Incorporated. All rights reserved. No part of this publication may be reproduced, stored in a retrieval system, or transmitted, in any form or by any means, electronic, mechanical, photocopy­ ing, recording, or otherwise, without the prior written permission of the publisher. Printed in the United States of America. Published simultaneously in Canada. UNIX is a registered trademark of AT&T. DEFGHIJ-AL-898 PREFACE Computer users spend a lot of time doing simple, mechanical data manipula­ tion - changing the format of data, checking its validity, finding items with some property, adding up numbers, printing reports, and the like.
    [Show full text]
  • IBM VM/370 (Ems) Terminal User's Guide for FORTRAN IV Program Product Program Products
    SC28-6891-1 IBM VM/370 (eMS) Terminal User's Guide for FORTRAN IV Program Product Program Products Program Numbers 5734-F01 5734-F02 5734-F03 5734-LM1 5734-LM3 Page of SC28-6891-0,-1 Revised May 13, 1977 By TNL SN20-922S Second Edition (April 1975) This edition, as amended by technical newsletters SN20-9201 and SN20-9225, applies to Release 1.0 of the IBM Virtual Machine Facility/370 (VM/370) (CMS). This edition is a reprint of SC28-6891-0 incorporating changes released in Technical Newsletters SN28-0609 (dated March 1, 1973) and SN28-0620 (dated January 3, 1974). Changes are listed in the Summary of Amendments, Number 3, on the facing page. Information in this publication is subject to significant change. Any such changes will be published in new editions or technical newsletters. Before using the publication, consult the latest IBM System/360 Bibliography, GC20-0360, or IBM System/370 Bibliography, GC20-0001, and the technical newsletters that amend the particular bibliography, to learn which editions are applicable and current. Requests for copies of IBM publications shou'ld be made to your IBM representative or to the IBM branch office that serves your locality. Forms for readers' comments are provided at the back of this publication. If the forms have been removed, address comments to IBM Corporation, P. O. Box 50020, Programming Publishing, San Jose, California 95150. Comments and suggesti~ns become the property of IBM. © Copyright International Business Machines Corporation 1972 Summary of Amendments Number 1 Date of Publication: March 1, 1973 Form of Publication: TNL SN28-0609 to SC28-6891-0 CP and CMS Command Abbreviations Maintenance: Documentation Only Valid abbreviations have been added to the summary descriptions of significant CP and CMS commands.
    [Show full text]
  • Journal Import Requirements and Technical Guidance
    Journal Import Requirements and Technical Guidance Document Purpose The purpose of this document is to provide technical requirements information regarding the Journal Import process for those involved in the remediation of systems impacted by Workday Release 4 functionality. Prior to Workday Release 4 in July 2017, journal import utilizes the Journal Staging Area (JSA). This document provides information about the design that will be used to replace the JSA process of uploading files into Oracle with the new process for loading files into Workday. The process covers both non-Internal Service Provider (non-ISP) and Internal Service Provider (ISP) Journal Imports. Process Due to the large number of JSA sources, one of the guiding principles for the new Journal Import process has been that the overall process should feel familiar and require minimal training for end-users. In order to accomplish this goal, the design(s) utilizes the existing Managed File Transfer (MFT) source directories; the file formats, while different, utilize a file format that contains a Header (GLH) record and multiple Detail (GLD) records. The formats can be viewed in the template file - ISP and non-ISP journal file layouts. The designers of the process are aware that there are use cases that will require some sources to submit both JSA files to be routed to EBS at the same time that they are submitting Journal Import files to be imported into Workday. This use case is very constrained and will only last for a very short period of time. If you think this may apply to you, the team would like to hear from you.
    [Show full text]
  • Streampix 5 Tech Support:[email protected]
    Norpix Inc - www.norpix.com StreamPix 5 Tech Support:[email protected] STREAMPIX 5 Copyright Norpix Inc. (C) 2009-2013 StreamPix5 - Copyright Norpix Inc. (C) 2013 (1/187) Norpix Inc - www.norpix.com StreamPix 5 Tech Support:[email protected] Table of Contents About StreamPix 5...................................................................................................................................8 Minimum system requirements................................................................................................................9 Installing StreamPix...............................................................................................................................10 Authorization codes...............................................................................................................................11 StreamPix 5 Basics................................................................................................................................12 Ribbon Interface overview.................................................................................................................12 Faster !..........................................................................................................................................14 Default list of Keyboard Shortcuts.................................................................................................15 The Sequence slider ....................................................................................................................16
    [Show full text]
  • The UNIX Time- Sharing System
    1. Introduction There have been three versions of UNIX. The earliest version (circa 1969–70) ran on the Digital Equipment Cor- poration PDP-7 and -9 computers. The second version ran on the unprotected PDP-11/20 computer. This paper describes only the PDP-11/40 and /45 [l] system since it is The UNIX Time- more modern and many of the differences between it and older UNIX systems result from redesign of features found Sharing System to be deficient or lacking. Since PDP-11 UNIX became operational in February Dennis M. Ritchie and Ken Thompson 1971, about 40 installations have been put into service; they Bell Laboratories are generally smaller than the system described here. Most of them are engaged in applications such as the preparation and formatting of patent applications and other textual material, the collection and processing of trouble data from various switching machines within the Bell System, and recording and checking telephone service orders. Our own installation is used mainly for research in operating sys- tems, languages, computer networks, and other topics in computer science, and also for document preparation. UNIX is a general-purpose, multi-user, interactive Perhaps the most important achievement of UNIX is to operating system for the Digital Equipment Corpora- demonstrate that a powerful operating system for interac- tion PDP-11/40 and 11/45 computers. It offers a number tive use need not be expensive either in equipment or in of features seldom found even in larger operating sys- human effort: UNIX can run on hardware costing as little as tems, including: (1) a hierarchical file system incorpo- $40,000, and less than two man years were spent on the rating demountable volumes; (2) compatible file, device, main system software.
    [Show full text]
  • K-Watch & K-Manager Pro Application Software User
    K-Watch & K-Manager Pro Application Software User Manual K-Watch & K-Manager Pro Patent Information This product may be protected by one or more patents. For further information, please visit: www.grassvalley.com/patents/ Copyright and Trademark Notice Grass Valley®, GV® and the Grass Valley logo and/or any of the Grass Valley products listed in this document are trademarks or registered trademarks of GVBB Holdings SARL, Grass Valley USA, LLC, or one of its affiliates or subsidiaries. All other intellectual property rights are owned by GVBB Holdings SARL, Grass Valley USA, LLC, or one of its affiliates or subsidiaries. All third party intellectual property rights (including logos or icons) remain the property of their respective owners. Copyright © 2021 GVBB Holdings SARL and Grass Valley USA, LLC. All rights reserved. Specifications are subject to change without notice. Terms and Conditions Please read the following terms and conditions carefully. By using K-Watch and K- Manager Pro documentation, you agree to the following terms and conditions. Grass Valley hereby grants permission and license to owners of K-Watch and K- Manager Pro to use their product manuals for their own internal business use. Manuals for Grass Valley products may not be reproduced or transmitted in any form or by any means, electronic or mechanical, including photocopying and recording, for any purpose unless specifically authorized in writing by Grass Valley. A Grass Valley manual may have been revised to reflect changes made to the product during its manufacturing life. Thus, different versions of a manual may exist for any given product.
    [Show full text]
  • Using and Administering Linux: Volume 2 Zero to Sysadmin: Advanced Topics
    Using and Administering Linux: Volume 2 Zero to SysAdmin: Advanced Topics David Both Using and Administering Linux: Volume 2 David Both Raleigh, NC, USA ISBN-13 (pbk): 978-1-4842-5454-7 ISBN-13 (electronic): 978-1-4842-5455-4 https://doi.org/10.1007/978-1-4842-5455-4 Copyright © 2020 by David Both This work is subject to copyright. All rights are reserved by the Publisher, whether the whole or part of the material is concerned, specifically the rights of translation, reprinting, reuse of illustrations, recitation, broadcasting, reproduction on microfilms or in any other physical way, and transmission or information storage and retrieval, electronic adaptation, computer software, or by similar or dissimilar methodology now known or hereafter developed. Trademarked names, logos, and images may appear in this book. Rather than use a trademark symbol with every occurrence of a trademarked name, logo, or image we use the names, logos, and images only in an editorial fashion and to the benefit of the trademark owner, with no intention of infringement of the trademark. The use in this publication of trade names, trademarks, service marks, and similar terms, even if they are not identified as such, is not to be taken as an expression of opinion as to whether or not they are subject to proprietary rights. While the advice and information in this book are believed to be true and accurate at the date of publication, neither the authors nor the editors nor the publisher can accept any legal responsibility for any errors or omissions that may be made.
    [Show full text]