1 |
On Wed, Nov 16, 2016 at 1:42 PM, Jorge Almeida <jjalmeida@×××××.com> wrote: |
2 |
> |
3 |
> I knew Gentoo doesn't force the use of dbus, but I had the flag set, |
4 |
> since I expected assorted breakages. For example, when viewing a pdf |
5 |
> file, will updating the view when the file changes be possible without |
6 |
> dbus? This is the kind of trouble I expect. Not the fault of Gentoo, |
7 |
> anyway. |
8 |
> |
9 |
> As for the *kit stuff, I just don't have it. It's safe to do without |
10 |
> that stuff, as far as I can tell. |
11 |
> ... |
12 |
> For my needs, Gentoo is the best distro out there. (Until recently, I |
13 |
> used Slackware, as well as Gentoo. Had to give up on Slackware 14.2, |
14 |
> with regret. Because pulseaudio,) |
15 |
> |
16 |
|
17 |
To each his own, and I'm glad Gentoo supports running without any of |
18 |
this stuff, but on a semi-typical system I'd suggest that you're |
19 |
probably better off having this stuff installed than otherwise. |
20 |
|
21 |
I'd been running without pulseaudio for ages, but finally got around |
22 |
to installing it because I was having audio issues when running |
23 |
multiple X11 sessions. With pulse it just works, and installing pulse |
24 |
was pretty trivial. Sure, it is overkill in the most basic |
25 |
configurations, but as soon as you start getting multiple audio |
26 |
devices/users/etc all going at the same time the purpose for the |
27 |
complexity becomes more apparent. |
28 |
|
29 |
As far as dbus/policykit goes, it really is just an IPC |
30 |
implementation, because IPC on Linux isn't all that great |
31 |
out-of-the-box. It was shot down for the kernel, but a revamped |
32 |
solution is probably likely to take its place there, and then |
33 |
everybody will just use the kernel version (and you'll see dbus |
34 |
disappear in your process list). Sure, it is more complex than |
35 |
sending SIGUSR1 to a process (while trying to remember which of |
36 |
less-dedicated signals do what for what daemon), but it is a lot more |
37 |
capable. Policykit also lets you do stuff like saying this user is |
38 |
allowed to restart this service, but not do anything else, and so on, |
39 |
using a configuration which is flexible and works across different |
40 |
applications/etc. |
41 |
|
42 |
Again, you can sort-of live without this stuff, and there is nothing |
43 |
wrong if you want to do that, but this stuff was written for a reason. |
44 |
At the very least I'd suggest understanding it all in case it actually |
45 |
might solve a problem for you. |
46 |
|
47 |
-- |
48 |
Rich |