Compproj:311 - SL7 DICE Environment

Total Page:16

File Type:pdf, Size:1020Kb

Compproj:311 - SL7 DICE Environment SL7DICEEnvironment < DICE < TWiki https://wiki.inf.ed.ac.uk/DICE/SL7DICEEnvironment TWiki > DICE Web > ResearchAndTeachingUnit > SL7DICEEnvironment (04 Mar 2015, GrahamDutton) CompProj:311 - SL7 DICE Environment Project homepage for porting of the DICE environment software packages to the LCFG SL7 platform. The Observations section is also (occasionally!) updated. This page was referred to during the SL7Meeting20150106. CompProj:311 - SL7 DICE Environment 2015-02-22 - Alpine gripes 2015-02-19 - Display blanking 2015-02-18 - Switch flipped! 2015-02-18 - Development meeting talk 2015-02-10 - Towards a usable desktop 2015-01-27 - "Remaining" Tasks 2015-01-25 - New environment package lists 20 Nov 2014 - More login ramblings 12 Nov 2014 - Update 09 Nov 2014 - The Display Manager 07 Nov 2014 - More notes 04 Nov 2014 — Observations on SL7 so far 07 Oct 2014 - Notes on KDE 29 Sep 2014 - Proposal 24 Sep 2014 - discussion 1. What is the _env list for? 2. What constitutes "environment"? 2015-02-22 - Alpine gripes A roundup of two irritating issues with alpine ("updated" to 2.11 but I haven't checked its provenance yet; this is not a release from the original UW maintainers) as I found it on SL7: The packaged "default" speller hunspell (actually an RPM dependency), seems very poor in its default mode of operation. It's tripping over contractions and all sorts of words it should be able to avoid (and the SL6 speller has no problem with). attempts to open links in my web browser of choice (a custom w3m wrapper) fail because apparently the $HOME in my mailcap file (alpine uses mailcap's text/html entry) isn't being evaluated any more. Easily fixed but a strange change of behaviour. 2015-02-19 - Display blanking Investigated one case where a desktop display wouldn't sleep of its own accord (we won't be running a screensaver on the lightdm greeter, but we'd still expect displays to power down on machines that don't sleep). It appears that the X DPMS library was lying to us, or being lied to by the monitor, which claimed to be off (state "3"). Explicitly setting it back on (state 0) caused everything to work again as it should. I couldn't see any root cause, but noticed an EDID error in the system log. If anyone spots this behaviour on an SL7 machine, just get in touch. I'd rather we found and fixed the problem than had to deploy anything ... 2015-02-18 - Switch flipped! Apologies for the delay. Customisable login screens are here. Good sources of information on the customisation setup: $ man lcfg-webpic <dice/options/webpic.h> by "default" I've gone with an image of my own creation but I anticipate different sites / labs / machines functions will take advantage of the customisation. Exam PCs and "kiosk" machines, for example, will require custom setups. Remember that these values can all use LCFG template interpolation so it would be straightforward to advertise, for 1 of 8 02/11/16 18:17 SL7DICEEnvironment < DICE < TWiki https://wiki.inf.ed.ac.uk/DICE/SL7DICEEnvironment example, which groups of users were permitted to log into a given machine. Added summary documentation at LoginScreens (authoritative webpic documentation will of course remain with the component). Notes about dice-getres: Note that there's a possible bootstrapping problem in the use of getres to provide background resolution: if lightdm starts before webpic no background will have been configured, and if webpic starts before the lightdm X session, there's a possibility no resolution can be determined and the component might either fail or fall back to default resolution. We'll see how bad this is in practice before investing any effort to fix it given that, either way, it can be solved with a single reconfigure. This could be related to Bug:847 but, no surprise, more investigation is required. A possible (extreme) solution would be to call webpic as part of the lightdm pre-greeter script, dissolving the webpic component into lightdm. 2015-02-18 - Development meeting talk Some outline points for today's talk. Package lists These are mostly (all?) in place. I'll explain which ones are where, what they're for, how to choose between them. devel package sets new rules for devel packages, and how to access them. Package list inclusion and why this isn't part of this project, but more of a negotiation with machine managers. When not to use package lists Where else to look before resorting to one. Pending changes to the workflow This includes streamlined "yummy" list generation and an as-yet undefined process for promoting packages to option sets. Suggestions? This has been designed so far towards RAT workflow, but we're not the only ones adding packages. If we rattle through the above I can talk about some of the side tasks attached to this project. Login screen: lcfg-webpic and included tools rasterize.js, getres update: documented in LoginScreens Alternative window managers: MATE, wmii, fvwm2, and the use of xscreensaver and idle_curiosity. bash default .rc names: again, this is a discussion first and foremost. already discussed: .brc remains (but .bashrc is supported!) There is outstanding work attached to X config including .xinit infrastructure (including the screensaver and idle_curiosity) and wmii/fvwm2 default config. UPDATE: points raised during the talk: building custom bash: RAT need to rebuild "our" bash patches for SL7. Or rather include them: I reckon I built the package some time ago... Subversion the version mismatch is getting annoying for those of us straddling operating systems. I'll deploy svn-1.7 to SL6 machines after a sys-announce notice period. Alternative WMs we should document Gnome → MATE and other alternatives. Don't forget Cinnamon would be a nice extra alternative in addition to MATE. Liaise with Alastair about enforcing / encouraging xscreensaver on other desktop managers I need to export my handy yumtopklist script into the utils directory (I realise now I was hoping to add partitioning by package source, first) this is done. Other packages: missing the cosignego stack. 2015-02-10 - Towards a usable desktop Since last update... 2 of 8 02/11/16 18:17 SL7DICEEnvironment < DICE < TWiki https://wiki.inf.ed.ac.uk/DICE/SL7DICEEnvironment Package lists have been tweaked and streamlined, and the rules for their use improved, though this hasn't been heavily tested yet. The -devel package lists have been moved into the env lists, with instructions to add the packges wherever possible. Plenty of new "base" packages added to the environment lists as appropriate. This is of course ongoing and we're currently investigating problems with pidgin and SASL/GSSAPI authentication against the Informatics XMPP server (everything else seems to work(!)) The MATE environment has been added as an alternative desktop/WM. fvwm2 is soon to join them. The lcfg-webpic component has been completed, allowing fully dynamic control of the lightdm greeter's appearance. A major goal of this development was to allow "unusual" configurations to take advantage of alternative login screens without the effort involved in SL6, for example on lab exam desktops. However in addition to this the dynamic nature of the component (allowing full content control from LCFG, local file or even web if required) means it can have much wider utility, for example displaying lab status or site information. A last-minute addition to the lcfg-webpic infrastructure is the dice-getres utility which retrieves the resolution of the primary display so that background images can be presented correctly at (theoretically) any resolution. Progress on the sleep-compatibility of non-standard desktop environments continues as part of the idle_curiosity project. Numerious other little tweaks here and there... Also since the last update I'm attempting to change the way effort is reported against this project, so I'm trying to attribute even tenuous, tangential development effort against the SL7 project if at all possible. 2015-01-27 - "Remaining" Tasks The bulk of the blocking work has now been done, so I ought to recap what remains. Not all of this falls strictly under the remit of this project so I'll link to alternative tracking sources where they become apparent. Guidance documentation on where to add packages - the new package lists aren't the only / best place to add optional packages. Actually adding packages! This will be done under guidance from RAT or the documentation as above. Yummy modifications to support generation of the package lists. Mechanism to produce rpms lists from yummy files - in consultation with MPU. ~Mechanism for delivery of devel packages: this will depend on the above mechanism.~ ~Additional options for window management~ Compatibility of non-standard desktop environments with sleep [this is definitely off-project but part of some ongoing CPD] 2015-01-25 - New environment package lists I'll talk more about the rationale as part of the next update, but in collaboration with Stephen I've reworked the SL7 environment lists and made plans for the next stage to ease management. I removed most of the provisional env lists which had been put in place: REMOVED dice_el7_*.rpms : we don't need to handle any difference between SL7 and EL7 at the DICE layer. Should we require it, I'd propose renaming each SL7 file to its EL7 equivalent and using a simple #include in the SL7 file to manage only the differences. REMOVED dice_[es]l7_desktop.rpms : we no longer want to have a definition of "desktop" at the package list level. This should live at the header level, allowing each type of machine to pick package lists as appropriate REMOVED dice_[es]l7_env.rpms : the env list has been heavily abused.
Recommended publications
  • Ubuntu Kung Fu
    Prepared exclusively for Alison Tyler Download at Boykma.Com What readers are saying about Ubuntu Kung Fu Ubuntu Kung Fu is excellent. The tips are fun and the hope of discov- ering hidden gems makes it a worthwhile task. John Southern Former editor of Linux Magazine I enjoyed Ubuntu Kung Fu and learned some new things. I would rec- ommend this book—nice tips and a lot of fun to be had. Carthik Sharma Creator of the Ubuntu Blog (http://ubuntu.wordpress.com) Wow! There are some great tips here! I have used Ubuntu since April 2005, starting with version 5.04. I found much in this book to inspire me and to teach me, and it answered lingering questions I didn’t know I had. The book is a good resource that I will gladly recommend to both newcomers and veteran users. Matthew Helmke Administrator, Ubuntu Forums Ubuntu Kung Fu is a fantastic compendium of useful, uncommon Ubuntu knowledge. Eric Hewitt Consultant, LiveLogic, LLC Prepared exclusively for Alison Tyler Download at Boykma.Com Ubuntu Kung Fu Tips, Tricks, Hints, and Hacks Keir Thomas The Pragmatic Bookshelf Raleigh, North Carolina Dallas, Texas Prepared exclusively for Alison Tyler Download at Boykma.Com Many of the designations used by manufacturers and sellers to distinguish their prod- ucts are claimed as trademarks. Where those designations appear in this book, and The Pragmatic Programmers, LLC was aware of a trademark claim, the designations have been printed in initial capital letters or in all capitals. The Pragmatic Starter Kit, The Pragmatic Programmer, Pragmatic Programming, Pragmatic Bookshelf and the linking g device are trademarks of The Pragmatic Programmers, LLC.
    [Show full text]
  • Annual Report 2006
    Annual Report 2006 Table of contents Foreword Letter from the Chairman, Dave Neary 4–5 A year in review 2006—a year in GNOME 8–10 Distributions in 2006 11 Events and community initiatives GUADEC—The GNOME Conference 12–13 GNOME hackers descend on MIT Media Center 14–15 GNOME User Groups 16 The www.gnome.org revamp 17 GNOME platform 17 GNOME Foundation Administrator 17 Foundation development The Women’s Summer Outreach Program 18–20 The GNOME Mobile and Embedded Initiative 21 The GNOME Advisory Board 22–23 PHOTO The GNOME Foundation Board and Advisory Board members by David Zeuthen (continued on the inside back cover) GNOME Foundation 3 Dear Friends, All traditions need a starting point, they say. What you now hold in your hands is the first annual report of the GNOME Foundation, at the end of what has been an eventful year for us. Each year brings its challenges and rewards for the members of this global project. This year, many of our biggest challenges are in the legal arena. European countries have been passing laws to conform with the European Union Copyright Directive, and some, including France, have brought into law provisions which we as software developers find it hard to understand, but which appear to make much of what we do illegal. We have found our- selves in the center of patent wars as bigger companies jockey for position with offerings based on our hard work. And we are scratching our heads trying to figure out how to deal with the constraints of DRM and patents in multimedia, while still offering our users access to their media files.
    [Show full text]
  • Informe Tradución Ao Galego Do Contorno GNOME 3.0
    INFORME DE TRADUCIÓN AO GALEGO DO CONTORNO GNOME 3.0 ABRIL 2011 Oficina de Software Libre da USC www.usc.es/osl [email protected] LICENZA DO DOCUMENTO Este documento pode empregarse, modificarse e redistribuírse baixo dos termos de unha das seguintes licenzas, a escoller: GNU Free Documentation License 1.3 Copyright (C) 2009 Oficina de Software Libre da USC. Garántese o permiso para copiar, distribuír e/ou modificar este documento baixo dos termos da GNU Free Documentation License versión 1.3 ou, baixo o seu criterio, calquera versión posterior publicada pola Free Software Foundation; sen seccións invariantes, sen textos de portada e sen textos de contraportada. Pode achar o texto íntegro da licenza en: http://www.gnu.org/copyleft/fdl.html Creative Commons Atribución – CompartirIgual 3.0 Copyright (C) 2009 Oficina de Software Libre da USC. Vostede é libre de: • Copiar, distribuír e comunicar publicamente a obra • Facer obras derivadas Baixo das condicións seguintes: • Recoñecemento. Debe recoñecer os créditos da obra do xeito especificado polo autor ou polo licenciador (pero non de xeito que suxira que ten o seu apoio ou apoian o uso que fan da súa obra. • Compartir baixo a mesma licenza.. Se transforma ou modifica esta obra para crear unha obra derivada, só pode distribuír a obra resultante baixo a mesma licenza, unha similar ou unha compatíbel. Pode achar o texto íntegro da licenza en: http://creativecommons.org/licenses/by-sa/3.0/es/deed.gl TÁBOA DE CONTIDOS Licenza do documento............................................................................................................3
    [Show full text]
  • Lumina-DE: Redefining the Desktop Environment for Modern Hardware
    Lumina-DE: Redefining the Desktop Environment for Modern Hardware Author: Ken Moore [email protected] PC-BSD/iXsystems Lumina Desktop source repository: https://github.com/pcbsd/lumina Date: Nov 2014 Abstract: As computers continue to advance into every aspect of our daily lives through the pervasiveness of cell phones and tablets, the traditional “desktop computer” is gradually being shifted to a smaller subset of the total systems in use. This presents a problem for open source operating systems, as the available open source graphical environments are increasingly designed for systems with powerful hardware or traditional mouse/keyboard inputs – resulting in a much lower percentage of devices that are physically capable of utilitizing the OS. The open-source Lumina desktop environment is designed to solve these problems by meeting its goals of being a highly flexible and scalable interface that runs with relatively little hardware requirements. The project also provides a simple framework for integrating OS-specific functionality directly into the interface for ease-of-use without causing conflict with the underlying system or affecting portability. This paper will take a top-level view of the Lumina desktop project, breaking it down to its components, explaining the framework and methodology, and listing the work that is still yet to be completed to achieve its goals. Please note: for all intents and purposes, there is no distinction between laptops and box-based desktop computers when it comes to the capabilities and distinctions of a graphical interface, so for the purposes of this paper they will both be considered “desktop” systems. The Problem: Smartphones, tablets, laptops and desktop computers all utilitize graphical interfaces to provide the user access to the capabilities of the device, but laptops and desktop computers are the only ones with fully open source desktop environments available.
    [Show full text]
  • 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..........................
    [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]
  • Var/Www/Apps/Conversion/Tmp
    : gettext lvresize run_init ! gettextize lvs runlevel ./ gettext.sh lvscan running-circles [ gfortran lwp-download run-parts [[ ghostscript lwp-dump runuser ]] gif2tiff lwp-mirror rvi { gij lwp-request rview } gindxbib lwp-rget rvim a2p git lz s2p ab git-receive-pack lzcat sa abrt-backtrace git-shell lzcmp sadf abrt-cli git-upload-archive lzdiff safe_finger abrtd git-upload-pack lzegrep sandbox abrt-debuginfo-install gjar lzfgrep saned abrt-handle-upload gjarsigner lzgrep sane-find-scanner ac gkeytool lzless sar accept glibc_post_upgrade.x86_64 lzma saslauthd accton glookbib lzmadec sasldblistusers2 aclocal gls-dns-forward lzmainfo saslpasswd2 aclocal-1.11 gls-email-iptables lzmore saytime aconnect gls-grade-securevnc-backend lzop scanimage acpid gls-makebridge m4 scp acpi_listen gls-munge-grub magnifier script activation-client gls-munge-rootpw mail scriptreplay addftinfo gls-resetvm Mail scrollkeeper-config addgnupghome gls-vserver-network mailq scrollkeeper-extract addpart gls-vserver-network2 mailq.postfix scrollkeeper-gen-seriesid addr2line glxgears mailq.sendmail scrollkeeper-get-cl adduser glxinfo mailstat scrollkeeper-get-content-list agetty gmake mailstats scrollkeeper-get-extended-content-list alias gneqn mailx scrollkeeper-get-index-from-docpath alsactl gnome-about make scrollkeeper-get-toc-from-docpath alsa-info gnome-about-me MAKEDEV scrollkeeper-get-toc-from-id alsa-info.sh gnome-appearance-properties makedumpfile scrollkeeper-install alsamixer gnome-at-mobility makemap scrollkeeper-preinstall alsaunmute gnome-at-properties
    [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]
  • Release Notes for Debian 7.0 (Wheezy), S/390
    Release Notes for Debian 7.0 (wheezy), S/390 The Debian Documentation Project (http://www.debian.org/doc/) November 20, 2018 Release Notes for Debian 7.0 (wheezy), S/390 This document is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License, version 2, as published by the Free Software Foundation. This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details. You should have received a copy of the GNU General Public License along with this program; if not, write to the Free Software Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA. The license text can also be found at http://www.gnu.org/licenses/gpl-2.0.html and /usr/ share/common-licenses/GPL-2 on Debian. ii Contents 1 Introduction 1 1.1 Reporting bugs on this document . 1 1.2 Contributing upgrade reports . 1 1.3 Sources for this document . 2 2 What’s new in Debian 7.0 3 2.1 Supported architectures . 3 2.2 What’s new for S390? . 4 2.3 What’s new in the distribution? . 4 2.3.1 CDs, DVDs and BDs . 5 2.3.2 Multiarch . 5 2.3.3 Dependency booting . 5 2.3.4 systemd . 5 2.3.5 Multimedia . 5 2.3.6 Hardened security . 5 2.3.7 AppArmor . 6 2.3.8 The stable-backports section .
    [Show full text]
  • Fedora 7 Release Notes
    Fedora 7 Release Notes Fedora Documentation Project Copyright © 2007 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. All other trademarks are the property of their respective owners. Abstract 1. Welcome to Fedora ................................................................................................................ 3 2. Release Highlights .................................................................................................................. 4 2.1. Fedora Tour ................................................................................................................. 4 2.2.
    [Show full text]
  • Upgrade Issues
    Upgrade issues Graph of new conflicts libsiloh5-0 libhdf5-lam-1.8.4 (x 3) xul-ext-dispmua (x 2) liboss4-salsa-asound2 (x 2) why sysklogd console-cyrillic (x 9) libxqilla-dev libxerces-c2-dev iceape xul-ext-adblock-plus gnat-4.4 pcscada-dbg Explanations of conflicts pcscada-dbg libpcscada2-dev gnat-4.6 gnat-4.4 Similar to gnat-4.4: libpolyorb1-dev libapq-postgresql1-dev adacontrol libxmlada3.2-dev libapq1-dev libaws-bin libtexttools2-dev libpolyorb-dbg libnarval1-dev libgnat-4.4-dbg libapq-dbg libncursesada1-dev libtemplates-parser11.5-dev asis-programs libgnadeodbc1-dev libalog-base-dbg liblog4ada1-dev libgnomeada2.14.2-dbg libgnomeada2.14.2-dev adabrowse libgnadecommon1-dev libgnatvsn4.4-dbg libgnatvsn4.4-dev libflorist2009-dev libopentoken2-dev libgnadesqlite3-1-dev libnarval-dbg libalog1-full-dev adacgi0 libalog0.3-base libasis2008-dbg libxmlezout1-dev libasis2008-dev libgnatvsn-dev libalog0.3-full libaws2.7-dev libgmpada2-dev libgtkada2.14.2-dbg libgtkada2.14.2-dev libasis2008 ghdl libgnatprj-dev gnat libgnatprj4.4-dbg libgnatprj4.4-dev libaunit1-dev libadasockets3-dev libalog1-base-dev libapq-postgresql-dbg libalog-full-dbg Weight: 5 Problematic packages: pcscada-dbg hostapd initscripts sysklogd Weight: 993 Problematic packages: hostapd | initscripts initscripts sysklogd Similar to initscripts: conglomerate libnet-akamai-perl erlang-base screenlets xlbiff plasma-widget-yawp-dbg fso-config- general gforge-mta-courier libnet-jifty-perl bind9 libplack-middleware-session-perl libmail-listdetector-perl masqmail libcomedi0 taxbird ukopp
    [Show full text]
  • 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.
    [Show full text]