DOCSLIB.ORG

Linux Client Migration Cookbook - a Practical Planning and Implementation Guide for Migrating to Desktop Linux

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Linux Client Migration Cookbook - a Practical Planning and Implementation Guide for Migrating to Desktop Linux Front cover Linux Client Migrationration Cookbook A Practical Planning and Implementation Guide for Migrating to Desktop Linux For anyone who is exploring or planning for a Linux desktop migration Provides in-depth detail on the technical and organizational challenges Includes methods for planning and implementation Chris Almond Art Cannon Jeroen van Hoof Oliver Mark Christian Patsch Thomas Schwaller Sekhar Vaddadi ibm.com/redbooks International Technical Support Organization Linux Client Migration Cookbook - A Practical Planning and Implementation Guide for Migrating to Desktop Linux December 2004 SG24-6380-00 Note: Before using this information and the product it supports, read the information in “Notices” on page xv. First Edition (December 2004) © Copyright International Business Machines Corporation 2004. All rights reserved. Note to U.S. Government Users Restricted Rights -- Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp. Contents Figures . ix Tables . xiii Notices . xv Trademarks . xvi Preface . xix The team that wrote this redbook. xix Acknowledgements . xxi Become a published author . xxi Comments welcome. xxii Part 1. Choosing Linux. 1 Chapter 1. Introduction. 1 1.1 The migration landscape today . 2 1.2 Identifying suitable environments . 3 1.3 Strategic context . 3 1.4 Client environments. 5 1.5 Why Linux . 5 1.6 Linux overview and distribution choices . 6 1.6.1 Licensing . 7 1.7 The rest of this book . 8 Chapter 2. The case for migration . 11 2.1 Why migrate . 12 2.1.1 Desktop security . 12 2.1.2 Costs related to Linux client . 14 2.1.3 Manageability of the Linux client . 16 2.1.4 Client customization . 18 2.1.5 OSS philosophy . 19 2.1.6 Ease of use of the client . 19 2.2 When to migrate - Or not to migrate . 20 2.2.1 Client roles fit thin/slim client model . 20 2.2.2 High number of migratable applications . 21 2.2.3 Organizational readiness . 21 2.3 Migration goals . 21 2.3.1 Pilot migration . 22 © Copyright IBM Corp. 2004. All rights reserved. iii 2.3.2 Full migration. 22 Part 2. Planning the pilot migration . 25 Chapter 3. Organizational and human factors planning . 27 3.1 Assessing usage patterns . 28 3.1.1 Role-based client segmentation . 28 3.1.2 Surveying user data . 29 3.1.3 End-user survey . 30 3.2 Establishing functional continuity . 30 3.2.1 Bridging applications . 30 3.2.2 Functionally equivalent utility applications . 31 3.2.3 Web applications. 32 3.2.4 Building bridges to the server . 32 3.3 Human factors . 33 3.4 Retraining considerations . 34 3.4.1 Bridging applications can separate retraining from migration . 35 3.4.2 Learning a new look and feel . 35 3.4.3 Familiar actions . 35 3.4.4 File systems: Everything has been moved . 35 3.4.5 Hands on Linux prior to migration . 36 Chapter 4. Technical planning . 37 4.1 Assessing the client IT environment . 39 4.1.1 Assessing the context . 39 4.1.2 Assessing the client hardware . 39 4.1.3 Assessing the client software configuration . 41 4.1.4 Assessing data dependencies . 42 4.1.5 Assessing the infrastructure . 44 4.1.6 Assessing the user . 45 4.2 Integrating with existing network services . 45 4.2.1 Setting the environment . 46 4.2.2 Authenticating with a Windows domain. 47 4.2.3 File sharing using domain shares . 48 4.2.4 Printing services in the domain . 49 4.2.5 DHCP and DNS configuration. 50 4.2.6 Web proxy interface . 51 4.3 Standardizing the desktop. 51 4.3.1 Linux standards. 51 4.3.2 Linux desktop environments . 53 4.3.3 Standardization issues . 56 4.4 Migrating applications . 63 4.4.1 Moving back to client/server computing . 64 4.4.2 Logical segmentation - Thin, slim, or fat . 64 iv Linux Client Migration Cookbook - A Practical Planning and Implementation Guide for Migrating to Desktop Linux 4.4.3 Functional segmentation - Fixed function to general office. 65 4.4.4 Software solutions for Linux . 67 4.5 Client administration planning . 68 4.5.1 Operating system and vendor distribution updates. 68 4.5.2 Application updates. 69 4.5.3 Remote administration . 70 4.5.4 Roll-out of additional or replacement clients . 70 4.5.5 Backup of clients . 71 4.5.6 Virus mitigation . 72 4.5.7 Example of administration of enterprise distributions . 72 4.6 Desktop vs. notebook considerations . 76 4.6.1 Hardware considerations . 76 4.6.2 Peripheral extensions . ..
Load more

Recommended publications
  • Copyrighted Material
    33_754935 bindex.qxp 11/7/05 10:09 PM Page 345 Index Applications Menu, 42–43, 68–71 • Symbols • Applixware Office package, 15 appointments, tracking, 210 * (asterisk), 249, 251 archives, packing and unpacking (tar), 20, \ (backslash), 248 337–338 - (dash), 94 arguments, command line, 247 . (dot), 92 asterisk (*), 249, 251 ! (exclamation point), 252–253 Asymmetric DSL (ADSL), 108–109 / (forward slash), 79, 81 attachments, e-mail, 154 > (greater-than sign), 249 audio CDs, playing, 221–223 - (hyphen), 95 authentication, 292 < (less-than sign), 249 automatic command completion, 250 . (period), 96 automatic login, 40, 318–319, 325 | (pipe), 248 ? (question mark), 251 " (quotation marks), 247 ; (semicolon), 248 • B • [] (square brackets), 252 backdoor, 292 .. (two dots or dot-dot), 92 background, desktop, 73–74, 75–76 backing up files, 20 backslash (\), 248 • A • base station, 129 bash (Bourne Again Shell) access point, wireless LAN, 129, 131 automatic command completion, 250 Adobe Portable Document Format. See PDF combining commands, 248 ADSL (Asymmetric DSL), 108–109 described, 47–48, 246 AES (Advanced Encryption Standard), 129 error messages, saving to file, 249–250 aggregator, RSS, 185 file, command input from, 249 AIM (America Online instant messaging output, saving to file, 249 service), 54, 161–162 repeating previously typed commands, Akregator news reader, 54, 185–186 252–253 amaroK music player, 224 syntax, 247–248 Apache Web server, 16 wildcards, 251–252 applets, 68, 75 bastion host, 293 application gateway, 292 bit bucket, 250 applications Blam RSS reader, 54 controlling, 18–19 block device, 94 development, 17 Bluetooth wireless, 20, 271 e-mail, 152–153 bookmark field, 200 GNOME Desktop, illustrated,COPYRIGHTED 64 boot menu MATERIAL items, installing, 27–28 GNU, 343 boot process, starting and stopping services, installing at setup, 32 263–264 KDE Desktop, illustrated, 64 booting, 26–27, 39–40 Linux packages, 11 Bourne Again Shell.
    [Show full text]
  • 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]
  • 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]
  • Linux on the Road
    Linux on the Road Linux with Laptops, Notebooks, PDAs, Mobile Phones and Other Portable Devices Werner Heuser <wehe[AT]tuxmobil.org> Linux Mobile Edition Edition Version 3.22 TuxMobil Berlin Copyright © 2000-2011 Werner Heuser 2011-12-12 Revision History Revision 3.22 2011-12-12 Revised by: wh The address of the opensuse-mobile mailing list has been added, a section power management for graphics cards has been added, a short description of Intel's LinuxPowerTop project has been added, all references to Suspend2 have been changed to TuxOnIce, links to OpenSync and Funambol syncronization packages have been added, some notes about SSDs have been added, many URLs have been checked and some minor improvements have been made. Revision 3.21 2005-11-14 Revised by: wh Some more typos have been fixed. Revision 3.20 2005-11-14 Revised by: wh Some typos have been fixed. Revision 3.19 2005-11-14 Revised by: wh A link to keytouch has been added, minor changes have been made. Revision 3.18 2005-10-10 Revised by: wh Some URLs have been updated, spelling has been corrected, minor changes have been made. Revision 3.17.1 2005-09-28 Revised by: sh A technical and a language review have been performed by Sebastian Henschel. Numerous bugs have been fixed and many URLs have been updated. Revision 3.17 2005-08-28 Revised by: wh Some more tools added to external monitor/projector section, link to Zaurus Development with Damn Small Linux added to cross-compile section, some additions about acoustic management for hard disks added, references to X.org added to X11 sections, link to laptop-mode-tools added, some URLs updated, spelling cleaned, minor changes.
    [Show full text]
  • About SEP Sesam Hybrid Backup and Disaster Recovery
    Hybrid Backup & Disaster Recovery SEP sesam’s Backup & Disaster Recovery Capabilities for the Red Hat Ecosystem 1 Global Storage Management SEP sesam’s Backup and Disaster Recovery Capabilities for the Red Hat Ecosystem Table of Contents Table of Contents 1 About this Document 3 About SEP 3 About SEP sesam Hybrid Backup and Disaster Recovery 3 SEP’s Mission 4 Red Hat Statement 4 SEP‘s Collaboration with Red Hat 5 Value Proposition for Red Hat Solutions 5 Red Hat® Enterprise Linux 7 Bare Metal Recovery Capability for Linux 8 Red Hat® Virtualization 8 Red Hat® Virtualization Backup White Paper 8 Red Hat® Storage 9 SEP‘s Collaboration with SAP 9 SAP HANA Certifications 10 SAP Ecosystem - Protection Overview 10 Datacenter 10 Platforms 10 Hypervisors 10 Operating Systems 10 Databases 11 Applications 11 SAP Statement 11 SEP sesam Customer References in SAP Environments 11 Uniorg 11 Kwizda 12 Linck 12 Inecom Business Solutions 12 Service Provider and Cloud engagement 12 SEP was named one of the 2018 Gartner Peer Insights Customers’ 12 Choice for Data Center Backup and Recovery Software Here are a few examples of our customers statements: 13 Summary / Authors 13 www.sepsoftware.com I SEP sesam’s Backup and Disaster Recovery Capabilities for the Red Hat Ecosystem 2 Global Storage Management SEP sesam’s Backup and Disaster Recovery Capabilities for the Red Hat Ecosystem About this Document This document serves a Red Hat® and SEP value proposition for the joint solutions. Beside of general information we will highlight the sup- port of Red Hat® Virtualization, Red Hat® Enterprise Linux®, Red Hat® Storage, SAP and Service Providers.
    [Show full text]
  • 17H30 : Accueil 18H00 : Présentation 19H00 : Apéro / Discussions
    Les Groupwares Open Source 17h30 : Accueil 18h00 : Présentation 19h00 : Apéro / Discussions RDV Techno Evolix ± Les Groupwares Open Source - 14 Avril 2011 - [email protected] - http://www.evolix.fr/ Sommaire - Présentation Evolix et Actualités - Qu'est-ce qu'un Groupware ? - Les protocoles, les standards - Les "clients" Groupware - Les Groupwares Open Source - Focus sur Zimbra - Témoignage de l'École Centrale de Marseille - Conclusion - Nouvelles offres Evolix RDV Techno Evolix ± Les Groupwares Open Source - 14 Avril 2011 - [email protected] - http://www.evolix.fr/ Présentation et Actualités 1/2 Evolix Infogérance d'infrastructures Open Source Chiffres clés : Créé en 2004 7 personnes + de 200 serveurs infogérés RCP couvrant son métier d©infogérance RDV Techno Evolix ± Les Groupwares Open Source - 14 Avril 2011 - [email protected] - http://www.evolix.fr/ Présentation et Actualités 2/2 News Evolix - Planet Evolix : http://planet.evolix.org/ - Dernières références... - WIP : infra EVOLIX-MNT, EvoLinux, Forge RDV Techno Evolix - 4ème édition - Rencontres clients/amis/prospects autour d'un sujet technique RDV Techno Evolix ± Les Groupwares Open Source - 14 Avril 2011 - [email protected] - http://www.evolix.fr/ Qu'est-ce qu'un Groupware ? Un Groupware est un logiciel favorisant le travail collaboratif. RDV Techno Evolix ± Les Groupwares Open Source - 14 Avril 2011 - [email protected] - http://www.evolix.fr/ Def. Groupware Pour mieux définir un Groupware, parlons des autres technologies que l©on retrouve dans un SI : GED (Gestion Electronique des Documents) : Alfresco, MS Project ERP (Logiciel de Gestion d©Entreprise) : OpenERP, OpenBravo, Dolibarr, SAGE, Ciel CRM (Gestion de la Relation Client) : SugarCRM, vTiger, Salesforce Project Management : Trac, Redmine, MS Project Gestion des identifiants/authentification : annuaires (LDAP,AD), SSO (CAS, Shibboleth, Kerberos) Messagerie : Postfix/Dovecot, Exchange, Lotus Notes ...de plus en plus de ces logiciels couvrent plusieurs domaines.
    [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]
  • Head-To-Head: Zimbra Vs Scalix
    Head-to-Head: Zimbra vs Scalix Key Positioning vs Scalix • Innovation leadership . Zimbra has consistently demonstrated innovation leadership in emerging areas of messaging and collaboration, including web-based mash-ups (Zimlets), rich web document authoring and sharing, native over-the-air mobile synchronization, comprehensive server-side indexing/search, and VOIP. Conversely, with less demonstrable innovation, Scalix has relied mostly upon TCO positioning based on Linux. In addition, Scalix’s reliance on HP OpenMail (15+ years old and discontinued by HP) and Oddpost limit Scalix’s ability to innovate in core product areas. • Foundation in open source. Zimbra started as an open source company (as most leading open source projects have done) and open sources all of its key product components -- providing full product transparency and customer investment protection. Conversely, Scalix is attempting to migrate to open source (a strategy without successful market precedent), is open sourcing a discontinued code base (likely not attractive to the open source community), and has no plans or entitlements to open source its web client. In addition, Zimbra has strong relationships with leading open source companies (such as Red Hat and MySQL), is deployed at many leading open source vendors (such as Digium/Asterisk and Mozilla), and has been a key contributor to open source projects such as the OpenAjax Alliance. Finally, Zimbra’s open source foundation enables clean bundling of best-of-breed open source components as product building blocks – a strategy Zimbra regularly employs with the Zimbra Collaboration Suite (which currently bundles 40+ open source components) to rapidly provide innovation and high-quality solutions.
    [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]
  • Report Received March 2006
    2005 was a busy year for me as of POSIX was published (the the USENIX standards represen- Shell and Utilities volume), and tative. There are three major it became a second ISO standard. NICHOLAS M. STOUGHTON standards that I watch carefully: Amendments to these standards I POSIX, which also incorpo- were also under development, USENIX rates the Single UNIX Specifi- and led to the addition of real- cation time interfaces, including Standards I ISO-C pthreads, to the core system call I The Linux Standard Base (LSB) set. Many of the other projects Activities died away as the people involved In order to do that, USENIX lost interest or hit political road- funds my participation in the blocks (most of which were Nick is the USENIX Standards committees that develop and reported in ;login: at the time). Liaison and represents the maintain these standards. Association in the POSIX, ISO C, Throughout 2005, the Free Until the end of the twentieth and LSB working groups. He is century, POSIX was developed the ISO organizational repre- Standards Group (FSG) also sentative to the Austin Group, helped fund these activities. For and maintained by IEEE exclu- a member of INCITS commit- each of these, let’s look at the his- sively. At the same time, the tees J11 and CT22, and the Open Group (also known as Specification Authority sub- tory of the standards, then at group leader for the LSB. what has happened over the past X/Open) had an entirely separate but 100% overlapping standard, [email protected] 12 months or so, and, finally, what is on the agenda for this known as the Single UNIX year.
    [Show full text]
  • Using Outlook™ & Insightconnector™ with Mdaemon
    Using Outlook™ & InsightConnector™ with MDaemon 6.0 Alt-N Technologies, Ltd 1179 Corporate Drive West, #103 Arlington, TX 76006 Tel: (817) 652-0204 © 2002 Alt-N Technologies. All rights reserved. Outlook™ is a trademark of Microsoft, Inc. InsightConnector™ is a trademark of Bynari, Inc. Other product and company names mentioned in this document may be trademarks. Contents Abstract................................................................................................................3 Outlook and Exchange Server Sharing.............................................................4 Sharing with InsightConnector™.......................................................................6 Installing, Configuring and Using InsightConnector™....................................7 Configuring MDaemon.....................................................................................7 Installing InsightConnector...............................................................................8 Configuring Outlook .........................................................................................9 Configuring InsightConnector ........................................................................10 Creating, Sharing and Synchronizing Folders................................................11 Creating....................................................................................................11 Sharing and Synchronizing.......................................................................12 InsightConnector™ 2 Alt-N Technologies Abstract
    [Show full text]