Re: RH tools and conf changes (was: Re: Vi backspace key problem)

[Dag Wieers <dag wieers com>]

On Thu, 21 Jul 2005, Ed Wilts wrote:

> On Thu, Jul 21, 2005 at 07:29:30PM +0200, Dag Wieers wrote:
> > On Thu, 21 Jul 2005, Ed Wilts wrote:
> > 
> > I thought you had to do upgradeany from RHEL3 to RHEL4 too. It was like 
> > that from RHEL2.1 -> RHEL3 iirc.
> 
> Nope - they're quite a bit different.  Arjan made it clear that
> upgradeany will break from RHEL3 to RHEL4.  I trust his opinion on this
> :-). https://www.redhat.com/archives/nahant-list/2005-February/msg00109.html
> 
> "The up2date based "method" (undocumented backdoor hack is a better
> description) just plain doesn't work and is guaranteed to hose your
> system."

upgradeany is anaconda, not up2date. So again, how does the upgradeany 
option to anaconda be different than a plain anaconda update. I think both 
are the same (if EL3 -> EL4 is supported by anaconda).


> > In any case I was only talking about the upgradeany kind of upgrade (using 
> > anaconda). Since upgradeany is just ignoring the distribution-check I'm 
> > not sure why you see it as 2 different things if upgrades are supported
> > (ie. in that case the distribution check does not fail) I'd think both 
> > were essentially the same.
> > 
> > Unless I'm wrong :)
> 
> The difference is that some of the devices are changing out from under
> you in an up2date upgrade.  It's much easier if everything is offline
> like it is with anaconda.
>
> That's why the anaconda-based upgrade is documented and upgradeany
> isn't.  See https://www.redhat.com/f/pdf/rhel4/UpgradeGuidelines.pdf

Again, upgradeany IS an anaconda option NOT up2date related.

Kind regards,
--   dag wieers,  dag wieers com,  http://dag.wieers.com/   --
[all I want is a warm bed and a kind word and unlimited power]