On Friday, 22. April 2005 09:17, David Johnson wrote: > I'm losing my laptop, which I was using to build, run and hack CVS KDE. > This was convenient because I could ssh to the laptop and get the > benefit of using a stable KDE to work on an unstable KDE. But I may > lose the laptop, so I'm trying to figure out a good way to get the same > benefit. The HOWTWO for two KDE versions doesn't work for me.
Do you mean it doesn't work or you don't find it attractive/it doesn't meet your needs? If the former, it would be a good thing if you could post some details so the HOWTO can get adjusted. I know for a fact that there are people out there using that kind of setup quite sucessfully. > The problem I am having is that I keep getting a "Error: Can't open > display: :0" message. I've tried setting the display to localhost:0 as > well with no effect. Googling told me I needed to nullfs mount my /tmp > directory so sockets would work, but that didn't fix the problem > either. I've also did a "xhost +" to make sure I had permission. Connecting over the network is probably easier: - Make sure you're *not* starting X with the -nolisten tcp option. If you're using kdm, check the ServerArgsLocal line in kdmrc. - chroot to your partition - set DISPLAY to your <host's real IP-address:0>, i.e. not 127.0.0.1:0 but for example 192.168.0.4:0 - outside your chroot, do xhost +192.168.0.4 Now programs in the chroot should be able to connect. -- ,_, | Michael Nottebrock | [EMAIL PROTECTED] (/^ ^\) | FreeBSD - The Power to Serve | http://www.freebsd.org \u/ | K Desktop Environment on FreeBSD | http://freebsd.kde.org _______________________________________________ kde-freebsd mailing list [email protected] http://freebsd.kde.org/mailman/listinfo/kde-freebsd
