Re: [Cooker] Proposal: Install a dchp-client by default on *every* new install.

[Michael Scherer]

Le 2 mai 08 à 13:46, Steve Morris a écrit :
> > > >
> > > As I have pointed out on numerous occasions before,  and other  
> > > people
> > > have reported recently, it is nothing unusual for networking to no
> > > properly interface to dhcp after a simple 'urpmi --auto-update', not
> > > just at install time. Hence the whole networking/dhcp interaction  
> > > needs
> > > to be revalidated.
> >
> >
> > after installing what rpm, with what distribution ?
> This is with cooker. With the volume of rpms that 'urpmi --auto- 
> update'
> usually installs it is impossible to determine what rpm package causes
> the problem. The usual indication is loss of internet access, and  
> having
> to modify the dns specification in the network configuration to get it
> back again.

By saying "loss of internet access", you mean that nothing answer to  
ping, that the default route is wrong, that a firewall is blocking the  
answer, that
the dns is wrong ?

And if you lose internet access, this should stop the upgrade from  
working, no, as you are downloading rpm from the internet, so the  
problem
will be easy to spot, as this is when the last rpm is installed.
And in any case, there is logs of what happens during the upgrade, I  
guess you didn't found anything useful in them ?

--
Michael Scherer