Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!usc!jarthur!uunet!sco!seanf
From: seanf@sco.COM (Sean Fagan)
Newsgroups: comp.unix.questions
Subject: Re: Summary of responses to file allocation, plea for changes in Unix
Message-ID: <6883@scolex.sco.COM>
Date: 28 Jun 90 22:28:07 GMT
References: <2387@nisca.ircc.ohio-state.edu>
Sender: news@sco.COM
Reply-To: seanf@sco.COM (Sean Fagan)
Organization: The Santa Cruz Operation, Inc.
Lines: 21

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.

-- 
-----------------+
Sean Eric Fagan  | "Just think, IBM and DEC in the same room, 
seanf@sco.COM    |      and we did it."
uunet!sco!seanf  |         -- Ken Thompson, quoted by Dennis Ritchie
(408) 458-1422   | Any opinions expressed are my own, not my employers'.