NetNews Usenet Archive 1992 #16/NN_1992_16.iso/spool/comp/os/os2/misc/25611

Internet Message Format | 1992-07-27 | 2.6 KB

Path: sparky!uunet!mcsun!sun4nl!tuegate.tue.nl!svin02!eba!ebh.eb.ele.tue.nl!wjw
From: [e-mail] (Willem Jan Withagen)
Newsgroups: comp.os.os2.misc
Subject: Re: OO File system (was re: os/2's som)
Message-ID: <[e-mail]>
Date: 27 Jul 92 10:59:56 GMT
References: <[e-mail]>
Sender: [e-mail] (The News system)
Reply-To: [e-mail]
Organization: Digital Systems, Eindhoven University of Technology, the Netherlands
Lines: 56

In article <[e-mail]>, unixg.ubc.ca![e-mail] writes:
=> In article <[e-mail]> [e-mail] (Carl Davidson)
=> writes:
=> >
=> >The best example of an object-oriented file system I know of is the
=> >Apollo Domain file system. It does *precisely* what Pete describes,
=> >i.e. the I/O system knows how to determine the type of object you are
=> >
=>
=> Hahahahhahha!
=>
=> If NT has an operating system like Domain, it'll fall flat on it's
=> face! Domain's BSD type UNIX sucked rocks! Incompatible, unstable,
=> unpredictable, etc.
=>
=> Gimme Sun hardware/software any day over Apollo. Good thing HP bailed
=> Apollo out.
=>

Prrrrrrrrrrf, hi, ha ha.
I'll bite.

There's nothing more sucking than NFS. A braindead protocol which
unfortunatly has become the defacto standard. (I know: this
discussion shouldn't be here. Try in comp.sys.sun, ....)

We've got plenty of diffent boxes around, and if HP had made the
effort of porting Domain/OS to the HP/7xx, we would have kept one of the
most advanced OS'es there has been around.

And it is most certainly not Incompatible, unstable, etc,......
It's only not NFS compatible, but certainly more stable than NFS.

The apollo display system did things on a lousy 68010, which don't even
perform properly under X on an HP/7xx.

And there's a lot more. (It's currently a thread on comp.sys.apollo)

But even in OS/2 there's only a poor man's object-typing to the file
system. If I've got this TeX-dvi file, than I can create an
application, called Dvi-viewer, which is activated when I double-click
on an *.dvi file. The OS sort of knows what application needs to be
executed when the view function is called. It's only a poor man's
object-typing because here it depends on the filename extension.

I think it is also possible to create ones own types, but I'm not shure
yet what that buys me.

    Willem Jan.
--
Digital Information Systems Group, Room EH 10.35
Eindhoven University of Technology
P.O. 513                             Tel: [phone],Fax: [phone]
5600 MB Eindhoven                    The Netherlands
Internet:  [e-mail]
X400:      C=nl;ADMD=400net;PRMD=surf;O=tue;OU=ele;OU=eb;S=WJW;