RE: [SLE] Shocked at SuSE 7.1 Upgrade Package
I have to agree with you. I have several servers that were either on 6.4
or 7.0. After the first two upgrades, I did a back up of all critical
services, and then proceeded with a new install. I was also several days
in getting my servers back up and running.
I would expect that SuSE would want to address this issue. In the
overall scheme of things, I think that 7.1 is an excellent package. All
my servers are performing very well. It seems to be that upgrade that
was shaky....
--
Kirk Moore
Lab Manager - IES team
Lab's 27/2525 and 27/1427
425-703-2255x14054
"Black Holes are created when God divides by zero!!!"
-----Original Message-----
From: Alexandr Malusek [mailto:Alexandr.Malusek@imv.liu.se]
Sent: Sunday, May 20, 2001 6:56 AM
To: Suse-Linux-E
Subject: Re: [SLE] Shocked at SuSE 7.1 Upgrade Package
Ed Harrison
I just got a copy of SuSE 7.1 Upgrade. The packaging is almost worthless -- not anything about upgrading.
I agree the documentation about upgrades should be _much better_. It should mention the procedure, resulting changes, possible problems, and it should be written for system administrators (professionals). I tried to upgrade 7.0 to 7.1 on my PC server (2x550 MHz, 512 MiB RAM). YaST2 was easy to use, and the upgrade proceeded quickly in the beginning. In the middle of the upgrade of approx. 1300 packages, I got a message about a Gnome package being older that the one already installed, and manual confirmation was needed in order to proceed. Many other Gnome and KDE packages had the same problem. Clicking OK soon appeared to be problematic since it took about 1-2 minutes for the rpm to process each of those packages. The whole installation would have taken days if I had done it this way. I aborted it, started again, and deselected all Gnome and KDE packages in YaST2 (it was laborious). YaST2 continued the upgrade but having encountered the same problem with a package I had forgotten to deselect I finally stopped the upgrade and made a new installation of 7.1. The new installation was fast so I could restore critical services soon, but the restoration of all services took me several days. -- Alexandr.Malusek@imv.liu.se -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/support/faq and the archives at http://lists.suse.com
I must say I find this a bit odd. I don't know about 6.4 -> 7.1, but I upgraded from 7.0 and it was the first upgrade I've ever performed with linux that went without a hitch. May I ask which services you were running that failed after the upgrade? Anders On Sunday 20 May 2001 16:40, Kirk Moore (Volt) wrote:
I have to agree with you. I have several servers that were either on 6.4 or 7.0. After the first two upgrades, I did a back up of all critical services, and then proceeded with a new install. I was also several days in getting my servers back up and running.
I would expect that SuSE would want to address this issue. In the overall scheme of things, I think that 7.1 is an excellent package. All my servers are performing very well. It seems to be that upgrade that was shaky....
* Anders Johansson
I must say I find this a bit odd. I don't know about 6.4 -> 7.1, but I upgraded from 7.0 and it was the first upgrade I've ever performed with linux that went without a hitch. May I ask which services you were running that failed after the upgrade?
Hmm, I guess they had already installed the latest KDE packages .. I've upped 7 boxes (running 6.4 or 7.0) to 7.1 whitout a hitch. Colleague of mine had hoime boxes with 6.2 and 6.4 and also upgraded whitout problems. However, what can (and always will) be a problem is if you've installed packages (like the latest KDE stuff) that's newer than what's on the CDs. I would like to see a ``keep all newer'' option in the upgrade procedure ;) As for documentation, since you've bought an upgrade, you should have the ``The Book'' from the previous version,w hich gives pretty good update info. What would be nice is a mini - update guide (pretty much like the getting started guide) which simply lists you through the basic steps, and poijts out where you can get detailed info in ``the book''. Kind regards, -- Gerhard den Hollander Phone +31-10.280.1515 Global Technical Support Fax +31-10.280.1511 Jason Geosystems BV (When calling please note: we are in GMT+1) gdenhollander@jasongeo.com POBox 1573 visit us at http://www.jasongeo.com 3000 BN Rotterdam JASON.......#1 in Reservoir Characterization The Netherlands This e-mail and any attachment is/are intended solely for the named addressee(s) and may contain information that is confidential and privileged. If you are not the intended recipient, we request that you do not disseminate, forward, distribute or copy this e-mail message. If you have received this e-mail message in error, please notify us immediately by telephone and destroy the original message.
** Reply to message from Gerhard den Hollander
As for documentation, since you've bought an upgrade, you should have the ``The Book'' from the previous version,w hich gives pretty good update info.
The 7.1 update book has zilch. The 7.0 update book says to use Yast2-->Update System (yeah right--I was born last night). 6.4 documentation is sketchy, Yast2 was an infant then. Ed Harrison broadcasting on ----/ / _ ---/ / (_)__ __ ____ __ --/ /__/ / _ \/ // /\ \/ / -/____/_/_//_/\_,_/ /_/\_\ by SuSE(6.4), Kernel 2.4.4, X 4.0.3 or Warp 4, FP12 or Windows98 (running in vmware 2.0.4 for fun) PolarBarMailer 1.1.19a with SUN JDK 1.3
** Reply to message from Anders Johansson
I must say I find this a bit odd. I don't know about 6.4 -> 7.1, but I upgraded from 7.0 and it was the first upgrade I've ever performed with linux that went without a hitch. May I ask which services you were running that failed after the upgrade?
Ooooooh! I have not updated yet. I know better from the comments on this list over the past several months. What I was asking for was danger signs, hints, precautions, etc. As you can see from the new comments on the list, I may just do a new install. Many of my packages, including X and KDE 2.1.2 were compiled from source with glibc 2.1.3, and 7.1 has glibc2.2 which means, I think, re-configure time for a lot of stuff. Ed Harrison broadcasting on ----/ / _ ---/ / (_)__ __ ____ __ --/ /__/ / _ \/ // /\ \/ / -/____/_/_//_/\_,_/ /_/\_\ by SuSE(6.4), Kernel 2.4.4, X 4.0.3 or Warp 4, FP12 or Windows98 (running in vmware 2.0.4 for fun) PolarBarMailer 1.1.19a with SUN JDK 1.3
Hi, You wrote
** Reply to message from Anders Johansson
on Sun, 20 May 2001 17:02:32 +0200 I must say I find this a bit odd. I don't know about 6.4 -> 7.1, but I upgraded from 7.0 and it was the first upgrade I've ever performed with linux that went without a hitch. May I ask which services you were running that failed after the upgrade?
Ooooooh! I have not updated yet. I know better from the comments on this list over the past several months. What I was asking for was danger signs, hints, precautions, etc.
As you can see from the new comments on the list, I may just do a new install. Many of my packages, including X and KDE 2.1.2 were compiled from source with glibc 2.1.3, and 7.1 has glibc2.2 which means, I think, re-configure time for a lot of stuff.
You really SHOULD do a clean install. Although SuSE 6.4 is a great distro ( I still have one 6.4 machine running ) the differences between it and 7.1 are, to say the least, eons apart. Even tho you may have installed XF4, kernel 2.2 or 2.4 and probably other stuff as well, it doesn't guarantee you any closeness to an upgradeable system. My experience is that if you have gone any length into configuring or personalising your system, the upgrade PROBABLY doesn't work. - time is money. Also, I upgraded a 6.4 system to 7.0 and a lot of things broke. Also the install times were way out of the chart. The usual install ( yast1, manually select exactly what goes in and what doesn't ) takes me about 3 hours. That's including rudimentary security checks, making cloneconfig/bzImage ( needed for NVidia drivers on smp ) and patching XFree/KDE. The upgrade itself took almost 10 hours, and that left me with a system needing my attention off and on for a couple of weeks. - I only do clean installs. Having learnt from experience, I spend one hour seeking stray data on the machine being upgraded, back it up, wipe the box clean and start from scratch with a checklist of what _SHOULD_ be installed ( most think that the more the merrier :-) Have a nice install :-) -tosi ** Par-dun mye speeling, oy aeint fwum anh eenklish speekink coontry ;->
Ed Harrison broadcasting on ----/ / _ ---/ / (_)__ __ ____ __ --/ /__/ / _ \/ // /\ \/ / -/____/_/_//_/\_,_/ /_/\_\ by SuSE(6.4), Kernel 2.4.4, X 4.0.3 or Warp 4, FP12 or Windows98 (running in vmware 2.0.4 for fun) PolarBarMailer 1.1.19a with SUN JDK 1.3
ROFL ** Par-dun mye speeling, oy aeint fwum anh eenklish speekink coontry ;-> On Monday 21 May 2001 07:10 pm, Tor Sigurdsson wrote:
Hi,
You wrote
** Reply to message from Anders Johansson
on Sun, 20 May 2001 17:02:32 +0200 I must say I find this a bit odd. I don't know about 6.4 -> 7.1, but I upgraded from 7.0 and it was the first upgrade I've ever performed with linux that went without a hitch. May I ask which services you were running that failed after the upgrade?
Ooooooh! I have not updated yet. I know better from the comments on this list over the past several months. What I was asking for was danger signs, hints, precautions, etc.
As you can see from the new comments on the list, I may just do a new install. Many of my packages, including X and KDE 2.1.2 were compiled from source with glibc 2.1.3, and 7.1 has glibc2.2 which means, I think, re-configure time for a lot of stuff.
You really SHOULD do a clean install.
Although SuSE 6.4 is a great distro ( I still have one 6.4 machine running ) the differences between it and 7.1 are, to say the least, eons apart.
Even tho you may have installed XF4, kernel 2.2 or 2.4 and probably other stuff as well, it doesn't guarantee you any closeness to an upgradeable system. My experience is that if you have gone any length into configuring or personalising your system, the upgrade PROBABLY doesn't work.
- time is money.
Also, I upgraded a 6.4 system to 7.0 and a lot of things broke. Also the install times were way out of the chart. The usual install ( yast1, manually select exactly what goes in and what doesn't ) takes me about 3 hours. That's including rudimentary security checks, making cloneconfig/bzImage ( needed for NVidia drivers on smp ) and patching XFree/KDE. The upgrade itself took almost 10 hours, and that left me with a system needing my attention off and on for a couple of weeks.
- I only do clean installs.
Having learnt from experience, I spend one hour seeking stray data on the machine being upgraded, back it up, wipe the box clean and start from scratch with a checklist of what _SHOULD_ be installed ( most think that the more the merrier :-)
Have a nice install :-)
-tosi
** Par-dun mye speeling, oy aeint fwum anh eenklish speekink coontry ;->
Ed Harrison broadcasting on ----/ / _ ---/ / (_)__ __ ____ __ --/ /__/ / _ \/ // /\ \/ / -/____/_/_//_/\_,_/ /_/\_\ by SuSE(6.4), Kernel 2.4.4, X 4.0.3 or Warp 4, FP12 or Windows98 (running in vmware 2.0.4 for fun) PolarBarMailer 1.1.19a with SUN JDK 1.3
participants (6)
-
Anders Johansson
-
Curtis Rey
-
Ed Harrison
-
Gerhard den Hollander
-
Kirk Moore (Volt)
-
Tor Sigurdsson