From mboxrd@z Thu Jan  1 00:00:00 1970
Message-ID: <20050129030207.24388.qmail@g.galapagos.bx.psu.edu>
Date: Fri, 28 Jan 2005 22:02:07 -0500
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] mkstemp() 
In-reply-to: <000501c50540$0cfdc290$0200000a@urjc1> 
References: <ACCF003CBA3D09458207DB0CB86AD17D0663DF@XMAIL.asuch.cas.cz>
	<000501c50540$0cfdc290$0200000a@urjc1>
Date: Fri, 28 Jan 2005 22:02:07 -0500
From: Scott Schwartz <schwartz@bio.cse.psu.edu>
Topicbox-Message-UUID: 384c8966-eace-11e9-9e20-41e7f4b1d025

| Creating a name with a random number in /tmp like /tmp/acme.paurea.987987 
| wouldn't suffice?. Given we have private namespaces and random numbers
| normally don't collide /tmp/acme.234234 or even /tmp/23234234 would probably 
| suffice too.

But still, it's nice to have a general solution.  Sometimes you do need
to create a file in a shared space.  One could even imagine a fileserver
that filled in the filename for you, rather like the special purpose
ones under /net.  In general you probably don't want to reserve the name
"clone", but "..." or "" might be ok.