Xref: utzoo comp.os.vms:9104 comp.unix.wizards:11438
Path: utzoo!attcan!uunet!seismo!sundc!pitstop!sun!decwrl!labrea!rutgers!bellcore!tness7!killer!pollux!dalsqnt!rpp386!jfh
From: jfh@rpp386.Dallas.TX.US (The Beach Bum)
Newsgroups: comp.os.vms,comp.unix.wizards
Subject: Re: VMS vs. UNIX file system
Message-ID: <7296@rpp386.Dallas.TX.US>
Date: 30 Sep 88 00:45:32 GMT
References: <411@marob.MASA.COM> <3597@encore.UUCP> <3438@crash.cts.com> <3625@encore.UUCP> <1127@fredonia.UUCP> <4136@bsu-cs.UUCP>
Reply-To: jfh@rpp386.Dallas.TX.US (The Beach Bum)
Organization: River Parishes Programming, Dallas TX
Lines: 25

In article <4136@bsu-cs.UUCP> dhesi@bsu-cs.UUCP (Rahul Dhesi) writes:
>In article <1127@fredonia.UUCP> mazumdar@fredonia.UUCP (Jin Mazumdar) writes:
>>Although UNIX does not have fixed length
>>records...
>
>It certainly does.  Look at the structure of /etc/utmp and /usr/adm/wtmp
>or equivalent files on your system.

not in the typical sense.  there is no file-system level support for
fixed length records.  unix files are byte streams, meaning [ with the
exception of certain device files ] you can read 1 byte or, hardware
permitting, 1MB.

with other operating systems the size of the record is fixed at file
creation time and may not be changed without copying the contents of
the file using a file conversion utility of some type.  /etc/utmp may
be read one byte at a time, except that the "records" would not have
any meaning.


-- 
John F. Haugh II (jfh@rpp386.Dallas.TX.US)                   HASA, "S" Division

      "Why waste negative entropy on comments, when you could use the same
                   entropy to create bugs instead?" -- Steve Elias