Due to the fact that Kopete doesn't do
Ya-Whore YahhOoooOooo messenger very well, I won't be using Yahoo instant messaging any more. I'll be using my mainstay messenger, AIM. Kopete does AIM nicely.
I think there was only like 2 or 3 people I knew who used Yahoo. To those people: Use AIM instead if you want to message me. If you don't, well, um... e-mail or call me or something. (grin)
Today, by mistake, I deleted 800 e-mails I was saving. Some were eFaxes, some were from friends, some were business related and so on. This is mail accumulated over the course of year or so. Anyway - all of them are gone.
In the past I would have absolutely freaked out at losing that many e-mails, and would probably be under the desk right now sucking my thumb in fetal position over losing that much stuff. That's not the case obviously. Instead I just shrugged my shoulders and said "Oh, well." As a matter of fact, I'm pleased that it's gone. Now I don't have to keep track of that crap.
This clean-up process, whether intentional or not, has been on ongoing process for me. I remember what my computer used to be like. It had fancy wallpaper, all custom icons, RAM-enhancing utilities, lotsa games, the latest and greatest web browsers and all sorts of other useless garbage. These days I run computers mostly "stock". I load 'em up, patch 'em up (no matter what operating system,) and run 'em. The hard drives are kept clean and I only install a few apps that I have saved to CD.
Sometimes it's just good to start back at zero, otherwise you get too wrapped up in minutia that doesn't matter at all.
...You guessed it, SuSE. (grin) But I'll talk about that in a minute. This is going to be a very nerdy post, so if you're not into SuSE Linux or couldn't care less about it, well.. tough. Don't read this post then. :-)
I did not go to work today, the car did not start this morning. It has since been fixed, but it can be very trying on the nerves when the car does not start. Meh.
So.. I spent most of the day toying with my SuSE box. As a matter of fact, this is my first entry from Linux. Woo-hoo. My biggest challenge today was "Okay.. I can use TightVNC to go from Windows-to-Linux really easy (see one of my previous posts on how I did that), but is it possible to go from Linux-to-Windows, kinda like the same way you use PuTTY?" Answer: Yes, this is how:
You must be logged into Linux (duh) and be in some type of X-Windows environment, whether it's KDE, GNOME, Blackbox or whatever.
You must have TightVNC installed with the viewer. You can also use regular VNC. You'll know if it's installed correctly if you can type vncviewer at a console prompt in X-Windows, and the vncviewer launches. Tip: VNC Viewer comes with RedHat preinstalled most of the time on newer installations. In SuSE, the TightVNC is located on their FTP site as a SuSE rpm that you can install with YaST. Really, really easy.
The Command Line SSH
As with a lot of things in *nix, you must connect from the command line first before launching vncviewer. It's called ssh.
The command line to use is (assuming the remote box is set up properly):
ssh -L local-port:localhost:remoteport -l username host_ip_address
Here are some better examples.
Assume that the host is:
On public IP address 192.168.1.100, and is Windows based with cygwin and tightvnc -- meaning the remote vnc port on the Windows box would be 5900 by default.
The command line would be:
ssh -L 5901:localhost:5900 -l username 192.168.1.100
Then you would launch vncviewer and put localhost:5901 and the remote Windows desktop will pop up.
But... what if you're running tighvnc server on the linux box you're connecting from and you get a "port in use" error? Yeah, I ran into that - and it stumped me until I found out that if you have a TightVNC server running on your *nix box, port 5900 is actually 0 where vncserver is concerned, so 5901 is actually 1. And no, you can't do localhost:1, because as you know, that port is already in use by your tightvnc server. If this is your situation, do this command line instead (and it does work):
ssh -L 8000:localhost:5900 -l username 192.168.1.100
When logging in this way, you would connect vncviewer to localhost:2100. Confused? Don't be. 8000 minus 5900 is 2100. Since 5900 is 0 on a *nix box with TightVNC server installed, 5900 + 2100 = 8000. Get it? Well, even if you don't - that's the way it works.
And yeah, connecting to a Windows box from a Linux box is damn slow. You may want to read up on vncviewer options by typing man vncviewer at the console prompt and putting in some compression/depth options.