1 / 6

Understanding Configuration Data Across Operating Systems: A Comparative Perspective

This article examines the intricacies of configuration data across various operating systems, including MS-DOS, UNIX/Linux, and modern Windows versions. It discusses how applications handle configuration through binary files, ASCII files, and the system registry, highlighting the evolution from pre-Windows 95 practices to current methods. The piece also explores the roles of primary and secondary vendors in printer interfacing and the impact of open-source solutions. Lastly, it addresses the nuances of user permissions and interoperability between Linux and Windows systems.

osma
Télécharger la présentation

Understanding Configuration Data Across Operating Systems: A Comparative Perspective

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Operating Systemsa CSA Perspective CPIS 210 John Beckett

  2. Configuration Data • Binary configuration files per-application • MS-DOS, Pre-95 Windows • ASCII configuration files per-application • UNIX/Linux • System Registry • Windows 95+ • Means registry can “get messed up” • Some programs still use former methods 

  3. Whose Job Is It? • Pre-Win95 • Printer interfacing was the app’s task • The Adobe solution • Get a Postscript-enabled printer • Apps need only relate to Postscript • Win95+ • Printer interfacing is the printer manufacturer’s task

  4. Stages of Control • Primary vendor ignores the function • Secondary vendor bridges the gap so their hardware or software will work • Open-source solutions may prevail • Primary vendor recognizes the need • May provide the function themselves • May provide architected interfaces so that “the right” third party can provide the function • Standard (de-facto or agreed) takes over

  5. e.g. IP Development • “Winsock” was used to connect with Internet • Lacking DHCP functionality • Marketing was under the table, and piracy prevailed • Microsoft provided the proper software • Additional functionality may confuse the issue • Few understand what “shared Internet connection” really does

  6. “We Call It…” • Linux: Symbolic Link • Windows: Shortcut • Implementation is similar • Details may be a problem • E.g. User directory: Had to implement “root” on a Windows computer to allow Linux to write on a shared drive using Samba. • Probably much smoother now • E.g. Permissions: These will vary in subtle ways between platforms, so beware

More Related