Board index Linux

FTP upgrade, RH4 -> RH5

FTP upgrade, RH4 -> RH5

Post by Carlos Lange » Sun, 28 Dec 1997 04:00:00



I happily (sigh) decided to upgrade my RH. Overall the worst
part (up to now) is that when I installed RH4.0, I followed the
suggestions in the manual and used a "/" partition with ONLY 30M.
To my surprise, during the FTP upgrade I ran out of space in "/".
Looking at the new manual I see that the suggested size increased...

Removing mail files from /var/spool/mail (and some other things), I
managed to get just enough space to finish the upgrade.

Current situation is that a lot of packages didn't install because
space in "/" is not enough. Also, I cannot receive email in the linux
box :(.

Looking at sizes, I have
Filesystem         1024-blocks  Used Available Capacity Mounted on
/dev/hda5              31199   31010        0    100%   /

Quote:> du -sk /var/lib/rpm

9347    /var/lib/rpm
Quote:>du -sk /lib

11793   /lib

So these are the bad guys.   I can see that I can resize "/", but that
means I have to reformat the hard drive (??), which I'd rather avoid.
Does anybody have other suggestions? If I create a link from
/var/lib/rpm to /usr/rpm (lots of space) will it work?

Thanks in advance,
Carlos

 
 
 
Top

1. RH4 --> RH5 Upgrade, (g)libc: What are the issues?

Hello, net.

I'm considering upgrading our RedHat 4 systems to RedHat 5.0.  I've been
trying to understand the problems that I can expect to develop after I
stick the CD in the drive, choose the upgrade option, and install all
the errata.

The main complaint seems to be some approximation of "Since RH5 is
glibc-based, your old (/usr/local/bin) programs, compiled against libc5
will no longer work.  Or something."

I have tried to locate a comprehensible account of why this might be,
but I have failed.  It seems to me that there should be no problem with
making glibc AKA libc6 be the default libc, so long as a copy of libc5
is still available.  This is precisely what the sonaming scheme is
supposed to ensure - that old binaries, linked against libc5 will still
seek out libc5 and ignore the incompatible libc6.

So, I'm missing something here.  What is it?

(a) Will the upgrade delete libc5 altogether?

(b) Will the upgrade somehow mess up the libc5 installation?

(c) Other?

And, is there a simple fix that does not involve recompiling every bit
of third-party software? We have rather rather a lot, unfortunately,
and some of it is pretty critical (ssh, amanda, ...).

Many thanks in advance,

Carlo Graziani
c-grazianiATuchicagoDOTedu (Sorry about that)

2. How to make "$<" text not echo?

3. upgrading RH4.2->RH5.1, utmp/wtmp problem

4. Reading is much more interesting than TV (0965/1708)

5. PROGRESS REPORT: Re: Minor probs. after upgrade RH4.1 -> RH4.2

6. Audio CD / Beginners question

7. Minor probs. after upgrade RH4.1 -> RH4.2

8. Adding additional hardware.

9. Upgrade RH5.1 >> RH5.2

10. RH5.0 -> RH5.1 upgrade doesn't help me...

11. Problem: Upgraded from RH4.1 to RH5.0

12. howto rh5 -> rh5.1 by ftp?

13. RH4.2-->RH5.1 and compile warnings


All times are UTC
Board index