|
Bluehz,
Thanks. Well, it seems the kde installation is allright, except no kdebase3-ssl-dev. I will suggest you update later all the kde packages that have (i) in front. This means a newer version is available. For your other question, I'm not sure I understand what you mean when you say XDarwin dissapears. Quote:
Cheers... |
Ok - lets say I launch a fullscreen XDarwin session. I usually do that and work on my Linux box. Everything is fine, can work on it for hours until let say I want to check my mail in OS X. I hit cmd+shift+A to switch out of fullscreen and back into OS X - so I can see the OS desktop, etc. Switch over and start whatever task I want. When I try to go back to XDarwin - its gone. Just disappeared - no dialogs, errors, etc.
Quote:
|
short list?
Huh, I am having some trouble setting up fink for 10.2. I have followed the instructions posted at sourceforge and everything works... sorta. fink -list gives me only this:
Code:
[localhost:/sw/etc] glenn% fink listShould my list of packages to install really be this short? Where is XFree86? Gees. :) Please advise. |
Bluehz,
So, you are working in 'one' computer, where you have installed MacOS X 10.2 and also installed XFree86 through Fink. Then, you start an XWindows session by double clicking the XDarwin.app in the Applications folder. You choose from the XDarwin dialogue box, 'fullscreen mode'. You work in XFree, till you want to switch to MacOS X desktop to use the mail.app, then to switch, you press the Command+option+A keys (default), and you are at the MacOS X desktop. If this is what you are doing, then to switch back to the XFree86 fullscreen desktop, just click once on the XDarwin.app icon in the apple Dock, and you will be in the Xfree86 desktop. If this is 'not' what you are doing, please tell me how do you start your XWindows session. And your setup. Cheers... |
Arakageeta,
Did you installed Fink from scratch in 10.2 or you upgraded Fink for 10.2? Did you run 'sudo fink list' ? Also, if you installed Fink from scratch, have you done: 'fink selfupdate-cvs' If you are using FinkCommander you probably need to update to the cvs version. Check the other thread about FinkCommander: http://forums.macosxhints.com/showth...&threadid=5483 Cheers... |
Oh hey look at that. It was the 'fink selfupdate-cvs' that killed me. All my packages are back!
|
Arakageeta,
Glad it worked. Cheers... |
sao - that is basically it, except that I don't have much luck starting XDarwin app itself - normally it launches, I choose fullscreen, and it quits. This may be because I have specifically NOT created an .xinitrc so it starts with the minimum of WM stuff (read below for why).
So here's what I actually do (all on G4): root@g4: startx -- -fullscreen -quartz # xdarwin launches and asks me if I want to # display the X11. Now within XDarwin - eterm. # The first thing I usually do within XDarwin is # click on the desktop to access the dropdown # menu and choose EXIT. This exits the WM as # much as possible. root@g4: xhost +linux.macvoodoo.lan root@g4: ssh -X root@linux # now on the linux box (SSH from g4) root@linux: export DISPLAY=g4.macvoodoo.lan:0.0 root@linux: startkde And that starts a KDE session for me running on the Linux box. The session itself is fantastic - all apps on the linux box launch, etc. In general KDE is MUCH FASTER than when I just launch KDE locally on the OSX box. Everything is fine until I switch out of XDarwin - for example to check mail in OS X. Use cmd+opt+A, switch to OS X app....and at some point while I am in the OSX app and XDarwin is in the background - XDarwin and my KDE session just disappear. It does not happen all the time - maybe 50% of the time. And it seems like the longer I stay in OS X the higher the odds of XDarwin exiting. Almost as if there is some sort of timeout value somewhere. I KNOW there has to be an easier method of getting a KDE session going than the one I use - but I have yet to find one that works. Please advise if you can. Sure would like to streamline the process. For one thing - you may wonder about the "...click on desktop, exit WM..." methodology I use. If this process is not done then the KDE session from the linux box comes up within windows (titlebars, etc). My method creates a completely full-screen KDE session - just like I was actually on the Linux box. Quote:
|
Bluehz,
I checked what you are doing and it seems to be fine. I'm a little reluctant to advice, I think osxpez will be more qualified to help you here. Cheers... |
bluehz: Have you tried using OroborOSX for this? I'd imagine that it would be a matter of starting OroborOSX. starting xterm or Eterm. logging in on the linux box with "ssh -X" and then do "startkde". Don't know if it would keep that dissapearing problem away, but it could be worth a try. I'll try myself. Just need to install kde on my linux box first. =) ... oh it's already done! (Debian GNU/Linux is god's gift to Mac folks who needs Linux). Yes, it worked like I described above. Got an error message about sound not beeing available. But KDE is there. Now I must just find some time playing with it. :)
|
osxpez - actually over the last few days I have done exactly what you were suggesting. Installed OrboroOSX. It does seem to be a bit more stable and I have yet to see it disappear. Thx for the advice!
Strangely enough though - I still have to do an: export DISPLAY=local.machine:0.0 after I get onto the Linux box. I thought that was covered by the ssh -X process but I guess not. -- I would like to amend my thoughts on OrboroOSX - not very reliable at all. IF (thats a BIG IF) I can get it to actually start then it stays open. The problem is - most times it will not launch. Watching the console it shows Xdarwin crashing every time. Sometimes if I continue to attempt to open OrboroOSX - maybe after the 15-20 launch it will actually launch and stay open. Not very effecient if you ask me.... |
Strange. OroborOSX never fails to start on my machine. It isn't that you already have Xfree running or something?
About that "ssh -X". It should be enough. But it could be that sshd on that linux box is set to not forward X11. Check with the sysadmin on the linux box. |
No Xfree already running and I verified that I did not have a ~/.xinitrc either - this caused problems at first. Even a blank one cause problems. Removing it completely solved it.
Also - I can easily start and stop Xfree manually so I know I have no problems there. Funny - OrborosOSX was working great on Fri. haven't changed a thing in the last two days either - no fink installs or anything. Quote:
|
X11 forwarding should be default. I think you can configure it in /etc/ssh/sshd.conf. You need to restart sshd after changes in this file I think.
|
Bluehz,
Yes, that's right, you need to put: ForwardX11 yes into /private/etc/ssh_conf as X11 forwarding is not switched on by default. Cheers... |
The thing is that X11 forwarding should be on by default on most Linux distributions. I've checked on my Debian GNU/Linux box and there the file to edit is:
/etc/ssh/sshd_config |
osxpez,
I'm sure you are right, just sticking my nose here. Cheers... |
FYI - on my Slackware Linux 8.1 box the default forwarding is OFF. What are the other two settings I see in the ssh.conf?
X11Forwarding yes #X11DisplayOffset 10 #X11UseLocalhost yes |
No idea. But in my sshd_config there's no mention of any "#X11UseLocalhost". Though I do have this line there:
X11DisplayOffset 10 |
| All times are GMT -5. The time now is 06:12 PM. |
Powered by vBulletin® Version 3.8.7
Copyright ©2000 - 2014, vBulletin Solutions, Inc.
Site design © IDG Consumer & SMB; individuals retain copyright of their postings
but consent to the possible use of their material in other areas of IDG Consumer & SMB.