Re: line 9xx has invalid contex

From: Tommy Reynolds (TommyReynolds_at_yahoo.com)
Date: 07/21/05 

Date: Thu, 21 Jul 2005 09:47:03 -0500

On Thu, 21 Jul 2005 13:19:10 +0000, Yvonne wrote:

> 2. I did upgrade my Bios to the latest available and it was from 1999, and
> ACPI isn't supported, so how can I remove the errorline?

Edit the "/etc/grub.conf" entry. Search for the line marked "kernel"
and append the string "acpi=no" (perhaps "noacpi" would also work).
 
> 3. These errors I don't know how to solve: WW) ATI : I2C bus Mach64
> initialisation failure. Deleted Mach64.

I suspect this is a message from the ATI video card driver. Just
ignore it. One day the driver will support everything about the
card.
 
> localhost kernel: There is already a security framework initialized,
> register_security failed.

This looks to be an SELINUX bogosity. I don't like SELINUX. I turn
it off using "selinux=no" on the kernel command line. Some folks
don't like me suggesting to turn it off, but unless you are running
an Internet-facing server it just ain't worth the trouble yet.
 
> localhost kernel: vesafb: probe of vesafb0 failed with error -6

The kernel thought it had identified the correct device driver for
this resource, but the driver reported failure when it actually
checked the device itself. Ignore it.
 
> localhost sshd[2225]: error: Bind to port 22 on 0.0.0.0 failed: Address
> already in use.

I am suspicious of that "0.0.0.0" IP address: it looks totally bogus.

As root, try this:

        # rm /etc/ssh/ssh_host*key
        # service sshd stop

and see if there are any sshd's running:

        # ps ax|fgrep sshd

If so, there is a rogue SSHD that wasn't started by a
"/etc/init.d/sshd" script. IIRC, earlier versions may have been run
by XINETD, so check the "/etc/xinetd.d/*" files for any sshd's run
from there. The current wisdom is that sshd should be a stand-alone
service.

When you are finished, be sure to restart the SSHD service:

        # service sshd start
 
> The computer seem to work correctly, so do I need to do something and
> what?

Yes. Don't break it ;-)
 
> 4. Now I have configured Samba. The linuxmachine is able to reach the
> shared folder on the Windowsmachine, but the Windowsmachine can't reach
> the Linuxmachine.

What do you mean here? Does the Windoze machine:

1) Even see the Linux host on the network?

2) See any public (no-login required) services?

3) Offer to login with a username/password?

Need more details.

Cheers!