home *** CD-ROM | disk | FTP | other *** search
- Xref: sparky comp.arch:11785 comp.sys.dec:6554 comp.sys.sgi:18217 comp.sys.hp:14255
- Newsgroups: comp.arch,comp.sys.dec,comp.sys.sgi,comp.sys.hp
- Path: sparky!uunet!spool.mu.edu!darwin.sura.net!bogus.sura.net!pandora.pix.com!stripes
- From: stripes@pix.com (Josh Osborne)
- Subject: Re: Comparison of Alpha, MIPS and PA-RISC-II wanted
- Message-ID: <BzIG5M.GDo@pix.com>
- Sender: news@pix.com (The News Subsystem)
- Nntp-Posting-Host: pandora.pix.com
- Organization: Pix Technologies -- The company with no adult supervision
- References: <BzGn32.37C@dscomsa.desy.de> <1gt111INNt3b@hpscit.sc.hp.com> <1992Dec19.012355.26665@ll.mit.edu>
- Date: Sat, 19 Dec 1992 14:27:21 GMT
- Lines: 24
-
- In article <1992Dec19.012355.26665@ll.mit.edu> ejon@ll.mit.edu (Eric Jones) writes:
- >In article <1gt111INNt3b@hpscit.sc.hp.com>, tim@computer.bri.hp.com (Tim Phipps) writes:
- >|> In a previous article Phil Hallam wrote:
- >|> [...The OS kernal only supports sequential files...]
-
- [someone else said, no fseek means they are random access files... then: ]
-
- >But isn't that exactly his point? Sure you can write an ISAM file
- >structure using fseek (and if you're REALLY smart, you might even
- >write an efficient one), but then how's anyone else going to use
- >your files?
-
- If you want others to access your files you make a lib that has functions
- to access them. For example: libdbm, libdbz, and libgdbm, and 4.4's libdb.
-
- This has many benifits, and many drawbacks. Take it elsewhere to disscuss
- it, it's gone far astray from comp.arch (assuming comp.arch is really
- comp.arch.hardware, as the FAQ seems to imply).
- --
- stripes@pix.com "Security for Unix is like
- Josh_Osborne@Real_World,The Multitasking for MS-DOS"
- "The dyslexic porgramer" - Kevin Lockwood
- We all agree on the necessity of compromise. We just can't agree on
- when it's necessary to compromise. - Larry Wall
-