Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!asuvax!mcdphx!riscokid.UUCP!fnf
From: fnf@riscokid.UUCP (Fred Fish)
Newsgroups: comp.unix.wizards
Subject: Re: Reserving Space on Disk
Message-ID: <13212@mcdphx.phx.mcd.mot.com>
Date: 16 Jul 90 22:02:46 GMT
References: <563@hhb.UUCP> <1990Jul15.211608.26025@virtech.uucp> <MOSS.90Jul15190502@ibis.cs.umass.edu>
Sender: listen@mcdphx.phx.mcd.mot.com
Reply-To: fnf@riscokid.UUCP (Fred Fish)
Organization: Motorola Microcomputer Division, Tempe, Az.
Lines: 19

In article <MOSS.90Jul15190502@ibis.cs.umass.edu> moss@cs.umass.edu writes:
>char buf[ONE_K];
>int i;
>
>for (i = 0; i < FOUR_K; ++i)
>  write (fd, buf, ONE_K);
>
>You might want to tune the size of buf up larger than what I have, but still
>somewhat "reasonable". Something between the size of a track and a cylinder on
>the disk might work reasonably well, say 64K or 128K. Enjoy!		Eliot

This reminds me, I've always wondered why there wasn't a /dev/full as a
standard part of unix.  It's the obvious counterpart of /dev/null, and
simply returns as many null bytes as you ask for.  Then all you would
have to do is:

	dd if=/dev/full of=myfile bs=1k count=4k

-Fred