Path: utzoo!attcan!uunet!cs.utexas.edu!tut.cis.ohio-state.edu!ucbvax!ulysses!swfc
From: swfc@ulysses.att.com (Shu-Wie F Chen)
Newsgroups: comp.unix.questions
Subject: Re: Summary of responses to file allocation, plea for changes in Unix
Message-ID: <13255@ulysses.att.com>
Date: 29 Jun 90 15:04:25 GMT
References: <2387@nisca.ircc.ohio-state.edu> <6883@scolex.sco.COM>
Sender: netnews@ulysses.att.com
Reply-To: swfc@ulysses.att.com (Shu-Wie F Chen)
Organization: AT&T Bell Labs
Lines: 22

In article <6883@scolex.sco.COM>, seanf@sco.COM (Sean Fagan) writes:
|>In article <2387@nisca.ircc.ohio-state.edu>
karl-d@nisca.ircc.ohio-state.edu (Doug Karl) writes:
|>>  I am in desperate need to allocate a Unix (BSD 4.3, SUN/OS, System V,
|>>  and NeXT/Mach) file prior to using it.  By "allocate" I mean that all of
|>>  the blocks in the file (10's of megabytes long) should be reserved to that
|>>  file instantly).
|>[and lots of other stuff]
|>
|>If you really need it, did you ever consider, before you started collecting,
|>writing an extremely large file (you can write 0's, if you want)?  That
|>would accomplish your purpose, although be a bit wasteful.
|>
|>Your situation doesn't work very well with UNIX anyway, since unix likes to
|>have copies of parts of files in memory, and your trick of just writing to
|>the disk could very well cause stuff to be lost.
  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

I don't understand this statement.

                     
*swfc