I have never experienced this restriction. The corruption has, once in a
while, infected X's VT, but it has usually gone for a currently text-mode VT.
> etc running on it. Often, (actually, maybe always, I am not sure) it
> happens while X is running, or after exiting from X...I often have a copy
> of the initialization messages that X prints when it starts up left on
> the VC thet X controlled (ie, getty's on VC1-6, X on 7..exit X, Alt-F7
> shows the hardware probing messages from X, etc.) Also, I have gotten a
> few lines of register dump when X crashed (unrelated problem--bad
> configuration on my part) left on the VC it was running on. I also have
> experienced the aforementioned random colors as well as text from
> whatever sprayed all over VCs...but never one with a getty running on it.
> <shrug> I'll keep my eyes open for any sort of pattern to it. Does anyone
> else have this problem who DOESN'T run X at all? I can't be sure if I was
> using X in all these instances or not. Seems it happened pack towards
> 1.2.1, but 1.1.45 and 1.1.72 were so long ago I don't remember.
I am beginning to detect X as a pattern here. For two days and sixteen
hours (good uptime, for this house) I've been running the system with no X,
and no corruption.
Plus, as soon as I decide to reboot I will be running a kernel without the
potentially-fatal psaux bug.
-- this mind intentionally left blank | Linux - anything else Ryan Smith-Roberts -- labrat@u.washington.edu | would be uncivilized!"In /this/ house, we obey the laws of THERMODYNAMICS!" -- Homer Simpson