From: Stanislav Brabec <sbrabec@suse.cz>
To: Karel Zak <kzak@redhat.com>
Cc: util-linux@vger.kernel.org
Subject: Re: [PATCH] rfkill: Add systemd integration
Date: Thu, 22 Nov 2018 17:09:26 +0100 [thread overview]
Message-ID: <81e98f5c-7c5f-1c75-cd48-45b30b516eed@suse.cz> (raw)
In-Reply-To: <20181122103907.vwjf6uprlxzthd7e@ws.net.home>
Karel Zak wrote:
> On Wed, Nov 21, 2018 at 09:04:37PM +0100, Stanislav Brabec wrote:
>> Add rfkill-block@.service and rfkill-unblock@.service templates.
>> These make rfkill integration to systemd easier.
>>
>> Files come from openSUSE rfkill package.
>>
>> Example:
>> Use `systemctl {start,stop} rfkill-block@bluetooth` to block or unblock
>> (disable or enable) the bluetooth device.
>
> OK, but why? ;-)
>
> Does anything within systemd depend on rfkill? I guess for humans is
> more friendly to call "rfkill unblock bluetooth" than use systemctl.
I am not sure about use case of the original author, but I guess
that it can be useful for suspend target and automatic unblocking when
using on demand services (e. g. bluetooth service called after
rfkill-unblock@bluetooth).
--
Best Regards / S pozdravem,
Stanislav Brabec
software developer
---------------------------------------------------------------------
SUSE LINUX, s. r. o. e-mail: sbrabec@suse.com
Křižíkova 148/34 (Corso IIa) tel: +49 911 7405384547
186 00 Praha 8-Karlín fax: +420 284 084 001
Czech Republic http://www.suse.cz/
PGP: 830B 40D5 9E05 35D8 5E27 6FA3 717C 209F A04F CD76
next prev parent reply other threads:[~2018-11-22 16:09 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-21 20:04 [PATCH] rfkill: Add systemd integration Stanislav Brabec
2018-11-22 10:03 ` Sami Kerola
2018-11-22 10:39 ` Karel Zak
2018-11-22 16:09 ` Stanislav Brabec [this message]
2018-11-24 8:15 ` Sami Kerola
2018-11-27 18:16 ` Stanislav Brabec
2018-12-10 12:53 ` Karel Zak
2018-12-10 13:12 ` [systemd-devel] " Lennart Poettering
2018-12-10 18:12 ` Stanislav Brabec
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=81e98f5c-7c5f-1c75-cd48-45b30b516eed@suse.cz \
--to=sbrabec@suse.cz \
--cc=kzak@redhat.com \
--cc=util-linux@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).