Message-ID: <515BC2F2.1050701@devever.net>
Date: Wed, 03 Apr 2013 06:49:38 +0100
From: Hugo Landau <hlandau@devever.net>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130307 Thunderbird/17.0.4
Precedence: list
MIME-Version: 1.0
To: alpine-devel@lists.alpinelinux.org
Subject: [alpine-devel] initrd and kernel-mode DHCP
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Hi.

Is there any purpose to having CONFIG_IP_PNP=y in the Alpine kernel 
configuration? It appears that this feature necessitates network drivers 
to be built into the kernel, rather than as modules, but since Alpine 
builds such drivers as modules, the feature is unusable. Correct me if 
I'm wrong on this.

If this were disabled, we could instead handle "ip=dhcp" in the command 
line via the initrd init script and udhcpc, after network drivers were 
loaded. The inclusion of network drives in the initrd would be 
configurable via mkinitfs to keep default initrd sizes down.

The ultimate goal here is to enable Alpine to usefully PXE boot. Once 
Alpine is able to obtain an IP at the initrd phase, further 
modifications to the initrd init script to permit NFS or HTTP servers to 
be specified in the alpine_dev argument should be relatively 
straightforward.

Hugo Landau


---
Unsubscribe:  alpine-devel+unsubscribe@lists.alpinelinux.org
Help:         alpine-devel+help@lists.alpinelinux.org
---