[syslinux] Network Boot IP Configuration Dilemma

[Fred Feirtag]

H. Peter Anvin wrote:

>Fred Feirtag wrote:
>  
>
>>...The error report
>>will never be "someone plugged a leasing IP server into the
>>network" it will be "my workstation is hanging sometimes."
>>Reducing the numer of ways a workstation hangs on bootup
>>is a good thing for anyone having to diagnose trouble calls.
>>    
>>
>
>The thing is, if someone is running a rogue DHCP server on your network,
>you'd have people's workstations hanging anyway.
>
Yes, though since my Linux server is often faster than the MS
servers that may appear from time to time, the hanging on bootup
can be rather intermittant.  And I guess the conclusion is, I see
reducing the number of failure modes, and reducing the ways
failures will be seen and reported by users as a priority, and you
see uniformity of usage as a priority.

>Perhaps I should explain that the only reason IPAPPEND is there is to
>support a small set of users with a particularly screwed up network
>infrastructure...
>
>...Given the number and the kinds of
>support requests it has generated, I'm getting pretty convinced that it
>was a bad idea.
>
>  
>
After reading the archives of this mailing list, I recall
thinking that at least some of the previous requests had
merit, and you suggested I take this issue to this mailing list.
If anyone else has input, I'll be interested to read it, if
not, sorry for wasting people's time.  Maybe to make the
situation known, you should just add a notation in
syslinux.doc that you have resolved that IPAPPEND is
deprecated.

--Fred

-- 
Fred Feirtag
Chief Technologist
Integrity Linux Systems, a division of Integrity Networking Systems, Inc.
1001 Medical Arts Avenue, NE
Albuquerque, NM  87012
email: ffeirtag at integrityns.com
phone: (505) 294 - 7747
fax: (505) 275 - 1125