Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!helios!bcm!dimacs.rutgers.edu!seismo!ukma!rex!wuarchive!zaphod.mps.ohio-state.edu!magnus.ircc.ohio-state.edu!csn!stan!marvin!toml From: toml@marvin.Solbourne.COM (Tom LaStrange) Newsgroups: comp.windows.x Subject: Re: Running window managers & other clients in subwindows Message-ID: Date: 26 Feb 91 20:53:45 GMT References: <270@trwacs.UUCP> Sender: toml@Solbourne.COM (Tom LaStrange) Organization: Solbourne Computer, Inc. Lines: 26 In-Reply-To: epstein@trwacs.UUCP's message of 26 Feb 91 18:37:11 GMT } We're trying to create a "virtual root" window which can then be } managed by a window manager, and run applications inside the } virtual root. The goals are (1) to have application windows forced } to stay inside the virtual root, and (2) to have the applications } iconified (automatically) when the virtual root is iconified. } } I know there was some discussion of this a few months ago...can } anyone suggest a resolution? I'd like to avoid rewriting clients } (especially window managers) to do this. I suppose that I could } create the virtual root, and then pass the window ID to the window } manager (and other clients) as a command line argument, but that } requires changing too much stuff. } } As a further point, when override-redirect windows get recreated, } I'd like them to be clipped by the virtual root, not the "real" root. } Can I prevent the client from referencing the "real" root? I guess } what I really want is a UNIX chroot() call in X! About the only way you're going to be able to do it transparently is to write a server extension. Then you will be able to specify your virtual root via the -display option. Work was done on this at HP during the X11R3 time frame but was abandoned because of some problems that I don't know the details of. -- Tom LaStrange toml@Solbourne.COM