John Allen wrote:
It is dhclient. You will need to do a man dhclient.conf and create a suitable dhclient.conf file.
Again I will say that this is ridiculous, can we not just go back to dhcpcd as the default DHCP client.
I'd like to second this.
I run linux at work and home and have a laptop I use at both locations, with NFS mounts from the servers at both locations. Consequently, I have been using DHCP to provide the laptop (and other machines) with the nisdomain information (as NFS really needs NIS, until I get round to figuring out LDAP). This stopped working when I stuck 9.1 RC1 on one of the home machines. I believe this is because of the switch to dhclient. Could be wrong, but that was how it looked to me. Or does dhclient support receiving the nisdomain?
And while I'm on the subject of using DHCP to pass the nisdomain, 9.0 seemed to be broken, if you used MCC to change any network settings. It seemed to add a DOMAINNAME=localhost line to the sysconfig scripts (network and ifcfg-eth*) if they did not already have a DOMAINNAME line. This then seemed to prevent the machine from receiving its nisdomain by DHCP, presumably because it assumed it already knew the domain. Deleting the offending lines gets it working again, but it seemed to me that they shouldn't be added in the first place, unless specifically instructed. I haven't got 9.1 working well enough to check if this is still happening, but thought I would mention it in case it needs fixing before final release (which is being rushed through much too quickly again).
Cheers,
Bruno Prior
