* Ibukun Olumuyiwa ([EMAIL PROTECTED]) wrote: > Traditionally elogin should be started using elogind (installed in > PREFIX/sbin at the moment). Just typing "elogind" at the command line > should fork elogin to the background and start a new X server etc etc. > > As far as using your initscripts, the problem is that your /etc/X11/prefdm > file is probably tailored to use either KDM, GDM or XDM as a last resort, > since nobody knows about elogin. ;) So your best option would be to hack > that file (which is what I did). You can look at > http://speedstar.xcomputerman.com/files/elogin/prefdm as an example. What > I have done is to modify it so that you can specify "Elogin" or > "Enlightenment" in /etc/sysconfig/desktop, and it will launch elogind as a > result. > > If your system does things a little differently, then you probably want to > take note of the fact that starting elogind with the -nodaemon option will > prevent it from forking to the background, which is probably the behavior > you want. I'm not sure but I believe there is also a file in the > data/init.d directory that allows you to add an elogin service to > /etc/init.d. > > Hope all this is helpful.
Thanks a lot. As soon as I get it working (I sent another message about some weird behavior), I'll hack my prefdm. Alan -- The hacker: someone who figured things out and made something cool happen. ------------------------------------------------------- This SF.net email is sponsored by: Scholarships for Techies! Can't afford IT training? All 2003 ictp students receive scholarships. Get hands-on training in Microsoft, Cisco, Sun, Linux/UNIX, and more. www.ictp.com/training/sourceforge.asp _______________________________________________ enlightenment-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
