From mboxrd@z Thu Jan  1 00:00:00 1970
X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on inbox.vuxu.org
X-Spam-Level: 
X-Spam-Status: No, score=-0.0 required=5.0 tests=T_SCC_BODY_TEXT_LINE
	autolearn=ham autolearn_force=no version=3.4.4
Received: (qmail 28362 invoked from network); 30 May 2022 14:58:38 -0000
Received: from 9front.inri.net (168.235.81.73)
  by inbox.vuxu.org with ESMTPUTF8; 30 May 2022 14:58:38 -0000
Received: from mimir.eigenstate.org ([206.124.132.107]) by 9front; Mon May 30 10:56:44 -0400 2022
Received: from abbatoir.myfiosgateway.com (pool-74-108-56-225.nycmny.fios.verizon.net [74.108.56.225])
	by mimir.eigenstate.org (OpenSMTPD) with ESMTPSA id 8441e009 (TLSv1.2:ECDHE-RSA-AES256-SHA:256:NO)
	for <9front@9front.org>;
	Mon, 30 May 2022 07:56:33 -0700 (PDT)
Message-ID: <F6E8DFA6B08AF5FBD2A9AAAEBF4A9444@eigenstate.org>
To: 9front@9front.org
Date: Mon, 30 May 2022 10:56:32 -0400
From: ori@eigenstate.org
In-Reply-To: <6bb0ee7b-0916-a6df-913e-3f41256ce1eb@posixcafe.org>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
List-ID: <9front.9front.org>
List-Help: <http://lists.9front.org>
X-Glyph: ➈
X-Bullshit: framework element STM control 
Subject: Re: [9front] [PATCH] private /srv attach option
Reply-To: 9front@9front.org
Precedence: bulk

Quoth Jacob Moody <moody@mail.posixcafe.org>:
> Attaching a private /srv does not effect future
> attaches to '#s' without the private option.
> I figure the global /srv can be explicitly
> given up through chdev if desired.

also, maybe it's time to sit down and think about
where this all goes, rather than tossing random
diffs over the fence.

- What is the current state of locking down... things?
- Why is the current state insufficient?
- Are there places where the current state should have
  been used, but wasn't because of its flaws?
- What exactly is the approach to securing things that
  we're trying to approach?

A soup of new features of 'rfork M' quality is a problem;
let's figure out where we're going.