An Up-To-Date Look at Free Software and Its Makers

Total Page:16

File Type:pdf, Size:1020Kb

An Up-To-Date Look at Free Software and Its Makers LINUXCOVER USERSTORY SchlagwortSchlagwort sollte sollte hier hier stehen stehenFree Software Projects COMMUNITY An up-to-date look at free software and its makers PROJECTS ON THE MOVE Free software covers such a diverse range of utilities, applications, and other assorted projects that it can be hard to find the perfect tool. We pick the best of the bunch. This month we cover Yast2 for Debian, KDE 4, Bluetooth headsets, and the Debian project. BY MARTIN LOSCHWITZ ovell GPL’d the Yast2 configura- scratch would have involved a lot of Yast2 Qt GUI can be built on other Linux tion tool shortly after acquiring work. The Yast4Debian project is cur- systems without any trouble. Unfortu- NSuse. The Yast2 sources were rently porting the Yast2 version supplied nately, porting the other components is freely accessible prior to this change, but with Suse 9.1, although an upgrade to far less trivial. There is even a module the license restricted use and distribu- the Suse 9.2 version is imminent. for Yast2 icons, and there are many inter- tion of the program. These license Yast2 comprises the Libyutil library, a dependencies between modules that do restrictions prevented legal full down- program core, and a number of addi- not appear to make much sense. For loads of the Suse media for a long time. tional modules. The core is simply an example, to compile the partitioning interpreter for Yast2’s own programming module, you need the Autoyast module. Yast4Debian language, YCP, which combines various Autoyast adds other dependencies, such Novell has stated that it intends to make elements of other common scripting lan- as the X11 configuration module, which Yast2 a universal standard. According to guages and is used to create new mod- in turn requires the X11 mouse and X11 Novell, distributors should modify the ules. Both the Yast2 libraries and the keyboard modules. Also, Autoyast Yast source code to match their own core were written in C++ and pre-con- depends on the Yast Online Update mod- products. The first major project to figured with autotools to support build- ule and the Bootloader module. tackle this task was Debian. The Debian ing on any Linux system. distribution does not have its own cen- Porting the modules will be the biggest Under the Hood tral configuration tool, and creating a challenge. User interfaces such as the The task of modifying the highly Suse- comprehensive tool like Yast2 from Yast2 Ncurses text interface and the specific infrastructure to match the tar- WWW.LINUX - MAGAZINE.COM ISSUE 60 NOVEMBER 2005 93 COMMUNITY Free Software ProjectsSchlagwort sollte hier stehen COVER STORY the previous ver- and the Kdesktop, which will act as the sion dates back root window that contains all other KDE almost three years windows. On the design side, Super- to October 21, karamba – an optional component previ- 2001. ously – will allow programmers to One major enhance more or less any aspect of the change to Qt desktop with a minimum of effort, giv- affects the license ing users a Mac OS X style task bar (Fig- rather than the ure 2). As a result, the developers are code. Qt users aiming for a modern and “completely originally only new desktop design.” A KDE 3 compati- had the option of bility library will provide a bridgehead selecting a free between KDE 4 and its predecessor. license on Linux, The KDE programmers have not yet but with Qt 4, the set a completion date. Of course, the manufacturer KDE people are not the only ones really Figure 1: The Yast4Debian project brings Suse’s popular Yast config- Trolltech intro- interested in the success of their devel- uration tool to Debian. duced the GPL opment activities: a few weeks ago, license for propri- Trolltech hired KDE programmer Aaron get distribution is even more complex etary programs by Windows developers Seigo to allow Aaron to concentrate on than compiling Yast2 and the accompa- in addition to the commercial license. KDE development. Trolltech seems to nying modules. In Debian’s case, pack- Some programmers are even talking be looking to make the best known Qt age management is a major challenge. A about porting KDE to Windows – now application an object of prestige. Yast2 module communicates with the that the legal issues have been removed, RPM database, but Debian uses the it is just a question of technology. Bluetooth Headsets on Linux Debian package format. On a more posi- Qt 4 also adds value for end users. The Bluetooth headsets are a useful thing. tive note, other Yast2 modules needed library now supports 64-bit architec- In the car, these cheap earphones can far less modification; for example, tures, and this means considerable per- replace a more expensive hands-free because Debian and Suse both use formance benefits. system, and they work with any Blue- shadow, the developers were able to The new engine, which goes by the tooth devices that support appropriate adopt the user management module name of Arthur, also deserves a men- audio profiles. A driver for the Alsa more or less unchanged. tion. It allows users to add painting and Sound System means that at least a few The Yast4Debian developers can point drawing functions to Qt applications in headsets can be used for listening to to the first fruits of their labor: besides a simple way. Arthur has a big speed music on Linux home PCs. This said, the the user configuration module, the parti- advantage over the QPainter tool pro- Alsa Bluetooth project has still not been tioner now also works without any trou- vided by Qt 3, and it interfaces with the formally accepted into the mainstream ble. But there is still much to do, and the GUIs of any operating systems that sup- Alsa developer branch. Besides the imminent move to the Yast2 version port Qt. This means that the developer source code and an installation guide, from the current Suse distribution will no longer needs to think about the spe- the snd-bt-sco module is available from add considerably to the workload. If you cific characteristics of a user interface. the project homepage at [4]. are interested in getting involved with The new Scribe font engine also removes The Alsa Bluetooth extension uses the the porting work, check out the project the font problems that affected Qt 3. A2DP (Advanced Audio Distribution Pro- homepage at [1] for details. All in all, Qt 4 gives KDE programmers file) protocol to support stereo sound, a powerful base for the next generation although this has been restricted to ste- Qt 4 and KDE 4 desktop. The project Wiki [2] for the reo reception thus far. Stereo transmis- The KDE development cycle is tradition- recently opened KDE 4 branch already sions have failed, as the current headset ally modeled on that of the underlying has an impressive list of suggested fea- hardware does not support this function. graphics library, Qt. For example, a tures. Among other things, the develop- However, new Bluetooth headsets that development branch of KDE 4.0 was ers plan icon rendering and optical don't have this problem are under devel- opened just after Qt 4.0 was released. updates of the individual KDE compo- opment, and the snd-bt-sco driver KDE 4.0 is designed to leverage the fea- nents. KDE will also improve the user already has the necessary functionality. tures the new Qt version offers, while at experience by using Qt’s own access the same time removing a few design methods for all icons and buttons, thus Bug Squashing Party weaknesses that affected KDE 3. providing a standardized look. There has been a bustle of activity at the The gap between the release dates The Plasma [3] project will be looking developer branch of Debian in the wake makes it obvious that some major to revamp the KDE 4 look. According to of the Debian Sarge release. For example, changes to KDE's Qt underpinnings plans, it will integrate various KDE ele- the future version of the distribution has must have taken place. Version 4.0 of the ments, including a completely reworked moved to GCC version 4.0. The migra- graphics library was released June 27; version of the Control Center, the Kicker, tion pushed the number of release-criti- 94 ISSUE 60 NOVEMBER 2005 WWW.LINUX - MAGAZINE.COM Schlagwort sollte hier stehen COVER STORY ADVERTISEMENT cal bug reports up to almost 600, and At the Debian Developer Conference this has left Debian developers facing the (DebConf) in Helsinki, Finland, a group task of removing the bugs. of programmers centered around Steve To get up to speed, Frank Lichtenheld McIntyre got together to discuss ways of initiated a bug squashing party at the simplifying the CD tool. Source code start of August. A bug squashing party restructuring is the central issue; at the consists of developers meeting on an IRC same time, the team will be looking to channel to hunt down the bugs in their update and improve automated depen- own and other project teams’ packages. dency checking. Steve McIntyre has The administrators loosen up the rules announced a number of goals on the for package uploads to allow anyone tak- Debian-Devel-Announce mailing list [6]. ing part to upload their patches directly. But the CD Tool is facing an even big- The group bug hunt led to the removal ger problem. To find out which packages of 32 release critical errors, letting a it should put where on the 14 CD set, the number of packages previously consid- tool draws on the results of the Popular- ered unstable make their way to testing.
Recommended publications
  • Red Hat Enterprise Linux 6 Developer Guide
    Red Hat Enterprise Linux 6 Developer Guide An introduction to application development tools in Red Hat Enterprise Linux 6 Dave Brolley William Cohen Roland Grunberg Aldy Hernandez Karsten Hopp Jakub Jelinek Developer Guide Jeff Johnston Benjamin Kosnik Aleksander Kurtakov Chris Moller Phil Muldoon Andrew Overholt Charley Wang Kent Sebastian Red Hat Enterprise Linux 6 Developer Guide An introduction to application development tools in Red Hat Enterprise Linux 6 Edition 0 Author Dave Brolley [email protected] Author William Cohen [email protected] Author Roland Grunberg [email protected] Author Aldy Hernandez [email protected] Author Karsten Hopp [email protected] Author Jakub Jelinek [email protected] Author Jeff Johnston [email protected] Author Benjamin Kosnik [email protected] Author Aleksander Kurtakov [email protected] Author Chris Moller [email protected] Author Phil Muldoon [email protected] Author Andrew Overholt [email protected] Author Charley Wang [email protected] Author Kent Sebastian [email protected] Editor Don Domingo [email protected] Editor Jacquelynn East [email protected] Copyright © 2010 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/. 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.
    [Show full text]
  • Suse Linux Enterprise Server 12 - Administration Guide Pdf, Epub, Ebook
    SUSE LINUX ENTERPRISE SERVER 12 - ADMINISTRATION GUIDE PDF, EPUB, EBOOK Admin Guide Contributors | 630 pages | 28 Apr 2016 | Samurai Media Limited | 9789888406500 | English | none SUSE Linux Enterprise Server 12 - Administration Guide PDF Book To prevent the conflicts, before starting the migration, execute the following as a super user:. PA, IA In todays service oriented IT zero downtime becomes more and more a most wanted feature. If you want to change actions for single packages, right-click a package in the package view and choose an action. When debugging a problem, you sometimes need to temporarily install a lot of -debuginfo packages which give you more information about running processes. If you are only reading the release notes of the current release, you could miss important changes. However, this can be changed through macro configuration. In this case, the oldest zswap pages are written back to disk-based swap. YaST snapshots are labeled as zypp y2base in the Description column ; Zypper snapshots are labeled zypp zypper. Global variables, or environment variables, can be accessed in all shells. If it is 0 zero the command was successful, everything else marks an error which is specific to the command. The installation medium must be inserted in the HMC. Maintaining netgroup data. This option fetches changes in repositories, but keeps the disabled repositories in the same state—disabled. The rollback snapshots are therefore automatically deleted when the set number of snapshots is reached. The visible physical entity, as it is typically mounted to a motherboard or an equivalent. When using the self-signed certificate, you need to confirm its signature before the first connection.
    [Show full text]
  • Red Hat Enterprise Linux 7 開発者ガイド
    Red Hat Enterprise Linux 7 開発者ガイド Red Hat Enterprise Linux 7 のアプリケーション開発ツールのご紹介 Red Hat Subject Matter ExpertsDave Brolley William Cohen Roland Grunberg Aldy Hernandez Karsten Hopp Jakub Jelinek Jeff Johnston Benjamin Kosnik Chris Moller Phil Muldoon Alex Kurtakov Charley Wang Development Community Kent Sebastian Red Hat Enterprise Linux 7 開発者ガイド Red Hat Enterprise Linux 7 のアプリケーション開発ツールのご紹介 Dave Brolley Red Hat Engineering ツール開発 [email protected] プロファイリング William Cohen Red Hat Engineering ツール開発 [email protected] プロファイリング Roland Grunberg Red Hat Engineering ツール開発 [email protected] Eclipse および Eclipse プラグイン Aldy Hernandez Red Hat Engineering ツール開発 [email protected] コンパイルおよびビルド Karsten Hopp Base Operating System コアサービス - BRNO [email protected] コンパイル Jakub Jelinek Red Hat Engineering ツール開発 [email protected] プロファイリング Jeff Johnston Red Hat Engineering ツール開発 [email protected] Eclipse および Eclipse プラグイン Benjamin Kosnik Red Hat Engineering ツール開発 [email protected] ライブラリおよびランタイムのサポート Chris Moller Red Hat Engineering ツール開発 [email protected] デバッグ Phil Muldoon Red Hat Engineering ツール開発 [email protected] デバッグ Alex Kurtakov Red Hat Engineering ツール開発 [email protected] Eclipse および Eclipse プラグイン Charley Wang Red Hat Engineering ツール開発 [email protected] Eclipse および Eclipse プラグイン Kent Sebastian [email protected] プロファイリング Red Hat Subject Matter Experts Development Community 編集者 Jacquelynn East Engineering コンテンツサービス [email protected] Don Domingo Red Hat Engineering コンテンツサービス [email protected] 法律上の通知 Copyright © 2012 Red Hat, Inc. and others. 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.
    [Show full text]
  • Kde-Guide-De-Developpement.Web.Pdf
    KDE Published : 2017-06-26 License : GPLv2+ 1 KDE DU POINT DE VUE D'UN DÉVELOPPEUR 1. AVEZ-VOUS BESOIN DE CE LIVRE ? 2. LA PHILOSOPHIE DE KDE 3. COMMENT OBTENIR DE L'AIDE 2 1. AVEZ-VOUS BESOIN DE CE LIVRE ? Vous devriez lire ce livre si vous voulez développer pour KDE. Nous utilisons le terme développement très largement pour couvrir tout ce qui peut conduire à un changement dans le code source, ce qui inclut : Soumettre une correction de bogue Écrire une nouvelle application optimisée par la technologie KDE Contribuer à un projet existant Ajouter de la fonctionnalité aux bibliothèques de développement de KDE Dans ce livre, nous vous livrerons les bases dont vous avez besoin pour être un développeur productif. Nous décrirons les outils que vous devrez installer, montrer comment lire la documentation (et écrire la vôtre propre, une fois que vous aurez créé la nouvelle fonctionnalité !) et comment obtenir de l'aide par d'autres moyens. Nous vous présenterons la communauté KDE, qui est essentielle pour comprendre KDE parce que nous sommes un projet « open source », libre (gratuit). Les utilisateurs finaux du logiciel n'ont PAS besoin de ce livre ! Cependant, ils pourraient le trouver intéressant pour les aider à comprendre comment les logiciels complexes et riches en fonctionnalités qu'ils utilisent ont vu le jour. 3 2. LA PHILOSOPHIE DE KDE Le succès de KDE repose sur une vue globale, que nous avons trouvée à la fois pratique et motivante. Les éléments de cette philosophie de développement comprennent : L'utilisation des outils disponibles plutôt que de ré-inventer ceux existants : beaucoup des bases dont vous avez besoin pour travailler font déjà partie de KDE, comme les bibliothèques principales ou les « Kparts », et sont tout à fait au point.
    [Show full text]
  • A U T O M at E D I N S Ta L L At
    Proceedings of LISA '99: 13th Systems Administration Conference Seattle, Washington, USA, November 7–12, 1999 A U T O M AT E D I N S TA L L AT I O N O F L I N U X S Y S T E M S U S I N G YA S T Dirk Hohndel and Fabian Herschel THE ADVANCED COMPUTING SYSTEMS ASSOCIATION © 1999 by The USENIX Association All Rights Reserved For more information about the USENIX Association: Phone: 1 510 528 8649 FAX: 1 510 548 5738 Email: [email protected] WWW: http://www.usenix.org Rights to individual papers remain with the author or the author's employer. Permission is granted for noncommercial reproduction of the work for educational or research purposes. This copyright notice must be included in the reproduced paper. USENIX acknowledges all trademarks herein. Automated Installation of Linux Systems Using YaST Dirk Hohndel and Fabian Herschel – SuSE Rhein/Main AG ABSTRACT The paper describes how to allow a customized automated installation of Linux. This is possible via CDRom, network or tape, using a special boot disk that describes the system that should be set up and either standard SuSE Linux CDs, customized install CDs, an appropriately configured installation server, or a tape backup of an existing machine. A control file on the boot disk and additional (optional) control files on the install medium specify which settings should be used and which packages should be installed. This includes settings like language, key table, network setup, hard disk partitioning, packages to install, etc. After giving a quick overview of the syntax and capabilities of this installation method, considerations about how to plan the automated installation at larger sites are presented.
    [Show full text]
  • Developer Guide
    Red Hat Enterprise Linux 6 Developer Guide An introduction to application development tools in Red Hat Enterprise Linux 6 Last Updated: 2017-10-20 Red Hat Enterprise Linux 6 Developer Guide An introduction to application development tools in Red Hat Enterprise Linux 6 Robert Krátký Red Hat Customer Content Services [email protected] Don Domingo Red Hat Customer Content Services Jacquelynn East Red Hat Customer Content Services Legal Notice Copyright © 2016 Red Hat, Inc. and others. 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, 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.
    [Show full text]
  • KDE Plasma 5
    Arvo Mägi KDE Plasma 5 Tallinn, 2017 1 Sissejuhatus KDE töökeskkonnale pani aluse saksa programmeerija Matthias Ettrich 14.10.1996. 2016. a oktoobris sai populaarne KDE seega 20. aastaseks. Hea ülevaate KDE ajaloost annab artikkel „19 Years of KDE History: Step by Step.” KDE 4.14 ilmumisega oli KDE saavutanud kasutusküpsuse, kuid edasine areng kippus takerduma – vaja oli põhimõttelisi uuendusi. Otsustati võtta kasutusele iseseisvatel moodulitel põhinev KDE 5 arhitektuur – Qt/Frameworks. Kõik KDE rakendusprogrammid, sh Plasma 5 töölaud, kasutavad ainult konkreetse rakenduse jaoks vajalikke mooduleid. Varem kasutati kõigi rakenduste jaoks ühist suurt teeki, mis raskendas muudatuste tegemist ja pidurdas arendustööd. Qt on C++ programmeerimiskeskkond. Pikaajalise toega Qt 5.9 LTS ilmus 31. mail 2017. KDE Frameworks on 70 moodulist koosnev komplekt, mis lihtsustab Qt keskkonnas KDE programmide koostamist. Frameworks veaparandused ja täiendused ilmuvad iga kuu. KDE Plasma 5 töölaud põhineb KDE Frameworksil (KF5). Töölaua veaparandused ilmuvad iga kuu, vajadusel mitu korda kuus, uued versioonid kord kvartalis. Plasma 5.8 LTS, mis on pikaajalise toega (18 kuud), ilmus 4.10.2016, veidi enne KDE 20. aastaseks saamist. Plasma 5.10 ilmus 30.05.2017. Järgmine pikaajalise toega Plasma 5.12 ilmub 2018. a jaanuaris. Plasma 5 töölaud on pälvinud palju kiitvaid hinnanguid ja sobib igapäevaseks tööks. Eeldab kaasaegset, mitme tuumaga protsessori ja piisava mäluga (vähemalt 4 GB) arvutit. SSD kettalt töötab välkkiirelt. Töölaud on keskkond rakendusprogrammide käivitamiseks ja kasutamiseks. KF5-le on üle viidud kõik KDE põhirakendused (failihaldur Dolphin, pildinäitaja Gwenview, konsool Konsole, teksti- redaktor Kate, ekraanitõmmise võtja Spectacle, videoredaktor Kdenlive, plaadikirjutaja K3b jt). Need on KDE Applications koosseisus, mille uued versioonid ilmuvad kolm korda aastas, veaparandused kord kuus.
    [Show full text]
  • Linux: Come E Perchх
    ÄÒÙÜ Ô ©2007 mcz 12 luglio 2008 ½º I 1. Indice II ½º Á ¾º ¿º ÈÖÞÓÒ ½ º È ÄÒÙÜ ¿ º ÔÔÖÓÓÒÑÒØÓ º ÖÒÞ ×Ó×ØÒÞÐ ÏÒÓÛ× ¾½ º ÄÒÙÜ ÕÙÐ ×ØÖÙÞÓÒ ¾ º ÄÒÙÜ ÀÖÛÖ ×ÙÔÔ ÓÖØØÓ ¾ º È Ð ÖÒÞ ØÖ ÖÓ ÓØ Ù×Ö ¿½ ½¼º ÄÒÙÜ × Ò×ØÐÐ ¿¿ ½½º ÓÑ × Ò×ØÐÐÒÓ ÔÖÓÖÑÑ ¿ ½¾º ÒÓÒ ØÖÓÚÓ ÒÐ ×ØÓ ÐÐ ×ØÖÙÞÓÒ ¿ ½¿º Ó׳ ÙÒÓ ¿ ½º ÓÑ × Ð ××ØÑ ½º ÓÑ Ð ½º Ð× Ñ ½º Ð Ñ ØÐ ¿ ½º ÐÓ ½º ÓÑ × Ò×ØÐÐ Ð ×ØÑÔÒØ ¾¼º ÓÑ ÐØØÖ¸ Ø×Ø ÐÖ III Indice ¾½º ÓÑ ÚÖ Ð ØÐÚ×ÓÒ ¿ 21.1. Televisioneanalogica . 63 21.2. Televisione digitale (terrestre o satellitare) . ....... 64 ¾¾º ÐÑØ ¾¿º Ä 23.1. Fotoritocco ............................. 67 23.2. Grafica3D.............................. 67 23.3. Disegnovettoriale-CAD . 69 23.4.Filtricoloreecalibrazionecolori . .. 69 ¾º ×ÖÚ Ð ½ 24.1.Vari.................................. 72 24.2. Navigazionedirectoriesefiles . 73 24.3. CopiaCD .............................. 74 24.4. Editaretesto............................. 74 24.5.RPM ................................. 75 ¾º ×ÑÔ Ô ´ËÐе 25.1.Montareundiscoounapenna . 77 25.2. Trovareunfilenelsistema . 79 25.3.Vedereilcontenutodiunfile . 79 25.4.Alias ................................. 80 ¾º × ÚÓÐ×× ÔÖÓÖÑÑÖ ½ ¾º ÖÓÛ×Ö¸ ÑÐ ººº ¿ ¾º ÖÛÐРгÒØÚÖÙ× Ð ÑØØÑÓ ¾º ÄÒÙÜ ½ ¿¼º ÓÑ ØÖÓÚÖ ÙØÓ ÖÖÑÒØ ¿ ¿½º Ð Ø×ØÙÐ Ô Ö Ð ×ØÓÔ ÄÒÙÜ ¿¾º ´ÃµÍÙÒØÙ¸ ÙÒ ×ØÖÙÞÓÒ ÑÓÐØÓ ÑØ ¿¿º ËÙÜ ÙÒ³ÓØØÑ ×ØÖÙÞÓÒ ÄÒÙÜ ½¼½ ¿º Á Ó Ò ÄÒÙÜ ½¼ ¿º ÃÓÒÕÙÖÓÖ¸ ÕÙ×ØÓ ½¼ ¿º ÃÓÒÕÙÖÓÖ¸ Ñ ØÒØÓ Ô Ö ½½¿ 36.1.Unaprimaocchiata . .114 36.2.ImenudiKonqueror . .115 36.3.Configurazione . .116 IV Indice 36.4.Alcuniesempidiviste . 116 36.5.Iservizidimenu(ServiceMenu) . 119 ¿º ÃÓÒÕÙÖÓÖ Ø ½¾¿ ¿º à ÙÒ ÖÖÒØ ½¾ ¿º à ÙÒ ÐÙ×ÓÒ ½¿½ ¼º ÓÒÖÓÒØÓ Ò×ØÐÐÞÓÒ ÏÒÓÛ×È ÃÍÙÒØÙ º½¼ ½¿¿ 40.1.
    [Show full text]
  • Translate's Localization Guide
    Translate’s Localization Guide Release 0.9.0 Translate Jun 26, 2020 Contents 1 Localisation Guide 1 2 Glossary 191 3 Language Information 195 i ii CHAPTER 1 Localisation Guide The general aim of this document is not to replace other well written works but to draw them together. So for instance the section on projects contains information that should help you get started and point you to the documents that are often hard to find. The section of translation should provide a general enough overview of common mistakes and pitfalls. We have found the localisation community very fragmented and hope that through this document we can bring people together and unify information that is out there but in many many different places. The one section that we feel is unique is the guide to developers – they make assumptions about localisation without fully understanding the implications, we complain but honestly there is not one place that can help give a developer and overview of what is needed from them, we hope that the developer section goes a long way to solving that issue. 1.1 Purpose The purpose of this document is to provide one reference for localisers. You will find lots of information on localising and packaging on the web but not a single resource that can guide you. Most of the information is also domain specific ie it addresses KDE, Mozilla, etc. We hope that this is more general. This document also goes beyond the technical aspects of localisation which seems to be the domain of other lo- calisation documents.
    [Show full text]
  • SUSE Linux Enterprise Server 11 SP4 System Analysis and Tuning Guide System Analysis and Tuning Guide SUSE Linux Enterprise Server 11 SP4
    SUSE Linux Enterprise Server 11 SP4 System Analysis and Tuning Guide System Analysis and Tuning Guide SUSE Linux Enterprise Server 11 SP4 Publication Date: September 24, 2021 SUSE LLC 1800 South Novell Place Provo, UT 84606 USA https://documentation.suse.com Copyright © 2006– 2021 SUSE LLC and contributors. All rights reserved. Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.2 or (at your option) version 1.3; with the Invariant Section being this copyright notice and license. A copy of the license version 1.2 is included in the section entitled “GNU Free Documentation License”. For SUSE trademarks, see http://www.suse.com/company/legal/ . All other third party trademarks are the property of their respective owners. A trademark symbol (®, ™ etc.) denotes a SUSE or Novell trademark; an asterisk (*) denotes a third party trademark. All information found in this book has been compiled with utmost attention to detail. However, this does not guarantee complete accuracy. Neither SUSE LLC, its aliates, the authors nor the translators shall be held liable for possible errors or the consequences thereof. Contents About This Guide xi 1 Available Documentation xii 2 Feedback xiv 3 Documentation Conventions xv I BASICS 1 1 General Notes on System Tuning 2 1.1 Be Sure What Problem to Solve 2 1.2 Rule Out Common Problems 3 1.3 Finding the Bottleneck 3 1.4 Step-by-step Tuning 4 II SYSTEM MONITORING 5 2 System Monitoring Utilities 6 2.1 Multi-Purpose Tools 6 vmstat 7
    [Show full text]
  • Using Your Desktop
    Valade_06.qxd 3/31/05 2:58 PM Page 73 CHAPTER 6 Using Your Desktop inux provides two basic types of interface for you to use when working with your computer: GUI (graphical user interface) and CLI (command-line interface). An L overview of the interface types is provided in Chapter 5. In this chapter, the most common type of interface, a GUI called a desktop, is discussed in detail. The CLI is dis- cussed in detail in Chapter 7. Linux can start without a desktop, but most users prefer to have Linux start with a desk- top. The installation instructions provided in Chapter 4 result in a desktop opening at startup. A desktop interface functions as the top of your desk, supplying an empty work- ing surface and a set of tools. Different distributions provide different desktops, but most provide KDE (K Desktop Environment) and/or GNOME (Gnu Network Object Model Environment)—the Big Two of Linux desktops. The default desktop differs by distribution. For instance, Fedora defaults to GNOME, and Mandrake/SuSE defaults to KDE. However, you can change the default once you decide which desktop you prefer. KDE and GNOME are open source software, each developed in a project of its own. New versions are released independently of Linux releases or the release of any specific Linux distribution. As a result, different distributions include different KDE and/or GNOME versions. In addition, KDE and GNOME are very configurable. Almost everything about them can be changed. Consequently, KDE and GNOME don’t look exactly the same in different distributions or versions of distributions.
    [Show full text]
  • Get Your Default KDE and GNOME Desktops in Line by David D
    Get Your Default KDE and GNOME Desktops in Line by David D. Scribner As mentioned in my last article, Get Your Default KDE and GNOME Menus in Line, the User Manuals for the KDE and GNOME GUI environments include instructions on modifying the user’s menus and desktop properties. Just as with the menus however, modifications to the desktop settings made by individual users are stored in the user’s home directory and have no affect on the “defaults” installed for new users. Being the system administrator, you may have custom desktop wallpaper, shortcut icons and panel (or Kicker, as KDE now calls it) icons that differ from those set up in the default configurations. If you wish to have the default desktops installed for new users tailored to include selected application icons in the panel or kicker (taskbar), or changes to the default desktop shortcuts, background, colors or style that GNOME and KDE normally set up for those new users, you will have to make a few modifications. This article is intended to cover the basic tasks of customizing such default installations. Since customizing the default desktops for your new users result in changes to the installed files, back up any of these files/directories before proceeding with any modifications! Desktop Configuration Skeletons Items pertaining to the desktop you want your new users to be greeted with are perhaps easiest to configure by placing the relevant KDE and GNOME desktop configuration files in the /etc/skel directory. You could modify the master files KDE and GNOME use to create new user setups, but they may be overwritten should you upgrade to a newer version of the environment.
    [Show full text]