Before I emerged the latest baselayout, I had a network config line in /etc/conf.d/net that looked like: iface_eth0="hostname broadcast 192.168.1.255 netmask 255.255.255.0" (I know, according to /etc/conf.d/net.example that I should probably be using config_eth0 instead now). Hostname is a valid host in /etc/hosts. After upgrading baselayout the system no longer configures eth0: instead hostname gets treated as a module name. The offending line in net.eth0 seems to be: (around line 545 in net.eth0) elif [[ ${conf[0]:0:1} == [[:digit:]] || ${conf[0]} == *:* ]]; then Since I was using a symbolic hostname instead of a numeric one it isn't passing the test. Changing /etc/init.d/net to the actual ip address fixes the problem. I'm posting this as a bug because systems that used to boot no longer work. I try and avoid entering an IP address multiple times, so I prefer to enter it once in /etc/hosts and use the name everwhere else; it seems that conf.d/net is sufficiently overloaded in its syntax to make it hard to have this anymore. Reproducible: Always Steps to Reproduce: 1. 2. 3.
Huh? Hostname belongs to /etc/conf.d/hostname
Its not setting "hostname", its setting the ip address of an interface using a name instead of a numeric address.
Interesting - I didn't know that using hostnames worked - heh. And we supply no documentation even hinting that we support this. Older versions of baselayout would doing things different if the hostname was dhcp or adsl - it would start dhcp/adsl instead of picking the ip address. I also think that stopping this behaviour with baselayout-1.11.x is good as it would not be consistent and I can forsee other issues with what you want. So I'm not going to fix this.