| 1 |
Thanks for the FUD. |
| 2 |
|
| 3 |
On Jul 22, 2013 11:15 PM, "Volker Armin Hemmann" <volkerarmin@××××××××××.com> |
| 4 |
wrote: |
| 5 |
> |
| 6 |
> yeah, because it is so great to have that monster systemd on your box. |
| 7 |
Because xml configs are awesome and binary logs even more and I always |
| 8 |
wanted an init with builtin webbrowser. Security? bah, not needed. |
| 9 |
|
| 10 |
Funny. I dont remember any xml blobs on my systemd configs. And my logs are |
| 11 |
sent to syslog-ng as text, too. Id say i dont have a builton webbrowser but |
| 12 |
i start emacs as a service ;) |
| 13 |
|
| 14 |
Its fair to say you havent the slightest idea what youre talking about so |
| 15 |
heaven knows how well youre misusing classic security practices right now. |
| 16 |
|
| 17 |
> |
| 18 |
> So when do I have to install mysql to use it? How long until some crap |
| 19 |
ala windows-registry is forced down my throat? |
| 20 |
|
| 21 |
Since this is a gnome topic? The registry was here like more than a year |
| 22 |
now. |
| 23 |
|
| 24 |
> |
| 25 |
> |
| 26 |
> |
| 27 |
> 2013/7/22 Canek Peláez Valdés <caneko@×××××.com> |
| 28 |
>> |
| 29 |
>> ConsoleKit is for all practical purposes unmaintained, and all of the |
| 30 |
>> packages you mentioned it support systemd just fine. Emerge systemd, |
| 31 |
>> and purge CK from your system; I did that almost a year ago. |
| 32 |
>> |
| 33 |
>> Regards. |
| 34 |
>> |
| 35 |
>> On Mon, Jul 22, 2013 at 2:03 AM, Helmut Jarausch |
| 36 |
>> <jarausch@××××××××××××××××.de> wrote: |
| 37 |
>> > Hi, |
| 38 |
>> > |
| 39 |
>> > gnome-base/gnome-settings-daemon-3.8.4 requires systemd |
| 40 |
>> > |
| 41 |
>> > sys-auth/consolekit-0.4.6 cannot coexist with systemd |
| 42 |
>> > |
| 43 |
>> > but many packages depend on sys-auth/consolekit : |
| 44 |
>> > |
| 45 |
>> > emerge -vpc sys-auth/consolekit gives |
| 46 |
>> > |
| 47 |
>> > sys-auth/consolekit-0.4.5_p20120320-r2 pulled in by: |
| 48 |
>> > gnome-base/gnome-session-3.8.2.1-r1 requires sys-auth/consolekit |
| 49 |
>> > gnome-base/gnome-shell-3.8.3-r1 requires sys-auth/consolekit |
| 50 |
>> > kde-base/kdm-4.10.5 requires sys-auth/consolekit |
| 51 |
>> > net-misc/networkmanager-0.9.8.2-r2 requires sys-auth/consolekit |
| 52 |
>> > net-wireless/bluez-4.101-r5 requires sys-auth/consolekit |
| 53 |
>> > sys-apps/accountsservice-0.6.34 requires sys-auth/consolekit |
| 54 |
>> > sys-auth/pambase-20120417-r2 requires |
| 55 |
>> >>=sys-auth/consolekit-0.4.5_p2012[pam] |
| 56 |
>> > sys-auth/polkit-0.111 requires sys-auth/consolekit[policykit] |
| 57 |
>> > x11-apps/xdm-1.1.11-r3 requires sys-auth/consolekit |
| 58 |
>> > x11-misc/slim-1.3.5-r2 requires sys-auth/consolekit |
| 59 |
>> > |
| 60 |
>> > |
| 61 |
>> > So, what to do? Obviously, I don't want an unbootable system. |
| 62 |
>> > |
| 63 |
>> > How did you resolve this conflict? |
| 64 |
>> > |
| 65 |
>> > Many thanks for a hint, |
| 66 |
>> > Helmut |
| 67 |
>> |
| 68 |
>> |
| 69 |
>> |
| 70 |
>> -- |
| 71 |
>> Canek Peláez Valdés |
| 72 |
>> Posgrado en Ciencia e Ingeniería de la Computación |
| 73 |
>> Universidad Nacional Autónoma de México |
| 74 |
>> |
| 75 |
> |
Archives