Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.2 9/18/84; site psivax.UUCP
Path: utzoo!watmath!clyde!burl!ulysses!allegra!oliveb!hplabs!sdcrdcf!psivax!friesen
From: friesen@psivax.UUCP (Stanley Friesen)
Newsgroups: net.unix-wizards,net.unix
Subject: Re: unix file system
Message-ID: <586@psivax.UUCP>
Date: Tue, 30-Jul-85 16:57:33 EDT
Article-I.D.: psivax.586
Posted: Tue Jul 30 16:57:33 1985
Date-Received: Sat, 3-Aug-85 03:27:05 EDT
References: <3287@decwrl.UUCP> <4053@alice.UUCP>
Reply-To: friesen@psivax.UUCP (Stanley Friesen)
Organization: Pacesetter Systems Inc., Sylmar, CA
Lines: 22
Xref: watmath net.unix-wizards:14153 net.unix:5225
Summary: 

In article <4053@alice.UUCP> ark@alice.UUCP (Andrew Koenig) writes:
>> Some of us at Digital think we have found a basic problem with the  UNIX
>> file  system  for FORTRAN.  The problem is that there is no place to put
>> various kinds of information about  the  contents  of  the  file.
>
>The place to put information about the contents of the file
>is in the file itself.
>
	Absolutely! In fact the obvious solution is to place a header
at the beginning of the file containing such information as record
length, and write the Fortran I/O library so that it understands this
header. Something similar has *already* been incorporated into UNIX,
namely the executable(a.out) file format, which contains a header
specifying type(the "magic number") and the size of each portion
of the executable image. All that need be done is devise a variant
of this system for fixed-length record files!
-- 

				Sarima (Stanley Friesen)

{trwrb|allegra|cbosgd|hplabs|ihnp4|aero!uscvax!akgua}!sdcrdcf!psivax!friesen
or {ttdica|quad1|bellcore|scgvaxd}!psivax!friesen