>> right.  i was thinking of smoething a little more silly like
>> 
>> 	int f = open(NULL, O_RDWR|O_CREAT|O_UNLINK, 0);
>> 
>> which would give me back something that had a link count of zero.
>
>On what medium would it store its data?

off=hand, i'd say that NULL would imply whatever "." was, or you could
pass a path in, from which the kernel would intuit a specific file
system.

the point is that the file, while backed by disk space somewhere, does
not really exist, and gets deallocated when the file descriptor is
closed.  it's sort of like kernel support for tmpfile, but safer.

-- 
|-----< "CODE WARRIOR" >-----|
codewarrior@daemon.org             * "ah!  i see you have the internet
twofsonet@graffiti.com (Andrew Brown)                that goes *ping*!"
andrew@crossbar.com       * "information is power -- share the wealth."