Re: Network problems with testing using netinst CD-image
On Fri, Jul 07, 2006 at 01:30:54PM +0200, Svante Signell wrote:
> On Fri, 7 Jul 2006 10:30:33 +0200, Geert Stappers wrote:
> >On Fri, Jul 07, 2006 at 09:35:29AM +0200, Svante Signell wrote:
> >>
> >> Can you explain why ifup/ifdown is not available in the shell during
> >> install but after reboot? Is the ifupdown package part of the network
> >> install?
>
> >The install program is not a full blow system.
> >It doesn't use the very same utilities as an installed system.
>
> OK, it is here the udebs come in, right?
Yep.
[ ... ]
> >Great! Five working boxes makes it easy to explain that
> >the non-working box is the odd one.
>
> What do you mean?? I've been running various GNU/Linux distributions
> like Redhat, SuSe, Mandrake/Mandriva and Debian and I like Debian best.
> That is the reason for having Debian on all boxes.
I mean that it is difficult to say "d-i works fine for me"
when someone says "d-i doesn't work", especial when no information
about the hardware is at hand. Bashing hardware is neither helpfull
to promote software.
> >Where you were ranting^Wlooking for ping and other debug tools not
> >available, we forgot to speak about the tools that are available.
>
> >What says `ifconfig`, `lsmod` `lspci | grep Ethernet` inside d-i?
>
> Started the d-i in rescue mode and configured the network manually and
> all works properly! Very strange. However, when things did not work I checked
> both ifconfig and lsmod and all was OK then too!
Does that mean that problem can't be reproduced ( a.k.a. "is gone" ) ?
In other words: is there something where we can make d-i better?
> BTW: lspci is not available in d-i, at least I could not find it.
AFAIK is lspci at least two months in d-i. Beta 2 didn't yet include it.
Cheers
Geert Stappers
Reply to: