- Original Message -
From: Steve Philp [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Wednesday, September 29, 1999 4:50 AM
Subject: Re: [Re: [Re: [newbie] Upgradeing all packages destroys my system]]
Let's get past all of the Windows-centric thinking that we've become
accustomed
Ty Mixon wrote:
Ok - then any idea why I got the original error?
ldconfig didn't get run after installing new libs.
--
Steve Philp "The Internet is like crack
Network Administratorfor smart people..."
Advance Packaging Corporation --Arsenio Hall
Well, for the most part. You can put in a Kernel update, then
reconfigure LILO to enable you to access it without the install
procedure, but you do of course have to restart the system to use the
new Kernel.
As for the software part, I guess that I am a creature of habit. So
often in Win31 and
"Ernest N. Wilcox Jr." wrote:
This entire thread started out from a message triggered by not running
ldconfig after upgrading some libraries. To imagine that it degraded to
this level of FUD and disinformation is absolutely amazing. Let's look
at the statements made in just this reply (Sorry
I'm still too new at Linux to help with the repair job, but I can
explain why you need to do the installer. When you are running an
installed Linux system, the files you want to replace in a version
upgrade are being used by the system, and cannot be replaced. That is
why you need a boot disk, so
That mostly makes sense, but I kinda thought that one of the great things
about Linux was the 'no need to reboot on upgrades' part. Guess not system
upgrades, just end user software?
Ty
"Ernest N. Wilcox Jr." [EMAIL PROTECTED] wrote:
I'm still too new at Linux to help with the repair job, but
I'm still too new at Linux to help with the repair job, but I can
explain why you need to do the installer. When you are running an
installed Linux system, the files you want to replace in a version
upgrade are being used by the system, and cannot be replaced. That is
Can't say I've ever seen
Ok, but I don't understand why I can't just grab the rpms, and then upgrade
what I have installed, using kpackage or rpm. Which is why I didn't read the
readme or install files - didn't think I had to do an install. That's what I
get for thunking . . .
Anyhow I wrote down the error messages,
On 26 Sep 1999, Tymanthius Rune Speak wrote:
Ok, but I don't understand why I can't just grab the rpms, and then upgrade
what I have installed, using kpackage or rpm.
INIT: version 2.76 booting
sh: error in loading shared libraries: libreadline.so.4.0: cannot open shared
object file: no
