From: Demi Marie Obenour <demiobenour@gmail.com>
To: Alyssa Ross <hi@alyssa.is>
Cc: devel@spectrum-os.org
Subject: Re: [PATCH 2/3] img/app: dbus: don't listen on VSOCK
Date: Mon, 17 Nov 2025 17:08:47 -0500 [thread overview]
Message-ID: <178e38b1-8dd9-4427-98a8-57b66a592ba4@gmail.com> (raw)
In-Reply-To: <87ikfcltxe.fsf@alyssa.is>
[-- Attachment #1.1.1: Type: text/plain, Size: 1980 bytes --]
On 11/14/25 06:45, Alyssa Ross wrote:
> Demi Marie Obenour <demiobenour@gmail.com> writes:
>
>> On 11/13/25 12:56, Alyssa Ross wrote:
>>> Demi Marie Obenour <demiobenour@gmail.com> writes:
>>>
>>>>> diff --git a/img/app/image/etc/s6-rc/dbus-vsock/notification-fd.license b/img/app/image/etc/s6-rc/dbus-vsock/notification-fd.license
>>>>> new file mode 100644
>>>>> index 0000000..0d3d47c
>>>>> --- /dev/null
>>>>> +++ b/img/app/image/etc/s6-rc/dbus-vsock/notification-fd.license
>>>>> @@ -0,0 +1,2 @@
>>>>> +SPDX-License-Identifier: CC0-1.0
>>>>> +SPDX-FileCopyrightText: 2025 Alyssa Ross <hi@alyssa.is>
>>>>> diff --git a/img/app/image/etc/s6-rc/dbus-vsock/run b/img/app/image/etc/s6-rc/dbus-vsock/run
>>>>> new file mode 100755
>>>>> index 0000000..37fae7d
>>>>> --- /dev/null
>>>>> +++ b/img/app/image/etc/s6-rc/dbus-vsock/run
>>>>> @@ -0,0 +1,17 @@
>>>>> +#!/bin/execlineb -P
>>>>> +# SPDX-License-Identifier: EUPL-1.2+
>>>>> +# SPDX-FileCopyrightText: 2025 Alyssa Ross <hi@alyssa.is>
>>>>> +
>>>>> +if { modprobe vsock }
>>>>> +
>>>>> +export LISTEN_FDS 1
>>>>> +getpid LISTEN_PID
>>>>> +export SYSTEMD_LOG_LEVEL notice
>>>>> +
>>>>> +systemd-socket-activate -l vsock::219 --now
>>>>> +
>>>>> +# Notify readiness.
>>>>> +if { fdmove 1 3 echo }
>>>>> +fdclose 3
>>>>> +
>>>>> +socat ACCEPT-FD:4,fork UNIX-CONNECT:/run/session-bus
>>>>
>>>> I'd prefer to use NOTIFY_SOCKET here.
>>>
>>> Then we have to run a whole background process to translate the
>>> systemd protocol to the s6 one. Doesn't seem worth it to me.
>> Whoops, wrong environment variable name :). I meant $LISTEN_FDS.
>
> I still don't understand what you mean. You'd like this to calculate
> 2 + LISTEN_FDS, and substitute that into the socat command line, even
> though we know the result will always be 4?
Nevermind, your version is fine. I wasn't sure this is a stable API
but I'm pretty sure it is.
--
Sincerely,
Demi Marie Obenour (she/her/hers)
[-- Attachment #1.1.2: OpenPGP public key --]
[-- Type: application/pgp-keys, Size: 7253 bytes --]
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2025-11-17 22:08 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-13 11:10 [PATCH 1/3] img/app: move init to /usr/bin Alyssa Ross
2025-11-13 11:10 ` [PATCH 2/3] img/app: dbus: don't listen on VSOCK Alyssa Ross
2025-11-13 17:46 ` Demi Marie Obenour
2025-11-13 17:56 ` Alyssa Ross
2025-11-13 19:32 ` Demi Marie Obenour
2025-11-14 11:45 ` Alyssa Ross
2025-11-14 22:15 ` Demi Marie Obenour
2025-11-17 22:08 ` Demi Marie Obenour [this message]
2025-11-17 22:19 ` Demi Marie Obenour
2025-11-18 15:03 ` Alyssa Ross
2025-11-13 11:10 ` [PATCH 3/3] pkgs: remove dbus overlay Alyssa Ross
2025-11-17 22:13 ` Demi Marie Obenour
2025-11-18 15:03 ` Alyssa Ross
2025-11-17 22:07 ` [PATCH 1/3] img/app: move init to /usr/bin Demi Marie Obenour
2025-11-18 15:03 ` Alyssa Ross
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=178e38b1-8dd9-4427-98a8-57b66a592ba4@gmail.com \
--to=demiobenour@gmail.com \
--cc=devel@spectrum-os.org \
--cc=hi@alyssa.is \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://spectrum-os.org/git/crosvm
https://spectrum-os.org/git/doc
https://spectrum-os.org/git/mktuntap
https://spectrum-os.org/git/nixpkgs
https://spectrum-os.org/git/spectrum
https://spectrum-os.org/git/ucspi-vsock
https://spectrum-os.org/git/www
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).