From Bugzilla Helper: User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; .NET CLR 1.1.4322) Description of problem: When an interface is configured with ifup, the virtual interfaces attached to it (ethx:n) are also loaded despite they have ONBOOT=no configured. This is caused by ifup-aliase NOT looking for the ONBOOT parameter. It can be corrected by adding: if [ "${ONBOOT}" = "no" -o "${ONBOOT}" = "NO" ]; then exit 0 fi on the new_interface() function. Version-Release number of selected component (if applicable): initscripts-7.93.13 How reproducible: Always Steps to Reproduce: 1.ifup eth0 2. 3. Actual Results: eth0 and eth0:1 are up Expected Results: Only eth0 should be up (eth0:1 should also be up IF is says ONBOOT=yes, otherwise ifup eth0:1 should specified to bring up the interface) Additional info:
*** This bug has been marked as a duplicate of 155497 ***