On Wed, Aug 10, 2005 at 10:49:55AM -0400, Adrian Irving-Beer wrote: > On Wed, Aug 10, 2005 at 09:49:45AM -0400, Michael Walma wrote: > > > I think I am looking at trying to do the same thing. What I want to > > be able to do is use my laptop, in effect, as a wireless display > > connected to my desktop machine which resides in my basement. I > > want all apps, even the window manager, to be running on the > > desktop, so that I have a seamless experience; being at the laptop > > or being at the desktop is identical. > > This part is easy. You run an X server with nothing on it, and then > run the X session (window manager, etc.) on the target system, > pointing at your server with the DISPLAY environment variable. I've > done this plenty in the old days. No offence meant but you'll need to spell that out a little bit more clearly for it to be helpful to me, because: - The phrase "An X server with nothing on it" means nothing to me. Does that mean that the tower in my basement does something involving XDMCP? Or does it mean something else? - How do I get a modern window manager to acknowledge that I want to speak to something remote? As I understand it, "xhost +whatever" _permits_ my laptop to talk X to my desktop, but doesn't actually make it happen. What does? Ideally, here, this would be part of the pull-down menus that the display managers provide. The $DISPLAY envvar should take care of itself in this scenario. > The tricky part, and the part I'm assuming people are trying to figure > out here, is how to disconnect the session and reattach it later. I've > never tried that. That'd be gravy if I could make it work, but that's not the meat of what I'm after. -- "Not to expose your true feelings to an adult seems to be instinctive from the age of seven or eight onwards." - George Orwell