public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Rich Freeman <rich0@gentoo.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] sans-dbus was: gnome intrusion?
Date: Wed, 16 Nov 2016 20:48:52 -0500	[thread overview]
Message-ID: <CAGfcS_n7a8maBbSrzCyXvKtC6j12O61=iTYEUAL28=xDkMdveQ@mail.gmail.com> (raw)
In-Reply-To: <CAKpSnp+QFEgAFk-R1ta75WtFQFKgEzjm1b7t++Q2S5fgdiKNSw@mail.gmail.com>

On Wed, Nov 16, 2016 at 1:42 PM, Jorge Almeida <jjalmeida@gmail.com> wrote:
>
> I knew Gentoo doesn't force the use of dbus, but I had the flag set,
> since I expected assorted breakages. For example, when viewing a pdf
> file, will updating the view when the file changes be possible without
> dbus? This is the kind of trouble I expect. Not the fault of Gentoo,
> anyway.
>
> As for the *kit stuff, I just don't have it. It's safe to do without
> that stuff, as far as I can tell.
> ...
> For my needs, Gentoo is the best distro out there. (Until recently, I
> used Slackware, as well as Gentoo. Had to give up on Slackware 14.2,
> with regret. Because pulseaudio,)
>

To each his own, and I'm glad Gentoo supports running without any of
this stuff, but on a semi-typical system I'd suggest that you're
probably better off having this stuff installed than otherwise.

I'd been running without pulseaudio for ages, but finally got around
to installing it because I was having audio issues when running
multiple X11 sessions.  With pulse it just works, and installing pulse
was pretty trivial.  Sure, it is overkill in the most basic
configurations, but as soon as you start getting multiple audio
devices/users/etc all going at the same time the purpose for the
complexity becomes more apparent.

As far as dbus/policykit goes, it really is just an IPC
implementation, because IPC on Linux isn't all that great
out-of-the-box.  It was shot down for the kernel, but a revamped
solution is probably likely to take its place there, and then
everybody will just use the kernel version (and you'll see dbus
disappear in your process list).  Sure, it is more complex than
sending SIGUSR1 to a process (while trying to remember which of
less-dedicated signals do what for what daemon), but it is a lot more
capable.  Policykit also lets you do stuff like saying this user is
allowed to restart this service, but not do anything else, and so on,
using a configuration which is flexible and works across different
applications/etc.

Again, you can sort-of live without this stuff, and there is nothing
wrong if you want to do that, but this stuff was written for a reason.
At the very least I'd suggest understanding it all in case it actually
might solve a problem for you.

-- 
Rich


  reply	other threads:[~2016-11-17  1:49 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 [this message]
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
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='CAGfcS_n7a8maBbSrzCyXvKtC6j12O61=iTYEUAL28=xDkMdveQ@mail.gmail.com' \
    --to=rich0@gentoo.org \
    --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