Re: Netcfg and allow-hotplug vs auto

2007-07-16 Thread Otavio Salvador
"Matheus Morais" <[EMAIL PROTECTED]> writes: >alferes:~# mii-tool -v >eth0: negotiated 100baseTx-FD flow-control, link ok > product info: vendor 00:40:63, model 50 rev 10 > basic mode: autonegotiation enabled > basic status: autonegotiation complete, link ok > capabil

Re: Netcfg and allow-hotplug vs auto

2007-07-16 Thread Matheus Morais
On 7/14/07, Frans Pop <[EMAIL PROTECTED]> wrote:On Thursday 12 July 2007 20:59, Matheus Morais wrote: The most likely cause is that you have multiple NICs in your system and the order in which they are recognized is different after reboot then it was during installation. The problem also happen

Re: Netcfg and allow-hotplug vs auto

2007-07-14 Thread Otavio Salvador
Frans Pop <[EMAIL PROTECTED]> writes: > On Thursday 12 July 2007 20:59, Matheus Morais wrote: >> netcfg module is responsible to write >> /etc/network/interfaces at installation time right? Why use >> allow-hotplug instead auto in network configuration file? > > Mostly because it improves support

Re: Netcfg and allow-hotplug vs auto

2007-07-14 Thread Frans Pop
On Thursday 12 July 2007 20:59, Matheus Morais wrote: > netcfg module is responsible to write > /etc/network/interfaces at installation time right? Why use > allow-hotplug instead auto in network configuration file? Mostly because it improves support for laptops which may not always be connected

Netcfg and allow-hotplug vs auto

2007-07-12 Thread Matheus Morais
I've been with this doubt a couple months but just now I found some time to comment about it. I've customized some parts of debian-installer and I always still facing the same issue. netcfg module is responsible to write /etc/network/interfaces at installation time right? Why use allow-hotplug ins