DOCSLIB.ORG

Third Party Terms for Modular Messaging 3.0 (July 2005)

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Third Party Terms for Modular Messaging 3.0 (July 2005) Third Party Terms for Modular Messaging 3.0 (July 2005) Certain portions of the product ("Open Source Components") are licensed under open source license agreements that require Avaya to make the source code for such Open Source Components available in source code format to its licensees, or that require Avaya to disclose the license terms for such Open Source Components. If you are a licensee of this Product, and wish to receive information on how to access the source code for such Open Source Components, or the details of such licenses, you may contact Avaya at (408) 577-7666 for further information. The Open Source Components are provided “AS IS”. ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDERS OR THE CONTRIBUTORS OF THE OPEN SOURCE COMPONENTS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THE PRODUCT, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. Avaya provides a limited warranty on the Product that incorporates the Open Source Components. Refer to your customer sales agreement to establish the terms of the limited warranty. In addition, Avaya’s standard warranty language as well as information regarding support for the Product, while under warranty, is available through the following web site: http://www.avaya.com/support. The Open Source Components may embody copyrights of the persons named below: © 1984, 1990-2004 Sun Microsystems, Inc., 4150 Network Circle, Santa Clara, California 95054 U.S.A. All Rights Reserved © 2003 David Zeuthen, [email protected] © 1999-2004 The Apache Software Foundation © 2000 Fourthought, Inc. All rights reserved. © 1993 Alec Muffett © 2001-2002, Damian Conway. All Rights Reserved. © 1996-2002 Julian R Seward. All rights reserved. © 1998, 1999, 2000 Thai Open Source Software Center Ltd. and Clark Cooper © 2001, 2002 Expat maintainers. © 1995, 1996, 1997, 1998, and 1999 WIDE Project. All rights reserved. © 2002, Xiph.org Foundation © 1996, 2000, 2001 Todd C. Miller. All rights reserved. © 1999,2000,2001 Jim Knoble © 1995 - 2005 Red Hat, Inc., All Rights Reserved © 2001 Thorsten Kukuk. © 1992 Keith Muller. © 1996-2003, PostgreSQL Global Development Group © 1989 - 1994, Julianne Frances Haugh. All rights reserved. © 2002 by WyrmCorp © 1991, 1992 Paul Kranenburg. © 1993 Branko Lankester © 1993 Ulrich Pegelow © 2000-2004 CollabNet. All rights reserved. © 1994-1996,1998-2003 Todd C. Miller. All rights reserved. © 1998-2002 University of Chicago. All rights reserved. © 1980, 1983, 1987 - 2000 The Regents of the University of California. All rights Reserved. Third Party Terms for Modular Messaging 3.0 (July 2005) © 1994 – 1995 Loi Kim Lam © 1996 Expert Interface Technologies © 1998 Scriptics Corporation © 1990-2004 Info-ZIP. All rights reserved. © 2000-2002 by Solar Designer © 1990-2003 Sleepycat Software. All rights reserved. © 1984-2003 by Carnegie Mellon University © 2001-2003, Networks Associates Technology, Inc. All rights reserved. © 2001-2003, Cambridge Broadband Ltd. All rights reserved. © 2003-2004, Sparta, Inc. All rights reserved. © 1998-2004 The OpenSSL Project © 1995-1998 Eric A. Young, Tim J. Hudson. All rights reserved. © 1996-2004 Internet Systems Consortium, Inc. ("ISC") © 1997 Andrew G Morgan © 1994-2002 by Cold Spring Harbor Laboratory © 1996-2002 by Boutell.Com, Inc. © 1999-2002 Philip Warner © 1999-2002 Greg Roelofs © 1999-2002 John Ellson © 2000-2002 Doug Becker © 1994-2002 Thomas G. Lane © 2000-2002 Maurice Szmurlo and Johan Van den Brande © 1986-1995 Ian F. Darwin © 1994-1995 Cronyx Ltd.; Changes © 1996 by Andrey A. Chernov, Moscow, Russia. © 2000-2002 MIYASHITA Hisash © 2003 Motonobu Ichimura © 2002 - 2003 Phil Dibowitz © 1991 by Software Research Associates, Inc. © 1991-1998, Thomas G. Lane. All Rights Reserved. © 1988-1997 Sam Leffler; © 1991-1997, 1999-2002, 2004 Silicon Graphics, Inc. © 2001-2003 by the Institute of Electrical and Electronics Engineers, Inc., and The Open Group. © 1985-2004 Free Software Foundation, Inc. © 1997-2003 University of Cambridge © 1995-2003 Sullivan Beck. All rights reserved. © 1994-1997 Tim Bunce © 1997-2000 Edmund Mergl © 2002 Jeffrey W. Baker © 1997-2002 Graham Barr. © 1995-2004 Gisle Aas © 1997 Uwe Hollerbach. © 1995-2002 Paul Marquess. All rights reserved © 1987-1989, 1991, 1993, 1998, The Open Group Third Party Terms for Modular Messaging 3.0 (July 2005) © 2001, 2002, 2004 Than Ngo <[email protected]> © 2001-2004 Harald Hoyer <[email protected]> © 2001, 2002 Philipp Knirsch <[email protected]> © 2001-2003 Trond Eivind Glomsr <[email protected]> © 2000 Crutcher Dunnavant <[email protected]>, © 2001-2003 Brent Fox <[email protected]> © 2001-2004 Tim Waugh <[email protected]> © 2000 Michael Madore © 2003 Greg Kroah-Hartman <[email protected]> © 1999 Thomas Sailer ([email protected]) © 1993, 2000, 2001 Yggdrasil Computing, Inc. © 1991, 1992, 1993, 1994, 1995, 2002 Ian Lance Taylor © 1993-1998 Hirotsugu KAKUGAWA. All rights reserved. © 1997-2001 Bradford L. Barrett ([email protected]) © 1999, 2003 Carlo Wood <[email protected]> © 1997, 1998, 1999, 2001 Josh MacDonald © 2000-2002 Joe Piolunek © 2001-2002 Mark J. Horn © 2000-2003 Hewlett-Packard Company © 2003 Matthew Allum © 2000 Helix Code, Inc. © 2001-2003 Mikael Hallendal <[email protected]> © 1993, 1994 by California Institute of Technology. © 1999-2000, Michael A. Chase. © 1995 Martijn Koster. All rights reserved. © 2001-2003 AxKit.com Ltd, All rights reserved. © 2002 Christian Glahn, All rights reserved. © 2001, Matt Sergeant, [email protected] © 2001-2004, Valek Filippov © 1999, (URW)++ Design & Developmentt © 1999-2003 Ximian, Inc. © 2000-2004 IBM Corp. © 2004 Henrique de Moraes Holschuh <[email protected]> © 1992-2000 Trolltech AS. All rights reserved. © 2003 by John Joganic <[email protected]> © 1993-2002, Juergen Weigert ([email protected]) © 1993-2002, Michael Schroeder ([email protected]) © 1987 Oliver Laumann © 1995 Science Access Project, Oregon State University. © 1998 by Jaroslav Kysela <[email protected]> © 2001 by Kevin Atkinson © 1998-2000, 2003-2004, Michael Pruett © 1997, 1998, 1999, 2000, 2001 Virtual Unlimited B.V. Third Party Terms for Modular Messaging 3.0 (July 2005) © 2002, 2003, Bob Deblier © 1987-1988, 1993, 1994 by Digital Equipment Corporation © 2000, Intel Corporation © 2000-2003 Geoff Thorpe, and Cryptographic Appliances, Inc. © 1999,2000 Dov Grobgeld © 2001,2002 Behdad Esfahbod © 1995-1997 Peter Mattis, Spencer Kimball and Josh MacDonald © 1998 Owen Taylor © 1998, 1999 Tom Tromey © 1997-1999 AvantGo, Inc. All Rights Reserved. © 2001, 2002 Johan Dahlin <[email protected]> © 2000,2001,2002,2003 Nikos Mavroyanopoulos © 1998-1999, 2001 Damon Chaplin © 2000 CodeFactory AB © 2000 Jonas Borgstr├╢m <[email protected]> © 2000-2002 Anders Carlsson [email protected] © 1997 Martin Jones ([email protected]) © 1997 Torben Weis ([email protected]) © 2001 - Mikael Hermansson <[email protected]> and Chris Phelps <[email protected]> © 2002 - Jeroen Zwartepoorte © 2003 - Gustavo Giríldez and Paolo Maggi © 1998 By The Rasterman (Carsten Haitzler) © 1999, 2000 Andreas Gruenbacher, <[email protected]> © 1999-2001 Raph Levien <[email protected]> © 2002-2004 Dodji Seketeli © April 2000Charles 'Buck' Krasic © April 2000 Erik Walthinsen © 2002 Lutz M├╝ller <[email protected]> © 1998-2003 James Henstridge <[email protected]> © 1998-2003 Miguel de Icaza <[email protected]> © 1998-2003 Lauris Kaplinski <[email protected]> © 1998-2003 Chema Celorio <[email protected]> © 2004 g10 Code GmbH © 2002-2004 Jody Goldberg ([email protected]) © 1998, 1999 Andrew T. Veliath © 2003, 2004 Simon Josefsson © 1999,2000,2001,2002 Andreas Bombe © 2001, 2002 Manfred Weihs <[email protected]> © 2002 Christian Toegel <[email protected]> © 2000, 2001 Eazel, Inc. © 2002 Dom Lachowicz <[email protected]> © 1991-2003 Miquel van Smoorenburg © 2001 Francis James Franklin Third Party Terms for Modular Messaging 3.0 (July 2005) © 2001, 2002 Havoc Pennington © 2003 Kim Woelders © 1997-2002 Net Integration Technologies, Inc. © 2000 MySQL AB & MySQL Finland AB & TCX DataKonsult AB © 1999-2003 Joe Orton © 1999-2000 Tommi Komulainen <[email protected]> © 1999-2000, Peter Boos <[email protected]> © 2001 AB Strakt, All rights reserved © 2001 Ben Greear © 2001-2003 Josh Coalson © 2003,2004 Andi Kleen, SuSE Labs. © 1998 Richard H. Porter and Red Hat Software © 2001,2003 Keith Packard © 1999-2000 Pawel W. Olszta. All Rights Reserved. © 1997 Eric S. Raymond © 1998-2003 Daniel Veillard. All Rights Reserved. © 2000 Bjorn Reese and Daniel Veillard. © 2000 Gary Pennington and Daniel Veillard. © 1998 Bjorn Reese and Daniel Stenberg. © 2001-2002 Thomas Broyer, Charlie Bozeman and Daniel Veillard. All Rights Reserved. © 1992-1998 Werner Almesberger. All rights reserved. © 2004 Kirk Bauer © 1987, 1988, 1993, 1994 X Consortium © 1989, 1990, 1991 Jim Frost. © 2002-2003 Aleksey Sanin. All Rights Reserved. © 2002-2003, 2004 by Thomas E. Dickey. All rights reserved. © 1985-2004 by the Massachusetts Institute of Technology. © 1988 Evans & Sutherland Computer Corporation. © 1996 - 2004,
Load more

Recommended publications
  • Projects on the Move
    :FDDLE@KP Free Software Projects 8elg$kf$[Xk\fm\im`\nf]]i\\jf]knXi\Xe[`kjdXb\ij GIFA<:KJFEK?<DFM< Finally there’s a free alternative to the proprietary Flash on the web. Unfortunately, it implements Microsoft technology whose software patents might render the free Moonlight license useless. BY CARSTEN SCHNOBER Microsoft and Novell formed an alliance Flash format as a global standard for problems to newcomers because you can with the aim of establishing a Flash al- complex, interactive web content. The download a prebuilt version of the pl- ternative for Linux. After one year of co- proprietary browser plugin by Adobe is ugin from the project website and click operation between developers from both like a red flag to a bull for many Linux to install (Figure 1). Thus far, Moonlight companies, a beta version of the Silve- users. Because the source code is not supports only Linux systems using Fire- light free implementation, Moonlight, is available, developers and users of the fox, although the makers claim that it now available. Many members of the free operating system have been forced will support OpenSolaris and the Kon- Linux community suspect that the to rely on Adobe providing updates. In queror and Opera browsers in the near Moonlight Linux implementation [1] is the past, Adobe has been reticent with future. being used to establish Microsoft's Sil- respect to timeliness and completeness. For licensing reasons, the binary pack- verlight [2] technology on a cross-plat- age leaves out all multimedia codecs, form basis, thereby infiltrating the soft- ;Xe^\ijXe[9\e\]`kj thus seriously limiting its own function- ware freedom fighters’ fortress.
    [Show full text]
  • Mono for Cross-Platform Control System Environment
    monomono forfor crosscross--platformplatform controlcontrol systemsystem environmentenvironment H.H. NishimuraNishimura andand C.C. TimossiTimossi,, LBNL,LBNL, Berkeley,Berkeley, CACA 94720,94720, U.S.AU.S.A Work supported by the U.S. Department of Energy under Contract No. DE-AC03-76SF00098 .NET.NET FrameworkFramework z MicrosoftMicrosoft ÄÄ ECMA/ISOECMA/ISO z 1.01.0 inin 20022002 z 1.11.1 inin 20032003 z 2.02.0 inin 20052005 z 3.03.0 inin 2006?2006? z WindowsWindows VistaVista isis .NET.NET--based.based. z C#C# andand manymany otherother languages.languages. .NET.NET missesmisses 22 pieces..pieces.. WhatWhat isis Mono?Mono? z AnAn independentindependent implementationimplementation ofof .NET.NET FrameworkFramework byby XimiaXimiann ÄÄNovell.Novell. z Linux,Linux, FreeBSD,FreeBSD, UNIX,UNIX, MacMac OSOS X,X, SolarisSolaris andand WindowsWindows z s390/s390x,s390/s390x, SPARC,SPARC, PowerPC,PowerPC, x86,x86, x86x86--64,64, IA64,IA64, ARMARM z DualDual LicensedLicensed byby NovellNovell HPHP atat www.mono-project.com SearchSearch MonoMono atat www.wikipedia.orgwww.wikipedia.org WhoWho mademade Mono?Mono? z MiguelMiguel dede IcazaIcaza z CreatedCreated GnomeGnome withwith FedericoFederico MenaMena inin 1997.1997. z CreatedCreated MonoMono inin 20012001 atat XimianXimian.. z ““MonoMono andand GNOME.GNOME. TheThe longlong replyreply”” z 0606 FebFeb 20022002 z http://mail.gnome.org/archives/gnomehttp://mail.gnome.org/archives/gnome-- hackers/2002hackers/2002--February/msg00031.htmlFebruary/msg00031.html z NowNow underunder Novell.Novell. IsIs MonoMono aa CrossCross--PlatformPlatform .NET?.NET? z DefinitelyDefinitely YES!YES! z AsAs .NET.NET RuntimeRuntime EnvironmentEnvironment z AsAs .NET.NET DevelopmentDevelopment EnvironmentEnvironment z AA fewfew yearsyears behindbehind thethe ““.NET.NET onon WindowsWindows””.. z NonNon--graphicalgraphical classesclasses areare basicallybasically OK.OK.
    [Show full text]
  • GIMP Toolkit: GTK+ V1.2
    'Construction d’IHM $ GIMP Toolkit: GTK+ v1.2 Alexis N´ed´elec Ecole Nationale d’Ing´enieursde Brest TechnopˆoleBrest-Iroise, Site de la Pointe du Diable CP 15 29608 BREST Cedex (FRANCE) e-mail : [email protected] & enib=li2 °c A.N. 1 % 'GTK+ v1.2 : GIMP Toolkit $ Table des Mati`eres Introduction 3 Premier Programme: Hello World 10 Signaux et R´eflexes 14 Description de Widget 22 Container de Widgets 32 Entr´eesde Texte 43 Les Listes multi-colonnes 76 Repr´esentation d’arborescence 89 Bibliographie 107 & enib=li2 °c A.N. 2 % 'GTK : GIMP Toolkit $ Introduction On peut d´efinirGTK comme: . une API “Orient´eObjet” . pour le d´eveloppement d’IHM graphiques (GUI) . sous Licence GNU (LGPL) Glossaire de Sigles: . GNU : GNU’s Not Unix ou “Vive le Logiciel Libre !”. GNOME : GNU Network Object Model Environment . GIMP : General Image Manipulation Program . GDK : GIMP Drawing Kit . GTK : GIMP ToolKit & enib=li2 °c A.N. 3 % 'GTK : GIMP Toolkit $ Introduction Le Projet GNOME: . 1997: Miguel de Icaza du “Mexican Autonomous National University” . objectifs : d´eveloppement de logiciels libres (open source) . inspir´edes d´eveloppements de KDE (Qt) GNOME est bas´esur un ensemble de librairies existantes . glib: utilitaire pour la cr´eationet manipulation de structures . GTK+: Boˆıte`aoutils pour le d´eveloppement d’IHM graphiques . ORBit: Le Broker GNOME (CORBA 2.2) pour la distribution d’objets . Imlib: pour la manipulation d’images sous X Window et GDK & enib=li2 °c A.N. 4 % 'GTK : GIMP Toolkit $ Introduction Librairies sp´ecifiquesdu projet GNOME . libgnome: utilitaires (non-GUI) de bases pour toute application GNOME .
    [Show full text]
  • Linux Platform 3.0.5
    Open Source Used In Linux Platform 3.0.5 Cisco Systems, Inc. www.cisco.com Cisco has more than 200 offices worldwide. Addresses, phone numbers, and fax numbers are listed on the Cisco website at www.cisco.com/go/offices. Text Part Number: 78EE117C99-140544257 Open Source Used In Linux Platform 3.0.5 1 This document contains licenses and notices for open source software used in this product. With respect to the free/open source software listed in this document, if you have any questions or wish to receive a copy of any source code to which you may be entitled under the applicable free/open source license(s) (such as the GNU Lesser/General Public License), please contact us at [email protected]. In your requests please include the following reference number 78EE117C99-140544257 The product also uses the Linux operating system, Centos Full 6.8. Information on this distribution is available at http://vault.centos.org/6.8/os/Source/SPackages/. The full source code for this distribution, including copyright and license information, is available on request from [email protected]. Mention that you would like the Linux distribution source archive, and quote the following reference number for this distribution: 132404382-140544257. Contents 1.1 acl - libraries 2.2.49 :6.el6 1.1.1 Available under license 1.2 atop 1.27 :2.el6 1.2.1 Available under license 1.3 attr_libattr 2.4.44 :7.el6 1.3.1 Available under license 1.4 avahi 0.6.25 :15.el6_8.1 1.4.1 Available under license 1.5 bind 9.8.2 :0.47.rc1.el6_8.3
    [Show full text]
  • The GNOME Desktop Environment
    The GNOME desktop environment Miguel de Icaza ([email protected]) Instituto de Ciencias Nucleares, UNAM Elliot Lee ([email protected]) Federico Mena ([email protected]) Instituto de Ciencias Nucleares, UNAM Tom Tromey ([email protected]) April 27, 1998 Abstract We present an overview of the free GNU Network Object Model Environment (GNOME). GNOME is a suite of X11 GUI applications that provides joy to users and hackers alike. It has been designed for extensibility and automation by using CORBA and scripting languages throughout the code. GNOME is licensed under the terms of the GNU GPL and the GNU LGPL and has been developed on the Internet by a loosely-coupled team of programmers. 1 Motivation Free operating systems1 are excellent at providing server-class services, and so are often the ideal choice for a server machine. However, the lack of a consistent user interface and of consumer-targeted applications has prevented free operating systems from reaching the vast majority of users — the desktop users. As such, the benefits of free software have only been enjoyed by the technically savvy computer user community. Most users are still locked into proprietary solutions for their desktop environments. By using GNOME, free operating systems will have a complete, user-friendly desktop which will provide users with powerful and easy-to-use graphical applications. Many people have suggested that the cause for the lack of free user-oriented appli- cations is that these do not provide enough excitement to hackers, as opposed to system- level programming. Since most of the GNOME code had to be written by hackers, we kept them happy: the magic recipe here is to design GNOME around an adrenaline response by trying to use exciting models and ideas in the applications.
    [Show full text]
  • The Glib/GTK+ Development Platform
    The GLib/GTK+ Development Platform A Getting Started Guide Version 0.8 Sébastien Wilmet March 29, 2019 Contents 1 Introduction 3 1.1 License . 3 1.2 Financial Support . 3 1.3 Todo List for this Book and a Quick 2019 Update . 4 1.4 What is GLib and GTK+? . 4 1.5 The GNOME Desktop . 5 1.6 Prerequisites . 6 1.7 Why and When Using the C Language? . 7 1.7.1 Separate the Backend from the Frontend . 7 1.7.2 Other Aspects to Keep in Mind . 8 1.8 Learning Path . 9 1.9 The Development Environment . 10 1.10 Acknowledgments . 10 I GLib, the Core Library 11 2 GLib, the Core Library 12 2.1 Basics . 13 2.1.1 Type Definitions . 13 2.1.2 Frequently Used Macros . 13 2.1.3 Debugging Macros . 14 2.1.4 Memory . 16 2.1.5 String Handling . 18 2.2 Data Structures . 20 2.2.1 Lists . 20 2.2.2 Trees . 24 2.2.3 Hash Tables . 29 2.3 The Main Event Loop . 31 2.4 Other Features . 33 II Object-Oriented Programming in C 35 3 Semi-Object-Oriented Programming in C 37 3.1 Header Example . 37 3.1.1 Project Namespace . 37 3.1.2 Class Namespace . 39 3.1.3 Lowercase, Uppercase or CamelCase? . 39 3.1.4 Include Guard . 39 3.1.5 C++ Support . 39 1 3.1.6 #include . 39 3.1.7 Type Definition . 40 3.1.8 Object Constructor . 40 3.1.9 Object Destructor .
    [Show full text]
  • The Gnome Desktop Comes to Hp-Ux
    GNOME on HP-UX Stormy Peters Hewlett-Packard Company 970-898-7277 [email protected] THE GNOME DESKTOP COMES TO HP-UX by Stormy Peters, Jim Leth, and Aaron Weber At the Linux World Expo in San Jose last August, a consortium of companies, including Hewlett-Packard, inaugurated the GNOME Foundation to further the goals of the GNOME project. An organization of open-source software developers, the GNOME project is the major force behind the GNOME desktop: a powerful, open-source desktop environment with an intuitive user interface, a component-based architecture, and an outstanding set of applications for both developers and users. The GNOME Foundation will provide resources to coordinate releases, determine future project directions, and promote GNOME through communication and press releases. At the same conference in San Jose, Hewlett-Packard also announced that GNOME would become the default HP-UX desktop environment. This will enhance the user experience on HP-UX, providing a full feature set and access to new applications, and also will allow commonality of desktops across different vendors' implementations of UNIX and Linux. HP will provide transition tools for migrating users from CDE to GNOME, and support for GNOME will be available from HP. Those users who wish to remain with CDE will continue to be supported. Hewlett-Packard, working with Ximian, Inc. (formerly known as Helix Code), will be providing the GNOME desktop on HP-UX. Ximian is an open-source desktop company that currently employs many of the original and current developers of GNOME, including Miguel de Icaza. They have developed and contributed applications such as Evolution and Red Carpet to GNOME.
    [Show full text]
  • A Brief History of GNOME
    A Brief History of GNOME Jonathan Blandford <[email protected]> July 29, 2017 MANCHESTER, UK 2 A Brief History of GNOME 2 Setting the Stage 1984 - 1997 A Brief History of GNOME 3 Setting the stage ● 1984 — X Windows created at MIT ● ● 1985 — GNU Manifesto Early graphics system for ● 1991 — GNU General Public License v2.0 Unix systems ● 1991 — Initial Linux release ● Created by MIT ● 1991 — Era of big projects ● Focused on mechanism, ● 1993 — Distributions appear not policy ● 1995 — Windows 95 released ● Holy Moly! X11 is almost ● 1995 — The GIMP released 35 years old ● 1996 — KDE Announced A Brief History of GNOME 4 twm circa 1995 ● Network Transparency ● Window Managers ● Netscape Navigator ● Toolkits (aw, motif) ● Simple apps ● Virtual Desktops / Workspaces A Brief History of GNOME 5 Setting the stage ● 1984 — X Windows created at MIT ● 1985 — GNU Manifesto ● Founded by Richard Stallman ● ● 1991 — GNU General Public License v2.0 Our fundamental Freedoms: ○ Freedom to run ● 1991 — Initial Linux release ○ Freedom to study ● 1991 — Era of big projects ○ Freedom to redistribute ○ Freedom to modify and ● 1993 — Distributions appear improve ● 1995 — Windows 95 released ● Also, a set of compilers, ● 1995 — The GIMP released userspace tools, editors, etc. ● 1996 — KDE Announced This was an overtly political movement and act A Brief History of GNOME 6 Setting the stage ● 1984 — X Windows created at MIT “The licenses for most software are ● 1985 — GNU Manifesto designed to take away your freedom to ● 1991 — GNU General Public License share and change it. By contrast, the v2.0 GNU General Public License is intended to guarantee your freedom to share and ● 1991 — Initial Linux release change free software--to make sure the ● 1991 — Era of big projects software is free for all its users.
    [Show full text]
  • Gconf: Manageable User Preferences
    GConf: Manageable User Preferences Havoc Pennington Red Hat, Inc. [email protected], http://pobox.com/˜hp Abstract liMirror and ACAP. Finally, it presents some initial ideas for a Phase Two version of GConf. GConf is a system for storing user prefer- Phase Two is very much a work-in-progress. ences, being deployed as part of the GNOME 2.0 desktop. This paper discusses the ben- 2 Motivation efits of the GConf system, the strengths and weaknesses of the current implementation, and plans for future enhancements. Several years ago it was becoming obvious that GNOME’s initial approach to storing prefer- ences (a simple API for writing key-value pairs 1 Introduction to files) had a lot of limitations: GConf started out very simply in late 1999, as • It did not work for preferences that af- my first project at Red Hat. It was a straightfor- fected or were manipulated by multiple ward response to concrete problems encoun- applications, because there was no way tered while creating the GNOME desktop, and for applications to know a setting had designed to be implementable in a few months changed. GNOME 1.x contains numerous by a programmer with limited experience (i.e., hacks to work around this, and apps have by me). Much of the current implementation to be restarted before certain preferences (let’s call it Phase One) was created at that take effect. time. • Administration features were missing, GConf saw some limited use as part of the such as applying different defaults to dif- GNOME 1.4 platform—specifically in Nau- ferent groups of users, or storing defaults tilus and Galeon—but it wasn’t widely adopted for many machines on one network server.
    [Show full text]
  • Information on Open Source Software When Filling in The
    Information on Open Source Software When filling in the below list, please follow these instructions: - Use a separate sheet for each firmware version. - Mark the firmware version and the product in which the firmware is used on the first side. - It is of utmost importance that the list includes all Open Source software contained in the firmware. - Specify the precise name of the software including its version number (Example: Siproxd – SIP proxy/masquerading daemon Version: 0.5.10). - Specify the license under which the software is released including (if applicable) its version (Example: General Public License Version 2 or BSD-3 clause license). - If available, add any information on copyright notice or eventual remarks. Firmware and version: AT904L-03.18 Product: AT904L Software and version number License and License Version Copyright notice / remarks Encode and Decode base64 files Public domain John Walker 1.5 bridge-utils 1.4 General Public License Version 2 Lennert Buytenhek BusyBox 1.16.2 General Public License Version 2 Peter Willis, Emanuele Aina, Erik Andersen, Laurence Anderson, Jeff Angielski, Enrik Berkhan, Jim Bauer, Edward Betts, John Beppu, David Brownell, Brian Candler, Randolph Chung, Dave Cinege, Jordan Crouse, Magnus Damm, Larry Doolittle, Glenn Engel, Gen- nady Feldman, Robert Griebl, Karl M. Hegbloom, Daniel Jacobowitz, Matt Kraai, Rob Landley, Stephan Linz, John Lombardo, Glenn Mc- Grath, Manuel Novoa III, Vladimir Oleynik, Bruce Perens, Rodney Radford, Tim Riker, Kent Robotti, Chip Rosenthal, Pavel Roskin, Gyepi Sam, Rob Sullivan, Linus Torvalds, Mark Whitley, Charles P. Wright, Enrique Zanardi, Tito Ra- gusa, Paul Fox, Roberto A. Fogli- etta, Bernhard Reutner-Fischer, Mike Frysinger, Jie Zhang Mac 802.11 2011-04-19 General Public License Version 2 Luis R.
    [Show full text]
  • Project Utopia
    Project Utopia http://0-delivery.acm.org.innopac.lib.ryerson.ca/10.1145/1100000/10901... Project Utopia Robert Love Abstract Users—what will they plug in next? Robert is making the computer make sense of hardware, so you don't have to. For the better part of a decade, Linux enthusiasts have waxed poetic on the inherent greatness and looming success of Desktop Linux. Our kernel is so robust! Our applications are infinitely configurable! This is the year of Desktop Linux! Who would ever use Microsoft Windows? These claims and similar—particularly when made back in the 20th century—seem, in retrospect, so trite. Not that I stand righteous—oh no, I laid the praise down as thick as anyone else did. I too was a convert. At least, I did until I realized that hardware support in Linux was awful. Like a deck of cards, my rosy view of Desktop Linux came crashing down, making an 180 degree turn from glowing to ghastly. Heartbroken, I cried myself to sleep every night and went on an inexplicable diet consisting only of cheese and pudding. But this did not last long. One day, the Linux community decided to do something about it. We outlined a plan not only to reach feature parity with the other desktop operating systems, but also to surpass them. Hardware support has come a long way in the last year and a half. This is the story of just how far. A Past Since Forgotten The steps for installing a new hardware peripheral on a Mac might go a bit like this: Step 1: plug hardware in to Mac.
    [Show full text]
  • About This Particular Macintosh 6.03
    Cover ATPM About This Particular Macintosh™ 6.03: About the personal computing experience™ Volume 6, Number 3 March 1, 2000 Sign up for free subscriptions at: http://www.atpm.com/subscribe or send email to: [email protected] ATPM 6.03 ←→1 Cover Cover Art Copyright © 2000 David Knopfler david@knopfler.com http://www.knopfler.com We need new cover art every month! Write to us! Contributors Eric Blair Daniel Chvatik Paul Fatula Scott Feldstein Matthew Glidden Edward Goss Lisa Haller Tom Iov ino Nick Kratz Robert Paul Leitao William Lovett Colin Mansfield Jamie McCornack Grant Osborne David Ozab David Spencer Michael Tsai Christopher Turner Macintosh users like you Please write for ATPM! Check out the FAQ. Editorial Staff Publisher/Editor-in-Chief - Michael Tsai Managing Editor - Daniel Chvatik Associate Editor/Reviews - Paul Fatula ATPM 6.03 ←→2 Cover Associate Editor/Shareware Reviews - William Lovett Copy Editors - Raena Armitage Johann Campbell Paul Fatula Brooke Smith Adam Zaner Publicity Manager - Christopher Turner Contributing Editor/Welcome - Robert Paul Leitao Contributing Editors/Opinion - Tom Iovino Scott Feldstein Contributing Editors/Reviews - Eric Blair Evan Trent Vac a nt Contributing Editor/How To’s & Reviews - Jamie McCornack Contributing Editor/Trivia - Edward Goss Contibuting Editor/Music - David Ozab Contributing Editor/Networking - Matthew Glidden Contributing Editor/Web - David Spencer Help Jedi - Christopher Turner Hollywood Guy - Mike Shields Webmaster - Michael Tsai Assistant Webmaster - A. Lee Bennett Interviews
    [Show full text]