I assume the significant changes were for ip6 since
other than adding a location for the dump and
statistics file, it adds these 3 zones which looks
like they are all for ip6 support. Since I am not
using ip6 and do not know anyone who is yet I assume
it is safe to leave these out.
zone
"0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.ip6.arpa"
IN {
type master;
file "named.ip6.local";
allow-update { none; };
};
zone "255.in-addr.arpa" IN {
type master;
file "named.broadcast";
allow-update { none; };
};
zone "0.in-addr.arpa" IN {
type master;
file "named.zero";
allow-update { none; };
};
--- "Bryan J. Smith" <thebs413@xxxxxxxxxxxxx> wrote:
> Has nothing to do with YUM.
> It has to do with RPM.
>
> If the changes in a package are significant enough,
> then any
> existing configuration files are renamed ".rpmsave"
> and new
> ones take their place.
>
> If the changes are not significant enough that the
> existing
> configuration files will work, the new ones are
> added with
> ".rpmnew".
>
> This is how it has been for a long, long time in the
> RHL
> world.
>
> Now I agree you should _never_ see this out of a
> RHEL/CentOS
> update. That's the whole purpose of backporting
> changes in
> RHEL/CentOS updates -- to _avoid_ this from every
> occurring.
>
> But apparently it did.
>
>
> --
> Bryan J. Smith | Sent from Yahoo Mail
> mailto:b.j.smith@xxxxxxxx | (please excuse any
> http://thebs413.blogspot.com/ | missing headers)
> _______________________________________________
> CentOS mailing list
> CentOS@xxxxxxxxxx
> http://lists.centos.org/mailman/listinfo/centos
>
__________________________________
Yahoo! Mail - PC Magazine Editors' Choice 2005
http://mail.yahoo.com
