All of the files which were updated by the SLXT install process are backed up to <filename>_<YYMMDD> in the same directory as the originals. So, if you installed SLXT on the 12th of August '99, the /etc/X11/xdm/Xsession file (for example) would have been backed up to /etc/X11/xdm/Xsession_990812.
The SLXT install process changes files in the /usr/lib/X11/xdm directory and in /etc. You can use find to identify these files:-
find / -name "*_990812" -ls
...and move the originals back into position to restore normal operation.
The most important of the modified files are:-
/etc/rc.d/rc.local & /etc/inetd.conf
By moving the originals back into place, you can disable the start-up of SLXT specific daemons.
You might also want to comment out these lines in /etc/rc.d/rc.xterm:-
echo -en "X-Font-Server "; Start_XFS;
RH6.0, and above, start it by default anyway.
The /tftpboot directory contains the SLXT client directory structure and the client links to the network-bootable SPARC-Linux kernel. This directory can be between 7~20MB (depending upon which version of SLXT you have installed). If you have other diskless clients (other than SLXT clients) booting from your server you need to be very careful about what you remove. Deleting the SPARCLinux kernel and SLXT_root directory is a safe way to recover the bulk of the space used by SLXT, but I would recommend that you leave all of the links in place, rather than risk disabling one of your diskless clients by mistake.
If you have no clients other than the SLXT Xterminals (ie:- the SLXT install actually created the /tftpboot directory), then you can quite safely go ahead and remove the whole /tftpboot directory.
Last updated: $Date: 2003/05/18 08:25:02 $. Gaijin@pobox.COM