"Fixing" bug 883999 did not affect this problem. Each update of netcfg still wants to obliterate the HOSTNAME timestamp that in an upgrade installation should be a hallmark of the original installation. It still eliminates a hardlink that preserves the timestamp, replacing it with a currently timestamped symlink. There could be an rpmnew, if the new netcfg package must leave evidence of its installation. An rpmsave is backwards. If both hostname and HOSTNAME exist as either hard or soft link, there is nothing netcfg installation needs to do. An immutable flag on hostname shouldn't prevent netcfg from installing.