On Fri, 4 Jan 2002 06:54:59 +0100, Geert Stappers [EMAIL PROTECTED]
said:
Geert Why worry about about a extra BOOTP request, when we have a
Geert complete installation to do on mostly single NIC computers?
Strange, I only do FAI on multi-NIC computers since it is for a network
Hi,
When rcS_fai tries to get bootp parameters, it does a query on every
interface the machine has. This can take a lot of time for nothing.
the following patch tries the defaut interface first, and break the loop
after the first successfull query. (use the attached file to avoid
copy-paste
On Thu, 3 Jan 2002 16:11:23 +0100 (CET), Phil [EMAIL PROTECTED] said:
Hi, When rcS_fai tries to get bootp parameters, it does a query
on every interface the machine has. This can take a lot of time
for nothing.
This could be made much simpler. If the variable $netdevices is
On Thu, 3 Jan 2002, Thomas Lange wrote:
On Thu, 3 Jan 2002 16:11:23 +0100 (CET), Phil [EMAIL PROTECTED] said:
Hi, When rcS_fai tries to get bootp parameters, it does a query
on every interface the machine has. This can take a lot of time
for nothing.
This could be made
On Thu, 3 Jan 2002, Geert Stappers wrote:
Moreover,
I don't see why every NIC in $netdevices should query a bootp server.
One answered query should be enough.
Even a single NIC computer does three(3) BOOTP-requests:
- BootROM where to get my kernel-image request
- Kernel where to get my
At 0:51 +0100 1/4/02, Phil wrote:
On Thu, 3 Jan 2002, Geert Stappers wrote:
Moreover,
I don't see why every NIC in $netdevices should query a bootp server.
One answered query should be enough.
Even a single NIC computer does three(3) BOOTP-requests:
- BootROM where to get my kernel-image