*BSD News Article 68368


Return to BSD News archive

Path: euryale.cc.adfa.oz.au!newshost.anu.edu.au!harbinger.cc.monash.edu.au!news.rmit.EDU.AU!news.unimelb.EDU.AU!munnari.OZ.AU!news.ecn.uoknor.edu!qns3.qns.com!imci4!newsfeed.internetmci.com!swrinde!howland.reston.ans.net!blackbush.xlink.net!rz.uni-karlsruhe.de!news.uni-stuttgart.de!news.rhrz.uni-bonn.de!saph2.physik.uni-bonn.de!juengst
From: juengst@saph1.physik.uni-bonn.de (Henry G. Juengst)
Newsgroups: comp.unix.misc,comp.unix.bsd.misc
Subject: Re: How to delete files within C programs
Date: 12 May 1996 19:31:05 GMT
Organization: Institut fuer Strahlen- und Kernphysik
Lines: 93
Sender: juengst@saph2.physik.uni-bonn.de (Henry G. Juengst)
Distribution: world
Message-ID: <4n5e9p$33m@news.rhrz.uni-bonn.de>
References: <Oum-El-Kheir.Benkahla-3004961724540001@mac-ugm-3.imag.fr> <4mv7jj$fl7@innocence.interface-business.de> <4mvdoj$6e2@news.rhrz.uni-bonn.de> <3193FA77.7BC5F06A@lambert.org>
Reply-To: juengst@saph1.physik.uni-bonn.de
NNTP-Posting-Host: saph1.physik.uni-bonn.de
Xref: euryale.cc.adfa.oz.au comp.unix.misc:22657 comp.unix.bsd.misc:1020


In article <3193FA77.7BC5F06A@lambert.org>, Terry Lambert <terry@lambert.org> writes:
>Henry G. Juengst wrote:
>] The point at the beginning was, that I think the names 'unlink'
>] and 'remove' are meaningless and unclear for beginners. This
>] is the case for most identifier in unix/C. Therefore unix and
>] C are no good environment for beginners. A good book might
>] help, but that does not make it much better (of course, that
>] depends on the person).
>
>There is no method of arranging software such that it is intuitive
>for a user to interact with it.

Right. But we can make it easier. It is not too much work to
use readable identifiers with a hierachy instead of abbreviations.
X11 and VMS show that (not perfectly).

>
>Humans and computers do not share common schnelling points.
>
>The Schnelling pint "READ.ME" poses the unbridgable question
>"How am I supposed to do that?".
>
>Even the Macintosh has problems "What is 'double click'?".
>

Or does the mouse need cheese? :-)

>
>All systems have learning curves.
>

Sure.

>
>I think the negative statements regarding the "Openness" of
>"OpenVMS" are pretty much tied to the ability to compile existing
>code for the thing and have it run ("Open software platform")
>and the ability to run it on commodity hardware ("Open
>architecture").
>
>VMS can not build most existing code becaue it strictly
>implements one of the few published API standards which it
>conforms to: POSIX.  The implementation, like that of Windows
>NT, is a marketing checkbox, not a real usable engineering
>soloution.

Of course, it is not trivial to compile unix specific code for another
operation system. But the reverse way is also hard. Anyway, the list
of running unix software on VMS systems is long enough to show that
it is not impossible.

BTW, POSIX compatiblity is one of the arguments which is used in
most discussions about the compatiblity of a unix operation system.
But we also know that POSIX is not enough.

>
>VMS does not run on commodity hardware, much as DEC would like
>economies of scale to kick in in the production of their
>proprietary hardware line to allow them to twist the definition
>of "commodity".

I think most hardware is proprietary. This changes in combination
with hardware. BSD is also running on VAXes. OSF/1 (now 'DEC unix')
runs on Alphas. 

>
>Protestations to the contrary will not change these facts, and
>thus, from that perspective, VMS is *not* open.  You can freely
>choose a different perspective, but indoing so, realize that
>you will be in the minority.

Perhaps this also depends on the definition of "open".

May be the situation on the market changes in somes years. I do not
know. But do not forget what AT&T und the Berkeley University did with
their unix lines.

>					Regards,
>                                        Terry Lambert
>                                        terry@lambert.org
>---
>Any opinions in this posting are my own and not those of my present
>or previous employers.

Henry

--
juengst@saph1.physik.uni-bonn.de         [131.220.161.1]  (Internet)
omni:.de.uni-bonn.physik.saph1::juengst                   (DECnet/OSI, phase V)
saph1::juengst                           [26.358]         (DECnet, phase IV)

Any opinions in this mail are my own.