On Monday 09 September 2002 23:11, Randy Kramer wrote: > On Monday 09 September 2002 04:03 pm, Teemu Torma wrote: > > That works, since I did upgrade just last weekend one machine from > > 8.2 to cooker (or about 9.0 RC2). Never tried upgrade from 8.1 > > remotely though. > > Is it appropriate to throw the standard warning in here somewhere -- > "never upgrade, install the new version" (or am I mixed up?)
I honestly don't know. My laptop that I am using right now, was initially 8.1, then updated to cooker before 8.2 and followed it until the release, and now to cooker again around 9.0 Beta 4--just using urpmi. Of course, if you do it this way, there will always be some problem somewhere, simply because the simple package upgrade did not do the same thing than installing a clean release would do. But on the other hand, I don't want to spent long time to figure out all custom things I've done or extra packages I have installed, or redo configuration of all the services. I probably would not dare to do an upgrade from the CD though. In that case, I would have no idea what goes wrong if something happens. With urpmi and local (rsync'ed) source, I have a lot of control to fix dependencies or force the installation. Things could go wrong still, though, but I have never had a backup plan other than "I'll deal with it if it happens". A set of CD's for full installation is a wise thing to have, but I am not wise. Come to think of it, a backup would be wise too... (BTW, I did pretty much the same thing on a RedHat machine once, from 5.0 to ~7.0 in multiple stages, something like 5.0 -> 5.2 -> 6.? -> 7.0, before finally installing Mandrake. And there was no urpmi, but I did it by recompiling some critical packages from new src.rpm's, like glibc, rpm, gcc, and finally doing rpm -Fvh for the rest with manual dependency resolution). Teemu
Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
