DOCSLIB.ORG

Going Barefoot with UNIX for the DB2 DBA

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Going Barefoot with UNIX for the DB2 DBA IDUG DB2 Tech Conference Sydney, Australia, September 12 - 14, 2012 Going Barefoot with UNIX for the DB2 DBA Robert Mala, Database Administrator Session Code: 1089 Date and time: 13th September 2012, 10.30am to 11.30am Platform: DB2 for LUW Abstract: Using UNIX can be bewildering until you have grasped the basic concepts, capabilities and features. DBAs with a z/OS background find UNIX to be arcane, esoteric, and pernickety. Getting the UNIX “mindset” takes effort, but once obtained UNIX becomes a capable, powerful and productive environment in which to work. Stepping through tailored examples using DB2 LUW, this presentation is for the DB2 DBA wanting to go barefoot with UNIX. Objectives: - Introduce UNIX concepts, capabilities and features. - Understand and cultivate a UNIX "mindset". - Provide tailored examples using DB2 LUW with UNIX. - Getting the most from the interactive Korn Shell. Speaker Biography: Robert has worked with DB2 and SQL for over 20 years and has worked in a variety of database centric roles for organisations in Australia and Europe. Robert is IBM Certified for DB2 UDB Database Administration for LUW & z/OS, and DB2 UDB Family Application Development. "Going Barefoot with UNIX for the DB2 DBA" by Robert Mala Page 1 IDUG DB2 Tech Conference Sydney, Australia, September 12 - 14, 2012 Click to edit Master title style Agenda • UNIX Software Tools Philosophy • Simple Commands • Compound Commands • awk • Secure Shell • Interactive Korn Shell • GNU screen Regardless of the platform or product, the activities of a Database Administrator are broadly the same. From checking house keeping has completed successfully to promoting changes, deploying stored procedures to tuning SQL. The working practices and methods may vary but the basic activities of a Database Administrator remain the same. GUIs can give a large productivity boost for certain types of activities. They can also be very confining. GUIs restrict you to what the developers of the GUI think is needed. This can result in having to do activities in a less than optimal way. The tooling can also leave large gaps in functionality leaving you to find alternatives. GUIs shield you from the underlying commands and insulate you from server side information which at times is critical to doing the job effectively. If you are responsible for looking after many instances of db2 over many servers, GUIs can be unwieldy when trying to apply changes globally. CLIs give the freedom to do just about anything. That freedom comes at a cost of a steep learning curve. Scripts can be developed for common activities so that you need not reinvent the wheel each time. However the command line can be a harsh and unforgiving place. It requires a good level of typing skills and time to build the knowledge and skills to be able to drive the CLI proficiently. Driving the CLI via UNIX is a potent mix. It gives the freedom and flexibility of the CLI coupled with an environment that can super charge your productivity. Going barefoot with Unix for the DB2 DBA requires study and practice to establish practices and finger habits. Which once established will enable you to develop command line scripts that help you do you job quickly and efficiently. "Going Barefoot with UNIX for the DB2 DBA" by Robert Mala Page 2 IDUG DB2 Tech Conference Sydney, Australia, September 12 - 14, 2012 Click to edit Master title style UNIX Software Tools Philosophy • It's a philosophy, not standardised methodology • Based on pragmatic and practical experience • Programs designed to do one thing well • Create new programs rather than extend • Text stream as the universal interface • Output of one program can be used as input to another • Sum is greater than the parts There are a number of guiding principles used when developing UNIX commands and programs in general. Collectively they are referred to as the UNIX Software Tools Philosophy. The philosophy is not a standard or methodology developed by a committee or from academic ponderings. Instead, it is based on the pragmatic and practical experience of a number of individuals who contributed to the development of UNIX. There are several interpretations of the philosophy but the points of interest for this presentation are: •Design programs to do one thing well. •Create new programs rather than extend existing ones. •Use text as the universal interface •Make the output of one program usable as input to another. Creating new programs rather than extend existing ones goes some way in explaining the overlap of functionality between programs. The idea is programs become overly complex when they are extended. As additional options and features are added the program becomes more difficult to use. This philosophy is complimentary to the "do one thing well" guideline. The down side to creating new programs is that UNIX appears to have a number of programs that have overlapping uses. In part this has given UNIX a reputation as being disorderly collection of tools. The benefit of creating new programs is that tools are small light weight programs can be coupled together in various ways. "Going Barefoot with UNIX for the DB2 DBA" by Robert Mala Page 3 IDUG DB2 Tech Conference Sydney, Australia, September 12 - 14, 2012 Click to edit Master title style Simple Commands Name Description awk Pattern scanning and processing language cat Concatenate and print files cut Cut out selected fields of each line of a file date Display the date and time df Report free disk space find Find files grep Search text for a pattern nl Line numbering filter print / printf Write output / formatted output sed Stream editor sort Sort, merge, or sequence check text tr Translate characters uniq Report or filter out repeated lines wc Line, word, byte or character count xargs Constructs parameter lists and runs commands While there are many unix utilities there are some that are used very frequently. Of all the utilities, grep, sed, and awk are the “work horses”. The list of commands above is by no means extensive or exhaustive. Though my experience has been that the above utilities will cover 95% of my activities. I haven’t included vi, ed or ex editors, even though these can be driven from the command line. What makes unix so powerful is when commands are combined. This requires that programs are developed using the unix software tools philosophy. Programs can then be combined in many different ways. This leads to the whole becoming greater than the some of the parts. Complex results can be achieved from simple steps. There is a similar mindset in combining unix utilities as to writing complex sql statements. In unix, the biggest hurdle is to not think in terms of iterative processing of records within files. Doing so will lead to overly complicated solutions that go against the unix way. Instead you need to think of commands processing files and data streams. Once you have master this way of thinking the utilities provided by unix will start to work for you rather than against you. "Going Barefoot with UNIX for the DB2 DBA" by Robert Mala Page 4 IDUG DB2 Tech Conference Sydney, Australia, September 12 - 14, 2012 Click to edit Master title style Compound Commands • Pipeline Command • List Commands • And , Or , Sequential , Compound List , Background Process • Command Grouping • Subshell , Brace • Iteration Commands • for , while , until Compound commands are used combine commands. There are various ways to combine commands including pipelines, list commands, command grouping and iteration commands. "Going Barefoot with UNIX for the DB2 DBA" by Robert Mala Page 5 IDUG DB2 Tech Conference Sydney, Australia, September 12 - 14, 2012 Click to edit Master title style Pipeline Command • Pipelines are the easiest way to work with UNIX • The | ( pipeline ) operator is used to combine commands command [ | [ newline… ] command ]… • pipeline is a sequence of one or more simple or compound commands. • Stdin for command comes from the keyboard or previous command • Stdout for command goes to the terminal or next command The pipe is arguably the most important construct in unix. Pipes are used to flow data from one command to another. It's named as an analogy to a physical pipe. Several unix philosophies make pipes very effective. Namely text as the universal interface, output of a command should reflect the format of the input, doing one thing well. When programs follow these philosophies, pipes allows commands to work together. The shell does not run the commands in a pipe directly. Child processes are created for each command. While you can think of the sequence of execution going left to right, in reality all commands are running concurrently. Though they might not be doing anything if waiting on input from the previous command. To improve the efficiency and performance of a pipeline, previous commands should filter as much of the data as quickly as possible. Commands that must process the entire data-stream before passing data to the next command, such as sorting, are costly. This should all sound very familiar if you tune sql statements. One or more newlines can be entered after the | character. From the command line you will be given the secondary prompt ( PS2 is normally set to a > character) which indicates that ksh is waiting for the rest of the pipeline to be entered. Adding newlines to a pipeline is useful as it makes reading and understanding the pipeline easier. "Going Barefoot with UNIX for the DB2 DBA" by Robert Mala Page 6 IDUG DB2 Tech Conference Sydney, Australia, September 12 - 14, 2012 Click to edit Master title style Pipeline Command Unix tools solution to show word frequency $ man grep | > tr -cs '[:alnum:]' '[\n*]' | > tr '[:upper:]' '[:lower:]' | > sort | > uniq -c | > sort -k1,1nr -k2 | > head -3 108 the 47 a 25 to The pipeline in the slide demonstrates the power of pipelines ( examples using db2 coming up shortly).
Load more

Recommended publications
  • Freenas® 11.0 User Guide
    FreeNAS® 11.0 User Guide June 2017 Edition FreeNAS® IS © 2011-2017 iXsystems FreeNAS® AND THE FreeNAS® LOGO ARE REGISTERED TRADEMARKS OF iXsystems FreeBSD® IS A REGISTERED TRADEMARK OF THE FreeBSD Foundation WRITTEN BY USERS OF THE FreeNAS® network-attached STORAGE OPERATING system. VERSION 11.0 CopYRIGHT © 2011-2017 iXsystems (https://www.ixsystems.com/) CONTENTS WELCOME....................................................1 TYPOGRAPHIC Conventions...........................................2 1 INTRODUCTION 3 1.1 NeW FeaturES IN 11.0..........................................3 1.2 HarDWARE Recommendations.....................................4 1.2.1 RAM...............................................5 1.2.2 The OperATING System DeVICE.................................5 1.2.3 StorAGE Disks AND ContrOLLERS.................................6 1.2.4 Network INTERFACES.......................................7 1.3 Getting Started WITH ZFS........................................8 2 INSTALLING AND UpgrADING 9 2.1 Getting FreeNAS® ............................................9 2.2 PrEPARING THE Media.......................................... 10 2.2.1 On FreeBSD OR Linux...................................... 10 2.2.2 On WindoWS.......................................... 11 2.2.3 On OS X............................................. 11 2.3 Performing THE INSTALLATION....................................... 12 2.4 INSTALLATION TROUBLESHOOTING...................................... 18 2.5 UpgrADING................................................ 19 2.5.1 Caveats:............................................
    [Show full text]
  • Linux on the Road
    Linux on the Road Linux with Laptops, Notebooks, PDAs, Mobile Phones and Other Portable Devices Werner Heuser <wehe[AT]tuxmobil.org> Linux Mobile Edition Edition Version 3.22 TuxMobil Berlin Copyright © 2000-2011 Werner Heuser 2011-12-12 Revision History Revision 3.22 2011-12-12 Revised by: wh The address of the opensuse-mobile mailing list has been added, a section power management for graphics cards has been added, a short description of Intel's LinuxPowerTop project has been added, all references to Suspend2 have been changed to TuxOnIce, links to OpenSync and Funambol syncronization packages have been added, some notes about SSDs have been added, many URLs have been checked and some minor improvements have been made. Revision 3.21 2005-11-14 Revised by: wh Some more typos have been fixed. Revision 3.20 2005-11-14 Revised by: wh Some typos have been fixed. Revision 3.19 2005-11-14 Revised by: wh A link to keytouch has been added, minor changes have been made. Revision 3.18 2005-10-10 Revised by: wh Some URLs have been updated, spelling has been corrected, minor changes have been made. Revision 3.17.1 2005-09-28 Revised by: sh A technical and a language review have been performed by Sebastian Henschel. Numerous bugs have been fixed and many URLs have been updated. Revision 3.17 2005-08-28 Revised by: wh Some more tools added to external monitor/projector section, link to Zaurus Development with Damn Small Linux added to cross-compile section, some additions about acoustic management for hard disks added, references to X.org added to X11 sections, link to laptop-mode-tools added, some URLs updated, spelling cleaned, minor changes.
    [Show full text]
  • Cygwin User's Guide
    Cygwin User’s Guide Cygwin User’s Guide ii Copyright © Cygwin authors Permission is granted to make and distribute verbatim copies of this documentation provided the copyright notice and this per- mission notice are preserved on all copies. Permission is granted to copy and distribute modified versions of this documentation under the conditions for verbatim copying, provided that the entire resulting derived work is distributed under the terms of a permission notice identical to this one. Permission is granted to copy and distribute translations of this documentation into another language, under the above conditions for modified versions, except that this permission notice may be stated in a translation approved by the Free Software Foundation. Cygwin User’s Guide iii Contents 1 Cygwin Overview 1 1.1 What is it? . .1 1.2 Quick Start Guide for those more experienced with Windows . .1 1.3 Quick Start Guide for those more experienced with UNIX . .1 1.4 Are the Cygwin tools free software? . .2 1.5 A brief history of the Cygwin project . .2 1.6 Highlights of Cygwin Functionality . .3 1.6.1 Introduction . .3 1.6.2 Permissions and Security . .3 1.6.3 File Access . .3 1.6.4 Text Mode vs. Binary Mode . .4 1.6.5 ANSI C Library . .4 1.6.6 Process Creation . .5 1.6.6.1 Problems with process creation . .5 1.6.7 Signals . .6 1.6.8 Sockets . .6 1.6.9 Select . .7 1.7 What’s new and what changed in Cygwin . .7 1.7.1 What’s new and what changed in 3.2 .
    [Show full text]
  • The Elinks Manual the Elinks Manual Table of Contents Preface
    The ELinks Manual The ELinks Manual Table of Contents Preface.......................................................................................................................................................ix 1. Getting ELinks up and running...........................................................................................................1 1.1. Building and Installing ELinks...................................................................................................1 1.2. Requirements..............................................................................................................................1 1.3. Recommended Libraries and Programs......................................................................................1 1.4. Further reading............................................................................................................................2 1.5. Tips to obtain a very small static elinks binary...........................................................................2 1.6. ECMAScript support?!...............................................................................................................4 1.6.1. Ok, so how to get the ECMAScript support working?...................................................4 1.6.2. The ECMAScript support is buggy! Shall I blame Mozilla people?..............................6 1.6.3. Now, I would still like NJS or a new JS engine from scratch. .....................................6 1.7. Feature configuration file (features.conf).............................................................................7
    [Show full text]
  • Upgrade Operations Guide
    Oracle® Communications Network Charging and Control Upgrade Operations Guide Release 12.0.2 December 2018 Copyright Copyright © 2018, Oracle and/or its affiliates. All rights reserved. This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited. The information contained herein is subject to change without notice and is not warranted to be error- free. If you find any errors, please report them to us in writing. If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, then the following notice is applicable: U.S. GOVERNMENT END USERS: Oracle programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, delivered to U.S. Government end users are "commercial computer software" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, shall be subject to license terms and license restrictions applicable to the programs. No other rights are granted to the U.S. Government.
    [Show full text]
  • A Quick and Easy Guide to Tmux
    7/24/2018 A Quick and Easy Guide to tmux Ham Vocke writing stu about software (/) Home (/) Blog (/blog) About Me (/about) Talks (/talks) (https://github.com/hamvocke) (https://twitter.com/hamvocke) (http://www.hamvocke.com/feed.xml) A Quick and Easy Guide to tmux 16 Aug 2015 terminal 13 minutes read I love working with the command line. Seriously, I think there’s hardly any more productive and more versatile tool for a software developer than the terminal. Maybe it’s the hacker/wizard/neckbeard kind of feeling I get when using a terminal, I don’t know. At work we do lots of pair programming. Everyone’s got their own laptop and can set it up the way they like. And since I love working with the command line I’ve spent quite some time doing (only sane! I swear!) modications to my terminal environment that make working with the command line more pleasant and streamlined. This is why my pair usually will be greeted by something like this: https://www.hamvocke.com/blog/a-quick-and-easy-guide-to-tmux/ 1/21 7/24/2018 A Quick and Easy Guide to tmux If they’ve worked with me before they know what they are up to. But every once in a while there will be a new team member who doesn’t know my environment. Usually this is the point where they will ask something like “WTF am I looking at?” and it’s my time to shine! Because what they’re looking at is nothing less than the best thing since sliced bread.
    [Show full text]
  • Tmux: Terminal Multiplexer
    tmux: Terminal Multiplexer Tom Ryder [email protected] https://sanctum.geek.nz/ What is tmux? ● tmux is a terminal multiplexer. ● Runs in the TTY, or your favourite terminal emulator ● Start any number of virtual terminals within it ● Arrange terminals in any way you like ● And most importantly: Attach/detach without interrupting running programs ● Extremely useful for sysadmin work where X is unavailable, and many other things Simple use case ● You SSH in to your faraway server. ● You start a process interactively, that you think will only take a few minutes... – ...but it takes ages! – ...and you forgot to redirect the output to a file! – ...and interrupting the process will break things! – ...and your laptop is running out of battery! ● What to do? Simple use case ● The shell way: Bash: $ long-running-job [Ctrl-Z] to suspend $ bg $ disown $ logout Still works, and useful to remember in a pinch! ● Lets the process complete safely, but... ● ...you lose all the output, and you can’t (easily) “adopt” the process again. ● Your job has a dependency on your SSH connection. ● If only we could fix that... Simple use case ● The multiplexer way: tmux: $ tmux $ long-running-job [Ctrl-B, d] to detach $ logout ● And then later: $ ssh yourhost $ tmux attach ● And your job’s output is sitting there, like you never left. Another use case ● You run a program like Mutt on a server to read and write mail ● Your connection is flaky ● Every time your SSH connection cuts, you completely lose the message you were writing, or your place in the mail queue
    [Show full text]
  • GNU Screen Cheat Sheet by Mynocksonmyfalcon Via Cheatography.Com/92701/Cs/22367
    GNU Screen Cheat Sheet by mynocksonmyfalcon via cheatography.com/92701/cs/22367/ Basic Screen Options Managing screen windows screen Launch a new, unnamed screen session CTRL+a c Create a new screen window screen -S name Launch a new screen session called name CTRL+a CTRL+a Return to previous active window screen -ls List all running screen sessions CTRL+a " Display screen window list screen -r name Connect to a screen session called name CTRL+a n Change to the next window in the list CTRL+a : Exit all applica​ tions and close screen session CTRL+a p Change to the previous window in the CTRL+a Detach from a screen session list CTRL+a d name Detach from the screen session name CTRL+a number Change to window by number, for 0-9 CTRL+a ? View screen help CTRL+a ' name OR Change to window by name OR by number number Other screen options CTRL+a w Display window bar if not visible CTRL+a [ Enter copy mode CTRL+a A Rename current window CTRL+a ] Paste Split Screen Management CTRL+a M Monitor a window for activity CTRL+a S Split window horizon​ tally CTRL+a _ Monitor a window for silence CTRL+a | Split window vertically CTRL+a Enter a digraph (non-ASCII character) CTRL+V CTRL+a TAB Move to the next display region CTRL+a H Enable logging for the screen session CTRL+a X Remove the current region CTRL+a Enable vertical scrolling for mouse usage (also works CTRL+a Q Remove all regions except for the current region ESC with arrow keys) By mynocksonmyfalcon Not published yet.
    [Show full text]
  • Linux Shell Scripting Cookbook Second Edition
    Linux Shell Scripting Cookbook Second Edition Over 110 practical recipes to solve real-world shell problems, guaranteed to make you wonder how you ever lived without them Shantanu Tushar Sarath Lakshman BIRMINGHAM - MUMBAI Linux Shell Scripting Cookbook Second Edition Copyright © 2013 Packt Publishing All rights reserved. No part of this book may be reproduced, stored in a retrieval system, or transmitted in any form or by any means, without the prior written permission of the publisher, except in the case of brief quotations embedded in critical articles or reviews. Every effort has been made in the preparation of this book to ensure the accuracy of the information presented. However, the information contained in this book is sold without warranty, either express or implied. Neither the authors, nor Packt Publishing, and its dealers and distributors will be held liable for any damages caused or alleged to be caused directly or indirectly by this book. Packt Publishing has endeavored to provide trademark information about all of the companies and products mentioned in this book by the appropriate use of capitals. However, Packt Publishing cannot guarantee the accuracy of this information. First published: January 2011 Second edition: May 2013 Production Reference: 1140513 Published by Packt Publishing Ltd. Livery Place 35 Livery Street Birmingham B3 2PB, UK. ISBN 978-1-78216-274-2 www.packtpub.com Cover Image by Parag Kadam ([email protected]) Credits Authors Project Coordinator Shantanu Tushar Shiksha Chaturvedi Sarath Lakshman Proofreader Reviewers Linda Morris Rajeshwari K. John C. Kennedy Indexer Hemangini Bari Anil Kumar Sudhendu Kumar Production Coordinator Aravind SV Shantanu Zagade Acquisition Editor Cover Work Kartikey Pandey Shantanu Zagade Lead Technical Editor Ankita Shashi Technical Editors Jalasha D'costa Amit Ramadas Lubna Shaikh About the Authors Shantanu Tushar is an advanced GNU/Linux user since his college days.
    [Show full text]
  • Upgrade Operations Guide
    Oracle® Communications Network Charging and Control Upgrade Operations Guide Release 12.0.0 December 2017 Copyright Copyright © 2017, Oracle and/or its affiliates. All rights reserved. This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited. The information contained herein is subject to change without notice and is not warranted to be error- free. If you find any errors, please report them to us in writing. If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, then the following notice is applicable: U.S. GOVERNMENT END USERS: Oracle programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, delivered to U.S. Government end users are "commercial computer software" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, shall be subject to license terms and license restrictions applicable to the programs. No other rights are granted to the U.S. Government.
    [Show full text]
  • Mosh Research Paper
    Mosh: An Interactive Remote Shell for Mobile Clients Keith Winstein and Hari Balakrishnan M.I.T. Computer Science and Artificial Intelligence Laboratory, Cambridge, Mass. fkeithw,[email protected] Abstract Figure 1: Mosh in use. Mosh (mobile shell) is a remote terminal application that supports intermittent connectivity, allows roaming, and speculatively and safely echoes user keystrokes for better interactive response over high-latency paths. Mosh is built on the State Synchronization Protocol (SSP), a new UDP-based protocol that securely synchronizes client and server state, even across changes of the client’s IP address. Mosh uses SSP to synchronize a character- cell terminal emulator, maintaining terminal state at both client and server to predictively echo keystrokes. Our evaluation analyzed keystroke traces from six different users covering a period of 40 hours of real-world us- age. Mosh was able to immediately display the ef- fects of 70% of the user keystrokes. Over a commer- cial EV-DO (3G) network, median keystroke response mote servers feel more like the local computer, because latency with Mosh was less than 5 ms, compared with most keystrokes are reflected immediately on the user’s 503 ms for SSH. Mosh is free software, available from display—even in full-screen programs like a text editor http://mosh.mit.edu. It was downloaded more than or mail reader. 15,000 times in the first week of its release. These features are possible because Mosh operates at a different layer from SSH. While SSH securely con- 1 Introduction veys an octet-stream over the network and then hands it off to a separate client-side terminal emulator to be inter- Remote terminal applications are almost as old as packet- preted and rendered in cells on the screen, Mosh contains switched data networks.
    [Show full text]
  • GEODATEN NUTZEN QGIS: Laientaugliches System Mit Allen Profi-Funktionen S
    Mosh: SSH-Booster für COMMUNITY-EDITIONRecipes: Leckeres kochen den mobilen Einsatz S. 52 und mit anderen teilen S. 38 Frei kopieren und beliebig weiter verteilen ! 05.2018 05.2018 Routen planen, Tracks auswerten, geografische Daten verknüpfen, Karten bauen GEODATEN GEODATEN GEODATEN NUTZEN QGIS: Laientaugliches System mit allen Profi-Funktionen S. 16 QMapShack: Touren planen und GPS-Tracks verwalten S. 30 GMT: Maßgeschneidertes S. 24 Kartenmaterial im Eigenbau OSGeo Live: Alle wichtigen GIS-Tools einsatzfertig auf Live-DVD S. 10 Der neue Raspberry Pi 3 Modell B+ im Detail S. 80 Mehr Performance, Gigabit-LAN, 5-GHz-WLAN, Power-over-Ethernet – unser Test zeigt, was die Neuauflage bringt und welche Kompromisse die Entwickler machen Statt Dropbox und Skype LAN-Monitoring mit Linux Nextcloud 13 mit Videochats und Verdächtige Datenströme und Hosts Ende-zu-Ende-Verschlüsselung S. 64 im Netz aufspüren und beobachten S. 44 Top-Distris auf zwei • LAN-Monitoring • Logisim • Mosh • Nextcloud 13 • Pipewire • Raspberry Pi 3 B+ • Recipes • Redcore Linux • • Raspberry Pi 3 B+ Recipes Redcore • LAN-Monitoring Logisim Mosh Nextcloud 13 Pipewire Heft-DVDs LAN-MONITORING • MOSH • NEXTCLOUD 13 • PIPEWIRE • RASPI 3 B+ • • B+ 3 RASPI • PIPEWIRE • 13 NEXTCLOUD • MOSH • LAN-MONITORING EUR 8,50 EUR 9,35 sfr 17,00 EUR 10,85 EUR 11,05 EUR 11,05 2 DVD-10 05 www.linux-user.de Deutschland Österreich Schweiz Benelux Spanien Italien 4 196067 008502 05 Editorial Blendwerk Sehr geehrte Leserinnen und Leser, eigentlich muss man Facebook für die durch den Cambridge-Analytica-Skan- dal losgetretene Diskussion um den Umgang mit personenbezogenen Daten ja danken: Die Affäre macht unmissver- ständlich klar, dass die Debatten rund um Privacy bislang in völlig falschen Jörg Luther Bahnen liefen.
    [Show full text]