From nobody Sat Dec 11 17:57:28 2021
X-Original-To: freebsd-hackers@mlmmj.nyi.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1])
	by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 9ECF818E6EE6
	for <freebsd-hackers@mlmmj.nyi.freebsd.org>; Sat, 11 Dec 2021 17:57:47 +0000 (UTC)
	(envelope-from jamie@freebsd.org)
Received: from gritton.org (gritton.org [162.220.209.3])
	(using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)
	 key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256
	 client-signature RSA-PSS (2048 bits) client-digest SHA256)
	(Client CN "gritton.org", Issuer "gritton.org" (not verified))
	by mx1.freebsd.org (Postfix) with ESMTPS id 4JBFqH3KW8z4hlp;
	Sat, 11 Dec 2021 17:57:47 +0000 (UTC)
	(envelope-from jamie@freebsd.org)
Received: from gritton.org ([127.0.0.3])
	(authenticated bits=0)
	by gritton.org (8.16.1/8.16.1) with ESMTPA id 1BBHvSBH058010;
	Sat, 11 Dec 2021 09:57:28 -0800 (PST)
	(envelope-from jamie@freebsd.org)
List-Id: Technical discussions relating to FreeBSD <freebsd-hackers.freebsd.org>
List-Archive: https://lists.freebsd.org/archives/freebsd-hackers
List-Help: <mailto:freebsd-hackers+help@freebsd.org>
List-Post: <mailto:freebsd-hackers@freebsd.org>
List-Subscribe: <mailto:freebsd-hackers+subscribe@freebsd.org>
List-Unsubscribe: <mailto:freebsd-hackers+unsubscribe@freebsd.org>
Sender: owner-freebsd-hackers@freebsd.org
MIME-Version: 1.0
Date: Sat, 11 Dec 2021 09:57:28 -0800
From: James Gritton <jamie@freebsd.org>
To: freebsd-hackers <freebsd-hackers@freebsd.org>
Cc: Eugene Grosbein <eugen@grosbein.net>, Gleb Popov <arrowd@freebsd.org>,
        "Daniel O'Connor" <darius@dons.net.au>,
        Konstantin Belousov
 <kostikbel@gmail.com>
Subject: Re: What to use in place of abstract unix sockets?
In-Reply-To: <YbTYFaA4WvJOfJw9@kib.kiev.ua>
References: <CALH631kYAz+_=p6VUhxzx0tz8eox804PCK5A9POxQkZTdThZCQ@mail.gmail.com>
 <F0BE714E-E25B-4A49-AA6E-B0E906374446@dons.net.au>
 <CALH631m8P_NG3nTZ1JQ2hhZMTrAMuuGjS8Ahz_qDMu1bFDCzkw@mail.gmail.com>
 <58874E76-8541-46BF-A197-C984D6A869DF@dons.net.au>
 <CALH631nVvp2Ra4RYzEpPkQ-bi_sgqiQ5_XxrP35mTx=8R7dODg@mail.gmail.com>
 <f6cc691e-c709-8c9c-1325-aee14f09ebc1@grosbein.net>
 <YbTYFaA4WvJOfJw9@kib.kiev.ua>
User-Agent: Roundcube Webmail/1.4.11
Message-ID: <2c4d62457377d7bde6a0fbad1050ef8e@freebsd.org>
X-Sender: jamie@freebsd.org
Content-Type: text/plain; charset=US-ASCII;
 format=flowed
Content-Transfer-Encoding: 7bit
X-Rspamd-Queue-Id: 4JBFqH3KW8z4hlp
X-Spamd-Bar: ----
Authentication-Results: mx1.freebsd.org;
	none
X-Spamd-Result: default: False [-4.00 / 15.00];
	 REPLY(-4.00)[]
X-Spam: Yes
X-ThisMailContainsUnwantedMimeParts: N

On 2021-12-11 08:55, Konstantin Belousov wrote:
> That said, implementing 'abstract' unix socket addresses would be nice.

Though if that were to happen, I would want to separate the namespaces
of the abstract sockets.  This seems an analog to the POSIX shm
pseudo-file namespace, which has similar names that aren't really
files (though they still follow a file-like naming scheme).

And then we'd be back where we are now, with a way to add a socket to
a jail's namespace, but requiring per-jail sockets (because there is
no abstract namespace hard-link).

- Jamie