DOCSLIB.ORG

UNIX-Stammtisch Scientific Linux 7 Am Campus TU Chemnitz, Universitatsrechenzentrum¨

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
UNIX-Stammtisch Scientific Linux 7 Am Campus TU Chemnitz, Universitatsrechenzentrum¨ UNIX-Stammtisch Scientific Linux 7 am Campus TU Chemnitz, Universitatsrechenzentrum¨ UNIX-Stammtisch Scientific Linux 7 am Campus Andreas Heik TU Chemnitz, Universitatsrechenzentrum¨ 23. Februar 2016 1 / 24 Historie Wie alles begann . 1 [1992/93] Linux als Thema beim UNIX-Stammtisch [1995] erster PC im Referenz-Pool 1/288 (jetzt B207) [1996] erste offentliche¨ Compute- und Referenzserver (RedHat Linux 4.0) [1997] 2 Ausbildungspools (Dualboot: RedHat Linux 4.2, Windows NT 4.0) [1998] Linux erobert die Serverlandschaft [1999] 1. Chemnitzer Linuxtag [2002] Plane¨ zur Kommerzialisierung der RedHat Linux-Distribution Uberlegungen¨ fur¨ Umstieg auf Fedora Core oder Einsatz eines RHEL-Clones ! Scientific Linux: erster Eindruck: interessant, serios“¨ ” [2004] weitere Linux-Ausbildungspools (Scientific Linux 3) [2005] ca. 1300 Linux-Systeme (inkl. 528 CLIC-Knoten) (Scientific Linux 4) ... 1Quelle: Matthias Clauß 2 / 24 Linux in Zahlen Aktuelle Scientific Linux Installationen 280 produktive Server davon 188 URZ-Systeme 79 Entwicklungssysteme davon 57 URZ-Systeme 423 Desktop Arbeitsplatze¨ davon 57 URZ-Systeme davon 282 UB-Systeme 386 Pool Arbeitsplatze¨ in 18 Ausbildungspools P 1168 Linux-Systeme in unterschiedlichen Einsatzszenarien durch URZ administriert 2 2Stand: Januar 2016 3 / 24 Linux am Campus Distribution - Scientific Linux I Distribution fur¨ Forschungslabore und Universitaten¨ beteiligt sind: Fermilab, DESY und ETH Zurich,¨ (CERN nicht mehr dabei) I binarkompatibel¨ zu RedHat Enterprise Linux Distribution wird aus quelloffenen RHEL-Paketen erstellt I Erweiterung um zusatzliche¨ Softwarepakete fur¨ die Zielgruppe fur¨ URZ von großer Bedeutung: OpenAFS 4 / 24 Linux am Campus Entscheidung fur¨ Scientific Linux I Binarkompatibilit¨ at¨ zu RedHat Enterprise Linux Lauffahigkeit¨ von RHEL-zertifizierten Anwendungen I Langzeitsupport der Distribution I Verbreitung im wissenschaftlichen Bereich I stabile Plattform fur¨ Server- und Desktopsysteme I konservative Updatepolitik Bestandsschutz von Anwendungsversionen I Softwareumfang der Distribution passt auf Einsatzgebiete am Campus 5 / 24 Linux am Campus Distributions-Roadmap 2011 2012 2013 2014 2015 2016 2017 2018 2019 2020 ... Scientific Linux 5 SL 5.8 SL 5.9 Scientific Linux 6 SL 6.5 SL 6.6 SL 6.7 RedHat Enterprise Linux 7 Scientific Linux 7.x keine Neuauftrage¨ siehe auch: https://access.redhat.com/support/policy/updates/errata 6 / 24 Scientific Linux 7 am Campus Meilensteine [10/2014] Projektstart (Erschließung, Aufbau Infrastruktur, Integration, . ) [1/2015] interner Pilotbetrieb VPSH (Entwicklungssystem) [3/2015] Pilotbetrieb fur¨ interne URZ-Arbeitsplatze¨ (eingeschrankter¨ Softwareumfang) [4/2015] offentlicher¨ Pilotbetrieb VPSH (Nutzerforum) [5/2015] offentlicher¨ Pilotbetrieb in 1-2 Ausbildungspools (Feedback) [7/2015] Produktionsbetrieb Scientific Linux 7 (VPSH und LADM-Arbeitsplatze)¨ [9/2015] Installation der Ausbildungspool (offentliche¨ Arbeitsplatze¨ in der UB, . ) [2/2016] Vorbereitung Update auf SL 7.2 7 / 24 Scientific Linux 7 am Campus Rahmenbedingungen I Architektur: x86 64 (Distribution enthalt¨ zusatzlich¨ X86-Pakete) I Release: SL 7.x x86 64 (Link auf das aktuelle Release, Paketupdates moderiert) I Update vorhandener Systeme durch Neuinstallation (abgesetzte Datenpartitionen konnen¨ erhalten werden) I Paketrepositories: Scientific Linux 7 Base, Extra Packages for Enterprise Linux 7 (EPEL), URZ CONTRIB I ToSCA-Managementplattform Installation, Konfiguration, Systemmanagement I Xymon-Monitoring funktionsabhangiges¨ Dienstemonitoring 8 / 24 Scientific Linux 7 am Campus Neuerungen Bisher eingesetzten Technologien kritisch betrachten, neue Konzepte ” umsetzen!“ I System and Servicemanager systemd I Identity- and Authenticationprovider SSSD I Kerberostickets im Kernelkeyring (Ticket-Files in /tmp entfallen) I XFS als Standardfilesystem mit Logical Volume Manager (LVM) (flexibles Resizing) 3 I Precision Time Protocol chrony I konsistente Netzwerk Geratename¨ (Bug in VMware ACPI-Tabellen ! eno16777984) I Desktop-Umgebung und Anwendungen I ... 3http://chrony.tuxfamily.org/comparison.html 9 / 24 Scientific Linux 7 am Campus System and Servicemanager systemd I Neue Werkzeuge zur Verwaltung von Diensten und Runlevel I systemctl <start|stop|status> service I systemctl isolate <multi-user.target|graphical.target> I systemd-analyze <blame|plot> I Anpassungen der automatisierten Dienste-Konfiguration I /etc/daemon.conf - Whitelist I Anderungen¨ im Logging von Diensten I journalctl I Forward an syslog I RateLimit- und Retention-Einstellungen I Option PrivateTmp=true in Unit-Files (z.B. httpd) erzeugt gekapselten Namespace fur¨ /tmp-Verzeichnisse I siehe auch: man 5 systemd.exec I ... 10 / 24 Scientific Linux 7 am Campus Identity- and Authenticationprovider SSSD I Einfuhrung¨ notwendig aufgrund von Problemen mit GDM und Accounts Service im Zusammenspiel mit großer /etc/passwd (ca. 15000 Nutzer) I Identitaten¨ (UID, Gecos, Home, Shell) werden im LDAP bereitgestellt I Erweiterungen am LDAP-Schema I Erstellen von Indices fur¨ Suchanfragen I Hochverfugbarkeit¨ der LDAP-Infrastruktur I Authentifizierung erfolgt gegen Kerberos I Verwaltung der Kerberos-Tickets im Kernelkeyring I zusatzlicher¨ Mechanismus fur¨ AFS-Token erforderlich ! pam afs session I Integrationsmoglichkeit¨ in zentrale Authentifizierungsinfrastruktur fur¨ dezentral administrierter Linux-Systeme (LDAP-Parameter sind uberschreibbar,¨ z.B. fur¨ lokale Homeverzeichnisse) 11 / 24 Scientific Linux 7 am Campus Server I fruhzeitiger¨ Pilotbetrieb fur¨ virtuelle Server (VPSH) (uberschaubare¨ Installation und Softwarebestand, Erfahrungen, Feedback, . ) I virtuelle ProWebserver (mit neuem, veraltetem php) I Softwarenews: I Apache HTTP Server 2.4 I Anpassung der Konfiguration erforderlich (httpd.conf, .htaccess) I Unterstutzung¨ durch Bereitstellung von Templates I MariaDB 5.5 I kompatibel zu MySQL (API und ABI) I neue storage engines I PostgreSQL 9.2 I SoftwareCollections.org als zusatzliche¨ Paketquelle nutzbar? I Community-gepflegte Pakete, kein Bestandteil der Distribution I deutlich kurzere¨ Lebenszyklen 12 / 24 Scientific Linux 7 am Campus Desktop-Umgebungen I GNOME 3 I moderner Desktop mit neuen Bedienkonzepten I Basis dafur¨ ist GNOME Shell Hauptbestandteile sind top bar, Activities Overview und message tray I visuelle Effekte nutzen Hardwarebeschleunigung auf Basis von clutter (OpenGL Grafik Bibliothek) xorg-x11-drv-ati, xorg-x11-drv-intel, nvidia-x11-drv I uberschaubare¨ Einstellungen erweiterte Einstellungen im gnome-tweak-tool I Erweiterungen uber¨ https://extensions.gnome.org installierbar I GNOME Classic (Standard) I erganzt¨ den GNOME Desktop um traditionelle Funktionen I Applications- und Places-Menu¨ I Taskleiste (aktuelle Anwendungen, Workspace-Umschalter, . ) I Fensterdekoration (Minimieren, Maximieren) I Fensterwechsel mittels Super + Tab 13 / 24 Scientific Linux 7 am Campus Desktop-Umgebungen I GNOME 3 I moderner Desktop mit neuen Bedienkonzepten I Basis dafur¨ ist GNOME Shell Hauptbestandteile sind top bar, Activities Overview und message tray I visuelle Effekte nutzen Hardwarebeschleunigung auf Basis von clutter (OpenGL Grafik Bibliothek) xorg-x11-drv-ati, xorg-x11-drv-intel, nvidia-x11-drv I uberschaubare¨ Einstellungen erweiterte Einstellungen im gnome-tweak-tool I Erweiterungen uber¨ https://extensions.gnome.org installierbar I GNOME Classic (Standard) I erganzt¨ den GNOME Desktop um traditionelle Funktionen I Applications- und Places-Menu¨ I Taskleiste (aktuelle Anwendungen, Workspace-Umschalter, . ) I Fensterdekoration (Minimieren, Maximieren) I Fensterwechsel mittels Super + Tab 13 / 24 Scientific Linux 7 am Campus Desktop-Umgebungen I KDE-Plasma I stabile Version KDE 4.10.x I ahnlichen¨ Funktionen wie GNOME3 I aufgeraumte¨ Oberflache¨ I Vorkonfiguration der Einstellungen I MATE Desktop I leichtgewichtige Desktop-Oberflache¨ I bietet nahzu den Funktionsumfang der aus Scientific Linux 6 bekannten GNOME2-Oberflache¨ I Bereitstellung erfolgt uber¨ EPEL-Repo aktuell Probleme mit Paketqualitat¨ (defektes Standard-Thema, Abhangigkeiten¨ zu RHEL 7.2) I Haupteinsatzfeld: Universitatsbibliothek,¨ . 14 / 24 Scientific Linux 7 am Campus Desktop-Umgebungen I KDE-Plasma I stabile Version KDE 4.10.x I ahnlichen¨ Funktionen wie GNOME3 I aufgeraumte¨ Oberflache¨ I Vorkonfiguration der Einstellungen I MATE Desktop I leichtgewichtige Desktop-Oberflache¨ I bietet nahzu den Funktionsumfang der aus Scientific Linux 6 bekannten GNOME2-Oberflache¨ I Bereitstellung erfolgt uber¨ EPEL-Repo aktuell Probleme mit Paketqualitat¨ (defektes Standard-Thema, Abhangigkeiten¨ zu RHEL 7.2) I Haupteinsatzfeld: Universitatsbibliothek,¨ . 14 / 24 Scientific Linux 7 am Campus spezifische Anpassungen (kleine Auswahl) Den Standard als sinnvoll betrachten, Anpassungen sparsam einsetzen!“ ” I GDM-Benutzerliste deaktivieren I User-Switch (als anderer Benutzer anmelden) deaktivieren ! dconf I Bug im GDM, doppelte Abfrage des Benutzernamens (gefixed, warten auf Paketupdate) I Info-Mechanismus fur¨ Motd, Quota, . ! /etc/xdg/autostart/ und yad I Ausschalten des Arbeitsplatz aus Nutzersitzung deaktivieren ! polkit I Infobanner am GDM-Anmeldebildschirm anzeigen ! Modifikation der gnome-shell.css I ... 15 / 24 Scientific Linux 7 am Campus GSettings und dconf I Front- und Backend fur¨ nutzerspezifische (GUI)-Einstellungen (Ubergang¨ von gconf) I Key-Value basiertes Konfigurationssystem in unstrukturierten Datenbank, Logische Strukturierung der Schlussel¨ I Notifikation uber¨ Anderungen¨ I Uberlagerung¨ und verbindlichen Vorgaben moglich¨ ∼/.config/dconf/, /etc/dconf/db/ I Ubernahme¨ der textbasierten
Load more

Recommended publications
  • Desktop Migration and Administration Guide
    Red Hat Enterprise Linux 7 Desktop Migration and Administration Guide GNOME 3 desktop migration planning, deployment, configuration, and administration in RHEL 7 Last Updated: 2021-05-05 Red Hat Enterprise Linux 7 Desktop Migration and Administration Guide GNOME 3 desktop migration planning, deployment, configuration, and administration in RHEL 7 Marie Doleželová Red Hat Customer Content Services [email protected] Petr Kovář Red Hat Customer Content Services [email protected] Jana Heves Red Hat Customer Content Services Legal Notice Copyright © 2018 Red Hat, Inc. This document is licensed by Red Hat under the Creative Commons Attribution-ShareAlike 3.0 Unported License. If you distribute this document, or a modified version of it, you must provide attribution to Red Hat, Inc. and provide a link to the original. If the document is modified, all Red Hat trademarks must be removed. Red Hat, as the licensor of this document, waives the right to enforce, and agrees not to assert, Section 4d of CC-BY-SA to the fullest extent permitted by applicable law. Red Hat, Red Hat Enterprise Linux, the Shadowman logo, the Red Hat logo, JBoss, OpenShift, Fedora, the Infinity logo, and RHCE are trademarks of Red Hat, Inc., registered in the United States and other countries. Linux ® is the registered trademark of Linus Torvalds in the United States and other countries. Java ® is a registered trademark of Oracle and/or its affiliates. XFS ® is a trademark of Silicon Graphics International Corp. or its subsidiaries in the United States and/or other countries. MySQL ® is a registered trademark of MySQL AB in the United States, the European Union and other countries.
    [Show full text]
  • Technology Overview New Features Backupedge
    Technology Overview - BackupEDGE™ Introduction to the New Features in BackupEDGE 3.x Technology Overview BackupEDGE has a long history of providing reliable data protection for New Features many thousands of users. As operating systems, storage devices and BackupEDGE 3.x usage needs and tendencies have changed over the years, it has continuously met the challenge of providing inexpensive, stable backup and disaster recovery on a variety of UNIX and Linux platforms. Clients routinely find new and clever ways to utilize products. Storage devices have taken on new and exciting features, and incredible capacities. Products designed years ago had built-in limits that were thought to be beyond comprehension. Today, these limits are routinely exceeded. The need for data security is even more apparent. We’re constantly asking our To continue to meet the evolving needs of our clients, we are always clients what tools our asking what features of our products they find most useful, what products need to serve them improvements we can make, and what new requirements they have. better. We’ve used this knowledge to map out new product strategies designed to anticipate the needs of the next generation of users, systems and storage products. This has resulted in the creation of BackupEDGE 3.x, with a combination of internal improvements, new features and enhanced infrastructure designed to become the backbone of a new generation of storage software. Summary of Major Changes and Additions BackupEDGE 3.x features include: • Improvements to partition sizing, UEFI table cleanup after DR, and SharpDrive debugging (03.04.01 build 3). • Support for Rocky Linux 8.4 and AlmaLinux 8.4 (03.04.01 build 2).
    [Show full text]
  • SUSE® Linux Enterprise Desktop 12 and the Workstation Extension: What's New ?
    SUSE® Linux Enterprise Desktop 12 and the Workstation Extension: What's New ? Frédéric Crozat <[email protected]> Enterprise Desktop Release Manager Scott Reeves <[email protected]> Enterprise Desktop Development Manager Agenda • Design Criteria • Desktop Environment in SUSE Linux Enterprise 12 • GNOME Shell • Desktop Features and Applications 2 Design Criteria SUSE Linux Enterprise Desktop Interoperability Ease of Use Security Ease of Management Lower Costs 4 SUSE Linux Enterprise Desktop 12 • Focus on technical workstation ‒ Developers and System administrators • One tool for the job • Main desktop applications will be shipped: ‒ Mail client, Office Suite, Graphical Editors, ... • SUSE Linux Enterprise Workstation Extension ‒ Extend SUSE Linux Enterprise Server with packages only available on SUSE Linux Enterprise Desktop. (x86-64 only) 5 Desktop in SUSE Linux Enterprise 12 As Part of the Common Code Base SUSE Linux Enterprise 12 Desktop Environment • SUSE Linux Enterprise 12 contains one primary desktop environment • Additional light-weight environment for special use-cases: ‒ Integrated Systems • Desktop environment is shared between the server and desktop products 7 SUSE Linux Enterprise 12 Desktop Environment • GNOME 3 is the main desktop environment ‒ SLE Classic mode by default ‒ GNOME 3 Classic Mode and GNOME 3 Shell Mode also available • SUSE Linux Enterprise 12 ships also lightweight IceWM ‒ Targeted at Integrated Systems • QT fully supported: ‒ QT5 supported for entire SLE12 lifecycle ‒ QT4 supported, will be removed in future
    [Show full text]
  • Multi Software Product Lines in the Wild
    AperTO - Archivio Istituzionale Open Access dell'Università di Torino Multi software product lines in the wild This is the author's manuscript Original Citation: Availability: This version is available http://hdl.handle.net/2318/1667454 since 2020-07-06T10:51:50Z Publisher: Association for Computing Machinery Published version: DOI:10.1145/3168365.3170425 Terms of use: Open Access Anyone can freely access the full text of works made available as "Open Access". Works made available under a Creative Commons license can be used according to the terms and conditions of said license. Use of all other works requires consent of the right holder (author or publisher) if not exempted from copyright protection by the applicable law. (Article begins on next page) 27 September 2021 Multi Software Product Lines in the Wild Michael Lienhardt Ferruccio Damiani [email protected] [email protected] Università di Torino Università di Torino Italy Italy Simone Donetti Luca Paolini [email protected] [email protected] Università di Torino Università di Torino Italy Italy ABSTRACT 1 INTRODUCTION Modern software systems are often built from customizable and A Software Product Line (SPL) is a set of similar programs, called inter-dependent components. Such customizations usually define variants, with a common code base and well documented variabil- which features are offered by the components, and may depend ity [1, 6, 19]. Modern software systems are often built as complex on backend components being configured in a specific way. As assemblages of customizable components that out-grow the expres- such system become very large, with a huge number of possible siveness of SPLs.
    [Show full text]
  • Fermi.Gsfc.Nasa.Gov/Ssc
    Running the Fermi Science Tools on Windows Thomas E. Stephens (Innovim/GSFC) and the Fermi Science Support Center Team fermi.gsfc.nasa.gov/ssc Abstract Introduction The Fermi Science Tools, publicly released software for performing analysis on science data from The Fermi Science Tools, now distributed as the FermiTools (see poster P4.3) are developed collaboratively between the Fermi instrument teams and the Fermi Science Support Center (FSSC). Development of these tools began before the Fermi Gamma-ray Space Telescope, have been available and supported on Linux and Mac launch and the tools have been available since the very first public data release in 2009. since launch. Running the tools on a Windows based host has always required a virtual machine For a time, the Fermi Large Area Telescope (LAT) collaboration, maintained a natively compiled version of the tools for running Linux. New technologies, such as Docker and the Windows Subsystem for Linux has Windows, this version regularly had issues and was never publicly released or supported. It was discontinued, even made it possible to use these tools in a more native like environment. for use within the LAT collaboration, in 2014. In this poster we look at three different ways to run the Fermi Science Tools on Windows: via a VM, While it has always been possible to run the tools on Windows using a virtual machine with a Linux guest operating system, this is a somewhat “heavy” solution. With the recent development of both Docker and the Windows Subsystem a Docker container, and using the Windows Subsystem for Linux.
    [Show full text]
  • Linux? POSIX? GNU/Linux? What Are They? a Short History of POSIX (Unix-Like) Operating Systems
    Unix? GNU? Linux? POSIX? GNU/Linux? What are they? A short history of POSIX (Unix-like) operating systems image from gnu.org Mohammad Akhlaghi Instituto de Astrof´ısicade Canarias (IAC), Tenerife, Spain (founder of GNU Astronomy Utilities) Most recent slides available in link below (this PDF is built from Git commit d658621): http://akhlaghi.org/pdf/posix-family.pdf Understanding the relation between the POSIX/Unix family can be confusing Image from shutterstock.com The big bang! In the beginning there was ... In the beginning there was ... The big bang! Fast forward to 20th century... Early computer hardware came with its custom OS (shown here: PDP-7, announced in 1964) Fast forward to the 20th century... (∼ 1970s) I AT&T had a Monopoly on USA telecommunications. I So, it had a lot of money for exciting research! I Laser I CCD I The Transistor I Radio astronomy (Janskey@Bell Labs) I Cosmic Microwave Background (Penzias@Bell Labs) I etc... I One of them was the Unix operating system: I Designed to run on different hardware. I C programming language was designed for writing Unix. I To keep the monopoly, AT&T wasn't allowed to profit from its other research products... ... so it gave out Unix for free (including source). Unix was designed to be modular, image from an AT&T promotional video in 1982 https://www.youtube.com/watch?v=tc4ROCJYbm0 User interface was only on the command-line (image from late 80s). Image from stevenrosenberg.net. AT&T lost its monopoly in 1982. Bell labs started to ask for license from Unix users.
    [Show full text]
  • Cluster Management
    Cluster Management Cluster Management James E. Prewett October 8, 2008 Cluster Management Outline Common Management Tools Regular Expression OSCAR Meta-characters ROCKS Regular Expression Other Popular Cluster Meta-characters (cont.) Management tools SEC Software Management/Change Logsurfer+ Control Security plans/procedures, Risk Cfengine Analysis Getting Started with Cfengine Network Topologies and Packet Parallel Shell Tools / Basic Cluster Filtering Scripting Linux Tricks PDSH Cluster-specific issues Dancer’s DSH Checking Your Work Clusterit Regression Testing C3 tools (cexec) System / Node / Software Change Basic Cluster Scripting Management Logs Backup Management How to know when to upgrade, Logging/ Automated Log Analysis trade–offs Regular Expression Review Monitoring tools Cluster Management Common Management Tools OSCAR OSCAR Information Vital Statistics: Version: 5.1 Date: June 23, 2008 Distribution Formats: tar.gz URL: http://oscar.openclustergroup.org/ Cluster Management Common Management Tools OSCAR OSCAR cluster distribution features: I Supports X86, X86 64 processors I Supports Ethernet networks I Supports Infiniband networks I Graphical Installation and Management tools ... if you like that sort of thing Cluster Management Common Management Tools OSCAR OSCAR (key) Cluster Packages Whats in the box? I Torque Resource Manager I Maui Scheduler I c3 I LAM/MPI I MPICH I OpenMPI I OPIUM (OSCAR User Management software) I pFilter (Packet filtering) I PVM I System Imager Suite (SIS) I Switcher Environment Switcher Cluster Management
    [Show full text]
  • Pipenightdreams Osgcal-Doc Mumudvb Mpg123-Alsa Tbb
    pipenightdreams osgcal-doc mumudvb mpg123-alsa tbb-examples libgammu4-dbg gcc-4.1-doc snort-rules-default davical cutmp3 libevolution5.0-cil aspell-am python-gobject-doc openoffice.org-l10n-mn libc6-xen xserver-xorg trophy-data t38modem pioneers-console libnb-platform10-java libgtkglext1-ruby libboost-wave1.39-dev drgenius bfbtester libchromexvmcpro1 isdnutils-xtools ubuntuone-client openoffice.org2-math openoffice.org-l10n-lt lsb-cxx-ia32 kdeartwork-emoticons-kde4 wmpuzzle trafshow python-plplot lx-gdb link-monitor-applet libscm-dev liblog-agent-logger-perl libccrtp-doc libclass-throwable-perl kde-i18n-csb jack-jconv hamradio-menus coinor-libvol-doc msx-emulator bitbake nabi language-pack-gnome-zh libpaperg popularity-contest xracer-tools xfont-nexus opendrim-lmp-baseserver libvorbisfile-ruby liblinebreak-doc libgfcui-2.0-0c2a-dbg libblacs-mpi-dev dict-freedict-spa-eng blender-ogrexml aspell-da x11-apps openoffice.org-l10n-lv openoffice.org-l10n-nl pnmtopng libodbcinstq1 libhsqldb-java-doc libmono-addins-gui0.2-cil sg3-utils linux-backports-modules-alsa-2.6.31-19-generic yorick-yeti-gsl python-pymssql plasma-widget-cpuload mcpp gpsim-lcd cl-csv libhtml-clean-perl asterisk-dbg apt-dater-dbg libgnome-mag1-dev language-pack-gnome-yo python-crypto svn-autoreleasedeb sugar-terminal-activity mii-diag maria-doc libplexus-component-api-java-doc libhugs-hgl-bundled libchipcard-libgwenhywfar47-plugins libghc6-random-dev freefem3d ezmlm cakephp-scripts aspell-ar ara-byte not+sparc openoffice.org-l10n-nn linux-backports-modules-karmic-generic-pae
    [Show full text]
  • GNOME 3 Application Development Beginner's Guide
    GNOME 3 Application Development Beginner's Guide Step-by-step practical guide to get to grips with GNOME application development Mohammad Anwari BIRMINGHAM - MUMBAI GNOME 3 Application Development Beginner's Guide 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 author, 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: February 2013 Production Reference: 1080213 Published by Packt Publishing Ltd. Livery Place 35 Livery Street Birmingham B3 2PB, UK. ISBN 978-1-84951-942-7 www.packtpub.com Cover Image by Duraid Fatouhi ([email protected]) Credits Author Project Coordinator Mohammad Anwari Abhishek Kori Reviewers Proofreader Dhi Aurrahman Mario Cecere Joaquim Rocha Indexer Acquisition Editor Tejal Soni Mary Jasmine Graphics Lead Technical Editor Aditi Gajjar Ankita Shashi Production Coordinator Technical Editors Aparna Bhagat Charmaine Pereira Cover Work Dominic Pereira Aparna Bhagat Copy Editors Laxmi Subramanian Aditya Nair Alfida Paiva Ruta Waghmare Insiya Morbiwala About the Author Mohammad Anwari is a software hacker from Indonesia with more than 13 years of experience in software development.
    [Show full text]
  • Metadefender Core V4.17.3
    MetaDefender Core v4.17.3 © 2020 OPSWAT, Inc. All rights reserved. OPSWAT®, MetadefenderTM and the OPSWAT logo are trademarks of OPSWAT, Inc. All other trademarks, trade names, service marks, service names, and images mentioned and/or used herein belong to their respective owners. Table of Contents About This Guide 13 Key Features of MetaDefender Core 14 1. Quick Start with MetaDefender Core 15 1.1. Installation 15 Operating system invariant initial steps 15 Basic setup 16 1.1.1. Configuration wizard 16 1.2. License Activation 21 1.3. Process Files with MetaDefender Core 21 2. Installing or Upgrading MetaDefender Core 22 2.1. Recommended System Configuration 22 Microsoft Windows Deployments 22 Unix Based Deployments 24 Data Retention 26 Custom Engines 27 Browser Requirements for the Metadefender Core Management Console 27 2.2. Installing MetaDefender 27 Installation 27 Installation notes 27 2.2.1. Installing Metadefender Core using command line 28 2.2.2. Installing Metadefender Core using the Install Wizard 31 2.3. Upgrading MetaDefender Core 31 Upgrading from MetaDefender Core 3.x 31 Upgrading from MetaDefender Core 4.x 31 2.4. MetaDefender Core Licensing 32 2.4.1. Activating Metadefender Licenses 32 2.4.2. Checking Your Metadefender Core License 37 2.5. Performance and Load Estimation 38 What to know before reading the results: Some factors that affect performance 38 How test results are calculated 39 Test Reports 39 Performance Report - Multi-Scanning On Linux 39 Performance Report - Multi-Scanning On Windows 43 2.6. Special installation options 46 Use RAMDISK for the tempdirectory 46 3.
    [Show full text]
  • An Application Wants Access to the Keyring
    An Application Wants Access To The Keyring When Nilson journalized his virosis skateboard not frequently enough, is Filip sibyllic? Shannon fawningly,remains bawling he hunkers after Maheshhis topic exudate very affirmatively. perishably or pales any mongoose. Aerial Pembroke bestead Linux distro never disappoints in its elegance. If the user only allows it once, access is granted until the application terminates. Discuss Linux specific issues. Flash seems to be updating correctly again. From what i know the sync client is just using whats provided by the operating system and the underlying libraries. Have a question about this project? Once you give up the need to try to memorize passwords then using proper passwords is massively easier. PM by m Want to thank me? As with any list of known security concerns, this list is not exhaustive. AWS KMS keyring generates and encrypts the plaintext key. Questions are encouraged, noobs are welcome! If I do not remember my initial password how do I proceed from this point? It can be used in any application that needs safe password storage. It works for me. The purpose of the keyring is to manage your passwords and keys. Doing so removes the key from the keyring. The author of this thread has indicated that this post answers the original topic. Could open applications in the application wants access to an keyring used for. If I change the contents of the file to login, it will ask for the default keyring. This method worked thank you! So the password is not just about having a VPN set up.
    [Show full text]
  • Debian and Ubuntu
    Debian and Ubuntu Lucas Nussbaum lucas@{debian.org,ubuntu.com} lucas@{debian.org,ubuntu.com} Debian and Ubuntu 1 / 28 Why I am qualified to give this talk Debian Developer and Ubuntu Developer since 2006 Involved in improving collaboration between both projects Developed/Initiated : Multidistrotools, ubuntu usertag on the BTS, improvements to the merge process, Ubuntu box on the PTS, Ubuntu column on DDPO, . Attended Debconf and UDS Friends in both communities lucas@{debian.org,ubuntu.com} Debian and Ubuntu 2 / 28 What’s in this talk ? Ubuntu development process, and how it relates to Debian Discussion of the current state of affairs "OK, what should we do now ?" lucas@{debian.org,ubuntu.com} Debian and Ubuntu 3 / 28 The Ubuntu Development Process lucas@{debian.org,ubuntu.com} Debian and Ubuntu 4 / 28 Linux distributions 101 Take software developed by upstream projects Linux, X.org, GNOME, KDE, . Put it all nicely together Standardization / Integration Quality Assurance Support Get all the fame Ubuntu has one special upstream : Debian lucas@{debian.org,ubuntu.com} Debian and Ubuntu 5 / 28 Ubuntu’s upstreams Not that simple : changes required, sometimes Toolchain changes Bugfixes Integration (Launchpad) Newer releases Often not possible to do work in Debian first lucas@{debian.org,ubuntu.com} Debian and Ubuntu 6 / 28 Ubuntu Packages Workflow lucas@{debian.org,ubuntu.com} Debian and Ubuntu 7 / 28 Ubuntu Packages Workflow Ubuntu Karmic Excluding specific packages language-(support|pack)-*, kde-l10n-*, *ubuntu*, *launchpad* Missing 4% : Newer upstream
    [Show full text]