DOCSLIB.ORG

Product Correction Notice (PCN)

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text

Load more

Product Correction Notice # 1906S Product Correction Notice (PCN) Issue Date: December 12, 2016 Supplement 6 Date: December 12, 2016 Archive Date: NA PCN Number: 1906S SECTION 1 - CUSTOMER NOTICE Products Material Codes affected by this PCN: The following codes provide copies of CMS Server and the CMS Supervisor Web 700512605 CMS R17 Software DVD SPARC Load r17jd.d includes CMS Webclient cmsweb17jd.d 700512604 CMS R17 Software DVD X86 Load r17jd.d includes CMS Webclient cmsweb17jd.d 700512603 CMS R17 Software DVD LINUX Load r17jd.d includes CMS Webclient cmsweb17jd.d Copies of the CMS Supervisor Mobile App are available for free device download at iTunes store. Copies of CMS Supervisor PC Client, Terminal Emulator and Network Reporting are available for free download at http://support.avaya.com. R17 versions of the desktop PC client software are REQUIRED for use with CMS R17. The following will ship with new system orders: CMS Supervisor PC Client R17 LA_31 (this includes Terminal Emulator) CMS Network Reporting R17 LA_31 When available, the latest bug fix versions of CMS Supervisor PC Client and CMS Supervisor Mobile App should be used. Copies of CMS Supervisor PC Client, Terminal Emulator and Network Reporting are available for download at http://support.avaya.com. Copies of the CMS Supervisor Mobile App are available for download at the iTunes store. The latest Supervisor that supports R17 is R18 MA_20 and is available on the support.avaya.com site. R17 LA_31 is the latest R17 release, R18 MA_20 is the latest release that supports R17 CMS. Description: 12-December-2016- This PCN announces the availability of CMS R17 R6 14-December-2015 - This PCN announces the availability of CMS R17 R5 09-February-2015 - This PCN announces the availability of CMS R17 R4 21-July-2014 - This PCN announces the availability of the CMS Supervisor Mobile App. 02-June-2014 - This PCN announces the availability of CMS R17 R3 Bug fix descriptions are in the Release Notes for CMS R17 R3 04 Nov 2013 - This PCN announces the availability of CMS R17 R2 All Bug fixes are in the Release Notes for CMS R17 R2 Level of Class 2 Risk/Severity Class 1=High Class 2=Medium PCN Template Rev.121216 Avaya – Proprietary & Confidential. Page 1 of 18 © 2012 Avaya Inc. All Rights Reserved. Use pursuant to the terms of signed agreements or Avaya All trademarks identified by the ® or TM are policy. All other trademarks are the property of their owners. registered trademarks or trademarks, respectively, of Avaya Inc. Product Correction Notice # 1906S Class 3=Low Is it required Highly Recommended that this PCN be applied to my system? The risk if this The customer will not receive the benefit of new bug fixes. PCN is not installed: Is this PCN for Both US customers, non-US customers, or both? Does applying Yes, for more details see the Release Notes. this PCN disrupt my service during installation? Installation of New installations of CMS require Avaya installation at current per incident rates. this PCN is required by: Release notes The Release Notes are posted on http://support.avaya.com under the “CMS” product. and workarounds The Release Notes include detailed information on bug fixes and Solaris patches. are located: What materials See “Required Materials” above. are required to implement this PCN (If PCN can be customer installed): How do I order Avaya U.S. Direct Customers: Customers are to contact the Avaya Global Support Services (GSS) @ 1- this PCN 800-242-2121 to request the PCN. (If PCN can be customer Avaya U.S. BusinessPartners: Business Partners are to contact the Avaya Dealer Desk @ 800-222- installed): 7278, prompt 1, to order the PCN material outlined in this PCN notice. Avaya Non-U.S.: Non-U.S. customers are to contact their Regional Support Center. PCN Template Rev.121216 Avaya – Proprietary & Confidential. Page 2 of 18 © 2012 Avaya Inc. All Rights Reserved. Use pursuant to the terms of signed agreements or Avaya All trademarks identified by the ® or TM are policy. All other trademarks are the property of their owners. registered trademarks or trademarks, respectively, of Avaya Inc. Product Correction Notice # 1906S Virtual CMS Customers: Refer to Deploying Avaya Call Management System in an Avaya Customer Experience Virtualized Environment on http://support.avaya.com. Finding the This PCN is Customer Installable. Installation by Avaya is billable at current per incident rates. installation instructions When moving to a new R17 load, schedule downtime for installation and consult the information below (If PCN can to determine the proper upgrade process to follow: be customer Use the Platform upgrade process to: installed): to move from unsupported to supported R17 platforms. Please note that R17 supported platforms are T5120 4-core, T5120 8-core, T5220 8-core, T4-1, NetraX4270, Dell R620, Dell R720, Dell 730, and HP DL380P G8. Use the CUE upgrade process to: to move from supported 16.x loads to R17 Please note that the CUE upgrade process must be performed by Avaya Professional Services or authorized Business Partner. CUE upgrade by Avaya is billable at current per incident rates. Use the Base Load Upgrade process and document to: upgrade Avaya Call Management System (CMS) from an older CMS Release R17 base load to a newer CMS R17 load. If your upgrade does NOT fit one of these scenarios, consult the “Upgrade Paths” section in the CMS Change Description document for more information on upgrading from CMS releases prior to R16. This PCN 147307-14, Sun System Firmware 7.4.9, specific to Oracle T5120 and T5220 platforms includes 152059-06, Sun System Firmware 8.8.1.d, specific to Oracle SPARC T4-1 platforms these SPARC FW/OBP Patches This PCN 147307-14 152059-06 124149-16 119963-34 119966-02 120812-32 includes 126868-05 119254-93 138215-02 148043-03 146696-05 125555-16 these Solaris 142373-04 125279-06 125719-56 125725-03 140796-01 120272-39 SPARC patches: 138866-03 125731-12 127872-02 136893-02 119059-71 128298-02 137147-07 137321-03 120410-37 121095-05 121487-02 121734-14 142933-05 147442-02 147147-26 147143-17 146288-03 148023-05 147272-01 122212-46 123015-02 123132-02 123647-05 124399-04 119213-33 126363-10 126365-19 148881-03 120719-07 119812-19 120460-21 124393-11 124457-03 124628-16 118712-24 120753-16 118683-15 118718-07 140899-01 141016-01 139555-08 119246-42 119252-35 119278-48 119280-26 119286-03 119317-01 119397-11 119534-33 119757-37 119538-20 119906-21 144872-03 120199-21 119900-18 120201-07 142244-02 144047-01 124630-72 149057-01 125533-18 146075-01 142044-01 138096-02 138645-01 138649-01 PCN Template Rev.121216 Avaya – Proprietary & Confidential. Page 3 of 18 © 2012 Avaya Inc. All Rights Reserved. Use pursuant to the terms of signed agreements or Avaya All trademarks identified by the ® or TM are policy. All other trademarks are the property of their owners. registered trademarks or trademarks, respectively, of Avaya Inc. Product Correction Notice # 1906S 138766-01 139774-01 144186-02 139962-02 143609-04 139968-01 149498-01 142251-02 139976-01 139980-01 137080-07 137097-02 146694-02 149217-02 142529-01 142911-01 139989-02 140081-01 147793-20 147797-05 140404-01 140790-02 140792-01 140860-02 140905-02 140907-01 140912-03 142292-01 142394-01 142340-02 141444-09 141548-01 141032-01 141496-01 142240-01 148029-01 142397-01 142428-02 142430-01 144526-03 148336-02 147023-01 142909-17 144500-19 150529-01 147438-06 148027-06 148049-04 118777-19 141558-01 148985-02 138647-01 139520-02 124188-03 148035-11 143502-01 143506-11 123611-05 143733-03 149277-01 144180-02 144188-02 149622-04 145120-01 144742-02 143962-04 144909-03 148237-01 145648-07 146673-01 146679-01 147799-03 148031-05 147227-01 147217-04 148071-19 151912-06 119783-36 143725-08 148104-25 148112-02 148340-06 149061-02 148002-01 148004-01 148241-07 148322-14 148342-10 148383-01 148403-01 149171-02 148419-03 148423-01 148559-16 148627-02 148561-11 148565-01 148309-06 148693-01 148768-02 148870-01 150435-04 150510-03 148888-05 148948-01 148975-01 148045-04 149112-02 149149-01 149163-01 149165-01 149638-05 146582-05 149646-03 150025-01 150107-03 150113-03 150123-02 150119-04 150157-01 150173-05 150312-07 150180-02 150307-01 150310-03 150311-09 150383-15 150400-41 149167-07 149175-11 149173-08 149279-04 149496-02 150031-17 150032-01 150535-01 150537-01 150539-01 150545-02 150631-03 150832-13 150836-02 150912-01 151074-05 151148-01 151615-03 151696-01 151721-01 151914-07 151355-01 151561-01 145122-03 145923-03 148873-02 147010-01 118676-04 152083-01 150121-01 152260-01 152264-01 152363-01 118666-86 152076-21 152077-21 151672-03 This PCN 119255-93 138216-02 148337-01 119253-38 146697-05 142252-02 includes 125556-15 118668-86 118677-04 120720-07 140861-02 119281-26 these Solaris 119535-33 119813-21 120754-16 119961-16 119901-16 119758-37 x86 patches 122213-46 123614-02 125534-18 120461-21 119907-21 121735-14 123016-02 123133-02 120202-08 119060-70 119247-42 119398-10 119214-33 123612-06 119279-49 120273-41 119964-34 125720-67 125726-03 121096-05 123648-05 124400-05 124394-11 125732-12 125907-02 126364-10 127873-02 136894-02 124631-72 126869-05 137081-07 137098-02 124629-17 120200-21 137148-07 137322-03 138097-02 140791-02 140913-03 148076-18 142934-05 142089-03 145123-03 145924-03 147443-02 147148-26 148036-11 146076-01 PCN Template Rev.121216 Avaya – Proprietary & Confidential.
Recommended publications
  • Enchant 1300

    Enchant 1300

    ENCHANT 1300 Quick Start Guide For more information, please visit harmankardon.com / 1. WHAT’S IN THE BOX Soundbar Remote Control VOL Power Cables* HDMI Cable AUX cable Optical Cable (4ft, 1200mm) (4ft, 1200mm) (4ft, 1200mm) (4ft, 1200mm) Wall-Mount Brackets Product Information & Wall-mounted guide * Power cable quantities vary by region / 2. PLACE YOUR SOUNDBAR 2a. Place the soundbar on the table TV 2B. Wall mount the soundbar Use tape to stick the wall-mounted paper guide on the wall, push a pen tip through the center to mark the wall-mounted bracket location and remove the paper. 1 TV WALLMOUNTED PAPER GUIDE Using the appropriate anchors, screw the wall mount brackets on the pen mark; Fix the screws at the back of soundbar; then hook the soundbar on the wall. 3 2 x3 4 TV / 3. CONNECT YOUR SOUNDBAR 3a. Connect to your TV Option 1 (Best): HDMI TV HDMI OUT HDMI (ARC) (TV ARC) Option 2: OPTICAL TV OPTICAL OUT OPTICAL IN 3b. Connect to other devices HDMI 1 HDMI 2 HDMI 3 HDMI OUT / 4. POWER YOUR SYSTEM 1 2 3 After the power cord is plugged in, the soundbar will take about 30 seconds to start up and then will enter standby mode, ready to use. / 5. CONNECT TO WI-FI 1 2 3 HK ENCHANT 1300 Once the soundbar connects to the internet for the first time, it may detect a software update to improve performance. This update may take a few minutes to complete. / 6. CONTROL YOUR SOUNDBAR 6a. Top Panel Volume Volume Power Down Up Source Display 6b.
  • Designing and Packaging Printer and Scanner Drivers

    Designing and Packaging Printer and Scanner Drivers

    Designing and Packaging Printer and Scanner Drivers OpenPrinting MC on Linux Plumbers 2020 August 28, 2020 Till Kamppeter, OpenPrinting What we had ● Printer drivers – PPD files – Filters, perhaps also backends – All has to be in CUPS-specific directories ● Scanner drivers – Shared libraries with SANE ABI in SANE-specific directories ● Packaging – Binaries were built specific to destination distro and packaged in DEB or RPM packages – For each distro drivers need to be built, packaged, and tested separately – As files need to be in specific directories drivers cannot be installed with CUPS in a Snap or with scanning user applications in Snaps What we want ● Sandboxed packaging – Snaps – Distribution-independent: Install from Snap Store on any distro running snapd – More security: Every package with all its libraries and files in its own sandbox, fine-grained control for communication between packages – All-Snap distributions ● But – You cannot drop driver files into directories of a snapped CUPS or snapped user applications, Snaps do not see the system’s files – Snaps only communicate via IP or D-Bus, not by files ● Also – CUPS is deprecating support for PPD files, working by itself only in driverless IPP mode. The New Architecture ● Printer/Scanner Applications emulating an IPP device – Easily snappable: Communicates only via IP – Multi-function device support, Printing, Scanning, and Fax Out can be done in one Snap/Application – Web admin interface for vendor/device-specific GUI – Behaves like a network printer/scanner/multi-function
  • Desktop Migration and Administration Guide

    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.
  • Mdns/Dns-Sd Tutorial

    Mdns/Dns-Sd Tutorial

    MDNS/DNS-SD TUTORIAL In this tutorial, we will describe how to use mDNS/DNS-SD on Raspberry Pi. mDNS/DNS-SD is a protocol for service discovery in a local area network. It is standardized under RFCs 6762 [1] and 6763[2]. The protocol is also known by the Bonjour trademark by Apple, or Zeroconf. On Linux, it is implemented in the avahi package. [1] http://tools.ietf.org/html/rfc6762 [2] http://tools.ietf.org/html/rfc6763 About mDNS/DNS-SD There are several freely available implementations of mDNS/DNS-SD: 1. avahi – Linux implementation (http://www.avahi.org/) 2. jmDNS – Java implementation (http://jmdns.sourceforge.net/) 3. Bonjour – MAC OS (installed by default) 4. Bonjour – Windows (https://support.apple.com/kb/DL999?locale=en_US) During this course, we will use only avahi. However, any of the aforementioned implementations are compatible. Avahi installation avahi is available as a package for Raspbian. Install it with: sudo apt-get install avahi-deamon avahi-utils Avahi usage avahi-daemon is the main process that takes care of proper operation of the protocol. It takes care of any configuration of the interfaces and network messaging. A user can control the deamon with command line utilities, or via D-Bus. In this document, we will describe the former option. For the latter one, please see http://www.avahi.org/wiki/Bindings. Publishing services avahi-publish-service is the command for publishing services. The syntax is: avahi-publish-service SERVICE-NAME _APPLICATION- PROTOCOL._TRANPOSRT-PROTOCOL PORT “DESCRIPTION” --sub SUBPROTOCOL For instance, the command: avahi-publish-service light _coap._udp 5683 “/mylight” --sub _floor1._sub._coap._udp will publish a service named ‘light’, which uses the CoAP protocol over UDP on port 5683.
  • Reverse Engineering Power Management on NVIDIA Gpus - Anatomy of an Autonomic-Ready System Martin Peres

    Reverse Engineering Power Management on NVIDIA Gpus - Anatomy of an Autonomic-Ready System Martin Peres

    Reverse Engineering Power Management on NVIDIA GPUs - Anatomy of an Autonomic-ready System Martin Peres To cite this version: Martin Peres. Reverse Engineering Power Management on NVIDIA GPUs - Anatomy of an Autonomic-ready System. ECRTS, Operating Systems Platforms for Embedded Real-Time appli- cations 2013, Jul 2013, Paris, France. hal-00853849 HAL Id: hal-00853849 https://hal.archives-ouvertes.fr/hal-00853849 Submitted on 23 Aug 2013 HAL is a multi-disciplinary open access L’archive ouverte pluridisciplinaire HAL, est archive for the deposit and dissemination of sci- destinée au dépôt et à la diffusion de documents entific research documents, whether they are pub- scientifiques de niveau recherche, publiés ou non, lished or not. The documents may come from émanant des établissements d’enseignement et de teaching and research institutions in France or recherche français ou étrangers, des laboratoires abroad, or from public or private research centers. publics ou privés. Reverse engineering power management on NVIDIA GPUs - Anatomy of an autonomic-ready system Martin Peres Ph.D. student at LaBRI University of Bordeaux Hobbyist Linux/Nouveau Developer Email: [email protected] Abstract—Research in power management is currently limited supported nor documented by NVIDIA. As GPUs are leading by the fact that companies do not release enough documentation the market in terms of performance-per-Watt [3], they are or interfaces to fully exploit the potential found in modern a good candidate for a reverse engineering effort of their processors. This problem is even more present in GPUs despite power management features. The choice of reverse engineering having the highest performance-per-Watt ratio found in today’s NVIDIA’s power management features makes sense as they processors.
  • High Speed Visualization in the Jetos Aviation Operating System Using Hardware Acceleration*

    High Speed Visualization in the Jetos Aviation Operating System Using Hardware Acceleration*

    High Speed Visualization in the JetOS Aviation Operating System Using Hardware Acceleration* Boris Barladian[0000-0002-2391-2067], Nikolay Deryabin[0000-0003-1248-6047], Alexey Voloboy[0000-0003-1252-8294], Vladimir Galaktionov[0000-0001-6460-7539], and Lev Shapiro[0000-0002-6350-851X] The Keldysh Institute of the Applied Mathematics of RAS, Moscow, Russia [email protected],{voloboy, vlgal, pls}@gin.keldysh.ru Abstract. The paper discusses details of the pilot display visualization that uses the hardware acceleration capabilities of the Vivante graphics processor in the JetOS aviation operating system. Previously the OpenGL Safety Critical library was implemented without hardware acceleration. This was done in such a way because software library is easier to certify in accordance with the avionics re- quirements. But usage of the software OpenGL does not provide acceptable visualization speed for modern Flight Display and 3D relief applications. So more complex visualization approach utilized the GPU acceleration capabilities was elaborated. Although the OpenGL library was implemented for a specific GPU and took into account its specificity, the described approach to adapt the MESA open source library can be used for other GPUs. An effective algorithm for multi-window visualization using the implemented library with hardware acceleration is present. The described approach allows you to achieve the visu- alization speed acceptable for the pilot display of the aircraft. Keywords: Pilot Display, Embedded Systems, Real-time Operating System, OpenGL Safety Critical, Multi-windowing. 1 Introduction In [1] requirements were formulated for a real-time operating system (RTOS) de- signed to work with integrated modular avionics. In particular, the RTOS should comply with the ARINC 653 standard [2].
  • Veritas Netbackup™ Virtual Appliance Documentation

    Veritas Netbackup™ Virtual Appliance Documentation

    Veritas NetBackup™ Virtual Appliance Documentation Release 3.1.2 Veritas NetBackup™ Virtual Appliance 3.1.2 Documentation Legal Notice Copyright © 2019 Veritas Technologies LLC. All rights reserved. Veritas, the Veritas Logo, and NetBackup are trademarks or registered trademarks of Veritas Technologies LLC or its affiliates in the U.S. and other countries. Other names may be trademarks of their respective owners. This product may contain third-party software for which Veritas is required to provide attribution to the third party (“Third-party Programs”). Some of the Third-party Programs are available under open source or free software licenses. The License Agreement accompanying the Software does not alter any rights or obligations you may have under those open source or free software licenses. Refer to the Third-party Legal Notices document accompanying this Veritas product or available at: https://www.veritas.com/about/legal/license-agreements The product described in this document is distributed under licenses restricting its use, copying, distribution, and decompilation/reverse engineering. No part of this document may be reproduced in any form by any means without prior written authorization of Veritas Technologies LLC and its licensors, if any. THE DOCUMENTATION IS PROVIDED "AS IS" AND ALL EXPRESS OR IMPLIED CONDITIONS, REPRESENTATIONS AND WARRANTIES, INCLUDING ANY IMPLIED WARRANTY OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE OR NON-INFRINGEMENT, ARE DISCLAIMED, EXCEPT TO THE EXTENT THAT SUCH DISCLAIMERS ARE HELD TO BE LEGALLY INVALID. VERITAS TECHNOLOGIES LLC SHALL NOT BE LIABLE FOR INCIDENTAL OR CONSEQUENTIAL DAMAGES IN CONNECTION WITH THE FURNISHING, PERFORMANCE, OR USE OF THIS DOCUMENTATION. THE INFORMATION CONTAINED IN THIS DOCUMENTATION IS SUBJECT TO CHANGE WITHOUT NOTICE.
  • Linux Sound Subsystem Documentation Release 4.13.0-Rc4+

    Linux Sound Subsystem Documentation Release 4.13.0-Rc4+

    Linux Sound Subsystem Documentation Release 4.13.0-rc4+ The kernel development community Sep 05, 2017 CONTENTS 1 ALSA Kernel API Documentation 1 1.1 The ALSA Driver API ............................................ 1 1.2 Writing an ALSA Driver ........................................... 89 2 Designs and Implementations 145 2.1 Standard ALSA Control Names ...................................... 145 2.2 ALSA PCM channel-mapping API ..................................... 147 2.3 ALSA Compress-Offload API ........................................ 149 2.4 ALSA PCM Timestamping ......................................... 152 2.5 ALSA Jack Controls ............................................. 155 2.6 Tracepoints in ALSA ............................................ 156 2.7 Proc Files of ALSA Drivers ......................................... 158 2.8 Notes on Power-Saving Mode ....................................... 161 2.9 Notes on Kernel OSS-Emulation ..................................... 161 2.10 OSS Sequencer Emulation on ALSA ................................... 165 3 ALSA SoC Layer 171 3.1 ALSA SoC Layer Overview ......................................... 171 3.2 ASoC Codec Class Driver ......................................... 172 3.3 ASoC Digital Audio Interface (DAI) .................................... 174 3.4 Dynamic Audio Power Management for Portable Devices ...................... 175 3.5 ASoC Platform Driver ............................................ 180 3.6 ASoC Machine Driver ............................................ 181 3.7 Audio Pops
  • The Interplay of Compile-Time and Run-Time Options for Performance Prediction Luc Lesoil, Mathieu Acher, Xhevahire Tërnava, Arnaud Blouin, Jean-Marc Jézéquel

    The Interplay of Compile-Time and Run-Time Options for Performance Prediction Luc Lesoil, Mathieu Acher, Xhevahire Tërnava, Arnaud Blouin, Jean-Marc Jézéquel

    The Interplay of Compile-time and Run-time Options for Performance Prediction Luc Lesoil, Mathieu Acher, Xhevahire Tërnava, Arnaud Blouin, Jean-Marc Jézéquel To cite this version: Luc Lesoil, Mathieu Acher, Xhevahire Tërnava, Arnaud Blouin, Jean-Marc Jézéquel. The Interplay of Compile-time and Run-time Options for Performance Prediction. SPLC 2021 - 25th ACM Inter- national Systems and Software Product Line Conference - Volume A, Sep 2021, Leicester, United Kingdom. pp.1-12, 10.1145/3461001.3471149. hal-03286127 HAL Id: hal-03286127 https://hal.archives-ouvertes.fr/hal-03286127 Submitted on 15 Jul 2021 HAL is a multi-disciplinary open access L’archive ouverte pluridisciplinaire HAL, est archive for the deposit and dissemination of sci- destinée au dépôt et à la diffusion de documents entific research documents, whether they are pub- scientifiques de niveau recherche, publiés ou non, lished or not. The documents may come from émanant des établissements d’enseignement et de teaching and research institutions in France or recherche français ou étrangers, des laboratoires abroad, or from public or private research centers. publics ou privés. The Interplay of Compile-time and Run-time Options for Performance Prediction Luc Lesoil, Mathieu Acher, Xhevahire Tërnava, Arnaud Blouin, Jean-Marc Jézéquel Univ Rennes, INSA Rennes, CNRS, Inria, IRISA Rennes, France [email protected] ABSTRACT Both compile-time and run-time options can be configured to reach Many software projects are configurable through compile-time op- specific functional and performance goals. tions (e.g., using ./configure) and also through run-time options (e.g., Existing studies consider either compile-time or run-time op- command-line parameters, fed to the software at execution time).
  • The GNOME Census: Who Writes GNOME?

    The GNOME Census: Who Writes GNOME?

    The GNOME Census: Who writes GNOME? Dave Neary & Vanessa David, Neary Consulting © Neary Consulting 2010: Some rights reserved Table of Contents Introduction.........................................................................................3 What is GNOME?.............................................................................3 Project governance...........................................................................3 Why survey GNOME?.......................................................................4 Scope and methodology...................................................................5 Tools and Observations on Data Quality..........................................7 Results and analysis...........................................................................10 GNOME Project size.......................................................................10 The Long Tail..................................................................................11 Effects of commercialisation..........................................................14 Who does the work?.......................................................................15 Who maintains GNOME?................................................................17 Conclusions........................................................................................22 References.........................................................................................24 Appendix 1: Modules included in survey...........................................25 2 Introduction What
  • State of Linux Audio in 2009 Linux Plumbers Conference 2009

    State of Linux Audio in 2009 Linux Plumbers Conference 2009

    State of Linux Audio in 2009 Linux Plumbers Conference 2009 Lennart Poettering [email protected] September 2009 Lennart Poettering State of Linux Audio in 2009 Who Am I? Software Engineer at Red Hat, Inc. Developer of PulseAudio, Avahi and a few other Free Software projects http://0pointer.de/lennart/ [email protected] IRC: mezcalero Lennart Poettering State of Linux Audio in 2009 Perspective Lennart Poettering State of Linux Audio in 2009 So, what happened since last LPC? Lennart Poettering State of Linux Audio in 2009 RIP: EsounD is officially gone. Lennart Poettering State of Linux Audio in 2009 (at least on Fedora) RIP: OSS is officially gone. Lennart Poettering State of Linux Audio in 2009 RIP: OSS is officially gone. (at least on Fedora) Lennart Poettering State of Linux Audio in 2009 Audio API Guide http://0pointer.de/blog/projects/guide-to-sound-apis Lennart Poettering State of Linux Audio in 2009 We also make use of high-resolution timers on the desktop by default. We now use realtime scheduling on the desktop by default. Lennart Poettering State of Linux Audio in 2009 We now use realtime scheduling on the desktop by default. We also make use of high-resolution timers on the desktop by default. Lennart Poettering State of Linux Audio in 2009 2s Buffers Lennart Poettering State of Linux Audio in 2009 Mixer abstraction? Due to user-friendliness, i18n, meta data (icons, ...) We moved a couple of things into the audio server: Timer-based audio scheduling; mixing; flat volume/volume range and granularity extension; integration of volume sliders; mixer abstraction; monitoring Lennart Poettering State of Linux Audio in 2009 We moved a couple of things into the audio server: Timer-based audio scheduling; mixing; flat volume/volume range and granularity extension; integration of volume sliders; mixer abstraction; monitoring Mixer abstraction? Due to user-friendliness, i18n, meta data (icons, ...) Lennart Poettering State of Linux Audio in 2009 udev integration: meta data, by-path/by-id/..
  • VNC User Guide 7 About This Guide

    VNC User Guide 7 About This Guide

    VNC® User Guide Version 5.3 December 2015 Trademarks RealVNC, VNC and RFB are trademarks of RealVNC Limited and are protected by trademark registrations and/or pending trademark applications in the European Union, United States of America and other jursidictions. Other trademarks are the property of their respective owners. Protected by UK patent 2481870; US patent 8760366 Copyright Copyright © RealVNC Limited, 2002-2015. All rights reserved. No part of this documentation may be reproduced in any form or by any means or be used to make any derivative work (including translation, transformation or adaptation) without explicit written consent of RealVNC. Confidentiality All information contained in this document is provided in commercial confidence for the sole purpose of use by an authorized user in conjunction with RealVNC products. The pages of this document shall not be copied, published, or disclosed wholly or in part to any party without RealVNC’s prior permission in writing, and shall be held in safe custody. These obligations shall not apply to information which is published or becomes known legitimately from some source other than RealVNC. Contact RealVNC Limited Betjeman House 104 Hills Road Cambridge CB2 1LQ United Kingdom www.realvnc.com Contents About This Guide 7 Chapter 1: Introduction 9 Principles of VNC remote control 10 Getting two computers ready to use 11 Connectivity and feature matrix 13 What to read next 17 Chapter 2: Getting Connected 19 Step 1: Ensure VNC Server is running on the host computer 20 Step 2: Start VNC