[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Cheap hard disks (was: Re: updating glibc rpms)
- To: Omer Zak <omerz(at-nospam)actcom.co.il>
- Subject: Re: Cheap hard disks (was: Re: updating glibc rpms)
- From: Tzafrir Cohen <tzafrir(at-nospam)technion.ac.il>
- Date: Tue, 21 Aug 2001 19:36:15 +0300 (IDT)
- Cc: linux ILUG <linux-il(at-nospam)linux.org.il>
- Delivered-To: linux.org.il-linux-il@linux.org.il
- In-Reply-To: <Pine.GSU.4.30_heb2.09.0108211906440.829-100000@actcom.co.il>
- Sender: linux-il-bounce(at-nospam)cs.huji.ac.il
On Tue, 21 Aug 2001, Omer Zak wrote:
> Another approach:
> Nowadays, fat hard disks are dirt cheap.
> 1. Buy another hard disk.
> 2. Swap it into your PC
> 3. Install a modern Linux distribution on it, with the most up-to-date
> stable kernel, glibc and all the other goodies.
> 4. Normally, it is possible to connect more than one hard disk to PC.
> Connect your original hard disk and mount its partitions.
> 5. Apply (wherever relevant) your custom configuration files to
> applications, whose configuration was modified.
> 6. Copy over any of your own files, which you need from the old hard
> disk.
> 7. Reformat your old hard disk, install modern Linux on it and give it as
> a present to your nephew (or consult the footnote below).
>
> The most time consuming step would be step (5) above.It is a judgement
> call whether it's more difficult than upgrading glibc or not.
And since this consumes so much time (let alone shuting down the computer
for installing the extra disk ;-) ) I would first try to to the upgrade.
To be on the safe side, it might be good to prepare
/usr/local/lib/glibc2.1 and copy there all the libc2.1 libraries. After
the upgrade, in case some programs has problems with glibc2.2
(theoretically glibc2.2 is upward-compatible, or whatever the term is. I
figure that in practice this won't always work) you run the program with
LD_LIBRARY_PATH=/usr/local/lib/glibc2.1:$LD_LIBRARY_PATH
>
> On Tue, 21 Aug 2001, Oded Arbel wrote:
>
> > I myself updated glibcs onseveral occasions, and my conclusion is that the
> > safest route is to resolve all the depndency problems one by one, either by
> > installing new binary RPMs built against the new glibc and/or uninstalling
> > the old RPMs, re-building them from source against the new RPMs and
> > re-installing them.
> >
> > I know it seems like a really long and tedious process (and it is, trust me
> > on that :-) but its the only sure-fire way I know to do it, and I tried all
> > kinds.
Unfortunetly I'll have to try it some day :-(
--
Tzafrir Cohen
mailto:tzafrir@technion.ac.il
http://www.technion.ac.il/~tzafrir
=================================================================
To unsubscribe, send mail to linux-il-request@linux.org.il with
the word "unsubscribe" in the message body, e.g., run the command
echo unsubscribe | mail linux-il-request@linux.org.il