From: Mark Hindley <mark at hindley.org.uk>
To: iwd at lists.01.org
Subject: Re: [PATCH] Enable DBus activation on non-systemd systems.
Date: Sat, 13 Nov 2021 07:40:11 +0000 [thread overview]
Message-ID: <YY9r2xKMpN2UerTG@hindley.org.uk> (raw)
In-Reply-To: CFOFAY8M0DOT.XA6PQ5U1AUOG@mussels
[-- Attachment #1: Type: text/plain, Size: 1259 bytes --]
Érico,
On Sat, Nov 13, 2021 at 03:03:56AM -0300, Érico Nogueira wrote:
> For things like IWD, I feel DBus activation is definitely the wrong
> path. It should be a system service of some sort, so it can connect to a
> network without first being queried by a user manually, and it shouldn't
> be activated automatically.
Thanks, but I find this a confusing statement.
AFAIU iwd does use DBus activation currently. The Debian changelog contains this
entry:
* Recommend dbus (system bus)
Interaction with iwd happens via dbus, i.e. as used by the iwctl
command (or NetworkManager iwd backend).
Packages using D-Bus usually doesn't describe this in their package
relationships and implicitly rely on everyone having a bus available.
People using iwd however seems to be confused about the lack of a
startup script and fails to realize that "dbus activation" is the
intended way to start iwd so hopefully making the dbus relationship more
explicit will give a hint and help people figure this out.
So, given that DBus activation doesn't require systemd (but can make use of it),
I was trying to understand and suggest a fix for why iwd DBus activation doesn't
work in the non-systemd case.
Mark
next reply other threads:[~2021-11-13 7:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-13 7:40 Mark Hindley [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-11-13 6:03 [PATCH] Enable DBus activation on non-systemd systems
2021-11-12 15:56 Mark Hindley
2021-11-12 14:57 Marcel Holtmann
2021-11-12 14:02 Mark Hindley
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=YY9r2xKMpN2UerTG@hindley.org.uk \
--to=iwd@lists.linux.dev \
/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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox