On 03/30/2016 09:58 AM, Dave Howorth wrote:
On 2016-03-30 13:01, Anton Aylward wrote:
[...]
That worked because the things in your home directory were things that you wanted to share on all machines, like your .bashrc
No. that's true but its incidental. Yes the application ran on the remote machine so the scripts and binaries were all there for it. The point I was trying to make is that with X I can run a dumb X-terminal. I *have*, as I mentioned, run dumb X terminals in the terminal rooms at USENIX and InterOp of the past. No `/home on those! The point I was trying to make is that X does not need to transfer a frame-buffer.
But the whole model is broken now that platform-specific apps tend to keep their private data in dot directories in your home. So you can't share your home directory across platforms, which then means mounting the shared home somewhere else and symlinking all the locations of local home with documents etc to subdirectories of the shared home.
That's true for Windows but it doesn't matter for the case I was talking about. And it need not matter in general. The SUN "log in anywhere" case, the 'remote shares' had your ~/home on the server anyway and NFS mounted it local to your workstation. But again that's irrelevant; if you used X to log in to the server you would not be running the client application locally, they would be running on the server with your dot files local to them on the server.
It's a complete pain and would work much better if platform-specific data were held in a different place, with a symlink from home:
See above. The purpose of my post was not to go on about this but to make it clear that a) X11 is intrinsically a network protocol b) Wayland is not a local display protocol and still needs an X "shim" to do network access. -- A: Yes. > Q: Are you sure? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting frowned upon? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org