On Tue, Feb 9, 2010 at 3:19 PM, Eugene Vilensky <evilen...@gmail.com> wrote: > On Tue, Feb 9, 2010 at 12:35 PM, Chris Adams <cmad...@hiwaay.net> wrote: >> Once upon a time, Tom Sightler <tt...@tuxyturvy.com> said: >>> On Mon, 2010-02-08 at 22:47 -0600, Chris Adams wrote: >>> > Tru64 also supported in-place version upgrades, unlike RHEL, so if you >>> > were running 5.0A and really needed something in 5.1B, you didn't have >>> > to format the drive or build a new system (rolling updates in a cluster >>> > means users never even see an outage). >>> >>> I don't understand this part. You can certainly do 5.0 -> 5.1 style >>> upgrades "in-place", and you can upgrade between major versions using >>> boot media (either net boot, CD, whatever) if you wish, no requirement >>> to format the drive. >> >> According to the Red Hat docs, you can upgrade that way, but it is not a >> supported upgrade path. To me, that means they don't test it (or at >> least not much), so I can't expect it to work on a production system. >> If it breaks part of the way through, or installs a bogus package set, >> etc., I'm stuck with a busted system and no path back to a working >> system but to wipe and restore from backups. > > "yum update" from 5.3-->5.4 is not supported?
Yes it is. The above quote covers different things. What I think Chris was talking about was doing a full or partial upgrade from 3.9 to say 4.9 which would not exactly be supported. -- Stephen J Smoogen. Ah, but a man's reach should exceed his grasp. Or what's a heaven for? -- Robert Browning _______________________________________________ rhelv5-list mailing list rhelv5-list@redhat.com https://www.redhat.com/mailman/listinfo/rhelv5-list
