Jean-Francois Theroux wrote: > If it's using upstart, look in /etc/event.d. There's a script in there > that will most likely take care of x/gdm. Once you know the name of > it, you run 'stop script_name'. To prevent it from running on boot, > you need to modify the script a bit. I wish....
jer...@hostedapps:~$ ls /etc/event.d/ control-alt-delete rc4 tty1 last-good-boot rc5 tty2 logd rc6 tty3 rc0 rc-default tty4 rc1 rcS tty5 rc2 rcS-sulogin tty6 rc3 sulogin jer...@hostedapps:~$ sudo service stop gdm stop: unrecognized service jer...@hostedapps:~$ sudo service gdm stop stop: Unknown instance: This is slightly less than intuitive. Seriously, they can't be making me hack config files to stop boot services? This would be a step back, no? Apparently, stuff is now in /etc/init/, and init.d is deprecated, and symlinks to upstart? > ls -la /etc/init.d/ lrwxrwxrwx 1 root root 21 2009-11-05 13:12 udev -> /lib/init/upstart-job Jeremy _______________________________________________ mlug mailing list [email protected] https://listes.koumbit.net/cgi-bin/mailman/listinfo/mlug-listserv.mlug.ca
