I burned a CD set on friday (european morning) from a local mirror which was updated with the latest packages from ftp.debian.org that day. (This was done with slink_cd-1.07 scripts) The CD:s contains boot-floppies_2.1.8 and XFree86_3.3.2.3a-11.
The CD:s was used by a friend to install Slink this weekend. This friend is a Linux newbie but despite that a very nice guy. Everything went VERY WELL except for the xdm login loop. He 'configured' XFree86 but somehow also got xdm installed and ended up with the same loop as I had a while ago. He got caught in a loop where xdm fails and can't get out of it and into the CLI prompt. I told him this morning to use the <CTRL-ALT-Fx> ( where x=[1..6] ) to get into the command prompt, use dselect and remove the xdm package. Unfortunately I don't know the real reason for his xdm failure login loop. Before it was the Xsession script that had a syntax error but this is supposed to be fixed by now. I guess and hope it's his XFree86 configuration that isn't correct. It's way to easy to get xdm installed by accident and I think it will cause heavy traffic on the Debian mailing-lists after the 2.1 release. This is definitely Slinks weakest point for the moment. Would it be to difficult to remove the xdm package from all the standard selections so I have to install it afterwards. When one of the servers ( XF86_VGA16 ) installs a text could be shown that recommends the installation of the xdm package when I have a useable Xwindows configuration. //Gunnar Isaksson -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
