On Fri, 19 Nov 1999, Derek Simkowiak wrote:
> > > As it is, "Upgrade" does more-or-less an "rpm -U " and one has to hope
> > > everything goes well - which it does not, as I have painfully found out.
>
> > Completely agree here. You could add this to the list of problems: in
>
> What bugs me is needing to be physically in front of the machine
> (with boot floppy in hand) to do an upgrade.
>
> I have many Redhat systems sitting in client's offices, working as
> webservers, email, bind, etc. It's a real pain to drive out there to do
> an upgrade. Many of these machines have T1 connectivity--I should be able
> to do a full upgrade remotely.
rpm -F ~ftp/pub/mirrors/(release)/Mandrake/RPMS/*.rpm
(personaly i do mine a portion at a time)
> It would only be worse for a Beowulf cluster or web server farm.
same thing, just and a
for host in 1 2 3 4 5 6 7 8 9 ; do
(ssh -lroot $host -c "rpm -F ~blah/blah/*.rpm")
done
or something similar.
Were i to have a cluster here it would sync from a test machine
everything but machine specific config files after testing was completed
> For that reason alone, I think I am going to start using Debian.
You still gotta drive to install that, (always buged me to try and find
that many d**med floppys) We'll be look at a better interface for upgrades
than manual frubing your way thru rpm -F *.rpm soon, it does work but it's
not quite for the faint of heart. Trying it via rpm -U is even more time
consumeing... Have a try at rpm -F, and we'd love input on how you'd like
to see it improved
> --Derek
>
--
MandrakeSoft http://www.mandrakesoft.com/
--Axalon
