Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!uflorida!novavax!twwells!bill
From: bill@twwells.uucp (T. William Wells)
Newsgroups: comp.unix.wizards
Subject: Re: getcwd() and friends.
Message-ID: <892@twwells.uucp>
Date: 30 Apr 89 14:38:57 GMT
References: <3675@ficc.uu.net> <14689@rpp386.Dallas.TX.US> <FLEE.89Apr4223010@shire.cs.psu.edu> <16758@mimsy.UUCP> <FLEE.89Apr6112136@shire.cs.psu.edu> <144@titania.warwick.ac.uk> <824@necisa.necisa.oz> <4523@psuvax1.cs.psu.edu>
Reply-To: bill@twwells.UUCP (T. William Wells)
Organization: None, Ft. Lauderdale
Lines: 15
Summary:
Expires:
Sender:
Followup-To:
Distribution:
Keywords:

In article <4523@psuvax1.cs.psu.edu> schwartz@shire.cs.psu.edu (Scott Schwartz) writes:
: I think we need a good dose of Multics: Reading the time should be
: equivalent to accessing an object in virtual memory.  In fact, the
: whole operating system system should behave like that, filesystem,
: system calls, and so on.

Ack, NO! All we need is one rogue pointer and almost ANYTHING can
happen!

That notion is attractive, but the separation produced by having
system calls means that a much smaller class of errors is likely to
do random things to your operating environment.

---
Bill                            { uunet | novavax } !twwells!bill