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=none autolearn=ham
	autolearn_force=no version=3.4.4
Received: (qmail 24922 invoked from network); 26 Aug 2021 04:03:45 -0000
Received: from 1ess.inri.net (HELO 4ess.inri.net) (216.126.196.35)
  by inbox.vuxu.org with ESMTPUTF8; 26 Aug 2021 04:03:45 -0000
Received: from 5ess.inri.net ([107.191.111.177]) by 4ess; Wed Aug 25 23:55:02 -0400 2021
Message-ID: <E2CAB4C3558CF4F09660E633BEDC47F8@5ess.inri.net>
Date: Wed, 25 Aug 2021 23:36:29 -0400
From: sl@stanleylieber.com
To: 9front@9front.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 replication high-performance firewall-oriented solution 
Subject: [9front] plan9.ini fs= should accept full dial strings
Reply-To: 9front@9front.org
Precedence: bulk

let's say we want to do both serve a full file system
to certain clients *and* serve a specially constructed
namespace to generic clients trying to 9fs us on the
standard port.

currently, plan9.ini fs= value must be just an ip
address or host name. the system translates it
internally to tcp![ip]!564.

why can't fs= be any valid dial string?

sl