I'm getting a message during startup that says Services skipped in runlevel 5 smbfs

1)What does it mean?

I believe it means that the service was skipped because the network was not up yet. At least this is the way it works for me (on a laptop with suse 9.0): -for wired network, the network service does not exit until the interface is actually up, and then smbfs starts successfully after that -for wireless network (pcmcia card), the pcmcia and/or hotplug services starts and immediately returns. The interface doesn't get a valid connection until *after* the smbfs and nfs services start (and fail due to no connection available). Not sure if this is the same cause as your problem but my situation is a bit frustrating. It means I need to manually mount my nfs and smbfs filesystems after I login because I can't get the stock init scripts to properly wait for a hotplug wireless network connection. Last night I tried adjecting the "Required-Start" for smbfs and nfs to only start in runlevel 5 *after* xdm (a true hack for experimental purposes only) and it still wasn't enough time to get them to mount anything before exiting due to no net connection. I could hack the init scripts to delay/retry but I'll wait to see if there is a built in method first--anyone know?

2)How do I get rid of it?

For me, using a wired net connection was enough. Or you could `chkconfig smbfs off` ;-) No comments on your last 2 questions, sorry. I think it might be HW/BIOS dependent? Brett