mmm, ok
I'll leave instruction not to restart the terminals, and I'll try to get a look at the problem on site. Mike > Hi Mike > > I'm certainly not fighting with you <grin> trying to help ... > >> > Notice that the local machine is always the LOCAL machine. >> All true >> >> > even when the DISPLAY is mapped to another terminal. >> Yep > >> > Your KB is not mapped to another term (It cannot be), your DISPLAY >> is mapped to another term (It can be, and X is designed to do that) >> >> I do not belive you a correct here. The mouse still move the correct >> screen. (at least this is what I have been told) > > These two observations conflict! > > I know of no know way to tunnel the KB to another machine (irqs etc on > this machine) but the mouse events should be with KB_events on the other > machine, all as part of the DISPLAY. > > You do indeed have a wierd problem, but I'm certain that the DISPLAY is > mapped to another terminal by the server > server DISPLAYS keyboard events on another-DISPLAY > NOT > KB interface is tunnels to another machine. > > > :-((( looks like you will need to be 'there' to investigate and test the > reported observations. (hearsay - that's wot the beak calls it) > > >> > good luck > still! > James >> >> Cheers >> -- >> Mike O'Connor >> Service to Youth Council Inc >> [EMAIL PROTECTED] >> >> >> -- Mike O'Connor Service to Youth Council Inc [EMAIL PROTECTED] ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _____________________________________________________________________ Ltsp-discuss mailing list. To un-subscribe, or change prefs, goto: https://lists.sourceforge.net/lists/listinfo/ltsp-discuss For additional LTSP help, try #ltsp channel on irc.openprojects.net
