Quote:
Originally Posted by Dapper Dan gdm might be disabled in the init. In Crux there is an /etc/rc.conf where you tell it to start gdm, kdm, cups, etc. in /etc/rc.d. I think Gentoo has an /etc/rc.conf or /etc/conf.d. Open whichever with your favourite editor and see if gdm is listed there to start. Also, check in /etc/init.d and see if gdm is there. |
Gentoo has an /etc/runlevels/ dir. Into it, you can find many subdirs: boot, default.... Those match the runlevels defined in /etc/inittab:
Quote:
l0:0:wait:/sbin/rc shutdown
l1:S1:wait:/sbin/rc single
l2:2:wait:/sbin/rc nonetwork
l3:3:wait:/sbin/rc default
l4:4:wait:/sbin/rc default
l5:5:wait:/sbin/rc default
l6:6:wait:/sbin/rc reboot
#z6:6:respawn:/sbin/sulogin
|
To add a given service to a given runlevel, you'd just cd into /etc/runlevels/<given_runlevel>/ and then symlink the service into that dir. But that shouldn't be necesary. The standard way in Gentoo is this:
Quote:
|
rc-update add servide runlevel
|
For example:
Quote:
|
rc-update add xdm default
|
Then you fire up the service (this is not necesary, this is just to avoid needing to reboot to load the service)
The next time you bootup, the service should start automatically, as long as you start on the same runlevel that you added your service to.
EDIT: Once more: this is for Gentoo, so, I can't guarantee that it will work on Sabayon. Also, even if you use Sabayon, you should save yourself some pain and read the Gentoo handbook. Taking the easy way is not easy in Gentoo.