The LBX Mini-HOWTO

• Index
• Introduction
• What's The Status Of LBX?
• Who Can Benefit From LBX?
• Who Doesn't Need LBX?
• How Does LBX Work?
• What Do I Need To Use LBX?
• What Don't I Need To Use LBX?
• How Do I Start LBX?
• Problems
• Documentation
• Alternatives

8. How Do I Start LBX?

OK, here it is... after all that it's actually quite simple. Replace LOCAL and REMOTE below with the hostnames of your local workstation and remote system, respectively (don't get them mixed up!)

On LOCAL:

1. Start your X server.
2. Tell your X server that the remote system is allowed access. Using the host-list method, type xhost +REMOTE. If you use xauth you may need to do more than this; see the xauth(1) man page for more information. You should consult the Remote X Apps Mini-HOWTO if you're not familiar with remote X access permission setup.

On REMOTE:

1. Start lbxproxy and tell it to forward to the LOCAL X server, like this:

     $ lbxproxy -display LOCAL:0 :1 &
   

   This tells lbxproxy to use display :1 on the REMOTE system; if that system has >1 display already you can use :2 or whatever instead.
2. Set your DISPLAY environment variable to point to the display that lbxproxy is providing, instead of the normal display:

     $ DISPLAY=:1
     $ export DISPLAY
   

   Or, if you use csh or clones:

     % setenv DISPLAY :1
   

3. If you're using xauth you will need to ensure that your cookie is available locally. See the Remote X Apps Mini-HOWTO for more information on this.
4. Start your X applications!

That's it; all X apps that are started up pointing to :1 will use LBX. Of course, there's no reason you couldn't also start X apps pointing to LOCAL:0 and have both running at the same time.