From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: <3e150c50b648eee71367993586c7c474@vitanuova.com> To: 9fans@cse.psu.edu Subject: Re: [9fans] remove files in /srv Date: Tue, 1 Feb 2005 20:31:03 +0000 From: rog@vitanuova.com In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Topicbox-Message-UUID: febc1444-eacf-11e9-9d60-3106f5b1d025 > The real solution is to put directories in /srv and have a common > directory and personal directories. But instead I made a smaller > change and tightened up what can be removed. i've sometimes wondered whether it might be worth having the capability to have a non-shared /srv; e.g. #snew gives a new, clean instance of #s owned by the current user. it would be possible to move services between old and new by opening a file in the old #s and writing the fd to the new one. it would also be possible to access the globally shared #s, but perhaps only the hostowner could post names there. that way, there's no clash of service names when people cpu in; easier to implement than directories, too. then again #s is also the source of lots of useful hacks. just a thought.