seth vidal wrote:
On Thu, 2006-09-07 at 22:35 +0800, John Summerfield wrote:
Matt Hyclak wrote:
On Thu, Sep 07, 2006 at 10:09:08PM +0800, John Summerfield enlightened us:
Matt Hyclak wrote:
>Won't this also cause problems when upgrading to the next release?
Of course it will. :-(
Not with proper exclude= lines in your configuration it won't. After all, since you made the centos-release package yourself, you can control what goes in that file, so an exclude line should be trivial.
Eh? Doesn't Anaconda look at the release file to see what it's supposed to upgrade _from_? If it doesn't recognise it, how will it know how to upgrade?
Have we moved away from yum into respun CDs?
No, I was thinking of the upgrade many folk will want to do to CentOS 5.
If folk are creating alternative release packages I wonder whether they will create problems for themselves at that time.
While Anaconda has an argument to force it to upgrade, and it would almost certainly work upgrading CentOS4 (or even WBEL) to CentOS5, it's not the sort of thing people should use in the ordinary course of events.
pretty sure red hat doesn't support upgrades between major release versions.
I'm next to certain it does. It supported upgrades from whenever Anaconda appeard (5.x or so I think) right up to RHL 9 - even skipping releases, and upgrades to newer Fedora Core work. I don't see why upgrading RHEL 2.1 to 3 or 4 would not work.
There might be some manual work to do, replacing dropped packed (eg imapd) with newer (eg cyrus-imapd).
so I can't imagine it'll be supported in anything from 4 -> 5.
and I'll be fairly surprised if it's not:-)
One thin I have in mind is to try to upgrade RHL 7.3 to Centos 3 or 4 at some point. I fully expect to apply a little force in that case; that is what it's for (not a supported upgrade but probably will work).