Showing papers on "Software versioning published in 2003"

Metadata Efficiency in Versioning File Systems

Abstract: Versioning file systems retain earlier versions of modified files, allowing recovery from user mistakes or system corruption. Unfortunately, conventional versioning systems do not efficiently record large numbers of versions. In particular, versioned metadata can consume as much space as versioned data. This paper examines two space-efficient metadata structures for versioning file systems and describes their integration into the Comprehensive Versioning File System (CVFS), which keeps all versions of all files. Journal-based metadata encodes each metadata version into a single journal entry; CVFS uses this structure for inodes and indirect blocks, reducing the associated space requirements by 80%. Multiversion b-trees extend each entrys key with a timestamp and keep current and historical entries in a single tree; CVFS uses this structure for directories, reducing the associated space requirements by 99%. Similar space reductions are predicted via trace analysis for other versioning strategies (e.g., on-close versioning). Experiments with CVFS verify that its current-version performance is sim-ilar to that of non-versioning file systems while reducing overall space needed for history data by a factor of two. Although access to historical versions is slower than con-ventional versioning systems, checkpointing is shown to mitigate and bound this effect.

NPACI Rocks: tools and techniques for easily deploying manageable Linux clusters

Abstract: High-performance computing clusters (commodity hardware with low-latency, high-bandwidth interconnects) based on Linux are rapidly becoming the dominant computing platform for a wide range of scientific disciplines. Yet, straightforward software installation, maintenance, and health monitoring for large-scale clusters has been a consistent and nagging problem for non-cluster experts. The NPACI Rocks distribution takes a fresh perspective on management and installation of clusters to dramatically simplify software version tracking and cluster integration. NPACI Rocks incorporates the latest Red Hat distribution (including security patches) with additional cluster-specific software. Using the identical software tools used to create the base distribution, users can customize and localize Rocks for their site. Strong adherence to widely-used (de facto) tools allows Rocks to move with the rapid pace of Linux development. Version 2.2.1 of the toolkit is available for download and installation. Over 100 Rocks clusters have been built by non-cluster experts at multiple institutions (residing in various countries) providing a peak aggregate of 2 TFLOPS of clustered computing. Copyright © 2003 John Wiley & Sons, Ltd.

Method and system for servicing software

Abstract: A system and method for improved software servicing by installation of an updated version is provided. Using branch versioning techniques that support multi-branch development and release versioning techniques that support multi-version development, an update package may include updated files for each branch or release version. The least possible version from the update package may be installed to minimize the risk for potential software bugs introduced by the high frequency of changes made to a higher version. Additionally, any fix installed on a target machine running a particular version may be migrated when updating the target machine to a new version without losing the fix and regressing the change. Such an update may be uninstalled by reverse migration of any fixes before uninstalling files from the version update.

Synchronizing and controlling software downloads, such as for utility meter-reading data collection and processing

Abstract: A system and method for coordinating software downloads and executions, such as in a utility meter collection environment, employs a central server or head-end processor (110) that is coupled to communicate with a network of collection units, such as cell control units (108). A process, such as a state machine, tracks the status of software on the CCUs or groups of CCUs to coordinate software downloads and loading of the software on the CCUs, including adding new or past software versions.

Distributed versioning: consistent replication for scaling back-end databases of dynamic content web sites

Abstract: Dynamic content Web sites consist of a front-end Web server, an application server and a back-end database. In this paper we introduce distributed versioning, a new method for scaling the back-end database through replication. Distributed versioning provides both the consistency guarantees of eager replication and the scaling properties of lazy replication. It does so by combining a novel concurrency control method based on explicit versions with conflict-aware query scheduling that reduces the number of lock conflicts.We evaluate distributed versioning using three dynamic content applications: the TPC-W e-commerce benchmark with its three workload mixes, an auction site benchmark, and a bulletin board benchmark. We demonstrate that distributed versioning scales better than previous methods that provide consistency. Furthermore, we demonstrate that the benefits of relaxing consistency are limited, except for the conflict-heavy TPC-W ordering mix.

Versioning in a rules based decision management system

Abstract: A computer implemented decision management system which provides strategy versioning. The system (a) creates different strategy versions, (b) selects, without technical intervention, a respective strategy version of the created strategy versions, (c) applies, without technical intervention, the selected strategy version to determine interaction strategies, (d) monitors performance based on the determined interaction strategies, and (e) refines the selected strategy version in accordance with the monitored performance. To select and apply strategy versions without technical intervention, a GUI is used to enter, edit and select strategy versions at a desktop. From the GUI, the strategy versions are stored in relational tables within a relational data model. A versioning level is interjected between a system level and a segment level in a definition hierarchy, so that each strategy can be referenced as being a specific strategy version. Versioning can also be leveraged at other levels in the strategy hierarchy and in conjunction with inheritance.

Migration of configuration data from one software installation through an upgrade

Abstract: Setting parameter values are migrated through a new software upgrade. Each software version includes a version number. The version number of the new software is compared to a version number of the current software. The version number of the current software is determined by reading a version number parameter value stored in a non-volatile random access memory (NVRAM). If the version number of the new software is higher than the version number of the current software, for each setting parameter value within a new map file, either a current setting parameter value stored in the NVRAM or a default value from the map file, is loaded into a temporary memory. The map file, corresponding to the current version number parameter value stored in the NVRAM, is used to associate th

Autonomic software version management system, method and program product

Abstract: Under the present invention a software version is used on a first operational level by a set (e.g., one or more) of users. As the software version is being used, its performance is automatically monitored based on predetermined monitoring criteria. Specifically, data relating to the performance of the software version is gathered. Once gathered, the data is automatically analyzed to determine if the actual performance met an expected performance. Based on the analysis, a plan is developed and executed. In particular, if the actual performance failed to meet the expected performance, the software version (or components thereof) could be revised (e.g., via patches, fixes, etc.) to correct the defects, or even rolled back to a previous operational level. Conversely, if the actual performance met or exceeded the expected performance, the software version could be promoted to a next operational level.

Inside Windows Storage: Server Storage Technologies for Windows 2000, Windows Server 2003 and Beyond

Abstract: From the Book: Gordon Moore, Intel's co-founder once observed that the density of transistors per square inch was doubling every year. Subsequently, the pace dropped a little and the doubling was perceived to be once every 18 months instead of once every 12 months. According to industry analysts, the enterprise storage industry is still beating Moore's law in its growth. One estimate is that in the next few years, more data will be generated than what was ever created from the entire dawn of known history! Regardless of the exact role, one must concede that Windows servers have an important role to play in the enterprise storage industry. Knowledge of the storage aspects of the Windows operating system will prove to be invaluable in this situation. This book is a humble attempt to meet this perceived need. A word or two about the conventions used in this book would be helpful. The book uses the phrases "Windows NT" and "Windows Server family" interchangeably. Both are used when some feature that is common across all of Windows NT 4.0, Windows 2000 and Windows Server 2003 are being discussed. When needed, a particular version of the operating system is mentioned e.g. Windows 2000 or Windows Server 2003 and these refer to particular versions of the operating system rather than the operating system in a generic sense. This book has been written for the person somewhat conversant with computers systems and the IT industry that is looking to further his/her knowledge about the storage industry in general and Windows NT architecture details as they apply to storage devices. To be clear, this book is about enterprise storage, and consumer storage details are described cursorily, if at all. The bookattempts to strike a balance between catering to the software professional who knows nothing about storage and the professional somewhat conversant with storage, but looking for some good insights of Windows NT storage architecture. If the reader comes away with just one idea after reading this book, that idea is intended to be a deep appreciation of the steady acceleration of enterprise storage related features that each succeeding release of the Windows NT operating system has and will bring to market. This book attempts to strike a balance between the following aspects: Making information available on a timely basis. Providing detailed information and respecting intellectual property rights. The book covers a number of Software Development Kits (SDKs) that are only available under a Non Disclosure Agreement (NDA) basis. Hence the coverage of these has been necessarily limited to what is already publicly available information. The author has erred on the side of caution and preferred to provide only that information the author is certain is publicly available, but has added value to this often cryptic and difficult to locate information by providing the necessary explanations. Provide information on upcoming Windows NT releases and not just "stale" information about the past Windows NT releases. Such forward looking information is necessary in order to appreciate the clear focus Microsoft has devoted to enterprise storage in the Windows NT operating system. The obvious risk is that plans are subject to change. The book clearly mentions when some particular aspect is related to forthcoming Windows NT releases. A word of caution is in order book makes some forwarding looking statements in the form of expected features in forthcoming releases of the Windows NT operating systems. Microsoft has repeatedly made it clear that the only guaranteed way of identifying features in an operating system release is after the actual release. No matter what is said at trade shows, seminars, etc. there is no guarantee that some features tentatively discussed will ever ship, let alone ship with a particular version of the operating system. Hence the forward looking statements in this book are a best guess and should be treated as such. No material plans of any kind should be based upon these guesses. Any reader who does not appreciate the "Safe Harbor Statement" nature of the previous two paragraphs is highly encouraged to study (and not just read) them again. About This Book The book begins with an overview of Windows NT architecture including the Windows NT I/O sub system and storage driver architectures. This chapter is an attempt to condense the vast amount of information purveyed in the excellent books "Inside Windows NT" (Microsoft Press) and is intended for the reader that does not have the time available to peruse the book in its entirety. Chapter 2 describes Direct Attached Storage which was historically the first choice for storage. Chapter 3 describes Network Attached Storage which was the next major mile stone in enterprise storage. The Windows NT network stack is explained in detail, from the point of view of the storage professional. Chapter 4 describes Fibre Channel Storage Area Networks, a technology that is perceived to be now rapidly maturing and still holding its own in the face of upcoming new technology in the form of IP SCSI and Infiniband Chapter 5 covers the basics of backup/restore and the new Volume Shadow Copy Service (also popularly referred to as snapshots) in Windows Server 2003. Chapter 6 covers file systems and disk virtualization with particular reference to Windows NT. The chapter also discusses cluster file systems. Chapter 7 discusses storage management in general and the various storage management solutions as they apply to Windows NT. Chapter 8 covers new technologies in storage particularly IP Storage (which attempts to meld storage and IP networks) as well as Infiniband. Chapter 9 discusses Windows Server 2003 and Windows 2000 natively supported solutions to provide high availability services (including fail over, fail back, as well as load balancing) using multi ported dual HBAs in a Windows NT server. The chapter also discusses more mundane high availability and performance solutions such as RAID. While the rest of this book is organized into chapters based upon technologies, Chapter 10 is organized by Windows NT releases. Irrespective of what storage technology is being discussed, Chapter 10 traces the storage features as they appeared in Windows NT 4.0, Windows 2000 and expected features in Windows Server 2003 server and beyond. So read on, and I hope, enjoy.

Mining model versioning

Abstract: One implementation provides a computer system that allows front-end software applications to use multiple versions of a data mining model during execution of analytical tasks. In this implementation, the computer system includes a model version selection module that is operable to use a task name in a task request received from a front-end software application to determine a specific version of a data mining model to be used during execution of an analytical task. The computer system also includes a mapping module that is operable to map input data included in the task request received from the front-end software application into a format usable by the specific version of the data mining model.

The Versioning Machine

Abstract: This article describes the background and architecture of The Versioning Machine, a software tool designed to display and compare multiple versions of texts The display environment provides for features traditionally found in codex-based critical editions, such as annotation and introductory material It also takes advantage of opportunities afforded by electronic publishing, such as providing a frame to compare diplomatic versions of witnesses side by side, allowing for manipulatable images of the witness to be viewed alongside the diplomatic edition, and providing users with an enhanced typology of notes

Peer version control system

Abstract: A method of data control for a system server and a sub-network including a plurality of user terminals, the method comprising the steps of providing the system server with updated software versions, selecting one of the user terminals, requesting from the system server a list of the updated software versions that are absent in the selected user terminal, determining whether the unselected user terminals include any of the absent updated software versions, receiving the absent updated software versions to have been included in the unselected user terminals, receiving the absent updated software versions to have not been included in the unselected user terminals, and upgrading the selected user terminal with the received absent updated software versions.

Updating of software

Abstract: A software update system is disclosed, together with a corresponding method These comprise a server holding a database, a client software, and a communications medium to allow the client and server to communicate, the database including, for a plurality of software titles, a title identifier, a version identifier for that title, and a patch location, the client being adapted to use the title identifier to locate a software title resident on a computer system hosting the client, to use the version identifier to identify the present update level of that title, and to use the patch location to allow the download of a patch for that title It is preferred that the title identifier includes the file name of an executable file associated with the software title, and also that the version identifier includes at least one of the version number, the byte size of an executable file associated with the software title, and the version details encoded in the file properties of the executable file The client can interrogate the Windows Registry to ascertain the version number The patch location will usually be an Internet URL It is preferred that the client identifies available patches for selection by the user The user may wish to choose to download certain patches but not others, for example if bandwidth is limited

Caracterização de um processo de software para projetos de software livre

Abstract: Free Software (or Open Source) is software provided with source code that may be freely used, modified and redistributed. Free Software Projects are virtual communities of developers that work on a specific free software product. These developers work geographically dispersed, using simple tools to communicate and coordinate their actions over the Internet. This work analyzes these projects with respect to their software process; in other words, the activities they do to produce, manage and ensure the quality of their software. In the initial sections, I perform a large review of related work in this field, and provide an overview of the main characteristics of free software projects. The main contents of this dissertation is based on two years of participation in free software projects, and on a survey based on a questionnaire that describes over five hundred different free software projects. I present thirteen initial hypothesis, using them as a framework to analyze the results of the survey. Among the projects evaluated in this survey, some common aspects were observed. For instance, most projects have a small team, with less than five developers. I also found a balanced distribution of leadership systems described in other works, including Eric Raymond’s ‘benevolent dictator’ and the committee exemplified by the Apache project. The domains in which these projects tend to concentrate are software engineering and development, networks and security, and multimedia applications. Concerning the software process activities, most projects have their functional requirements established by their authors: the user base for most of the projects includes the development team and the free software community. A large proportion of the projects surveyed are based on pre-existing software, or on previously published standards. Little emphasis is placed on usability and conventional forms of quality assurance. Remarkably, this lack of emphasis on conventional process includes activities like review and testing. Among the tools used by the projects, mailing lists and versioning systems such as CVS come out ahead by a strong margin. A correlation was identified between the size of the project’s team and the software engineering activities that it realizes, but I could not establish a link between the age of the project and these activities. Other correlations were established between the size of the project’s codebase (in terms of lines of code) and its age, size and application domain. The dissertation concludes describing essential parts of the software process in free software projects, and offering suggestions for future work.

Installation relationship database

Abstract: A method and system for administering software product installation, removal and updating on a computer network according to a versioning database, including loading a software distribution set into a versioning database, the software distribution set comprising a software product having a plurality of files for operating the software product on a computer. Loading includes loading a first entity identifying the software distribution set into the versioning database, determining whether an identity of each of the plurality of files is currently identified as an entity currently provided on the versioning database, loading a plurality of second entities each corresponding to a respective file of the plurality of files, wherein only those files of the plurality of files determined not to be identified as an entity currently provided on the versioning database are loaded as second entities. The method and system further include storing the plurality of files, linking the first entity with the plurality of second entities, targeting a workstation in communication with the computer network for installation of the software product corresponding to the software distribution set and installing the software product on the targeted workstation.

Managing the Evolution of .NET Programs

Abstract: The component-based model of code execution imposes some requirements on the software components themselves, and at the same time lays some constraints on the modern run-time environment. Software components need to store descriptive metadata, and the run-time system must access this ‘reflectively’ in order to implement dynamic linking. Software components also undergo dynamic evolution whereby a client component experiences the effects of modifications, made to a service component even though these occurred after the client was built.

System and method for a configuration repository

Abstract: Disclosed are systems and methods for providing configuration information to an application server comprising a server, wherein the server includes web-based distributed authoring and versioning (WebDAV) compatibility, a configuration database disposed on the server, wherein the configuration database stores the configuration information, and a communication interface for facilitating communication between the configuration database and the application server, wherein the application server includes instructions for accessing the configuration database for retrieving configuration information.

Versions for Context Dependent Information Services

Abstract: Context dependent information delivery is an important requirement of cooperative information systems supporting global and mobile access. These systems must be able to adapt the content, structure and presentation of information according to various factors such as the user, the access device and the task at hand. We present a versioning model designed to manage context-varying versions of content, structure and presentation database objects. Further, we describe how this has been integrated into a general web publishing platform to dynamically compose web documents according to the current context state.

System and method for music search and discovery

Abstract: The invention provides a comprehensive and integrated music search and discovery tool that allows a user to find music information available from a provider in one place, by song or artist. The preferred embodiment comprises a mega indexer facility for versioning and bouncing of searchable runtime data structures across multiple systems that is atomic at the HTTP connection level. It further comprises a DCI Today platform for integration of a Web server within a client process providing a framework for secure client side Web applications even while off line. Finally, it comprises a server PreQueue for minimizing the overhead associated with waiting for remote resources in a multi-threaded IO model.

Reconciling versioning and context in hypermedia structure servers

Abstract: Contextual structure servers and versioning servers share a similar goal in allowing different views on a stored structure according to the viewer's perspective. In this paper we argue that a generic contextual model can be used to facilitate versioning. In order to prove our hypothesis we have drawn on our experiences with OHP-Version to extend FOHM's contextual model.

WebDAV: what it is, what it does, why you need it

Abstract: Legacy network file services such as NFS, SMB/CIFS, and AFP changed the way we worked File services running on cross-platform networks allowed us to save our files on remote systems and changed the way we exchanged files with each other Web technology changed our lives and the way we work again In the fall of 2002, due to the demand for a web integrated network file service with powerful content management capabilities, we are offering WebDAV (Web-based Distributed Authoring and Versioning) service in our instructional computer laboratories at Ringling School of Art and Design WebDAV is a set of extensions to HTTP (the protocol that drives the web), which allows users to collaborate with each other to edit and manage files on web servers across the networkWebDAV allows our institution to host a shared file space for each course Students in a course can access the shared space for collaboration with the instructor and other students in the same course Access to the WebDAV share is seamless by incorporating LDAP (Lightweight Directory Access Protocol) into the system to maintain single sign-onIn our implementation, we have integrated the Apache web server, Apache extensions for WebDAV and the LDAP based meta-directory model for user authentication information Furthermore, we have implemented a Perl script, which runs every hour to monitor WebDAV storage usage and triggers alarms for any disk quota breachIn this technical report, we will share our framework, tips and tricks we learned from our deployment of WebDAV with our colleagues We will explain how legacy network file services can be strengthened by providing WebDAV service on both the Windows and Unix platforms Furthermore, we will discuss the issues we had to address and the lessons we learned during and after the deployment process

Method for parallel downloading mobile communication system software

Abstract: This invention discloses a parallel download method for mobile communication system software in which, a background senda target board address and software version data to a parallel agent master process of base station conrol center which receives and stores the data in a memory and makes list according to the stored target board address after receiving the data and forwards the soft version to multiple target boards which makes great achevement in software version renew efficiency, normally, upgrade of a system with 100 base stations needs 8-10 hours at least, yet, software download of all equipments in the system can be finished in 1-2 hours now, besides, network load is greatly reduced.

MTS-switch generic verification

Abstract: An apparatus, method, and computer readable medium for automatically notifying a network administrator of a mismatch between a current software version level in a telecommunications switch and a corresponding entry in a database. The apparatus includes a computer for querying the telecommunications switch for the current software version level of the switch and for querying the database, wherein the database is associated with a switch translation system and the database includes an entry associated with the software version level of the switch. The computer compares the current software version level of the switch with the database entry associated with the software version level of the switch. The method and the computer readable medium include establishing communication between a host computer and a telecommunications switch; querying the switch for the current software version level of the switch; establishing communications between the host computer and a switch translation system; querying a database associated with the switch translation system for a corresponding entry in the database associated with the software version level of the switch; storing the current software version level of the switch in a data store associated with the host computer; and storing the database entry in a data store associated with the host computer.

Inside Windows Server 2003

Abstract: From the Book: The release of a new version of an operating system always brings up lots of questions. Is it worth the time and trouble to upgrade? What are the potential problems? How do I prepare for testing and evaluation and maybe for deployment? These decisions are especially complex in this situation because Windows.NET is not a revolutionary change from Windows 2000. Instead, it incorporates hundreds of improvements, large and small, that you'll need to evaluate, both separately and as a whole, to justify an upgrade. Windows.NET also represents the first time in the history of Microsoft's NT-based product line that the desktop code has been released separately from the server code. By the time.NET server products reach the market, XP will have been available for over a year. To deploy.NET servers, then, you'll need to know how to manage a complex mix of Windows.NET and Windows 2000 and NT servers accessed by any one of a half-dozen Windows clients, not to mention a wide variety of third-party clients. This book is designed to lead you through the complexities of a full Windows.NET deployment in a mixed operating environment. It starts with installing a single server and moves in logical progression through upgrading additional servers, installing hardware, handling name resolution, deploying and integrating Windows.NET DNS, installing and configuring Active Directory, and making.NET-based resources available to authorized clients, both on the local network and across the Internet. The release of Windows.NET also represents a milestone because Microsoft has finally gotten truly fanatical about security, so this book pays special attention to the new security features. Each chapteris constructed to present design principles first, followed by process descriptions that help you identify interoperability issues, and finally the procedures you'll need to install and configure the Windows.NET features covered by the chapter. Each chapter starts off with a list of new features in Windows.NET along with any significant improvements to features carried over from Windows 2000. Experienced Windows 2000 designers and administrators can use this list as a checklist to guide their evaluations. My approach to presenting process details for Windows.NET features reflects my background as a Naval nuclear power plant operator. In the nuclear program, it's not enough to know how to operate a piece of equipment. You have to know the principles behind each element of the equipment's design, how the equipment integrates into the plant as a whole, and how the equipment will affect plant operations if it fails in a variety of circumstances. I was fortunate because this experience allowed me to see how a team of operators, each with an encyclopedic knowledge of the equipment under his control, can keep complex systems running smoothly and even make the job seem easy. I hope to contribute something to your knowledge of Windows.NET so that you can build the same kind of team in your IT organization. Who Should Read This Book Any IT professional who designs, manages, or works with Windows technology should evaluate the features in Windows.NET. This book will help you with that evaluation. If you plan on installing one or more special-function Windows.NET servers, or upgrading to Windows.NET Active Directory, this book will show you how to prepare for the deployment and how to troubleshoot problems that might crop up along the way. If you have already migrated, or are in the process of migrating, to Windows 2000 and you want to know if.NET has any advantages for you, the New Features checklist at the beginning of each chapter will help guide you to the items you need for your evaluation. At a macro level, I was particularly impressed with the attention to security at all levels, especially IIS, and the improvements to Windows DNS, Active Directory replication, trust relationships between forests, the new Active Directory Migration Tool (ADMT), the integrated Resultant Set of Policy (RSoP) tools for group policy management, and the significant new features in terminal services, the Encrypting File System (EFS), Public Key Infrastructure (PKI), and the Distributed File System (Dfs). I would also call to your attention the overall improvement in performance, stability, and memory handling. It takes time and money to upgrade a large infrastructure, but with Windows.NET, you will be rewarded with a system that is fast, and handy to manage, and delivers benefits to your users in the form of speed and convenience. Who This Book Is Not For I've made the assumption throughout the book that you have experience with Windows NT servers and classic NT domains. If you have an IT background with other operating systems, and you prefer diving into the deep end of the pool when you approach a new subject, I think you'll find sufficient background explanations and references to help guide you through all but the most arcane subject areas. If you are just setting out to learn about Windows and networking technologies, this is not a good place to start. Because this is a book about.NET servers, if you are primarily concerned with deploying and managing desktops, you may want to check out one of the many books on Windows XP. If you want to know how the server-side features in Windows.NET interoperate with XP and Windows 2000 clients so you can effectively troubleshoot features such as folder redirection, offline files, group policies, resource sharing, name resolution, remote user access, certificate enrollment, EFS, and smart cards, you'll find plenty of details here. If you are primarily interested in certification on Windows.NET, most of the information you need to pass the exams is here but you may not find it arranged in a way that is conducive to exam preparation. If you want the hands-on experience to go with the paper on the wall, I think you'll benefit from the deployment format of this book as you prepare for the exams. Because of space limitations, this book does not cover the many new features of Internet Information Services (IIS) 6.0 or all the myriad aspects of application-mode terminal services. It also does not cover the interoperability features for Novell NetWare and Novell Directory Services (NDS), Services for Macintosh (SFM), or Services for Unix (SFU). Chapter 11, "Understanding Network Access Security and Kerberos," contains details of Windows.NET Kerberos interoperability with UNIX-based MITv5 Kerberos. Conventions This book uses the following typographical conventions:A new term is set in italics the first time it is introducedmd for example, Microsoft defines a site as an area of reliable, high-speed network communications. Paths for files, Active Directory objects, Registry keys and values, and group policy settings are set in fixed fontmd for example, the Hosts file is located in the \Windows\System32\Drivers\Etc folder, and DNS zone configuration information is stored in the Registry under HKLM Software Microsoft Windows NT CurrentVersion DNS Server Zones. Screen elements that are clicked, selected/deselected, checked/unchecked, opened/closed, or called out for specific attention are set in a fixed-pitch fontmdfor example, click Add to open the Add Standalone Snap-In window; or, deselect the Bridge All Site Links option to remove global transitive bridging for site links. Menu items are set in small capsmd for example, right-click the My Network Places icon and select PROPERTIES from the flyout menu. Names of graphical utilities and command-line utilities with specialized consoles are shown with an initial capital lettermd for example, the Certificates console allows you to view your personal certificates, and objects representing disabled domain controllers are removed using Ntdsutil.

Efficient Consistency for Erasure-coded Data via Versioning Servers (CMU-CS-03-127)

Abstract: This paper describes the design, implementation and performance of a family of protocols for survivable, decentralized data storage. These protocols exploit storage-node versioning to efficiently achieve strong consistency semantics. These protocols allow erasure-codes to be used that achieve network and storage efficiency (and optionally data confidentiality in the face of server compromise). The protocol family is general in that its parameters accommodate a wide range of fault and timing assumptions, up to asynchrony and Byzantine faults of both storage-nodes and clients, with no changes to server implementation or client-server interface. Measurements of a prototype storage system using these protocols show that the protocol performs well under various system model assumptions, numbers of failures tolerated, and degrees of reader-writer concurrency. We thank the members and companies of the PDL Consortium (including EMC, Hewlett-Packard, Hitachi, IBM, Intel, Microsoft, Network Appliance, Oracle, Panasas, Seagate, Sun, and Veritas) for their interest, insights, feedback, and support. We thank IBM and Intel for hardware grants supporting our research efforts. This material is based on research sponsored by the Air Force Research Laboratory, under agreement number F49620-01-1-0433, and by DARPA/ITO’s OASIS program, under Air Force contract number F30602-99-2-0539-AFRL. Garth Goodson was supported by an IBM Fellowship. The U.S. Government is authorized to reproduce and distribute reprints for Governmental purposes notwithstanding any copyright notation thereon. The views and conclusions contained herein are those of the authors and should not be interpreted as necessarily representing the official policies or endorsements, either expressed or implied, of the Air Force Research Laboratory or the U.S. Government.

Versioning of E-Learning Objects Enabling Flexible Reuse.

Abstract: One promise that has always been made in the field of e-learning is the possibility to create and deliver learning material that is adaptable to individual learners. Realising this vision requires the possibility to reuse existing learning objects, combining them in new contexts. Reuse, in turn, can only be supported, if a flexible versioning scheme is in place that can easily handle multiple versions of objects. In this paper, we analyse the requirements of e-learning systems for versioning support. Considering well-known design spaces for versioning systems we develop a versioning scheme that perfectly meets the requirement list. This socalled implicit versioning scheme allows for transparent versioning and reuse of arbitrary content objects. We explicitly stress on the integration of the versioning schemes into the authoring process of e-learning material and discuss its effects on the usability.

Data Modification Language for Full Support of Temporal Schema Versioning.

Abstract: We propose a language to define data update during schema versioning in a temporal object-oriented database With this language, a user can express multi-schema modifications involving extensional data from different schema versions at the same time, improving the database environment with temporal and versioning features concerning database modification We also provide the first steps towards a formal operational semantics for the specification of the basic metadata and database updates

V-Grid-A Versioning Services Framework for the Grid.

Abstract: A large variety of emerging Computational Grid applications require versioning services to support effective management of constantly changing datasets and implementations of data processing transformations. This paper presents V-Grid, a framework for generating Grid Data Services with versioning support from UML models that contain structural description for the datasets and schema tuning information. The generated systems can be integrated using active rules to support dynamic composition of versioning services and large federated workspaces consisting of objects that reside in the individual systems.