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.
I have setup a Red Hat AS3 server and would like to connect to it with cygwin's xwindows, on a MS Windows box. My cygwinis working fine and I can connect to other linux servers with xwindows configured, I just cannot connect to the one I have just setup.
I have installed kdebase with yum. When I try to run startx I get the errors below. Any idea what I am doing wrong?
Am I wrong to think that if I run startx and it runs then I should be able to connect remotely. startkde is for starting kde on the box same box correct? Like I login to console and run startkde, and this starts the graphical interface on the terminal I am on?
XFree86 Version 4.3.0 (Red Hat Enterprise Linux 3 release: 4.3.0-81.EL)
Release Date: 15 August 2003
X Protocol Version 11, Revision 0, Release 6.6
Build Operating System: Linux 2.6.9-1.906_ELsmp i686 [ELF]
Build Date: 16 March 2005
Build Host: not allowed to post urls yet...
Before reporting any problems, please make sure you are using the most
recent XFree86 packages available from Red Hat by checking for updates
at [ur1]not allowed to post urls yet...[/ur1] or by using the Red Hat Network up2date
tool. If you still encounter problems, please file bug reports in the
XFree86 bugzilla at [ur1]not allowed to post urls yet...[/ur1] and/or Red Hat
bugzilla at [ur1]not allowed to post urls yet...[/ur1]
Module Loader present
OS Kernel: Linux version 2.4.21-32.0.1.ELsmp (not allowed to post urls yet...) (gcc version 3.2.3 20030502 (Red Hat Linux 3.2.3-52)) #1 SMP Tue May 17 17:52:23 EDT 2005
Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/XFree86.0.log", Time: Tue Feb 21 11:25:50 2006
(EE) Unable to locate/open config file
(EE) Error from xf86HandleConfigFile()
Fatal server error:
no screens found
If you encounter a server crash, please report the problem by filing a bug
report in the XFree86 bugzilla at [ur1]not allowed to post urls yet...[/ur1] and/or Red Hat
bugzilla at [ur1]not allowed to post urls yet...[/ur1]. When filing your report, it
is very important that you explain your problem in as much detail as possible,
and include a complete description on how to reproduce the problem. After
submitting the bug report, attach the following files as uncompressed
individual file attachments using the bugzilla file attachment feature:
- X server log file: /var/log/XFree86.0.log
- Kernel log file: /var/log/messages
XIO: fatal IO error 104 (Connection reset by peer) on X server ":0.0"
after 0 requests (0 known processed) with 0 events remaining.
Thanks 007, I created the file and ran nohup startx & and tail nohup.out and it seems to have started correctly. No errors. But I am still unable to connect with my cygwin install, it just hangs and I never get the login screen. Below are the x processes I have running. I am a little confused from some of the stuff I am reading, sounds like I need the server to run x client, is that kdm then. I started it as well and have still not been able to connect.
Umm... you don't want to run startx or configure X on the remote machine, that will just start the X server on the remote machine (not what you want). This has absolutely nothing to do with X on the remote machine at all (it makes no difference if there were no X at all on that machine).
You want the programs to use the local X server on your Windows. You want to first start the X server in Cygwin (run startx in Cygwin). Then in the xterm, ssh using "ssh -Y user@host ..." (this enables X forwarding). Make sure that X forwarding is allowed in the /etc/ssh/sshd_config on the remote machine.