From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from out5-smtp.messagingengine.com ([66.111.4.29]) by ewsd; Thu Jan 23 10:09:35 EST 2020
Received: from compute1.internal (compute1.nyi.internal [10.202.2.41])
	by mailout.nyi.internal (Postfix) with ESMTP id 0A3EF22011
	for <9front@9front.org>; Thu, 23 Jan 2020 10:09:33 -0500 (EST)
Received: from imap35 ([10.202.2.85])
  by compute1.internal (MEProxy); Thu, 23 Jan 2020 10:09:33 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fastmail.fm; h=
	mime-version:message-id:in-reply-to:references:date:from:to
	:subject:content-type; s=fm2; bh=56lA3DAdCErhbV2PYQVu44Dr0wi+UuK
	/k+qxEgI6mEo=; b=QFNnzJlCaGNad5C9pmhhM8tKf/6phdCaUOyWrk2ylz+Edrd
	kqwp7AyZVPPVDoF3DUfQCbPWbxOlOQdmY8xXJgDtbfOZEBecxVQmgspQ10mEA0GM
	ZGC1iSMJSExq08vUh8V8WB/aweA5fr5FlHx5W+0jaq3LuEgmVVgY5DQriLrpvhGF
	swaCAn+qgwD0aW+4WeRr13A0VsCLzRtz8xFSYJ7lwG4YdLI0+EFqxl1eMUd95ZD4
	o82XR92/fhoKeXdXsKdQp7C4dd3PyLcVQcg6RfmlcEmvuH+FLFU5Vd3HcPdsYRXN
	qw/qqe7sFaMZq37cvBVNegU2EHxL+KuryVDTtXQ==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=
	messagingengine.com; h=content-type:date:from:in-reply-to
	:message-id:mime-version:references:subject:to:x-me-proxy
	:x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm1; bh=56lA3D
	AdCErhbV2PYQVu44Dr0wi+UuK/k+qxEgI6mEo=; b=l8djGff4l9ohR0T4GyQzeo
	DBoaJr1MyVJrLm07+LMGFOIm8e2WQiBqO3jY8SVAkxBeijIq51lH0UBmTjOeem1D
	zXIElBsOXLUjRYOiH4qTJrwKgOjuDwbi3CZDtWS0vyz8yT6YNJWshHE0ix3/2gR5
	MH56Fuwa1vESzMaQdlmpPIKWBPTG8O+2Do3yTjVx33Wo7bd/41k2cfi3mIOCUh0t
	X7pUnheozFrcO177shz4RRtY3UxKU+0spxnjzciJsFORURcv8OSWQI7syGqCNBQm
	VBq1SJi88zuMS6eZYpIVX2AHG4JcXwYf5JThk1vIcFAzTSFiyc1hPiFqCz/1anMw
	==
X-ME-Sender: <xms:LLcpXqhdacXVtKraltr75lKPmeao7WZXbGJzhblbXj_ynK-fCEDRGQ>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedugedrvddvgdeghecutefuodetggdotefrodftvf
    curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu
    uegrihhlohhuthemuceftddtnecunecujfgurhepofgfggfkjghffffhvffutgesthdtre
    dtreertdenucfhrhhomhepfdfgthhhrghnucfirghruggvnhgvrhdfuceovggvkhgvvgeh
    jeesfhgrshhtmhgrihhlrdhfmheqnecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrg
    hmpehmrghilhhfrhhomhepvggvkhgvvgehjeesfhgrshhtmhgrihhlrdhfmh
X-ME-Proxy: <xmx:LLcpXsHxRLBoxST1CB-nO3bGK40ZPd7XQrQH-EKc8S3TgacEB_5MBA>
    <xmx:LLcpXplyPqwPXX0-ETtPZSICZ_0b4kWgvjYtM-LFyn3Y6hPSF8UqJA>
    <xmx:LLcpXhgfhtskXyYaIsu5cdQjF1cpaycHjUg29BgvtmfyXSDJoWKQbQ>
    <xmx:LbcpXr9KNBmAPwZwtYxZcas6zTXJxzh0XGgSq4IR7tSXhBULvU0ODg>
Received: by mailuser.nyi.internal (Postfix, from userid 501)
	id CFDF814C009E; Thu, 23 Jan 2020 10:09:32 -0500 (EST)
X-Mailer: MessagingEngine.com Webmail Interface
User-Agent: Cyrus-JMAP/3.1.7-775-g74f2d12-fmstable-20200121v1
Mime-Version: 1.0
Message-Id: <fa1bd66a-a917-4a87-8a2b-d91c3bb95c73@www.fastmail.com>
In-Reply-To: 
 <CAFSF3XMCqvXicsGjtotMwih4GC2HHTQg0ha5ZSL5wFVkuYNtYQ@mail.gmail.com>
References: <5c2e3e1c-99a4-4caf-9ab4-615035aec1f8@www.fastmail.com>
 <EFC0BF3379A3C032D5568E0E5CB5D3A1@a-b.xyz>
 <CAHjwAuz4a-+om6cXazWhQnVLHjCuh5rY73zN2Y0SsStgHojZgQ@mail.gmail.com>
 <f4e58d5cca0ecd34@orthanc.ca>
 <a92cb1f0-de96-46ae-bb97-27136874d390@www.fastmail.com>
 <CAFSF3XPZrfGxjRZ9JHArvir2tPXoDfvKtK_Ua_7ETrSjGm4CXg@mail.gmail.com>
 <f13fad75-4ac3-4110-a96b-e74e3dfcab75@www.fastmail.com>
 <CAFSF3XMCqvXicsGjtotMwih4GC2HHTQg0ha5ZSL5wFVkuYNtYQ@mail.gmail.com>
Date: Thu, 23 Jan 2020 15:09:12 +0000
From: "Ethan Gardener" <eekee57@fastmail.fm>
To: 9front@9front.org
Subject: Re: [9front] rio wishlists
Content-Type: text/plain
List-ID: <9front.9front.org>
List-Help: <http://lists.9front.org>
X-Glyph: ➈
X-Bullshit: non-blocking transactional full-stack information dependency solution 

On Wed, Jan 22, 2020, at 4:47 PM, hiro wrote:
> i just don't like having two slightly different systems for the same
> thing. environment files and normal files.

I see what you mean, but already we have mount and /shr offering two slightly different systems for another single task, that of mounting removable storage. This situation exists primarily due to rio's private namespaces. This is actually the reason I thought about how to make rio work without private namespaces. ;) On the other hand, I'm not really sure my way would be more elegant overall. I don't hate /srv, it's simple and I admit it may be useful with other private-namespace situations.