Disable display manager on boot: Difference between revisions

From Rsewiki
No edit summary
 
(One intermediate revision by the same user not shown)
Line 5: Line 5:
inspect /etc/init, there is a configuration entry for the installed display manager, e.g.
inspect /etc/init, there is a configuration entry for the installed display manager, e.g.


  gdm.conf or
  gdm.conf (gnome ubuntu)
  kdm.conf
  kdm.conf (kubuntu)
lightdm.conf (xubuntu)


To start the display manager and graphic user interface when needed only, make a manual override file for the display manager:
To start the display manager and graphic user interface when needed only, make a manual override file for the display manager:
Line 13: Line 14:
  echo "manual" > /etc/init/gdm.override
  echo "manual" > /etc/init/gdm.override
  echo "manual" > /etc/init/kdm.override
  echo "manual" > /etc/init/kdm.override
echo "manual" > /etc/init/lightdm.override
  exit
  exit


Line 20: Line 22:
  sudo gdm    or
  sudo gdm    or
  sudo kdm
  sudo kdm
sudo ligntdm
===failsafe boot - root shell===
if you need failsafe boot and use the roor shell, you will need to remount the disk in rw mode to fix problems
mount -n -o remount,rw /

Latest revision as of 10:56, 26 June 2012

On robots that is normally without a screen, there is no need to run a display manager and a graphic user interface.

This will save some memory and start less processes.

inspect /etc/init, there is a configuration entry for the installed display manager, e.g.

gdm.conf (gnome ubuntu)
kdm.conf (kubuntu)
lightdm.conf (xubuntu)

To start the display manager and graphic user interface when needed only, make a manual override file for the display manager:

sudo bash
echo "manual" > /etc/init/gdm.override
echo "manual" > /etc/init/kdm.override
echo "manual" > /etc/init/lightdm.override
exit

After reboot, there will be a text login only. To (re)start the display manager (graphic login screen) use the command

sudo gdm     or
sudo kdm
sudo ligntdm

failsafe boot - root shell

if you need failsafe boot and use the roor shell, you will need to remount the disk in rw mode to fix problems

mount -n -o remount,rw /