From: Alan McKinnon <alan.mckinnon@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: sans-dbus was: gnome intrusion?
Date: Sat, 19 Nov 2016 23:07:37 +0200 [thread overview]
Message-ID: <e4e29e28-f991-9923-ac82-ac2b0dccf21a@gmail.com> (raw)
In-Reply-To: <20161119204409.11828.251A07F0@matica.foolinux.mooo.com>
On 19/11/2016 22:47, Ian Zimmerman wrote:
> On 2016-11-19 14:16, Rich Freeman wrote:
>
>> Presumably if you sent a dbus message to your service manager asking
>> it to start a daemon that doesn't count as being behind your back.
>
> I did not - some program which I never heard of but is part of the DE du
> jour did, without any explicit configuration to do so. Typically when
> loading some library which I never heard of, also part of said DE, for
> the first time.
>
> I hope you agree this is very different from daemons started by init
> (whatever flavor).
>
I do not agree.
The big two DE's start dbus because the developers write code that needs
it. There is no explicit config to start it in the form of "dbus=yes" in
kde.conf because it is required.
init starts a whole bunch of stuff. It's all terribly mysterious until
you read the relevant docs, at which point it ceases to be so mysterious
and becomes knowledge.
Same with everything KDE, Gnome et al do that you are complaining about.
It's only worth complaining about being mysterious because you have not
yet studied them and understand them.
Yes I know init and KDE are very very different beasts from different
eras with different approaches to getting stuff done and so can appear
completely different. But within the contact of /this/ thread, they are
very similar. And you don't understand one of them to anything like the
same standard you understand the other.
--
Alan McKinnon
alan.mckinnon@gmail.com
next prev parent reply other threads:[~2016-11-19 21:09 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-14 9:32 [gentoo-user] gnome intrusion? Jorge Almeida
2016-11-14 17:37 ` [gentoo-user] " Ian Zimmerman
2016-11-14 19:03 ` Jorge Almeida
2016-11-14 20:37 ` Kai Krakow
2016-11-14 21:49 ` Jorge Almeida
2016-11-14 23:51 ` Kai Krakow
2016-11-16 12:47 ` [gentoo-user] sans-dbus was: " Miroslav Rovis
2016-11-16 18:42 ` Jorge Almeida
2016-11-17 1:48 ` Rich Freeman
2016-11-17 7:56 ` [gentoo-user] " Ian Zimmerman
2016-11-17 9:08 ` Rich Freeman
2016-11-19 9:21 ` Kai Krakow
2016-11-19 19:06 ` Ian Zimmerman
2016-11-19 19:16 ` Rich Freeman
2016-11-19 20:47 ` Ian Zimmerman
2016-11-19 21:07 ` Alan McKinnon [this message]
2016-11-19 21:23 ` Ian Zimmerman
2016-11-19 22:34 ` Canek Peláez Valdés
2016-11-19 22:36 ` Alan McKinnon
2016-11-20 0:36 ` Walter Dnes
2016-11-19 21:59 ` [gentoo-user] " Tom H
2016-11-19 22:15 ` Rich Freeman
2016-11-20 18:40 ` [gentoo-user] " Kai Krakow
2016-11-14 23:38 ` [gentoo-user] " Andrew Tselischev
2016-11-14 23:52 ` Jorge Almeida
2016-11-15 17:39 ` [gentoo-user] " Ian Zimmerman
2016-11-15 19:23 ` Jorge Almeida
2016-11-15 19:32 ` Alan McKinnon
2016-11-15 19:45 ` Jorge Almeida
2016-11-16 2:10 ` [gentoo-user] " Walter Dnes
2016-11-16 7:23 ` Jorge Almeida
2016-11-16 9:08 ` Neil Bothwick
2016-11-16 11:25 ` Jorge Almeida
2016-11-16 20:51 ` [gentoo-user] " Kai Krakow
2016-11-16 21:20 ` Jorge Almeida
2016-11-17 20:42 ` [gentoo-user] " Frank Steinmetzger
2016-11-17 20:49 ` Jorge Almeida
2016-11-17 23:32 ` Frank Steinmetzger
2016-11-14 23:55 ` [gentoo-user] " Kai Krakow
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=e4e29e28-f991-9923-ac82-ac2b0dccf21a@gmail.com \
--to=alan.mckinnon@gmail.com \
--cc=gentoo-user@lists.gentoo.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