...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.
Yeah I know. I keep talking about SuSE a lot. But heck this is cool stuff!
SuSE has been running very well and has proved to be extremely stable (so far). I have installed a bunch of apps, like gAIM (AOL Messenger for Linux) and so on. Everything has been running smooth. My only complaint is that some of the icons and other menus in the system are a bit too big, but I am figuring out how to customize stuff and am getting used to it.
It is simply amazing how far X-Windows has come in the Linux operating environment. It loads much faster than I remember years ago, and apps are WAY easier to install now too. I'm finding myself actually enjoying using Linux now. I still haven't figured out how to do Samba right (as in sharing files between Windows/Linux) but I'm sure that will come in time.
I'm hoping some other good stuph will happen in my life soon so I can stop talking about SuSE. :-)
The server has been up and running for a day now. After a few attempts with Condition Zero, the box just wasn't up to the task. There is something about CZ which for some reason uses more server process than CS does. So... I went with a CS mod instead of CZ. Works much much better. I saw 8 people on the server today. The ping rates were a little high, but, the server did not crash. As I type this right now, there are a few people on the CS server right now. It's running good for what the box and pipe allow which is all I could ask for. (grin)
In addition to the nerdy game server things I've been doing, I decided to give SuSE Linux another shot today on the blow-up box (2.4GHz P4 Dell Dimension) to see if I could get TightVNC to work on remote. As normal readers of this blog will know, my first attempt failed miserably. But guess what, I figured it out this time. IT WORKS. Kick... Ass. I will be posting screen shots in my next post so people can see what it looks like. The reason I can't post screen shots now is because I have to reinstall SuSE to get the partitioning of the hard drives correct. I did a Windows/Linux dual-boot thing just in case the SuSE failed again.
Some of you may be wondering why I was trying so hard to get SuSE working in the first place, and why I don't just stick with Windows. Here's a few good reasons why:
Windows crashes. Everyone knows this. Linux does not crash. Well, that's not entirely true, you can crash it - but - you'd have to be literally trying to crash it on purpose.
2. File integrity
Ever have a file that for some reason just got corrupted, like an MP3 that for some reason started to get little "glitches" in it? That's Windows doing that. I notice that over time Windows will eventually start corrupting files, even by having them just sit there and do nothing. I've never understood that... but that's just Windows for ya.
3. Virus free
The majority of viruses that exist on the internet are made for Windows because everyone uses Windows. I can safely say that Linux users never have this problem. Viruses are mainly gearned towards mainstream applications and operating systems.. like Windows.
So anyway, more info on that when I'm done with it.