On Thu, Mar 21, 2013 at 7:45 PM, João Matos <jaon...@gmail.com> wrote: > Hi list, > > do you know some guide to switch form systemd to openrc, or keep both? I > googled and I didn't find. > > The motivation is that I'm studing many server stuff, and I'm tired of > search for alternatives to systemd (that is really good). I also set up some > servers, using openrc on them, so, sometimes I like to reproduce the > configuration o my machine. > > If possible, I prefer to keep both. If not, I'll switch back to openrc. > > I've enable the openrc user flag, updated the system, I created a grub > entrace, and everything seems to work pretty well on openrc, but I cant > start the X. "no screens found", but dbus, udev and consolekit are started > without error. > > Everything is working with systemd.
For "server stuff", you should have no problem. If the machine where you want to have both systemd and OpenRC also works as a desktop workstation, right now that is not possible; there are several desktop packages that cannot decide at run time if they use systemd (actually, logind) or ConsoleKit (polkit being the most obvious). So you'll need to remove the systemd USE flag, add the consolekit one, and recompile the necessary packages to get back to a systemd-less desktop. Be aware that ConsoleKit is basically dead; it has no upstream, no new features are being developed for it, and I don't think even basic security bugs are actively fixed. Everything that depended on ConsoleKit has switched or is considering switching to logind, which right now is provided only by systemd (Canonical is working in an alternative implementation, and I believe some *BSD guys were also looking into the matter). When the logind alternative implementations are ready, maybe it will be possible to again boot to both OpenRC and systemd with the same binaries; right now is not possible. Regards. -- Canek Peláez Valdés Posgrado en Ciencia e Ingeniería de la Computación Universidad Nacional Autónoma de México
