DOCSLIB.ORG

A Delay Tolerant Networking and System Architecture for Developing Regions

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
A Delay Tolerant Networking and System Architecture for Developing Regions A Delay Tolerant Networking and System Architecture for Developing Regions Michael Demmer Electrical Engineering and Computer Sciences University of California at Berkeley Technical Report No. UCB/EECS-2008-124 http://www.eecs.berkeley.edu/Pubs/TechRpts/2008/EECS-2008-124.html September 25, 2008 Copyright 2008, by the author(s). All rights reserved. Permission to make digital or hard copies of all or part of this work for personal or classroom use is granted without fee provided that copies are not made or distributed for profit or commercial advantage and that copies bear this notice and the full citation on the first page. To copy otherwise, to republish, to post on servers or to redistribute to lists, requires prior specific permission. A Delay Tolerant Networking and System Architecture for Developing Regions by Michael Joshua Demmer B.S. (Brown University) 1998 A dissertation submitted in partial satisfaction of the requirements for the degree of Doctor of Philosophy in Computer Science in the GRADUATE DIVISION of the UNIVERSITY OF CALIFORNIA, BERKELEY Committee in charge: Professor Eric Brewer, Chair Professor Scott Shenker Professor AnnaLee Saxenian Fall 2008 A Delay Tolerant Networking and System Architecture for Developing Regions Copyright 2008 by Michael Joshua Demmer 1 Abstract A Delay Tolerant Networking and System Architecture for Developing Regions by Michael Joshua Demmer Doctor of Philosophy in Computer Science University of California, Berkeley Professor Eric Brewer, Chair Technology has shown significant potential in developing countries, as appropriate de- signs matched with real world need can effectively bridge information gaps, provide greater trans- parency, and improve communication efficiency. Unfortunately, many developing regions environ- ments have a lack of affordable network connectivity. Even where there is connectivity, networks are often characterized by frequent, lengthy, and unpredictable link outages, along with limited bandwidth and congested usage. These challenged network conditions, along with the desire to ex- tend the reach of the network, motivate a different approach to developing applications that is more tolerant of intermittent network characteristics. To address these issues, we have developed an overall system framework aimed at easing the development and deployment of applications in challenged network environments. Our ap- proach is built on a robust implementation of the Delay Tolerant Networking architecture, a generic store-and-forward overlay network that uses medium-term storage within the network to buffer 2 messages during link outages. We present an approach to data routing in these environments that achieves effective results by leveraging the fact that many intermittent network topologies still have an underlying topological stability. We extend the DTN architecture to include a publish/subscribe session layer, providing a more natural fit for many applications and a more robust and efficient framework for communication. Finally, we leverage this framework in TierStore, a distributed shared storage system that eases the adaptation of existing storage-oriented applications and the development of new ones. In this dissertation, we present the design rationale for these contributions, describe and evaluate our implementation efforts, and discuss ways in which our system framework can ease the burden of application development and make deployments more robust. Professor Eric Brewer Dissertation Committee Chair i For my loving wife Rachel ii Contents List of Figures v List of Tables vii 1 Introduction 1 1.1 Potential Benefits of Technology in Developing Regions .............. 3 1.2 Network Connectivity Challenges .......................... 6 1.3 Our Approach ..................................... 9 1.4 Dissertation Outline .................................. 12 2 Background 13 2.1 Store and Forward Networking ............................ 13 2.2 Caching and Replication ............................... 16 2.3 Consistency vs. Availability ............................. 18 2.4 Offline Applications .................................. 20 2.5 Design Themes .................................... 22 3 Implementing the Delay Tolerant Networking Architecture 25 3.1 Delay Tolerant Networking Overview ........................ 28 3.2 Implementation Structure ............................... 32 3.3 Daemon / Router Interface .............................. 37 3.4 Bundle State Management .............................. 39 3.5 Endpoint Identifiers .................................. 42 3.5.1 Links and Adjacencies ............................ 43 3.6 Convergence Layer Interface ............................. 45 3.7 Application Interface ................................. 47 3.8 Simulator Framework ................................. 50 3.9 Evaluation ....................................... 52 3.9.1 Overhead Comparison ............................ 54 3.9.2 Intermittency Tolerance ........................... 58 3.10 Conclusions ...................................... 64 iii 4 Delay Tolerant Link State Routing 65 4.1 Routing Protocol Design Space ............................ 68 4.1.1 Standard Approaches ............................. 68 4.1.2 MANET Routing ............................... 70 4.1.3 DTN Routing ................................. 71 4.2 DTLSR Design .................................... 73 4.2.1 Features of Link State ............................ 73 4.2.2 Modifying Standard Link State ........................ 76 4.3 The DTLSR Protocol ................................. 77 4.3.1 Messages and Flooding ............................ 78 4.3.2 Update Frequency / Expiration ........................ 80 4.3.3 Calculating Best Paths ............................ 81 4.3.4 Administrative Areas ............................. 83 4.3.5 Local Advertisements ............................ 84 4.4 Evaluation ....................................... 85 4.4.1 Protocols Compared ............................. 87 4.4.2 Simulation Scenario ............................. 88 4.4.3 Delivery Results ............................... 89 4.4.4 Delay Results ................................. 91 4.5 Conclusions ...................................... 93 5 A Publish / Subscribe Session Layer for Delay Tolerant Networks 94 5.1 Motivations ...................................... 98 5.2 Design Considerations ................................ 101 5.2.1 Service Model and Session Names ...................... 101 5.2.2 Application Roles .............................. 102 5.2.3 Sequence Identifiers and Obsolete Messages ................ 105 5.2.4 Group Membership and Bundle State .................... 107 5.3 Implementation Details ................................ 110 5.3.1 Session Service Interface ........................... 110 5.3.2 Sequence Identifiers and Vector Clocks ................... 112 5.3.3 Session Membership Protocol ........................ 114 5.4 Related Work ..................................... 116 5.5 Conclusions ...................................... 117 6 TierStore: A Distributed Filesystem for Challenged Networks in Developing Regions 119 6.1 TierStore Design ................................... 122 6.2 Related Work ..................................... 124 6.3 TierStore in Detail .................................. 127 6.3.1 System Components ............................. 129 6.3.2 Objects, Mappings, and Guids ........................ 129 6.3.3 Versions .................................... 130 6.3.4 Persistent Repositories ............................ 132 6.3.5 Updates .................................... 133 6.3.6 Immutable Objects and Deletion ....................... 135 iv 6.3.7 Publications and Subscriptions ........................ 138 6.3.8 Update Distribution .............................. 139 6.3.9 Views and Conflicts ............................. 140 6.3.10 Manual Conflict Resolution ......................... 143 6.3.11 Automatic Conflict Resolution ........................ 145 6.3.12 Object Extensions .............................. 146 6.3.13 Security .................................... 147 6.3.14 Metadata ................................... 148 6.4 TierStore Applications ................................ 149 6.4.1 E-mail Access ................................ 149 6.4.2 Content Distribution ............................. 151 6.4.3 Offline Web Access .............................. 152 6.4.4 Data Collection ................................ 153 6.4.5 Wiki Collaboration .............................. 154 6.5 Evaluation ....................................... 155 6.5.1 Microbenchmarks .............................. 156 6.5.2 Multi-node Distribution ........................... 157 6.5.3 Ongoing Deployments ............................ 160 6.6 Conclusions ...................................... 160 7 Conclusions and Future Work 162 7.1 Dissertation Review .................................. 162 7.2 Design Themes .................................... 164 7.3 Application Examples ................................. 165 7.3.1 Voice Message Phone ............................ 166 7.3.2 Educational Content Distribution ...................... 167 7.3.3 Microfinance Transaction Log Synchronization ............... 168 7.3.4 Remote Medical Consultation ........................ 169 7.4 Future Research Opportunities ............................ 170 7.4.1 Rethinking the Networking API ....................... 171 7.4.2 Exposing Network Reachability ....................... 173 7.4.3 Link Predictions and Erasure Coded Reliability ............... 174 7.4.4
Load more

Recommended publications
  • Why Youtube Buffers: the Secret Deals That Make—And Break—Online Video When Isps and Video Providers Fight Over Money, Internet Users Suffer
    Why YouTube buffers: The secret deals that make—and break—online video When ISPs and video providers fight over money, Internet users suffer. Lee Hutchinson has a problem. My fellow Ars writer is a man who loves to watch YouTube videos— mostly space rocket launches and gun demonstrations, I assume—but he never knows when his home Internet service will let him do so. "For at least the past year, I've suffered from ridiculously awful YouTube speeds," Hutchinson tells me. "Ads load quickly—there's never anything wrong with the ads!—but during peak times, HD videos have been almost universally unwatchable. I've found myself having to reduce the quality down to 480p and sometimes even down to 240p to watch things without buffering. More recently, videos would start to play and buffer without issue, then simply stop buffering at some point between a third and two-thirds in. When the playhead hit the end of the buffer—which might be at 1:30 of a six-minute video—the video would hang for several seconds, then simply end. The video's total time would change from six minutes to 1:30 minutes and I'd be presented with the standard 'related videos' view that you see when a video is over." Hutchinson, a Houston resident who pays Comcast for 16Mbps business-class cable, is far from alone. As one Ars reader recently complained, "YouTube is almost unusable on my [Verizon] FiOS connection during peak hours." Another reader responded, "To be fair, it's unusable with almost any ISP." Hutchinson's YouTube playback has actually gotten better in recent weeks.
    [Show full text]
  • Who Owns the Eyeballs? Backbone Interconnection As a Network Neutrality Issue Jonas from Soelberg
    Who Owns the Eyeballs? Backbone interconnection as a network neutrality issue Jonas From Soelberg Name: Jonas From Soelberg CPR: - Date: August 1, 2011 Course: Master’s thesis Advisor: James Perry Pages: 80,0 Taps: 181.999 Table of Contents 1 Introduction ..................................................................................................................... 4 1.1 Methodology ....................................................................................................................................... 6 2 Understanding the Internet ........................................................................................ 9 2.1 The History of the Internet ............................................................................................................ 9 2.1.1 The Internet protocol ................................................................................................................................. 9 2.1.2 The privatization of the Internet ......................................................................................................... 11 2.2 The Architecture of the Internet ................................................................................................ 12 2.2.1 A simple Internet model .......................................................................................................................... 12 2.2.2 The e2e principle and deep-packet inspection ............................................................................. 14 2.2.3 Modern challenges to e2e ......................................................................................................................
    [Show full text]
  • Volume 1, Section 5.1: Managed Tiered Security
    Enterprise SM VOLUME 1, SECTION 5.1: MANAGED TIERED SECURITY SERVICES Enterprise SM 5.1 MANAGED TIERED SECURITY SERVICES [C.2.7.4, M.2.1.3] Level 3 will support the GSA’s Multi-Tier Security Profiles (MTSP) initiative in accordance with Tier-2 – Protected Service specifications. We teamed with one of the world’s leading Managed Security Services providers, , to offer one of the most complete and reliable Managed Security Solutions available. Our solution is designed to meet or exceed the Government’s requirements for MTSP Tier 2 service, as defined in RFP Section C.2.7.4.1.1.2. A description of our offering is provided below. Responses to the requirements of RFP Section L.34.1.6 follow. The Level 3 MTSP Tier 2 solution includes the Help Desk function specified for Tier 1 service, and additional technical and management components to support security needs of Sensitive but Unclassified (SBU) mission functions and information. Our Managed Tiered Security Service (MTSS) offering will provide a vehicle for agencies to order individual managed security services a la carte or in a bundle. The components include: Volume 1, Section 5.1 Page 667 Rev. 3-5-2007 Managed Tiered Security Services TQC-JTB-05-0002 © 2007 Level 3 Communications, Inc. All rights reserved. Use or disclosure of data contained on this sheet is subject to the restric ions on the title page of this proposal. Enterprise SM Agencies will gain efficiencies and cost savings through service bundling, versus ordering any of the Managed Security Services a la carte.
    [Show full text]
  • Lecture 8: Overview of Computer Networking Roadmap
    Lecture 8: Overview of Computer Networking Slides adapted from those of Computer Networking: A Top Down Approach, 5th edition. Jim Kurose, Keith Ross, Addison-Wesley, April 2009. Roadmap ! what’s the Internet? ! network edge: hosts, access net ! network core: packet/circuit switching, Internet structure ! performance: loss, delay, throughput ! media distribution: UDP, TCP/IP 1 What’s the Internet: “nuts and bolts” view PC ! millions of connected Mobile network computing devices: server Global ISP hosts = end systems wireless laptop " running network apps cellular handheld Home network ! communication links Regional ISP " fiber, copper, radio, satellite access " points transmission rate = bandwidth Institutional network wired links ! routers: forward packets (chunks of router data) What’s the Internet: “nuts and bolts” view ! protocols control sending, receiving Mobile network of msgs Global ISP " e.g., TCP, IP, HTTP, Skype, Ethernet ! Internet: “network of networks” Home network " loosely hierarchical Regional ISP " public Internet versus private intranet Institutional network ! Internet standards " RFC: Request for comments " IETF: Internet Engineering Task Force 2 A closer look at network structure: ! network edge: applications and hosts ! access networks, physical media: wired, wireless communication links ! network core: " interconnected routers " network of networks The network edge: ! end systems (hosts): " run application programs " e.g. Web, email " at “edge of network” peer-peer ! client/server model " client host requests, receives
    [Show full text]
  • Globalfs: a Strongly Consistent Multi-Site File System
    GlobalFS: A Strongly Consistent Multi-Site File System Leandro Pacheco Raluca Halalai Valerio Schiavoni University of Lugano University of Neuchatelˆ University of Neuchatelˆ Fernando Pedone Etienne Riviere` Pascal Felber University of Lugano University of Neuchatelˆ University of Neuchatelˆ Abstract consistency, availability, and tolerance to partitions. Our goal is to ensure strongly consistent file system operations This paper introduces GlobalFS, a POSIX-compliant despite node failures, at the price of possibly reduced geographically distributed file system. GlobalFS builds availability in the event of a network partition. Weak on two fundamental building blocks, an atomic multicast consistency is suitable for domain-specific applications group communication abstraction and multiple instances of where programmers can anticipate and provide resolution a single-site data store. We define four execution modes and methods for conflicts, or work with last-writer-wins show how all file system operations can be implemented resolution methods. Our rationale is that for general-purpose with these modes while ensuring strong consistency and services such as a file system, strong consistency is more tolerating failures. We describe the GlobalFS prototype in appropriate as it is both more intuitive for the users and detail and report on an extensive performance assessment. does not require human intervention in case of conflicts. We have deployed GlobalFS across all EC2 regions and Strong consistency requires ordering commands across show that the system scales geographically, providing replicas, which needs coordination among nodes at performance comparable to other state-of-the-art distributed geographically distributed sites (i.e., regions). Designing file systems for local commands and allowing for strongly strongly consistent distributed systems that provide good consistent operations over the whole system.
    [Show full text]
  • Emerging Cyber Threats to the United States Hearing
    EMERGING CYBER THREATS TO THE UNITED STATES HEARING BEFORE THE SUBCOMMITTEE ON CYBERSECURITY, INFRASTRUCTURE PROTECTION, AND SECURITY TECHNOLOGIES OF THE COMMITTEE ON HOMELAND SECURITY HOUSE OF REPRESENTATIVES ONE HUNDRED FOURTEENTH CONGRESS SECOND SESSION FEBRUARY 25, 2016 Serial No. 114–55 Printed for the use of the Committee on Homeland Security Available via the World Wide Web: http://www.gpo.gov/fdsys/ U.S. GOVERNMENT PUBLISHING OFFICE 21–527 PDF WASHINGTON : 2016 For sale by the Superintendent of Documents, U.S. Government Publishing Office Internet: bookstore.gpo.gov Phone: toll free (866) 512–1800; DC area (202) 512–1800 Fax: (202) 512–2104 Mail: Stop IDCC, Washington, DC 20402–0001 COMMITTEE ON HOMELAND SECURITY MICHAEL T. MCCAUL, Texas, Chairman LAMAR SMITH, Texas BENNIE G. THOMPSON, Mississippi PETER T. KING, New York LORETTA SANCHEZ, California MIKE ROGERS, Alabama SHEILA JACKSON LEE, Texas CANDICE S. MILLER, Michigan, Vice Chair JAMES R. LANGEVIN, Rhode Island JEFF DUNCAN, South Carolina BRIAN HIGGINS, New York TOM MARINO, Pennsylvania CEDRIC L. RICHMOND, Louisiana LOU BARLETTA, Pennsylvania WILLIAM R. KEATING, Massachusetts SCOTT PERRY, Pennsylvania DONALD M. PAYNE, JR., New Jersey CURT CLAWSON, Florida FILEMON VELA, Texas JOHN KATKO, New York BONNIE WATSON COLEMAN, New Jersey WILL HURD, Texas KATHLEEN M. RICE, New York EARL L. ‘‘BUDDY’’ CARTER, Georgia NORMA J. TORRES, California MARK WALKER, North Carolina BARRY LOUDERMILK, Georgia MARTHA MCSALLY, Arizona JOHN RATCLIFFE, Texas DANIEL M. DONOVAN, JR., New York BRENDAN P. SHIELDS, Staff Director JOAN V. O’HARA, General Counsel MICHAEL S. TWINCHEK, Chief Clerk I. LANIER AVANT, Minority Staff Director SUBCOMMITTEE ON CYBERSECURITY, INFRASTRUCTURE PROTECTION, AND SECURITY TECHNOLOGIES JOHN RATCLIFFE, Texas, Chairman PETER T.
    [Show full text]
  • THE FUTURE of IDEAS This Work Is Licensed Under a Creative Commons Attribution-Noncommercial License (US/V3.0)
    less_0375505784_4p_fm_r1.qxd 9/21/01 13:49 Page i THE FUTURE OF IDEAS This work is licensed under a Creative Commons Attribution-Noncommercial License (US/v3.0). Noncommercial uses are thus permitted without any further permission from the copyright owner. Permissions beyond the scope of this license are administered by Random House. Information on how to request permission may be found at: http://www.randomhouse.com/about/ permissions.html The book maybe downloaded in electronic form (freely) at: http://the-future-of-ideas.com For more permission about Creative Commons licenses, go to: http://creativecommons.org less_0375505784_4p_fm_r1.qxd 9/21/01 13:49 Page iii the future of ideas THE FATE OF THE COMMONS IN A CONNECTED WORLD /// Lawrence Lessig f RANDOM HOUSE New York less_0375505784_4p_fm_r1.qxd 9/21/01 13:49 Page iv Copyright © 2001 Lawrence Lessig All rights reserved under International and Pan-American Copyright Conventions. Published in the United States by Random House, Inc., New York, and simultaneously in Canada by Random House of Canada Limited, Toronto. Random House and colophon are registered trademarks of Random House, Inc. library of congress cataloging-in-publication data Lessig, Lawrence. The future of ideas : the fate of the commons in a connected world / Lawrence Lessig. p. cm. Includes index. ISBN 0-375-50578-4 1. Intellectual property. 2. Copyright and electronic data processing. 3. Internet—Law and legislation. 4. Information society. I. Title. K1401 .L47 2001 346.04'8'0285—dc21 2001031968 Random House website address: www.atrandom.com Printed in the United States of America on acid-free paper 24689753 First Edition Book design by Jo Anne Metsch less_0375505784_4p_fm_r1.qxd 9/21/01 13:49 Page v To Bettina, my teacher of the most important lesson.
    [Show full text]
  • QUESTION 20-1/2 Examination of Access Technologies for Broadband Communications
    International Telecommunication Union QUESTION 20-1/2 Examination of access technologies for broadband communications ITU-D STUDY GROUP 2 3rd STUDY PERIOD (2002-2006) Report on broadband access technologies eport on broadband access technologies QUESTION 20-1/2 R International Telecommunication Union ITU-D THE STUDY GROUPS OF ITU-D The ITU-D Study Groups were set up in accordance with Resolutions 2 of the World Tele- communication Development Conference (WTDC) held in Buenos Aires, Argentina, in 1994. For the period 2002-2006, Study Group 1 is entrusted with the study of seven Questions in the field of telecommunication development strategies and policies. Study Group 2 is entrusted with the study of eleven Questions in the field of development and management of telecommunication services and networks. For this period, in order to respond as quickly as possible to the concerns of developing countries, instead of being approved during the WTDC, the output of each Question is published as and when it is ready. For further information: Please contact Ms Alessandra PILERI Telecommunication Development Bureau (BDT) ITU Place des Nations CH-1211 GENEVA 20 Switzerland Telephone: +41 22 730 6698 Fax: +41 22 730 5484 E-mail: [email protected] Free download: www.itu.int/ITU-D/study_groups/index.html Electronic Bookshop of ITU: www.itu.int/publications © ITU 2006 All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU. International Telecommunication Union QUESTION 20-1/2 Examination of access technologies for broadband communications ITU-D STUDY GROUP 2 3rd STUDY PERIOD (2002-2006) Report on broadband access technologies DISCLAIMER This report has been prepared by many volunteers from different Administrations and companies.
    [Show full text]
  • High Velocity Kernel File Systems with Bento
    High Velocity Kernel File Systems with Bento Samantha Miller, Kaiyuan Zhang, Mengqi Chen, and Ryan Jennings, University of Washington; Ang Chen, Rice University; Danyang Zhuo, Duke University; Thomas Anderson, University of Washington https://www.usenix.org/conference/fast21/presentation/miller This paper is included in the Proceedings of the 19th USENIX Conference on File and Storage Technologies. February 23–25, 2021 978-1-939133-20-5 Open access to the Proceedings of the 19th USENIX Conference on File and Storage Technologies is sponsored by USENIX. High Velocity Kernel File Systems with Bento Samantha Miller Kaiyuan Zhang Mengqi Chen Ryan Jennings Ang Chen‡ Danyang Zhuo† Thomas Anderson University of Washington †Duke University ‡Rice University Abstract kernel-level debuggers and kernel testing frameworks makes this worse. The restricted and different kernel programming High development velocity is critical for modern systems. environment also limits the number of trained developers. This is especially true for Linux file systems which are seeing Finally, upgrading a kernel module requires either rebooting increased pressure from new storage devices and new demands the machine or restarting the relevant module, either way on storage systems. However, high velocity Linux kernel rendering the machine unavailable during the upgrade. In the development is challenging due to the ease of introducing cloud setting, this forces kernel upgrades to be batched to meet bugs, the difficulty of testing and debugging, and the lack of cloud-level availability goals. support for redeployment without service disruption. Existing Slow development cycles are a particular problem for file approaches to high-velocity development of file systems for systems.
    [Show full text]
  • Using the Andrew File System on *BSD [email protected], Bsdcan, 2006 Why Another Network Filesystem
    Using the Andrew File System on *BSD [email protected], BSDCan, 2006 why another network filesystem 1-slide history of Andrew File System user view admin view OpenAFS Arla AFS on OpenBSD, FreeBSD and NetBSD Filesharing on the Internet use FTP or link to HTTP file interface through WebDAV use insecure protocol over vpn History of AFS 1984: developed at Carnegie Mellon 1989: TransArc Corperation 1994: over to IBM 1997: Arla, aimed at Linux and BSD 2000: IBM releases source 2000: foundation of OpenAFS User view <1> global filesystem rooted at /afs /afs/cern.ch/... /afs/cmu.edu/... /afs/gorlaeus.net/users/h/hugo/... User view <2> authentication through Kerberos #>kinit <username> obtain krbtgt/<realm>@<realm> #>afslog obtain afs@<realm> #>cd /afs/<cell>/users/<username> User view <3> ACL (dir based) & Quota usage runs on Windows, OS X, Linux, Solaris ... and *BSD Admin view <1> <cell> <partition> <server> <volume> <volume> <server> <partition> Admin view <2> /afs/gorlaeus.net/users/h/hugo/presos/afs_slides.graffle gorlaeus.net /vicepa fwncafs1 users hugo h bram <server> /vicepb Admin view <2a> /afs/gorlaeus.net/users/h/hugo/presos/afs_slides.graffle gorlaeus.net /vicepa fwncafs1 users hugo /vicepa fwncafs2 h bram Admin view <3> servers require KeyFile ~= keytab procedure differs for Heimdal: ktutil copy MIT: asetkey add Admin view <4> entry in CellServDB >gorlaeus.net #my cell name 10.0.0.1 <dbserver host name> required on servers required on clients without DynRoot Admin view <5> File locking no databases on AFS (requires byte range locking)
    [Show full text]
  • Filesystems HOWTO Filesystems HOWTO Table of Contents Filesystems HOWTO
    Filesystems HOWTO Filesystems HOWTO Table of Contents Filesystems HOWTO..........................................................................................................................................1 Martin Hinner < [email protected]>, http://martin.hinner.info............................................................1 1. Introduction..........................................................................................................................................1 2. Volumes...............................................................................................................................................1 3. DOS FAT 12/16/32, VFAT.................................................................................................................2 4. High Performance FileSystem (HPFS)................................................................................................2 5. New Technology FileSystem (NTFS).................................................................................................2 6. Extended filesystems (Ext, Ext2, Ext3)...............................................................................................2 7. Macintosh Hierarchical Filesystem − HFS..........................................................................................3 8. ISO 9660 − CD−ROM filesystem.......................................................................................................3 9. Other filesystems.................................................................................................................................3
    [Show full text]
  • Wang Systems Networking VS Network Core (Standard Components) Software Bulletin Release 8.21 Release 8.30
    ... ·.·,:·:··.···'Wang Systems Networkiitg VS Network Core (Standard Components) Software Bulletin Release 8.21 Release 8.30 .. ' ~ t -..~ ~. ·.J. ~ \~ --- ..,·I Wang Systems Networking VS Network Core (Standard Components) Software Bulletin Release 8.21 Release 8.30 1st Edition - July 1986 Copyright c Wang Laboratories, Inc., 1986 71 S-0542.01 i\'14§• WANG LABORATORIES, INC. ONE INDUSTRIAL AVE., LOWELL, MA 01851 TEL. (617) 459-5000, TWX 710-343-6769, TELEX 94-7421 Disclaimer of Warranties and Limitation of Liabilities The staff of Wang Laboratories, Inc., has taken due care in preparing this manual. How­ ever, nothing contained herein modifies or alters in any way the standard terms and conditions of the Wang purchase, lease, or license agreement by which the product was acquired, nor increases in any way Wang's liability to the customer. In no event shall Wang or its subsidiaries be liable for incidental or consequential damages in connection with or arising from the use of the product, the accompanying manual, or any related materials. Software Notice All Wang Program Products (software) are licensed to customers in accordance with the terms and conditions of the Wang Standard Software License. No title or ownership of Wang software is transferred, and any use of the software beyond the terms of the aforesaid license, without the written authorization of Wang, is prohibited. Warning This equipment generates, uses, and can radiate radio frequency energy and, if not ,~ installed and used in accordance with the instructions manual, may cause interference to radio communications. It has been tested and found to comply with the limits for a Class A computing device, pursuant to Subpart J of Part 15 of FCC rules, which are designed to provide reasonable protection against such interference when operated in a commercial environment.
    [Show full text]