On Thu, Jul 25, 2002 at 03:48:29PM -0600, Andrew Falanga wrote:
> >
> >
> >run vncserver :0. start X, but instead of starting a window manager
> >in your .xinitrc, run vncviewer localhost:0 in full screen mode.
> >     set up your ~/.vnc/xstartup to run e.g. startkde.
> >
> >>soon.  Also, the link in the FAQ to whomever it was that wrote an RFB 
> >>protocol program to accomplish the sharing of :0 didn't work.
> >>
> >
> >     Can't comment on this part :-)
> >
> >     Austin
> >_______________________________________________
> >VNC-List mailing list
> >[EMAIL PROTECTED]
> >http://www.realvnc.com/mailman/listinfo/vnc-list
> >
> 
> I must have done something wrong here.  I'll go through the steps that I 
> did.  Let me know if I missunderstood something in your instructions. 
>  Here goes.  I droped the machine to init 3 (I'm running RH 7.3). 
>  Logged in as the user I'm trying to get this working for, and did 
> vncserver :0.  Then, thinking that start X meant typing 'startx' I first 
> made sure that .xinitrc wasn't going to start a window manager.  In 
> fact, .xinitrc didn't even exist in her home dir.  So, I made and with 
> only one line and that is, 'vncviewer -shared -fullscreen localhost:0. 
>  Also, her xstartup file is starting kde.  Then I did startx, and X 
> failed because something was already using :0.
> 
> So, what did I do wrong?  What did I miss?
> 

        I had thought X was smart enough to find the first available
display - which maybe it is - but xinit/startx seems to set it to :0
explicitly when it starts the server. You can override it by doing
"startx -- :1", where the -- part means everything else is passed by
startx as an argument to X.
        Also IIRC .xinitrc has to be executable. You probably have to
"chmod +x ~/.xinitrc".

        Austin
_______________________________________________
VNC-List mailing list
[EMAIL PROTECTED]
http://www.realvnc.com/mailman/listinfo/vnc-list

Reply via email to