On Fri, 19 Dec 2003, Celestial Wizard wrote:

> Kevin Reichhart wrote:
> 
> >I have a laptop with a wireless card and a 10/100 port.  When gentoo comes
> >up, I get this:
> >
> >
> >Jan  3 19:00:31 localhost kernel: Linux Kernel Card Services 3.1.22
> >Jan  3 19:00:31 localhost kernel:   options:  [pci] [cardbus] [pm]
> >Jan  3 19:00:31 localhost kernel: ds: no socket drivers loaded!
> >
> >(yeah, I know... date's wrong... but ntp can wait ;-)
> >
> >
> >Once it comes up, I can:
> >
> >/etc/init.d/pcmcia zap
> >/etc/init.d/pcmcia start
> >/etc/init.d/net.eth1 start
> >
> >and the network comes up with no problems.  Is something not loading early
> >enough?
> >

That is exactly right, something is not loading early enough, and it's
probably a module. You can try either of the following procedure :
- Rebuild your kernel and include the module in it.
- Edit /etc/init.d/pcmcia to have it run later in the boot procedure.

> Do you need to add something to /etc/modules.conf?
> 
> >
> >Problem #2:
> >
> >/etc/init.d/sshd start yeilds this:
> >
> >
> >/etc/init.d/sshd restart
> >* Bringing eth0 up...
> >* Failed to bring eth0 up                                          [ !! ]
> >* Please make sure that /etc/conf.d/net has $iface_wlan0 set
> >* Starting sshd...
> >Missing privilege separation directory: /var/empty                  [ !! ]
> >
> >eth0 is the 802.3 (which isn't currently pluged in) and eth1 is the
> >wireless card that I brought up late (due to above problem).  How can I
> >get sshd to use eth1?

Your question is not linked to your problem. In order to have sshd use
eth1, you have to set the ListenAddress option in your
sshd_config. However, this will have no influence over the error
message you get. The message simply says that /etc/init.d/sshd depends
on net, so the system is trying to bring up every interface that are
listed in your default runlevel. If your network card isn't plugged in
yet, I would consider commenting out the "eth0" line in
/etc/conf.d/net, and removing net.eth0 from the default runlevel. This
should remove the message.

> >
> >Bonus question:
> >
> >What is causing the
> >Missing privilege separation directory: /var/empty                  [ !! ]
> >?
> >
> >
> >
> mkdir /var/empty
> not sure what the permissions should be
> root.root 755 ?

I do not have the same error message, and have enabled the
PrivilegeSeparation option in my sshd_config too. Here's what ls says
about the permissions for /var/empty :
drwxr-xr-x


I hope this helps,

Regards,

Jonathan

Attachment: pgp00000.pgp
Description: PGP signature

Reply via email to