On Nov 15, 2007 1:44 PM, Les Mikesell <lesmikesell@xxxxxxxxx> wrote: > Arthur Pemberton wrote: > > >>> > >>>> What's the point, though, unless you're in a setup where 90%+ of the > >>>> computers change every year[1]? > >>> Because client creation is much easier if you just tell it to DHCP > >>> rather than spending time to punch in technobabble numbers each time. > >> Huh? You get the mac address how? Looks to me like you're trading > >> the need to type a simple IP address with a much larger complexity on > >> the server side, whatever you do. > > > > ifconfig gives mac addresses last i checked. One just makes a note of > > the mac addresses of their serves, attach the same ip to the mac > > address everytime, and then everything can be run on dynamic IPs. > > That's not a horrible idea, but not really simpler than assigning the IP > directly - and it gets a little weird when you start copying vmware > images around in ways that make them want to make up new mac addresses. Fair enough. Although for non vm situations, i think it's easier. > There's also a problem where you have multiple nics and need to assign > some non-default static routes to one or more. I don't think there is a > way to do that with dhcp. Just to be clear, I was just providing a suggestion to _one_ of the problems. Last time I checked, I hated NetworkManager, not sure how good/bad it is in F8 -- Fedora 7 : sipping some of that moonshine ( www.pembo13.com ) -- fedora-devel-list mailing list fedora-devel-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-devel-list
