On Wed, 2 Aug 2000, J Kinsley wrote:
> However, I did not use any
> 'automagic' means to do this. I upgraded each individual package
> manually using Midnight Commander (MC). It took most of an evening
> to install the packages and retweak all the configs,
>
> On Wed, 2 Aug 2000, Ulrich Kiermayr wrote:
>
> > A Question: is it possible to do an upgrade (e.g. 6.1 -> 6.2) while the
> > system is up and running.
... ummm, Sure! and magically. Autorpm, pointed at a later
distro rpm archive will pull all the packages it can and stop
on the multiple dependencies which it cannot resolve.
These have to be manually 'walked thru'; Open two two windows
on the host to be upgraded. start a ncftp pointing int the
remote archive on one, and run
rpm -Uvh {list of several packages at once to satisfy dependencies}
in the other. Delete the ones successfully applied, and after
about three or four rounds, the rest will then install cleanly
with just autorpm. After doing it two or three times, the
precess is pretty painless.
I also find it helpful to keep yet another window open on
another box, so that I can identify which package contains
some of the library dependencies. (use: rpm -qf `which
{libraryname}`)
---------
Additionally, run lilo -v, and ldconfig -v
frequently; When upgrading rpm iteslf, run rpm --rebuilddb at
once before continuing.
Install the new kernel with -i, rather than -U, and keep the
old kernel around as a backup until you are sure it is going
to take.
Remember that SCSI hardware requires a good mkinitrd session.
.... stop and start again services as you see them upgrade, to
release the old shared libraries, and to get a jump on getting
the new config files set up.
---------
We have hosts which started life as RH 4.0 boxen, upgrade and
running 6.2 which we have never seen, never touched, in doing
remote administration. autorpm is that good.
We sell remote admin -- rpm and autorpm make it possible.
We have presented on the autprom upgrade process at the local
LUG. A minimal outline, which accompanied a show and tell at
the local LUG meeting is at:
http://stones.wcbe.org/~COLUG/notes/0002mtg/show.php3?file=RPM_UG_outline.html
Todd Fencel on this list has discussed this approach within
the last six weeks, as wekk --- check the archives.
I would add however, that having a boot floppy, and a
telephone line near the remote hosts greatly simplifies
matters when things fall apart.
--
end
==================================
.-- -... ---.. ... -.- -.--
Copyright (C) 2000 R P Herrold
[EMAIL PROTECTED] NIC: RPH5 (US)
My words are not deathless prose,
but they are mine.
Owl River Company 614 - 221 - 0695
"The World is Open to Linux (tm)"
... Open Source LINUX solutions ...
[EMAIL PROTECTED]
Columbus, OH
_______________________________________________
Redhat-devel-list mailing list
[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/redhat-devel-list
