OK, I admit it, I've failed the latest module in "administering your own systems", but I'm out of ideas about how to track down what is wrong.
I was using an existing system, with gdm, to build a new clfs system in an xterm. Unfortunately, the new system didn't boot so I went back to the host system and into chroot to check a few possibilities and recompile the kernel with a few things no longer modular. Didn't work, so back to the host, and after gdm was invoked the screen went black, but didn't get as far as painting an X background. I was able to get a tty, and changed to runlevel 3. From there I logged the output of 'startx' and dicovered it couldn't open a temp file : '/' was totally full, fortunately /home still had a lot of space. Managed to free up a reasonable amount of space. Rebooted (runlevel 5), still didn't get any further than a black screen. Back to runlevel 3, startx didn't, but this time there was nothing unusual in the log. At this point it occurred to me that maybe I'd changed something on the host when I was trying to fix the problems in the new system. No worries, I had a backup of everything except the latest kernel and modules, so I wiped the system and installed the backup. (fortunately, I have a third system on the disk :-) And then I removed the space-hogs (some static '.a' "libraries", and some documentation) to get back to 82% in-use. But it made no difference - I can't see anything in the logs that looks unusual, and I'm out of ideas. Sod's Law says it's something obvious that I'm overlooking - any suggestions ? ĸen -- das eine Mal als Tragödie, das andere Mal als Farce -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
