On Sun, Nov 11, 2012 at 8:58 PM, Keith Dart <ke...@dartworks.biz> wrote: > Re > 20121111175313.54b9acf1@dartworks.biz20121111175313.54b9acf1@dartworks.bizCADPrc80EwExpbdcJX1a+aE0DA=iopqw-QOaozmUBJCs5FGew-g@mail.gmail.com20121109171149.1d8a3e18@dartworks.biz509D9C62.9040909@gmail.com509D8E00.4030208@coolmail.sek7k1hn$ce6$1...@ger.gmane.org, > Canek Peláez Valdés said: >> Mmmh. I stopped using that overlay years ago. It's still maintained? > > Must be, it had all the necessary .service files that were missing from > the systemd install.
That doesn't mean anything; the format of the .service files is really simple and most of them will work from systemd-1 to systemd-195. > You probably still had those laying around from > when you did use the overlay. No, I do not. Which service files do you need from the package? The only one I needed (and wasn't included in its own package) was for vixie-cron. >> You can also link /etc/systemd/system/display-manager.service to your >> preferred login manager. Recent versions of systemd will take care of >> everything else. > > Except that there was no service file for my preferred login manager. > But I saw there was one installed for the "slim" manager. So rather > than fight, I switched. I also googled a little and found that lightdm > has an open bug for requesting systemd support.... Anyway, works fine > with slim, and it turns out I like it better anyway. Especially since > lightdm-gtk-greeter recently broke the background image support. systemd "support" is generally optional, not mandatory. In other words, if lightdm works with OpenRC, it will work with systemd; maybe it will not integrate a lot of features from it, but it will work as it works in OpenRC: as a standalone service. I'm pretty sure a Google search will give you several instances of service files for lightdm (or wathever login manager you want to use). Regards. -- Canek Peláez Valdés Posgrado en Ciencia e Ingeniería de la Computación Universidad Nacional Autónoma de México
