[newbie] Services

1999-11-15 Thread Chris Smallhorne

Hi there.

I recently recompiled my kernel.  I now get the following message when I
boot:


 "Starting amd: amd forgot to set AF_INET in udp sendmsg. Fix it!"


What does this mean?  Also, how do I fix it?  Any suggestions?

Thanks,
Chris.



Re: [newbie] Problems with 6.1 install

1999-10-01 Thread Chris Smallhorne

Axalon Bloodstone wrote:
 
 On Mon, 27 Sep 1999, Chris Smallhorne wrote:
 
  Pedro Timoteo wrote:
  
   Chris Smallhorne wrote:
  
I have recently upgraded to v6.1.  Since that time, I am no longer able
to run anything when I su from a terminal.  For example, if I try to run
control-panel, i get the following:
   
"Xlib: connection to ":0.0" refused by server
 Xlib: Client is not authorized to connect to Server
   
  
   That is supposed to happen. The X session is "yours", not root's, therefore
   when you "su" you don't have the DISPLAY environment variable set. A simple
   "export DISPLAY=0:0" solves it, though.
 
 
  Next question - where and when do I do this?  Do I ave to do it every
  time, or is it a setting I can put into a config file?
 
  Thanks,
  Chris.
 
 Thats incorrect, you should run 'xhost +local:' 'xhost +localhost' or
 learn to use xauth to add you X keys to root's .Xauthority. And you'd need
 to run it before su'ing
 
 --
 MandrakeSoft  http://www.mandrakesoft.com/
 --Axalon


Thanks? Axalon, but what you have written here means absolutely nothing
to me.  When am I supposed to enter these commands, and how frequently? 
What is xauth and what does it do?  

These problems never occurred in v6.0 - why should they start happening
now?  

Chris.



Re: [newbie] Problems with 6.1 install

1999-09-27 Thread Chris Smallhorne

Pedro Timoteo wrote:
 
 Chris Smallhorne wrote:
 
  I have recently upgraded to v6.1.  Since that time, I am no longer able
  to run anything when I su from a terminal.  For example, if I try to run
  control-panel, i get the following:
 
  "Xlib: connection to ":0.0" refused by server
   Xlib: Client is not authorized to connect to Server
 
 
 That is supposed to happen. The X session is "yours", not root's, therefore
 when you "su" you don't have the DISPLAY environment variable set. A simple
 "export DISPLAY=0:0" solves it, though.


Next question - where and when do I do this?  Do I ave to do it every
time, or is it a setting I can put into a config file?

Thanks,
Chris.



Re: [[newbie] message repeats]

1999-09-21 Thread Chris Smallhorne

Hi there.

I have recently tried to re-install vmware (the new beta version), to see if I can 
finally
get it to work.  However, I get the following message during the install:

"None of VMware's pre-built vmmon modules is suitable for your running kernel. Do you 
want
this script to try to build the vmmon module for your system (you need to have a C 
compiler
installed on your system)? [yes]

What is the location of the directory of C header files that match your running kernel?
[/usr/src/linux/include]

The directory of kernel headers (version 2.2.9-19mdk) does not match your running 
kernel
(version 2.2.9-27mdk). Consequently, even if the compilation of the module was 
successful,
the module would not load into the running kernel."

I answer the defaults to both questions - I assume that I have installed a C compiler 
because
I selected everything when I installed linux originally (stop laughing - I wasn't to 
know any
better :) ).  As you can see, I have compiled a new kernel (I think it worked - I 
don't get
any error messages during boot-up).  Can someone tell me (in simple terms) how I might 
be
able to fix this error?  If you require further info please ask, as I still have 
little to no
idea what I am doing in linux.

Thanks,
Chris.



Re: [[newbie] message repeats]

1999-09-21 Thread Chris Smallhorne

Thanks for the info Mike, I went to the VMware site to check it out -
here is what it said:

Software requirements

 1.VMware host operating system requirements
  glibc2 to glibc6  (glibc1 does not work)
  Linux kernel 2.0.32 to 36
  Linux kernel 2.2.0 and higher for SMP systems

   VMware will not run on systems that do not meet these
requirements.

Does this mean that I need to find a copy of kernel version 2.0.32 to
36, or should it work with 2.2.9-19mdk?  If I only need to go back to
2.2.9-19mdk, is it easier to do an "upgrade" install to go back to this
kernel version, or won't this work and will I be stuck with doing an
install from scratch?  I don't think I made a backup of the old kernel -
if I did, I don't know where I put it.  Is there any way to find out?

BTW, what does the -19mdk mean?

Thanks,
Chris.


Mike Fieschko wrote:

  "Chris" == Chris Smallhorne [EMAIL PROTECTED] writes:

 [snip]

 Chris The directory of kernel headers (version 2.2.9-19mdk) does
 Chris not match your running kernel (version
 Chris 2.2.9-27mdk). Consequently, even if the compilation of the
 Chris module was successful, the module would not load into the
 Chris running kernel."

 [snip]

 Chris messages during boot-up).  Can someone tell me (in simple
 Chris terms) how I might be able to fix this error?  If you

 [snip]

 Upgrade kernel-headers to 2.2.9-27mdk.

 But, you might want to check the VMware pages, since I believe vmware
 doesn't work with 2.2.9-27.  It does work with other kernel versions.

 --
 Mike Fieschko, West Orange, NJ, USA
 X-Mailer: XEmacs 21.1, VM 6.71 and random-sig.el
 X-Face header is me! http://www.cs.indiana.edu/picons/ftp/faq.html
 Kernel 2.2.13-7mdk mailto:[EMAIL PROTECTED]
 http://www.viconet.com/fieschko/home.htm
 Sep 21 St Matthew
 "Truth is sacred; and if you tell the truth too often nobody will
 believe it." - [G.K. Chesterton, in ILN, 2/24/06]