Ah yes, but the startx script will always leave $display as :0 and happily
appends the :1, :2 or whatever to $serverargs.
The real answer, I suppose, is to debug the script :-) but I haven't found
the time / inclination !!!
Owen
On Mon, 18 Sep 2000, you wrote:
> >
> > > No, the problem is that if you give the command startx -- :1 the command what
>you really �give� is xinit /usr/X11R6/bin/Your_wm -- :0 :1 . What xinit will do with
>this is open X under vt8 but open the corresponding windowmanager on vt7. I just
>tryed it with FreeBSD and it had the same effect so it is definitly not the kernel.
> >
> > Boy, I'm glad to see someone else agrees with me !!! ;-)
> >
> > If I have to post this on cooker or Xpert again I'll burst !!! :-)
> >
> > In startx change the last line, which is:
> > xinit $clientargs -- $display $serverargs
> > to
> > xinit $clientargs -- $serverargs
> >
> > Hope this helps :-),
> > Owen
> $display should be �helped� in the startx-script. According to the man-page for
>xinit the first :number will be the screen on which $clientags will apear while the
>rest of the commands will be parsed to the Xserver to be used there.
> startx :1 == xinit /usr/X11R6/bin/your_wm -- $display :1 = start your_wm on $display
>and Xserver on display 1. /= what you want if $display /= :1
> deleting $display is not the option because if you log on to a machine via telnet,
>do a EXPORT to local machine and did a startx you would expect that your_wm like
>(almost?) all other X-programs would appear on your local machine and not the machine
>to which you telnet to.
>
>
> P.S. I think that for ssh the same thing applies. Have never done it over an
>insecure network so don�t know how it exactly works
