On 07/06/2008 08:31:35 AM, Hugo Vanwoerkom wrote:
Karl O. Pinc wrote:
On 07/06/2008 07:27:05 AM, Hugo Vanwoerkom wrote:
Karl O. Pinc wrote:
What's the right way to run more than one X server?
, I _could_
just run X and startX
directly. Are there any out-of-the-box solutions
or should I just use inittab?
How would you use startx on monitors other than the first one that
has the console output?
In my case I'm thinking I wouldn't need more than "the first one",
if that. (My writing was not very clear, sorry.)
The thing is, the local machine is nothing more than a thin client.
The goal is to use a very minimal machine locally and have
all the compute power elsewhere.
Unless I really want to do _anything_ local, I don't need a
client side on the local machine at all. I can just run the server:
# this file is/etc/inittab
# console #8 disp0 connects to remote *dm via xdmcp
8:23:resspawn:X -query xclient.example.com -layout disp0
# console #9 disp1 connects to remote xsane front-end,
# started by a command=xsane in authorized_hosts,
# which in turns connects back to a local saned process
# to access a locally connected scanner.
9:23:resspawn:startx ssh -i /usr/local/etc/sanestuff/sanekey
[EMAIL PROTECTED] 'DISPLAY=xserver.example.com:1 xsane'
-- -layout disp1
(I've not tested the above.)
So, all the applications run remotely, all the desktop eyecandy is
generated remotely, and all the scanner image processing is done
remotely. (And I'm hoping that if I do cups right all the
awful gostscript printer munging is done remotely too.)
The local box has video cards, a nic, and no fan excepting the PSU.
Silence. Yay!
Karl <[EMAIL PROTECTED]>
Free Software: "You don't pay back, you pay forward."
-- Robert A. Heinlein
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
