Slackware :: New 13.1 Install The System Boot To A Command Prompt And Then Run /etc/rc.d/rc.4 To Start X?

2nd and 3rd might be linux kernel problems but may help someone else so I included here.1st -- run level 4, /etc/rc.d/rc.4 and xdm -nodaemonJust installed 13.1 on an odd system, including building a new kernel.One thing I do is have the system boot to a command prompt and then run /etc/rc.d/rc.4 to start XBut I found that the rc.4 uses xdm -nodaemon flag and it was causing problems so I removed and all is pretty good. I still see some odd behavior with the virtual ttys sometimes.2nd -- when building a new kernel, I found I need the device-mapper butcouldn't tell if that was a linux kernel issue or something to do with lilo, I didn't want and don't need multiple disk devices like for LVM or MD so I didn't plan to have this enabled.3rd -- CONFIG_EXT4_USE_FOR_EXT23 When that kernel config option was selected and I have only an EXT4 filesystem, the filesystem was mounted as an EXT2, even though the kernel had no EXT2 feature. /etc/fstab specified EXT4 but the mount command showed EXT2. A silent problem that could leave an unpleasant surprise since EXT2 hos no journaling.4th -- I had to run lilo -C by hand in a virtual tty before finishing the install. This was what I had to do when installing 13.0 on different hardware. It seems that the lilo part of the install needs some sorting out.