-----Original Message----- From: Brian Densmore
I believe that the tty2 could be written as tty[1-6] (where [1-6] means to write in any one of tty1 ...) and still have the same effect ... I'll try the tty1 and tty2 methods tonight and report back my findings.
-----Original Message----- From: Brian Kelsay
So, for clarity sake, the :0 is the first Xserver instance and it is being attached to the 7th virtual terminal (vt7). The :1 is the 2nd Xserver and it is attached to the 8th virtual terminal...
Works as expected. vt7 and vt8 are used and Alt-F7 and Alt-F8 work to get to the screens (Ctrl-Alt-Fn from inside X).
Jeremy Turner <> 11/30/04 01:46PM >>>
On Mon, Nov 29, 2004 at 11:13:02AM -0600, Brian Densmore wrote:
I'm running kdm and would like to know if anyone is running more than one desktop simultaneously?
Check the /etc/kdm/kde3/kdm/Xservers file. I have a line that says:
On my system it is /etc/kde3/kdm/Xservers and there are commented out lines like the one below. Although they have "reserve" in between the local.. and the X path. I removed that and restarted the system. I know I didn't need to do that. The commented out lines used progressive tty numbers so I left it alone. Hopefully it was done that way for a purpose. I was too chicken to change it. Maybe over the weekend when (theoretically) I have more time to fix anything I break.
So I now have entries like this in my Xserver file: ... :0 local@tty1 /usr/X11R6/bin/X -nolisten tcp vt7 :1 local@tty2 /usr/X11R6/bin/X -nolisten tcp :1 vt8 #:2 local@tty3 reserve /usr/X11R6/bin/X -nolisten tcp :2 vt9 #:3 local@tty4 reserve /usr/X11R6/bin/X -nolisten tcp :3 vt10 #:4 local@tty5 reserve /usr/X11R6/bin/X -nolisten tcp :4 vt11 #:5 local@tty6 reserve /usr/X11R6/bin/X -nolisten tcp :5 vt12 ...
You'll note the there is a :1 on the second line. This is necessary. It won't work without it.
:0 local@tty1 /usr/X11R6/bin/X -nolisten tcp vt7
My guess is that you would add a line just below it that says:
:1 local@tty2 /usr/X11R6/bin/X -nolisten tcp vt8
So Thanks again Jason, I didn't find that in any of the man pages I looked at. Just curious did you find it in a man page, or by browsing?
Brian
Brian Densmore wrote:
So Thanks again Jason, I didn't find that in any of the man pages I looked at. Just curious did you find it in a man page, or by browsing?
Erm... You probably meant Jeremy.
In any case, docs regarding this stuff exist. On the web you can find very thorough GDM docs -- including some really interesting features that enable all kinds of interesting possibilities in behavior for X sessions. KDM's docs are online in KDE but they are rather threadbare at the moment. KDM is essentially an extention to XDM. XDM's docs are pretty good, too. You can find them in 'man xdm'.
On Wed, Dec 01, 2004 at 09:48:50AM -0600, Brian Densmore wrote:
So Thanks again Jason, I didn't find that in any of the man pages I looked at. Just curious did you find it in a man page, or by browsing?
I downloaded the kdm debian package from packages.debian.org and extracted the data.tar.gz to see what files. I looked in the kdmrc file, and it has a section that says:
# If the value starts with a slash (/), it specifies the file, where X-servers # to be used by KDM are listed; the file is in the usual XDM-Xservers format. # Otherwise it's interpreted like one line of the Xservers file, i.e., it # specifies exactly one X-server. # Default is ":0 local@tty1 /usr/X11R6/bin/X -nolisten tcp vt7" # XXX i'm planning to absorb this file into kdmrc, but i'm not sure how to # do this best. Xservers=/etc/kde3/kdm/Xservers
That seemed to tip me off as what file to change. And the from looking at the Xservers file, I figured that if the top line worked, we could copy it and make a few changes creating the second X server.
I ran the same setup with GDM for a while, so I knew the feature had to be there for KDM. I don't use KDM, but I figured the kdmrc file would be similar to the gdm.conf file, so it'd probably be a quick fix.
Jason replied back to me directly after my first reply and pointed out that some non-free X drivers might not support multiple X server instances, but looks like that doesn't affect your situation. Maybe it'll help someone out someday in the archives.
Jeremy
On Wed, Dec 01, 2004 at 11:11:47AM -0600, Jeremy Turner wrote:
Jason replied back to me directly after my first reply and pointed out that some non-free X drivers might not support multiple X server instances, but looks like that doesn't affect your situation. Maybe it'll help someone out someday in the archives.
I've got the nVidia drivers on a Debian woody system with kde2 configured for multiple desktops, and last I checked, it worked OK.
FWIW, I discovered how to do this in much the same way as you described, by following my nose through the files. I may have done some find'ing and some grep'ping, but in general I'd say looking for related files in /etc is always a good place to start.
On Wed, 1 Dec 2004 14:11:25 -0600, D. Joe [email protected] wrote:
FWIW, I discovered how to do this in much the same way as you described, by following my nose through the files. I may have done some find'ing and some grep'ping, but in general I'd say looking for related files in /etc is always a good place to start.
One of the strengths of *nix is that such things are discoverable by poking around /etc - just grepping /etc/* for a word often finds me what I need to know even though I didn't know what file to look in.
-
Brian Densmore -
D. Joe -
Jason Clinton -
Jeremy Turner -
Monty J. Harder