| 1 |
On Mon, Oct 29, 2012 at 8:43 AM, João Matos <jaoneto@×××××.com> wrote: |
| 2 |
> Hi List. |
| 3 |
> |
| 4 |
> I've heard here that systemd is faster the openrc, so I decided to try it. |
| 5 |
> And indeed, it is :). I've spent many hours to make my system totaly |
| 6 |
> functional again, but it totally worth it. |
| 7 |
|
| 8 |
Kudos. |
| 9 |
|
| 10 |
> There is just one little problem remaining: NetworkManager starts, I can |
| 11 |
> connect the internet, but my kde applet cant see it is started, so I can't |
| 12 |
> manage my connections. It seems some people had similar problem, and were |
| 13 |
> able to solve it, but the topics weren't clear enough for me. I also seems |
| 14 |
> that there is something to to with pam or polkit. |
| 15 |
|
| 16 |
You need to move everything to use systemd. If an ebuild has optional |
| 17 |
dependencies on both systemd and consolekit, you need to set systemd, |
| 18 |
and disable consolekit. At least that's the way it works now with |
| 19 |
GNOME, and even some networkmanager versions needed to pick only one |
| 20 |
between consolekit and systemd. For good measure, you should be able |
| 21 |
to uninstall consolekit; it's deprecated, nobody is maintaining it, |
| 22 |
and it relies on hacks to work. systemd's session tracking is much |
| 23 |
more reliable and nicer. |
| 24 |
|
| 25 |
In particular, the following packages should be using the systemd USE |
| 26 |
flag, and not the consolekit one: |
| 27 |
|
| 28 |
net-misc/networkmanager |
| 29 |
sys-apps/accountsservice (don't know if KDE uses this) |
| 30 |
sys-auth/pambase (<==== CRITICAL) |
| 31 |
sys-auth/polkit (<==== CRITICAL) |
| 32 |
sys-fs/udisks (optional, I think) |
| 33 |
sys-power/upower (optional, I think) |
| 34 |
|
| 35 |
It used to be that you could install systemd, check it out, and if you |
| 36 |
didn't like it you just didn't used it (there was not even the need to |
| 37 |
uninstall it). However, consolekit is for all practical purposes dead, |
| 38 |
and systemd does that job better and with more features. So now you |
| 39 |
need to decide at compile time which one you wanna use; you cannot mix |
| 40 |
them. |
| 41 |
|
| 42 |
> The topics I'm talking about: |
| 43 |
> |
| 44 |
> https://bbs.archlinux.org/viewtopic.php?id=144763 |
| 45 |
> |
| 46 |
> http://forums.gentoo.org/viewtopic-t-924004-start-0.html |
| 47 |
> |
| 48 |
> Since we're talking about systemd, is it possible to it display something |
| 49 |
> during de boot, as openrc did? I just got a black screen until kdm starts. |
| 50 |
> I'll work on plymout, but I still think the informations r important. |
| 51 |
|
| 52 |
Plymouth will just hide even more information; it looks really pretty, |
| 53 |
though. I don't think you need to checkout anything at boot (I'm |
| 54 |
pretty sure the problems are the ones I mentioned it), but to debug |
| 55 |
systemd put this on your kernel command line: systemd.log_level=debug. |
| 56 |
All the boot output gets logged into /var/log/boot.log; also, using |
| 57 |
journalctl -b will give you all the output from the system from the |
| 58 |
last time you rebooted. |
| 59 |
|
| 60 |
Regards. |
| 61 |
-- |
| 62 |
Canek Peláez Valdés |
| 63 |
Posgrado en Ciencia e Ingeniería de la Computación |
| 64 |
Universidad Nacional Autónoma de México |
Archives