Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
Hey, I just got TightVNC installed, and I'm loving it! I have a Windows machine at home, and now I can run my Linux apps there as if I'm in my office. I have two quick questions (first being the more important one):
1. How can I set this up so that I can have xfce as the desktop I view when running this server. I have RedHat 9, with KDE as the default, yet when running vncserver I get Gnome?
2. I currently use TightVNC, and I only access my computer through ssh tunneling, I also do not have the vncserver running all the time. I only start it up once I'm in there, and kill it as soon as I'm done. Reading through this forum, those seem to be two highly recommended methods to making sure you keep your box as safe as possible. Am I missing anything else here?
1. I'm not entirely sure about TightVNC, but with ordinary VNC you need to alter the ~/.vnc/xstartup file to start your X environment of choice. I bet TightVNC does something similar.
2. This sounds like a decent set-up. Just be sure your SSH is updated to the latest version to avoid problems with known issues. You probably also want to check your firewall to make sure that it doesn't allow traffic on the normal VNC ports like 5901. If you can connect using just TightVNC, you've got a potential problem. You can also ratchet up the paranoia level by installing an IDS like Snort and a file monitor like Aide or Tripwire. None of these will stop an attack, but they will be able to help diagnose what happened if someone does manage to gain entry. I'd also have a visit to unSpawn's sticky threads at the top of the Security forum. Loads of good reading there.
Buick, please don't hijack threads... I realize this is a very related question, but yours is different enough that it deserves its own thread.
If you are using PuTTY to connect to a linux box, have a read through this thread and see if that clears up the problems.
Can I start up the vncserver during the session and than connect?
(I read that you need to have the vncserver up when connecting with a Windows client)
Well, if you want to use VNC to connect, then you have to have vncserver running. When I use VNC I usually connect with SSH, then start vncserver. If you just want console access, SSH is fine all by itself.
I'm glad you got it working. Please don't take my hijack comments too harshly since it wasnt' intended that way. My concern is actually for the people asking the questions. When someone posts a new question (even a related one) in the middle of a thread one of two things happen. Either the thread takes off in a new direction and the original poster might be left without the answers they are looking for or the new question doesn't get the attention it deserves because it is buried in a bunch of other replies.