The following USE changes are necessary to proceed:
(see "package.use" in the portage(5) man page for more details)
# required by gnome-base/gdm-3.8.3.1
# required by @selected
# required by @world (argument)
>=sys-auth/pambase-20120417-r2 systemd

does this mean that it is time to switch to systemd? _________________PC-Desktop: Ubuntu 14.04 amd64
Notebook Sony Vaio VPCEH: Gentoo ~amd64

The following USE changes are necessary to proceed:
(see "package.use" in the portage(5) man page for more details)
# required by gnome-base/gdm-3.8.3.1
# required by @selected
# required by @world (argument)
>=sys-auth/pambase-20120417-r2 systemd

ok but this will install systemd into my system.
So both systemd and openrc can live without problems or should i have to install systemd, configure it and then remove openrc?_________________PC-Desktop: Ubuntu 14.04 amd64
Notebook Sony Vaio VPCEH: Gentoo ~amd64

ok but this will install systemd into my system.
So both systemd and openrc can live without problems or should i have to install systemd, configure it and then remove openrc?

yes, they can coexists and you can safely continue using openrc_________________Only two things are infinite, the universe and human stupidity and I'm not sure about the former - Albert Einstein
ProjectFootball

I'am lucky that system boots fine after reboot, most services worked fine.

Before finally settle down to Systemd, I want to ask, systemd/udev/eudev or mdev, which one is recommend in gentoo?

Thanks.

I must understand I don't understand the underlined, afaik, systemd was merged into udev and not vice versa, I really don't understand how your system boots without udev.

Gentoo doesn't recommend either, as said before systemd shouldn't be in the list, the list should contain mdev, udev and eudev.
the former is not recommended if you need hotplug.
regarding the latter two, udev it pushed strongly by one gentoo dev here, eudev is a gentoo project maintained by gentoo programmers. I don't see any gentoo specific endorsement of either one in the near future ._________________Only two things are infinite, the universe and human stupidity and I'm not sure about the former - Albert Einstein
ProjectFootball

No, you cannot if you are a gnome user (here: gdm): Gnome uses all means to force systemd. The only way to remove systemd is to get rid of gnome.

Is there anything which can replace networkmanager + nm-applet combo (used with vpn), and which is as easy to use? I don't know of any and I have used wicd, wpa-gui, net.wlan0 in the past._________________emerge --quiet redefined | E17 vids: I, II | Now using e from git | e18, e19, and kde4 sucks :-/

I'am lucky that system boots fine after reboot, most services worked fine.

Before finally settle down to Systemd, I want to ask, systemd/udev/eudev or mdev, which one is recommend in gentoo?

Thanks.

I must understand I don't understand the underlined, afaik, systemd was merged into udev and not vice versa, I really don't understand how your system boots without udev.

Gentoo doesn't recommend either, as said before systemd shouldn't be in the list, the list should contain mdev, udev and eudev.
the former is not recommended if you need hotplug.
regarding the latter two, udev it pushed strongly by one gentoo dev here, eudev is a gentoo project maintained by gentoo programmers. I don't see any gentoo specific endorsement of either one in the near future .

I mean I removed sys-fs/udev not virtual/udev .

virtual/udev depends sys-fs/udev sys-apps/systemd or sys-fs/eudev.
But gnome need systemd, so seems to me the only way is to keep systemd and remove udev.

what does not makes sense? isn't that the main reason eudev came into existence? to decouple systemd within udev?

so logic dictates that if he had new enough udev, he doesn't need systemd._________________Only two things are infinite, the universe and human stupidity and I'm not sure about the former - Albert Einstein
ProjectFootball

what does not makes sense? isn't that the main reason eudev came into existence? to decouple systemd within udev?

so logic dictates that if he had new enough udev, he doesn't need systemd.

Sorry but answering that would be feeding the... You must know better as an experienced'ish user.

funny that you expect me to understand what you meant meanwhile referring to me as a troll, I'd expect better from someone who is a dev in gentoo.
I didn't see anything wrong in what I've wrote, nor in my answer, if you cannot stand such arguments, don't answer them at all.

moreover, you could have contacted me via pm and explain it to me if you didn't wanted to do that via the topic...

unless you or someone else point me to what I wrote wrong and prove it to me (if I was wrong and that was proved to me, I'd happily retract me statement and acknowledge my mistake), I'm staying with my statement._________________Only two things are infinite, the universe and human stupidity and I'm not sure about the former - Albert Einstein
ProjectFootball

Is there anything which can replace networkmanager + nm-applet combo (used with vpn), and which is as easy to use?

Maybe there are alternative frontends, but I am not aware of an alternative for networkmanager usable by non-experts.
AFAIK networkmanager does not depend on systemd yet, and I cannot imagine that it will, but unfortunately it depends on polkit which is much worse from a security point of view. It has practically become impossible to have a reasonable secure laptop with connections changing easily for non-expert users nowadays

seriously? I wrote "unmerge systemd, it is part of udev now." and you read "unmerge udev, it is part of systemd now."?_________________Only two things are infinite, the universe and human stupidity and I'm not sure about the former - Albert Einstein
ProjectFootball

TL;DR: I think it is best to try different things and make your own educated choice; but if you don't want to experiment, it's up to you if you follow the masses or the minority. Who the masses are depends on the way you look at it...

---

If you want to continue to use Gnome 3; yes, you will need systemd at the moment and something along the lines of USE="policykit systemd udev -consolekit", this does not imply that you need to remove openrc so you can keep that around. Some people are doing efforts to fork / unbundle the needed services; but, as far as I am aware of they are not currently in a state you can run them separately. Otherwise, I assume there would be a choice instead of a hard dependency in the ebuilds. If you don't want or need Gnome 3, feel free to consider to use alternatives.

DaggyStyle wrote:

seriously? I wrote "unmerge systemd, it is part of udev now." and you read "unmerge udev, it is part of systemd now."?

You may want to revise what systemd and udev are and the relation between them; as a hint, check the DESCRIPTION sections of `man systemd`, `man systemd-udevd` and `man 7 udev`. How can a system and service manager be part of software that does device management? Well, it can; but that wouldn't make much sense. systemd and openrc use udev, not the other way around. If you don't believe me, a simple Google query for "systemd udev" will show that udev's sources merged into systemd, others mentioning that udev became a part of systemd; so, the forks and unbundle efforts have been done to get udev back out of systemd...

chrisyu wrote:

Before finally settle down to Systemd, I want to ask, systemd/udev/eudev or mdev, which one is recommend in gentoo?

There is no single definitive recommendation from Gentoo itself; Gentoo is about choice (see About / Philosophy pages), and encourage users to try alternatives and decide for themselves.

From the community perspective; there are users that consider it written in a bad design, there are users for whom it hasn't worked, there are users that use it because they must and there are users that just use it and there are also users that love it. So, depending on whom you get an advice or recommendation from you will get different advice; some outweigh the other, but I don't think looking at popularity is necessary the best idea. At least, that isn't what choice is about; and if that's your choice, I guess you could stick to defaults and look at unassociated usage graphs for the packages you consider to use. Well, as long as they are compatible with one another; compatibility, that's often a problem you come across when you are making tough choices...

A nice DM would be one that supports multiple display servers, init systems, message buses, and so on and fits for everyone; but such a DM would probably never get finished.