From: <er...@he...> - 2004-08-17 22:57:51
|
On Tue, Aug 17, 2004 at 11:01:38AM -0600, Michal Jaegermann wrote: > > One option would be to leave interface configuration out of beoboot > > and let people do that using whatever distribution provided mechanism > > they have. There might be fewer collisions that way too. > > OTOH this will force everybody to hack their startup files and > for many this may be a PITA. I think that this is a bit too > radical. How about optional? If the addresses are there, do something, else ignore the interface and presume some other part of the OS setup has configured it. I think it's reasonable to phase it out. > > The rc.clustermatic script is the only piece that looks at the > > addresses on the interface lines. bpmaster and beoserv look at those > > lines to get interface names, not addresses. The daemons all get > > addresses directly from the interface (as they should). > > That is true but probably not a good enough reason to configure > interfaces to some random values. :-) Yeah, random values are bad. This is an argument to remove (or phase out) the interface configuration from beoboot altogether. It doesn't make much sense to me to have multiple mechanisms for sticking an address on a network interface in one system. - Erik |