Operating systems a csa perspective
This presentation is the property of its rightful owner.
Sponsored Links
1 / 6

Operating Systems a CSA Perspective PowerPoint PPT Presentation


  • 83 Views
  • Uploaded on
  • Presentation posted in: General

Operating Systems a CSA Perspective. CPIS 210 John Beckett. 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”

Download Presentation

Operating Systems a CSA 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.While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server.


- - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - -

Presentation Transcript


Operating systems a csa perspective

Operating Systemsa CSA Perspective

CPIS 210

John Beckett


Configuration data

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 


Whose job is it

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


Stages of control

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


E g ip development

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


We call it

“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


  • Login