home *** CD-ROM | disk | FTP | other *** search
- Xref: sparky comp.software-eng:2918 comp.arch.storage:526 comp.unix.internals:1582
- Newsgroups: comp.software-eng,comp.arch.storage,comp.unix.internals
- Path: sparky!uunet!sequent!muncher.sequent.com!dafuller
- From: dafuller@sequent.com (David Fuller)
- Subject: Re: Extent-based Filesystems (was: Large Application data sets )
- Message-ID: <1992Jul22.194214.20451@sequent.com>
- Sender: usenet@sequent.com (usenet )
- Nntp-Posting-Host: sequent.sequent.com
- Organization: Sequent Computer Systems Inc.
- References: <1992Jul13.090423.20408@metapro.DIALix.oz.au <33120@cbmvax.commodore.com> <1992Jul21.113652.4898@metapro.DIALix.oz.au>
- Date: Wed, 22 Jul 92 19:42:14 GMT
- Lines: 21
-
- >
- >Who implements extent-based filesystems commercially? How
- >does it compare with the alternatives?
- >
- >I've still to scrape together the money to buy a UNIX
- >machine where I can write my own brain-damaged filesystem.
- >Everybody else seems to have done so ;-)
-
- Well, CP/M had an extent-based file system.
-
- Every proprietary OS I can think of has strongly typed files and that
- means extenting.
-
- In fact, under Tandem's OS the UNIX style of file is given the name
- "unstructured files". Even their editor spits out structured files...
-
-
- --
- Dave Fuller All opinions expressed are my own and not
- Sequent Computer Systems those of Sequent Computer Systems, Inc.
- dafuller@sequent.com
-