From: "Róbert Čerňanský" <openhs@tightmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Systemd as drop-in replacement for udev?
Date: Thu, 5 Dec 2013 23:26:46 +0100 [thread overview]
Message-ID: <20131205232646.2f8a11bc@amit.kihnet.sk> (raw)
In-Reply-To: <CADPrc81YYieEUWxkJjL9mLu-=AJRJhqpHUWZwASQ+su5==Unog@mail.gmail.com>
On Thu, 5 Dec 2013 15:18:54 -0600
Canek Peláez Valdés <caneko@gmail.com> wrote:
> On Thu, Dec 5, 2013 at 2:36 PM, Róbert Čerňanský
> <openhs@tightmail.com> wrote:
> > Hello all,
> >
> > I am currently updating my system and Portage wants to replace udev
> > (204) with systemd (208). My question is (hopefully) simple:
> >
> > Can I use systemd as drop-in replacement for udev? In other words,
> > can I pretend that systemd is udev and continue using OpenRC as
> > with udev itself? I would then apply just udev 204 to 208 update
> > instructions (http://wiki.gentoo.org/wiki/Udev/upgrade).
> >
> > I am using WindowMaker and systemd was pulled in by
> > gnome-settings-daemon which in turn was pulled in by gdm. I would
> > like to stick with gdm.
>
> The GNOME stuff that requires systemd will not work under OpenRC from
> 3.10 on, you could get strange fails with gdm and
> gnome-settings-daemon. If it's gdm-3.8, then I think you can use
> systemd as udev replacement together with OpenRC, and I believe some
> people did it successfully.
Thanks. I have enabled openrc-force use flag found this in
gnome-settings-daemon emerge log, which confirms what you have said:
"gnome-settings-daemon needs Systemd to be *running* for working
properly. Please follow the this guide to migrate:
http://wiki.gentoo.org/wiki/Systemd
You are enabling 'openrc-force' USE flag to skip systemd requirement,
this can lead to unexpected problems and is not supported neither by
upstream neither by Gnome Gentoo maintainers. If you suffer any problem,
you will need to disable this USE flag system wide and retest before
opening any bug report."
So the it is clear to me now.
I will try openrc-force as temporal solution until I'll find a new
display manager and give heart breaking good by to GDM.
Regards,
Robert
--
Róbert Čerňanský
E-mail: openhs@tightmail.com
Jabber: hs@jabber.sk
next prev parent reply other threads:[~2013-12-05 22:26 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-05 20:36 [gentoo-user] Systemd as drop-in replacement for udev? Róbert Čerňanský
2013-12-05 21:18 ` Canek Peláez Valdés
2013-12-05 22:26 ` Róbert Čerňanský [this message]
2013-12-05 23:17 ` Canek Peláez Valdés
2013-12-06 6:32 ` J. Roeleveld
2013-12-06 7:51 ` Michael Hampicke
2013-12-06 7:53 ` Michael Hampicke
2013-12-06 10:44 ` J. Roeleveld
2013-12-07 6:43 ` [gentoo-user] " Jonathan Callen
2013-12-07 11:09 ` Róbert Čerňanský
2013-12-06 20:43 ` [gentoo-user] " Tom Wijsman
2013-12-06 17:26 ` Canek Peláez Valdés
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=20131205232646.2f8a11bc@amit.kihnet.sk \
--to=openhs@tightmail.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