On Thu, 30 May 2002 16:01:50 -0400 "Alfredo C.Lopez" <[EMAIL PROTECTED]> wrote:
> Hi again! > > Thanks for the comments David and drjung! > > El Mi� 29 May 2002 20:21, escribiste: > > Part of the design for shared libraries includes the ability to have > > different versions exist on a machine and have the proper one be > > used. If you take a look in /usr/lib, you'll see lots of version > > numbers in the library names. So, by theory and design one should > > be able to have glibc-2.1.3 and glibc-2.2.0 coexist on a machine > > without trouble. > > Yes, I know that. > > > Note the above statements appear to be theory and design. They are > > not necessarily fact. > > > > At least twice I have installed a new version of glibc, only to > > discover that basic commands like "ls" no longer work because the > > want the _old_ version of glibc. > > Me too. > > > > > The only safe way I know of upgrading glibc is to boot from the > > installation CDs and do a system upgrade. > > That's not an option..... :( > I have 12 machines to upgrade and only one cdrom (some of them are > servers for another 30 machines that boot from the net). > I know it could be solved(I could make an upgrade from the net with > nfs or ftp). > But I couldn't get the hole system down for the upgrade. It too > complex if something fails.... and I can't measure how long it will > take to make the system behave in the same ways it does now. > Between us..... I don't trust the upgrade..... ( may be I could do it > at home). > Here, in Argentina, when we have a problem like this, we say "se > arregla con alambre", that means something like "fix it with wires and > some thinking". Thanks for the response. > > ALF ALF... do you have a spare box with the similar hardware? If so I'd recommend this. (I just upgraded 5 boxes this way ) Install Mandrake 8.2 on the spare box. Using rsync... tarballs whatever you chose pull over all your config files from the first one you want to replace. (Yes you can even pull over the password file this way... just make sure you get all of the backups and shadow.) Test the new box to satisfy your self that it operates the same. Put the new drive in as the boot drive and move the original drive into slave. (just in case you forgot something and need to move it fast.) Run the new one for long enough that you are sure it's all working. Take out the old drive.... back it up to a tape or whatever you use first.... and it becomes the new drive for box 2. When I did it this way my total down time was under 5 minutes. Long enough to power down, unscrew and remove the original drive. And insert the new drive. The box has been up for about 2 months now and nobody complained. All 8 websites are going strong. Along with all of the other things this box does. James > > > >
Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
