Hi Thomas Thomas Pohl wrote:
> Package: install-doc > Version: 3.0.24 > > Installing Debian GNU/Linux 3.0 For Intel x86 > version 3.0.24, 18 December, 2002 > http://www.debian.org/releases/stable/i386/ch-init-config.en.html > > Moin, > > i made a installation with http on my new computer. DHCP was used. > After rebooting DHCP was not used. I don't understand. Was it not used because it didn't work, because you didn't want it to be used, or because you broke it? > It took a while for a Linux-newbie like me to find out. I think a hint > in chapter 8.1 "Make System Bootable" about this "no-DHCP-behaviour" > would be helpfull for other users. Well, there seems to be either a misunderstanding on your or my side, or an unpleasant bug in the installer. If you chose to configure your interface by DHCP during the installation to fetch the base packages, which obviously is what you have done according to what you are saying above, then the installer will lay out the boot scripts in such way, that your computer will automatically bring up the interfaces using DHCP during boot time! You don't have to install extra packages or do any thing else to get it working. If you chose DHCP during the first part of the installation, your interfaces will be configured using DHCP every time you switch on your computer. Well, but, if it would work, I guess you wouldn't be filing a bug report. So lets try to figure out what really happens on your machine. 1. Your computer is trying to configure the interfaces during boot, but you don't have any cable plugged in or your dhcp server isn't working. The networking scripts then try again for quite a long time, holding up the boot process. I can't imagine you wouldn't notice that booting takes extremely long. But if it does like that, and you'd like to configure the interfaces later on and not during boot (which is quite a natural setup for notebooks btw.), the problem seems to be that 2. You don't know how to manually bring up the interfaces. Well, no worrying, just issue # ifup eth0 to bring it up (eth0 or whatever, eth1, etc.). Note that this DOES automatically use DHCP if you chose DHCP during the installation process. #ifdown eth0 to stop it (as before, eth0 or whichever your favorite interface is). If this isn't the case, there could be a third problem, 3. The kernel you are using isn't compiled with CONFIG_PACKET=y and CONFIG_FILTER=y This stuff is needed for the dhcp client to operate AFAIK. > Google found a nice text from Martin Rasp about howto configure DHCP on > a Debian. > maybe you can use this part for the install-doc. > > -part of http://www.linux-fuer-alle.de/doc_show.php?docid=8------------ > > Auf meinem Arbeitsrechner musste ein DHCP-Client installiert sein. Das > Paket "pump" war bereits durch die Debian-Installation verf�gbar. > Ansonsten h�tte ich es nachtr�glich mit dem folgenden Kommando > installieren m�ssen: > > | apt-get install pump | Well, pump is not being used for woody installation dhcp, is it? > Anschlie�end editierte ich die Datei "/etc/network/interfaces": > > ### /etc/network/interfaces > ################################################# > > auto eth0 > iface eth0 inet dhcp > hostname speedy > > ############################################################################# If you chose DHCP during the first part of the installation, you get a /etc/networking/interfaces looking like this: # /etc/network/interfaces -- configuration file for ifup(8), ifdown(8) # The loopback interface auto lo iface lo inet loopback # The first network card - this entry was created during the Debian installation auto eth0 iface eth0 inet dhcp This will cause the networking script to try to configure the interface eth0 using a dhcp client. If you don't want to have the networke started automatically during boot time, you can comment out the "auto eth0" to look something like this # auto eth0 iface eth0 inet dhcp Now you have to bring up the interfaces manually by using the ifup and ifdown scripts as described above. I also suggest to have a look at man interfaces. > �ber den folgenden Befehl startete ich das Netzwerk neu: > > /etc/init.d/networking restart | Yeah, or ifup ifdown. So, finally, I would not suggest to include the above mentioned text in the installer manual, as it should not be needed if everything works the way it is intended to do. If it doesn't work like that, this is a software bug and shouldn't be cured by simply telling the user to fsck around with the interfaces script. But, altough a bit off topic, but in this context it came to my mind, I would strongly suggest to add a requester during the first part of the installation, after being asked if the user wants to use dhcp for interface configuration, a requester which now asks if the user does also want to have the network brought up immediately during boot time! Because this is seldom useful for notebook and similar configurations. But since the guys are working on a new installer anyway, I guess this would rather be a suggestion for debian-installer instead of boot-floppies. -- Best wishes, Andi -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
