> -Original Message-
> From: Mihamina Rakotomandimby
> [mailto:[EMAIL PROTECTED]
> Sent: 03 January 2007 10:04
> To: Gentoo mailing list
> Subject: [gentoo-user] net.eth0 device initiated services
>
>
> Hi,
> I have /etc/init.d/net.eth0.
> I dont want it to be launch at boot, but I dont w
Nelson, David (ED, PAR&D) wrote:
-Original Message-
From: Mihamina Rakotomandimby
[mailto:[EMAIL PROTECTED]
Sent: 03 January 2007 10:04
To: Gentoo mailing list
Subject: [gentoo-user] net.eth0 device initiated services
Hi,
I have /etc/init.d/net.eth0.
I dont want it to be launch at boot,
> -Original Message-
> From: Matt Richards [mailto:[EMAIL PROTECTED]
> Sent: 03 January 2007 12:06
> To: gentoo-user@lists.gentoo.org
> Subject: Re: [gentoo-user] net.eth0 device initiated services
>
-- snip --
> it might be a nice idea to look into how knoppix
On Wed, 3 Jan 2007 11:23:28 -, Nelson, David \(ED, PAR&D\) wrote:
> I tend to set the eth0 dhcpcd timeout at ~5 seconds. The DHCP server I
> usually use (the gentoo based server under my desk!) always responds
> within 5 seconds. When I'm out and about and using/"borrowing" a
> wireless connec
> -Original Message-
> From: Neil Bothwick [mailto:[EMAIL PROTECTED]
> Sent: 03 January 2007 13:06
> To: gentoo-user@lists.gentoo.org
> Subject: Re: [gentoo-user] net.eth0 device initiated services
>
-- snip --
> Or you could emerge ifplugd, then the startup
you can name the kernels in /boot anything, so long as the name is
referenced in /boot/grub/grub.conf correctly.
you can decrease the boot time by giving your dhcp client a timeout
value in seconds. I use 10 seconds for my desktops, because if my
dhcpserver isn't responding by then, it's proba
> Or you could emerge ifplugd, then the startup scripts won't try to
> initialise eth0 if no cable is detected.
Another alternative is netplug. I don't know how they compare, but I'm
using netplug sucessfully.
http://www.red-bean.com/~bos/netplug/README
Rgs,
Adam
--
gentoo-user@gentoo.org ma
7 matches
Mail list logo
