Template:Software Side Effects Fixes: Difference between revisions

From OLPC
Jump to navigation Jump to search
No edit summary
(gconf was moved to .config)
Line 11: Line 11:
sudo rm -f /etc/ssh/ssh_host_rsa_key{,.pub}
sudo rm -f /etc/ssh/ssh_host_rsa_key{,.pub}
Destroy the Sugar settings, forcing a first boot name prompt. Otherwise the cloned laptops won't be able to collaborate using activities, or the wrong names will be shown in Chat,
Destroy the Sugar settings, forcing a first boot name prompt. Otherwise the cloned laptops won't be able to collaborate using activities, or the wrong names will be shown in Chat,
rm -rf /home/olpc/.sugar /home/olpc/.gconf/desktop/sugar /home/olpc/.local/share/telepathy
rm -rf /home/olpc/.sugar /home/olpc/.config/gconf/desktop/sugar /home/olpc/.local/share/telepathy
Destroy the developer key request file. Otherwise the cloned laptops will apply for developer keys using the original laptop serial number and UUID.
Destroy the developer key request file. Otherwise the cloned laptops will apply for developer keys using the original laptop serial number and UUID.
rm -rf /home/.devkey.html
rm -rf /home/.devkey.html
If the laptop was ever registered with a school server, or you are not sure, clear the registration by destroying the GConf settings:
If the laptop was ever registered with a school server, or you are not sure, clear the registration by destroying the GConf settings:
rm -rf /home/olpc/.gconf*
rm -rf /home/olpc/.config/gconf*
Immediately shutdown without restarting sugar, to avoid the .sugar directory being recreated:
Immediately shutdown without restarting sugar, to avoid the .sugar directory being recreated:
sudo poweroff
sudo poweroff

Revision as of 00:51, 24 November 2015

Delete the ".olpc-configured" files which tell olpc-configure it does not have to run again. This allows some of the files deleted below to be checked for and replaced.

sudo rm -f /.olpc-configured
rm -f /home/olpc/.olpc-configured

Destroy any saved volume settings, forcing defaults. Otherwise the cloned laptop may start with silent speakers.

sudo rm -f /etc/alsa/asound.state

Destroy any saved network connections. Otherwise the cloned laptop cannot connect to the networks the original laptop used.

sudo rm -rf /etc/NetworkManager/system-connections/*

Destroy the saved hostname:

sudo rm -f /etc/sysconfig/network

If SSH was enabled, destroy the SSH host key. Otherwise other systems in your network may report problems connecting to the laptops over SSH.

sudo rm -f /etc/ssh/ssh_host_rsa_key{,.pub}

Destroy the Sugar settings, forcing a first boot name prompt. Otherwise the cloned laptops won't be able to collaborate using activities, or the wrong names will be shown in Chat,

rm -rf /home/olpc/.sugar /home/olpc/.config/gconf/desktop/sugar /home/olpc/.local/share/telepathy

Destroy the developer key request file. Otherwise the cloned laptops will apply for developer keys using the original laptop serial number and UUID.

rm -rf /home/.devkey.html

If the laptop was ever registered with a school server, or you are not sure, clear the registration by destroying the GConf settings:

rm -rf /home/olpc/.config/gconf*

Immediately shutdown without restarting sugar, to avoid the .sugar directory being recreated:

sudo poweroff