Mike Wright wrote:
Ed Greshko wrote:
Mike Wright wrote:
Hi Ed,
"static" is not a protocol.
It is in my ifcfg-eth0 file after a clean install....and I didn't put
it there.
And you did not. Frustrating, isn't it? It was put there by the
anaconda installer. I'm pretty certain that it is an error in the
installer; however, the good news is that all the other scripts seem to
be aware that it is a mistake and invisibly reset it to "none".
Of course the documentation could be change to cover the use of the far
more readable "static" which might be a better solution for user.
Fortunately, unless you are writing or using custom scripts that rely on
the documentation, everything since that error have error checking that
sets it back to what it should have been... everywhere, that is,
_except_ in the network-scripts.
C'est la vie.
Gotta love open source. We would not have known otherwise ;)
I'm curious where you got that information. I've searched off and on
for years and never found that documented anywhere although I have seen
it used somewhat frequently and which may actually be a source of errors
in some scripts. From:
The Official Red Hat Linux Reference Guide
Chapter 12. Network Scripts
BOOTPROTO=<protocol>, where <protocol> is one of the following:
none — No boot-time protocol should be used.
bootp — The BOOTP protocol should be used.
dhcp — The DHCP protocol should be used.
Additionally, grepping for BOOTPROTO in /etc/sysconfig/network-scripts/*
finds no test for static.
Based on that I'd have to say BOOTPROTO=none is correct.
hth,
Mike Wright
--
Bill Davidsen <davidsen@xxxxxxx>
"We have more to fear from the bungling of the incompetent than from
the machinations of the wicked." - from Slashdot
--
fedora-list mailing list
fedora-list@xxxxxxxxxx
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
