Portuguese Flash Cards
Total Page:16
File Type:pdf, Size:1020Kb
Load more
Recommended publications
-
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 -
Remote Desktop Server: XDMCP
SUSE® Linux Enterprise Setup and Optimization for Remote Graphical Access Frédéric Crozat <[email protected] Enterprise Desktop Release Manager Scott Reeves <[email protected] Enterprise Desktop Development Manager Agenda • Remote Desktop Methods • Demo • Other Remote Access Methods • Session monitoring and Management • Additional settings 2 Remote Desktop Server: XDMCP • Highly discouraged by SUSE ‒ Not secure: traffic is not encrypted ‒ Not adapted to modern desktops, causing huge latency • But still available 3 Remote Desktop server: VNC • Recommended protocol (security, caching) • Available through several means: ‒ Independent session with XVNC (configured through YaST Remote Administration module) ‒ Sharing existing GNOME session, through vino (GNOME Control Center / Sharing) 4 Remote Desktop Server: RDP • Microsoft protocol, always available on Windows products (both as client and server) • xrdp is providing independent graphical sessions support 5 Remote Desktop Clients • Vinagre ‒ Connect to VNC / SSH / Spice / RDP sessions • Vncviewer • Browser ‒ Java ‒ HTML5 • Security ‒ TLS support • Situations for alternative display and window managers 6 Demo Other Remote Access Methods • Connection via ssh ‒ Only for applications ‒ not full desktop ‒ Can't attach to running applications • Graphical apps in containers ‒ Can be done but not supported • Beware, X11 socket is NOT secure ‒ In the future, xdg-app and wayland will help 8 Accessing SUSE Linux Enterprise systems from Windows • For RDP: built-in • For X11: ‒ Micro Focus Reflection X 2014: ‒ Standalone X server or Domain mode (distributes workload and connectivity across multiple tiers) ‒ Xming (Free X server for Windows) ‒ Exceed ‒ Cygwin X server • For VNC: ‒ Vncviewer ‒ Libvirt Virt-viewer (TLS support) 9 Session monitoring and management • Systemd-loginctl 10 Session monitoring and management • systemd-loginctl is replacing ConsoleKit • loginctl [list-sessions]: output all sessions • loginctl session-status <session-number>: 2 - fcrozat (1000) Since: lun. -
Indicators for Missing Maintainership in Collaborative Open Source Projects
TECHNISCHE UNIVERSITÄT CAROLO-WILHELMINA ZU BRAUNSCHWEIG Studienarbeit Indicators for Missing Maintainership in Collaborative Open Source Projects Andre Klapper February 04, 2013 Institute of Software Engineering and Automotive Informatics Prof. Dr.-Ing. Ina Schaefer Supervisor: Michael Dukaczewski Affidavit Hereby I, Andre Klapper, declare that I wrote the present thesis without any assis- tance from third parties and without any sources than those indicated in the thesis itself. Braunschweig / Prague, February 04, 2013 Abstract The thesis provides an attempt to use freely accessible metadata in order to identify missing maintainership in free and open source software projects by querying various data sources and rating the gathered information. GNOME and Apache are used as case studies. License This work is licensed under a Creative Commons Attribution-ShareAlike 3.0 Unported (CC BY-SA 3.0) license. Keywords Maintenance, Activity, Open Source, Free Software, Metrics, Metadata, DOAP Contents List of Tablesx 1 Introduction1 1.1 Problem and Motivation.........................1 1.2 Objective.................................2 1.3 Outline...................................3 2 Theoretical Background4 2.1 Reasons for Inactivity..........................4 2.2 Problems Caused by Inactivity......................4 2.3 Ways to Pass Maintainership.......................5 3 Data Sources in Projects7 3.1 Identification and Accessibility......................7 3.2 Potential Sources and their Exploitability................7 3.2.1 Code Repositories.........................8 3.2.2 Mailing Lists...........................9 3.2.3 IRC Chat.............................9 3.2.4 Wikis............................... 10 3.2.5 Issue Tracking Systems...................... 11 3.2.6 Forums............................... 12 3.2.7 Releases.............................. 12 3.2.8 Patch Review........................... 13 3.2.9 Social Media............................ 13 3.2.10 Other Sources.......................... -
List of Application Added in ARL #2607
List of Application added in ARL #2607 Application Name Publisher .NET Framework 19.0 Microsoft .NET Runtime 6 Preview Microsoft .NET SDK 6 Preview Microsoft 3DMark UL 3uTools 2.35 3uTools 4D 17.6 4D 4K Stogram 3.0 OpenMedia ABACUS Studio 8.0 Avolution ABCpdf .NET 11.1 WebSupergoo Software ACQUITY Column Manager 1.7 Waters Acrobat Elements 17.1 Adobe ACT Enterprise Client 2.12 Access Control ACT Enterprise Client 2.3 Access Control ACTEnterprise 2.3 Vanderbilt Actiance Vantage OpenText Actional Agent 9.0 Progress Software Active Directory (AD) Bridge 8.5 Enterprise BeyondTrust Active Directory/LDAP Connector 5.0 Auth0 Active Intelligence Engine 4.4 Attivio ActivePresenter 8.1 Atomi Systems ActivePython 3.8 ActiveState ActivInspire 2.17 Promethean Activity Monitor 4.0 STEALTHbits Technologies Activity Monitor Agent 2.4 STEALTHbits Technologies ActiViz.NET 8.2 Supported Kitware SAS ActiViz.NET 8.2 Trial Kitware SAS ActiViz.NET 9.0 Supported Kitware SAS Acumen Cumulative 8.5 Deltek AD Tidy 2.6 Cjwdev AdAnalytics Adslytic Add-in Express for Microsoft Office and .NET 8.3 Professional Add-in Express Add-in Express for Microsoft Office and .NET 9.4 Premium Add-in Express Adlib PDF 5.1 Enterprise Adlib AdminStudio 2021 Flexera AdminStudio 2021 ZENworks Flexera Advance Design 2020 GRAITEC Advance Design 2021 GRAITEC Advanced SystemCare 14.0 IObit Advertising Editor 11.29 Microsoft Advisor 9.5 Belarc AFP Viewer 7.50 ISIS Papyrus Europe AG Agile Requirements Designer 3.1 Broadcom Alfresco Content Services 6.0 Alfresco Software AltspaceVR 4.1 Microsoft -
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 -
Xrdp.Log.Pdf
Printed by Stephen Quinney Feb 05, 19 13:46 xrdp.log.txt Page 1/3 * Wednesday 31st January 2018 Stephen has imported the XRDP configuration from SEE. Most of it has been put into lcfg−level headers so that it can be shared. At the top level the service is configured using the dice/options/external−xrdp−server.h header. There is a test service accessible at xrdp.inf.ed.ac.uk which seems to work well. A quick survey of clients for Linux suggests that the best is remmina. Stephen will be talking about the project at the next Development meeting so before then he will collect all his notes on a wiki page for the project. * Wednesday 7th February 2018 Since SEE has already put together a remote desktop solution which works well and is freely available, there seemed little point in trying other possible solutions; so a small test version of SEE’s RDP−based remote desktop service has been set up here in Informatics. It uses HAProxy as a load−balancing front end. In the trial service at xrdp.inf.ed.ac.uk, the front end routes connection requests to the less loaded of the two backend machines, or to an existing session if there is one. The test service will be open to computing staff. It’s envisaged that the full service will use real hardware rather than virtual, and that there will be separate staff and student services. The next work on this project will be to add some Informatics identity to the login screen; to change access controls on the PAM stack for the backend machines, to permit differences between staff and student services; and to document the services on computing.help. -
1. Why POCS.Key
Symptoms of Complexity Prof. George Candea School of Computer & Communication Sciences Building Bridges A RTlClES A COMPUTER SCIENCE PERSPECTIVE OF BRIDGE DESIGN What kinds of lessonsdoes a classical engineering discipline like bridge design have for an emerging engineering discipline like computer systems Observation design?Case-study editors Alfred Spector and David Gifford consider the • insight and experienceof bridge designer Gerard Fox to find out how strong the parallels are. • bridges are normally on-time, on-budget, and don’t fall ALFRED SPECTORand DAVID GIFFORD • software projects rarely ship on-time, are often over- AS Gerry, let’s begin with an overview of THE DESIGN PROCESS bridges. AS What is the procedure for designing and con- GF In the United States, most highway bridges are budget, and rarely work exactly as specified structing a bridge? mandated by a government agency. The great major- GF It breaks down into three phases: the prelimi- ity are small bridges (with spans of less than 150 nay design phase, the main design phase, and the feet) and are part of the public highway system. construction phase. For larger bridges, several alter- There are fewer large bridges, having spans of 600 native designs are usually considered during the Blueprints for bridges must be approved... feet or more, that carry roads over bodies of water, preliminary design phase, whereas simple calcula- • gorges, or other large obstacles. There are also a tions or experience usually suffices in determining small number of superlarge bridges with spans ap- the appropriate design for small bridges. There are a proaching a mile, like the Verrazzano Narrows lot more factors to take into account with a large Bridge in New Yor:k. -
Help Getting Help
Help Getting Help Whatever the newest user needs to know by Stan Reichardt https://newlug.sluug.org/ 1 Goals ● This will be a survey of finding help, within Linux Operating System Distributions and outside. ● Intended for newcomers, the true beginners. ● Some useful examples, certainly not everything. ● Some example commands needed installation. ● We will first explore help available within the command line terminal, which will then lead us into the richly abundant graphical help resources of the LinuxMint MATE Desktop Environment. 2 POSIX https://en.wikipedia.org/wiki/POSIX ● "POSIX defines the application programming interface (API), along with command line shells and utility interfaces, for software compatibility with variants of Unix and other operating systems." https://en.wikipedia.org/wiki/Unix_shell Users type commands into the shell. ● POSIX does not standardize help for new users. (AFAIK) Not intuitive ~ User has to know commands. Not intuitive with unix Not intuitive with linux 3 CLI vs GUI https://en.wikipedia.org/wiki/Command-line_interface ● "A command-line interface or command language interpreter (CLI), also known as command-line user interface,... ...is a means of interacting with a computer program where the user (or client) issues commands to the program in the form of successive lines of text (command lines)." ● "Today, many end users rarely, if ever, use command-line interfaces and instead rely upon graphical user interfaces (GUI) and menu- driven interactions." 4 CLI – Command Line Interface 1. $ a_command (without options) (sometimes) 2. $ a_command ? (old method) \ 3. $ a_command -? (old method) / 4. $ a_command --? 5. $ a_command -h (sometimes used for some other feature) 6. $ a_command --help 7. -
Installed Packages Gconf2.X86 64 3.2.6-8.El7 @Anaconda Geoip
Installed Packages GConf2.x86_64 3.2.6-8.el7 @anaconda GeoIP.x86_64 1.5.0-11.el7 @anaconda ModemManager.x86_64 1.6.0-2.el7 @anaconda ModemManager-glib.x86_64 1.6.0-2.el7 @anaconda NetworkManager.x86_64 1:1.4.0-12.el7 @anaconda NetworkManager-adsl.x86_64 1:1.4.0-12.el7 @anaconda NetworkManager-glib.x86_64 1:1.4.0-12.el7 @anaconda NetworkManager-libnm.x86_64 1:1.4.0-12.el7 @anaconda NetworkManager-libreswan.x86_64 1.2.4-1.el7 @anaconda NetworkManager-libreswan-gnome.x86_64 1.2.4-1.el7 @anaconda NetworkManager-team.x86_64 1:1.4.0-12.el7 @anaconda NetworkManager-tui.x86_64 1:1.4.0-12.el7 @anaconda NetworkManager-wifi.x86_64 1:1.4.0-12.el7 @anaconda OpenEXR-libs.x86_64 1.7.1-7.el7 @anaconda PackageKit.x86_64 1.0.7-6.el7.centos @anaconda PackageKit-command-not-found.x86_64 1.0.7-6.el7.centos @anaconda PackageKit-glib.x86_64 1.0.7-6.el7.centos @anaconda PackageKit-gstreamer-plugin.x86_64 1.0.7-6.el7.centos @anaconda PackageKit-gtk3-module.x86_64 1.0.7-6.el7.centos @anaconda PackageKit-yum.x86_64 1.0.7-6.el7.centos @anaconda PyQt4.x86_64 4.10.1-13.el7 @anaconda PyYAML.x86_64 3.10-11.el7 @anaconda abattis-cantarell-fonts.noarch 0.0.16-3.el7 @anaconda abrt.x86_64 2.1.11-45.el7.centos @anaconda abrt-addon-ccpp.x86_64 2.1.11-45.el7.centos @anaconda abrt-addon-kerneloops.x86_64 2.1.11-45.el7.centos @anaconda abrt-addon-pstoreoops.x86_64 2.1.11-45.el7.centos @anaconda abrt-addon-python.x86_64 2.1.11-45.el7.centos @anaconda abrt-addon-vmcore.x86_64 2.1.11-45.el7.centos @anaconda abrt-addon-xorg.x86_64 2.1.11-45.el7.centos @anaconda abrt-cli.x86_64 2.1.11-45.el7.centos -
Fedora 24 Installation Guide
Fedora 24 Installation Guide Installing Fedora 24 on 32 and 64-bit AMD and Intel Fedora Documentation Project Installation Guide Fedora 24 Installation Guide Installing Fedora 24 on 32 and 64-bit AMD and Intel Edition 1 Author Fedora Documentation Project Copyright © 2015 Red Hat, Inc. and others. The text of and illustrations in this document are licensed by Red Hat under a Creative Commons Attribution–Share Alike 3.0 Unported license ("CC-BY-SA"). An explanation of CC-BY-SA is available at http://creativecommons.org/licenses/by-sa/3.0/. The original authors of this document, and Red Hat, designate the Fedora Project as the "Attribution Party" for purposes of CC-BY-SA. In accordance with CC-BY-SA, if you distribute this document or an adaptation of it, you must provide the URL for the original version. Red Hat, as the licensor of this document, waives the right to enforce, and agrees not to assert, Section 4d of CC-BY-SA to the fullest extent permitted by applicable law. Red Hat, Red Hat Enterprise Linux, the Shadowman logo, JBoss, MetaMatrix, Fedora, the Infinity Logo, and RHCE are trademarks of Red Hat, Inc., registered in the United States and other countries. For guidelines on the permitted uses of the Fedora trademarks, refer to https://fedoraproject.org/wiki/ Legal:Trademark_guidelines. Linux® is the registered trademark of Linus Torvalds in the United States and other countries. Java® is a registered trademark of Oracle and/or its affiliates. XFS® is a trademark of Silicon Graphics International Corp. or its subsidiaries in the United States and/or other countries. -
Red Hat Enterprise Linux 8 Using the Desktop Environment in RHEL 8
Red Hat Enterprise Linux 8 Using the desktop environment in RHEL 8 Configuring and customizing the GNOME 3 desktop environment on RHEL 8 Last Updated: 2021-09-10 Red Hat Enterprise Linux 8 Using the desktop environment in RHEL 8 Configuring and customizing the GNOME 3 desktop environment on RHEL 8 Legal Notice Copyright © 2021 Red Hat, Inc. The text of and illustrations in this document are licensed by Red Hat under a Creative Commons Attribution–Share Alike 3.0 Unported license ("CC-BY-SA"). An explanation of CC-BY-SA is available at http://creativecommons.org/licenses/by-sa/3.0/ . In accordance with CC-BY-SA, if you distribute this document or an adaptation of it, you must provide the URL for the original version. Red Hat, as the licensor of this document, waives the right to enforce, and agrees not to assert, Section 4d of CC-BY-SA to the fullest extent permitted by applicable law. Red Hat, Red Hat Enterprise Linux, the Shadowman logo, 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. Node.js ® is an official trademark of Joyent. -
Made in San Pedro: the Production of Dress and Meaning in a Tz'utujil
Made in San Pedro: The production of dress and meaning in a Tz’utujil - Maya municipality by Emily Jean Oertling B.S., University of Rhode Island, 2010 M.A., London College of Fashion, 2012 AN ABSTRACT OF A DISSERTATION submitted in partial fulfillment of the requirements for the degree DOCTOR OF PHILOSOPHY Department of Interior Design and Fashion Studies College of Health and Human Sciences KANSAS STATE UNIVERSITY Manhattan, Kansas 2021 Abstract This study examines dress practices – encompassing design and production processes, discussion about dress, use, and styling decisions – in the Tz’utujil - Maya municipality of Tz’unun Ya’, commonly referred to by participants as San Pedro La Laguna (San Pedro), Guatemala. By examining the relationship between women and all available clothing, this study recognizes the development of traditions and attends to dress practices as a way to engage with local culture. This study identifies the dress in use in San Pedro and its importance in the community, determines the influences on dress practices, and evaluates the complexities of dress practices in view of cultural sustainability. Understanding if the dress practices of San Pedro are culturally sustainable required inquiries into people-product relationships, social interaction amongst community members, and the systems that produce these garments. A qualitative data collection method was employed – collecting data primarily through 60-90 minute, semi-structured online interviews with 21 Tz’utujil identifying women. The research process adapted to themes and curiosities emerging from the data. The goal was to understand, clarify, and confirm reoccurring actions, reasons, and motives relating to the phenomenon of dress practices in San Pedro.