sting sting said:
> Hello ,
> Thnxs everybody !
> Well , I had tried to follow Chris Purcel FAQ (in Tek Tips) , as he
> advised in his post;
> I did start linux rescue from RH CD #1 , I did say "yes" to mount the
> filesystem, (and
> ***NOT*** chose the "re
Hello ,
Thnxs everybody !
Well , I had tried to follow Chris Purcel FAQ (in Tek Tips) , as he advised
in his post;
I did start linux rescue from RH CD #1 , I did say "yes" to mount the
filesystem, (and
***NOT*** chose the "read only' option).
and erased glibc rpms ; but whe
Chris Purcell wrote
> I had this same problem a few weeks ago. I was able to fix it and wrote
> an FAQ on it at tek-tips.com.
>
> http://www.tek-tips.com/gfaqs.cfm/lev2/3/lev3/20/pid/54/fid/4094
It's worth noting that the reason you had this problem is that you "upgrade
apt-get to do the upgrade, 1 using just rpm -Uvh as per the poster).
I had to mount the drive in another machine and use rpm --root to remove the
multiple copies of glibc that ended up installed and then install the correct
one.
--
Capital punishment turns the state into a murderer. But imprisonm
> Hello ,
> Help !
> I have severe problem (cannot boot) after upgrading glibc and
> glibc-common on RedHat 9 ;
> I had glibc-2.3.2-11.9.i686.rpm
> I wanted to update to glibc-2.3.2-27.9.i386.rpm.
> rpm -Uvh glibc-2.3.2-27.9.i386.rpm said it needs updated glibc-commo
Hello ,
Help !
I have severe problem (cannot boot) after upgrading glibc and glibc-common
on RedHat 9 ;
I had glibc-2.3.2-11.9.i686.rpm
I wanted to update to glibc-2.3.2-27.9.i386.rpm.
rpm -Uvh glibc-2.3.2-27.9.i386.rpm said it needs updated glibc-common.
I had glibc-common-2.3.2-11.9.i386.rpm
damovand wrote:
Hi,
I think mod_auth_mysql is probably for authenticating a remote user of MySQL.
If I'm correct then I can comment out that statement. But my concern is the
incompatibility that exists. Why is it so? Am I going to have problems with
other modules and features? For exampl
On Wednesday 01 October 2003 02:32 pm, NfoCipher wrote:
> On Wed, 2003-10-01 at 12:43, damovand wrote:
> > Hello all,
> > am running RH9.0. Upgraded from RH 7.2 using the official Redhat CD
> > release in graphical mode.
> > I am not able to start httpd, I thought I needed to upgrade and I did bu
On Wed, 2003-10-01 at 12:43, damovand wrote:
> Hello all,
> am running RH9.0. Upgraded from RH 7.2 using the official Redhat CD release
> in graphical mode.
> I am not able to start httpd, I thought I needed to upgrade and I did but it
> still does not start.
>
> When I do:
reference
---
The following are installed, am I having a problem because of multiple
version? Could anyone please suggest any advice? What is GLIBC_2.0 and do I
need to set its values?
--
glibc-2.3.2-5
John Hinton wrote:
I'm finding a bit more, but still am at a loss. It seems that ld is
either also upgraded during my mess session. (this has been a few
weeks ago and I forgot exactly what all I did) This was when I
upgraded to glibc 2.3 i386 instead of glibc 2.3 i686 and have since
gone
I'm finding a bit more, but still am at a loss. It seems that ld is
either also upgraded during my mess session. (this has been a few weeks
ago and I forgot exactly what all I did) This was when I upgraded to
glibc 2.3 i386 instead of glibc 2.3 i686 and have since gone back to
glibc 2.2
OK, I'm one of the dummies that installed the wrong glibc 2.3, i386
instead of i686 on my RH7.2. After much ado, I got 2.2 back on and the
totally broken system running again. I still have at least these two issues.
1) Perl has a locale setting problem. Ideas to fix this?
Starting httpd:
The glibc getgrouplist buffer overflow described in RHSA-2003:249-11
(https://rhn.redhat.com/errata/RHSA-2003-249.html) also occurs on RH 7.3
(glibc-2.2.5-43). When should we expect a fix for RH 7.3?
=
Sincerely,
Matt Seitz
--
redhat-list mailing list
unsubscribe mailto:[EMAIL PROTECTED
I temporarily downgraded glibc rpm's to install oracle
on RedHat 9 using
this command:
rpm -Uvh --force glibc-2.3.2-5.i686.rpm
glibc-common-2.3.2-5.i386.rpm
glibc-devel-2.3.2-5.i386.rpm
which completed without error; and later, I
re-upgraded the packages
with this command:
rpm -Uvh glibc-
On Wed, 2003-08-20 at 22:25, Nick White wrote:
> nope, it just shows one glibc-2.3.2-11.9 package installed.
>
>
cool! I will definitely remember this thread.
Bret
--
redhat-list mailing list
unsubscribe mailto:[EMAIL PROTECTED]
https://www.redhat.com/mailman/listinfo/redhat-list
nope, it just shows one glibc-2.3.2-11.9 package installed.
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On
Behalf Of Bret Hughes
Sent: Wednesday, August 20, 2003 7:26 PM
To: [EMAIL PROTECTED]
Subject: RE: destroyed glibc!
On Wed, 2003-08-20 at 19:01, Nick White
On Wed, 2003-08-20 at 19:01, Nick White wrote:
> Thanks! I reinstalled the glibc packages from the RH9 CD, and all is
> well!
>
> If anyone else ever runs across this problem, I reinstalled glibc using:
>
> rpm -ivv --force --root /mnt/sysimage
> /mnt/source/RedHat/RPMS/
Thanks! I reinstalled the glibc packages from the RH9 CD, and all is
well!
If anyone else ever runs across this problem, I reinstalled glibc using:
rpm -ivv --force --root /mnt/sysimage
/mnt/source/RedHat/RPMS/glibc-2.3.2-11.9.i686.rpm
rpm -ivv --force --root /mnt/sysimage
/mnt/source/RedHat
On Wed, Aug 20, 2003 at 03:21:33PM -0700, Nick White wrote:
> A user, (who will no longer get root privileges) has totally messed up
> glibc, and the system no longer boots. All that he mentioned was
> something about libcommon and libc (glibc?). I can boot RedHat 9 into
> rescue m
On Wed, Aug 20, 2003 at 03:21:33PM -0700, Nick White wrote:
> A user, (who will no longer get root privileges) has totally messed up
> glibc, and the system no longer boots. All that he mentioned was
> something about libcommon and libc (glibc?). I can boot RedHat 9 into
> rescue m
A user, (who will no longer get root privileges) has totally messed up
glibc, and the system no longer boots. All that he mentioned was
something about libcommon and libc (glibc?). I can boot RedHat 9 into
rescue mode from the CD-ROM. Since the hard drive is mounted to
/mnt/sysimage, installing
On Sat, 26 Jul 2003 02:18:48 +0200
Michael Schwendt <[EMAIL PROTECTED]> wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On Fri, 25 Jul 2003 18:42:01 -0400, Tom Pollerman wrote:
>
> > > No, mc fails if rpm is broken. See /usr/share/mc/extfs/rpm
> > >
> > I apologize, if that is in
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Fri, 25 Jul 2003 18:42:01 -0400, Tom Pollerman wrote:
> > No, mc fails if rpm is broken. See /usr/share/mc/extfs/rpm
> >
> I apologize, if that is indeed the fact.
> My version of Midnight Commander (mc-4.5.51) makes no mention of
> needing a
On Fri, 25 Jul 2003 23:31:50 +0200
Michael Schwendt <[EMAIL PROTECTED]> wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On Fri, 25 Jul 2003 15:37:35 -0400, Tom Pollerman wrote:
>
> > Might Midnight Commander:
> >
> > /usr/bin/mc
> >
> > be able to do the install? I see where mc
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Fri, 25 Jul 2003 23:14:09 +0200, Olivier Dony wrote:
> Now I have gathered all the relevant rpms I would use to restore the
> system to the old state, ie :
>
> binutils-2.11.90.0.8-12.i386.rpm
> glibc-2.2.4-32.i386.rpm
> gli
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Fri, 25 Jul 2003 15:37:35 -0400, Tom Pollerman wrote:
> Might Midnight Commander:
>
> /usr/bin/mc
>
> be able to do the install? I see where mc displays the files inside a
> .rpm (including CONTENTS.cpio), and also gives an "install" and an
> "
> Really, rpm2cpio gives you access to a cpio archive inside the rpm.
> > Try something like
> >
> > mkdir test ; cd test
> > rpm2cpio glibc-2.3.2-27.9.i686.rpm | cpio -id
> > --no-absolute-filenames
> >
> > to extract the files inside. You could
package. Can you explain this a bit, I am very
> > new to redhat. (this is on RH7.2- Enigma)
>
> "man cpio" *grin* cpio is not specific to Red Hat Linux. ;)
>
> Really, rpm2cpio gives you access to a cpio archive inside the rpm.
> Try something like
>
> mkdi
. ;)
Really, rpm2cpio gives you access to a cpio archive inside the rpm.
Try something like
mkdir test ; cd test
rpm2cpio glibc-2.3.2-27.9.i686.rpm | cpio -id --no-absolute-filenames
to extract the files inside. You could also extract them within your
top-level directory and overwrite what&#x
>
> Ah yes but I have no idea as to how I can use rpm2cpio to bypass
> rpm and install a package. Can you explain this a bit, I am very
> new to redhat. (this is on RH7.2- Enigma)
>
I've never used cpio either. I just know it exists.
> Ah that sounds like a great idea too, how can I easily see w
On Friday, 25 July, 2003 17:57, Jonathan Bartlett wrote:
> I think you're stuck with rpm2cpio. Alternatively, you could build RPM
> statically on your machine, but my guess is that rpm2cpio would be easier.
Ah yes but I have no idea as to how I can use rpm2cpio to bypass
rpm and install a package
rote:
> > > On Friday, 25 July, 2003 16:50 Michael Schwendt wrote:
> > > > > In my case this is a remote server on which I have only
> > > > > ssh access, and thus no option of using a CD. I think
>
> >
no option of using a CD. I think
> > > > I need a solution to replace this broken glibc with the
> > > > original one coming with RedHat 7.2, but using only basic
> > > > things I can download.
[snip]
[moved from top-post
> > ssh access, and thus no option of using a CD. I think
> > > I need a solution to replace this broken glibc with the
> > > original one coming with RedHat 7.2, but using only basic
> > > things I can download.
> > >
> > > I guess what I'
On Friday, 25 July, 2003 16:50 Michael Schwendt wrote:
> > In my case this is a remote server on which I have only
> > ssh access, and thus no option of using a CD. I think
> > I need a solution to replace this broken glibc with the
> > original one coming with RedHat 7
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Fri, 25 Jul 2003 00:26:40 +0200, Olivier Dony wrote:
> In my case this is a remote server on which I have only
> ssh access, and thus no option of using a CD. I think
> I need a solution to replace this broken glibc with the
> origina
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Thu, 24 Jul 2003 02:11:19 +0200, Olivier Dony wrote:
> I am working on a Redhat 7.2 system with "kernel 2.4.19 #2 SMP". I think I
> broke everything by installing a new version of glibc using the --nodeps
> option of rpm. I s
since almost everything
seems to be still running fine, except mainly the rpm system :)
> (snip)
> Well, I guess you could check out
>
> http://www.redhat.com/swr/i686/glibc-2.3.2-27.9.i686_fl.html
>
> which at least lists all the files that rpm would install for you. Maybe y
> On Thursday, 24 July, 2003 22:45, David Demner wrote:
> > A number of people (including me) had this problem.
> >
> > --- Original reponse thanks to Michael Fratoni ---
> > Did you perhaps 'upgrade' to glibc*.i386.rpm on an i686 system?
> > If so, hav
Aeryn wrote:
Now, I would like to upgrade to the glibc 2.3 version. I have been told to
use the:
glibc-2.3.2-27.9.i686.rpm
glibc-common-2.3.2-27.9.i386.rpm
glibc-debug-2.3.2-27.9.i386.rpm
glibc-devel-2.3.2-27.9.i386.rpm
glibc-profile-2.3.2-27.9.i386.rpm
glibc-utils-2.3.2-27.9.i386.rpm
That set
On Thursday, 24 July, 2003 22:45, David Demner wrote:
> A number of people (including me) had this problem.
>
> --- Original reponse thanks to Michael Fratoni ---
> Did you perhaps 'upgrade' to glibc*.i386.rpm on an i686 system?
> If so, have a look here fo
Ug, now I am really confused...more like wary of upgrading glibc. Here is
what my systems has on it.
kernel2.4.18i686
glibc2.2.5i686
rpm4.0.4i386
glibc-devel2.2.5i386
glibc-common2.2.5i386
Now, I would like to upgrade to the glibc 2.3 version. I have been told to
use the:
glibc-2.3.2-27.9
A number of people (including me) had this problem.
--- Original reponse thanks to Michael Fratoni ---
Did you perhaps 'upgrade' to glibc*.i386.rpm on an i686 system?
If so, have a look here for possible fixes:
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=88456
--- Thanks again
Hello,
I badly need any help anyone can provide...
I installed the glibc-2.3.2-57 related rpm's on my redhat 7.2 system, and now
many things are broken, including the rpm system itself (segfault everytime I
try a rpm -Uvh/ivh). Most other programs using glibc are broken too, and I
need t
>am going to update on my linux server the Glibc from 2.2 to 2.3. Does
>>anybody know of any issues I may face with this upgrade? I am using the
>>Glibc 2.3 rpm to do the upgrade.
>
> Well, I killed my system by accidentally upgrading with the "i386" glibc
> instea
Well, I too updated my GLIBC tonight to version 2.3.2-57 and, after
recompiling my patched Qmail server, I find that now I cant install any
RPM's. I get a seg fault. I noticed several people have posted similar
posts as well. Can someone confirm that the latest rpm for GLIBC works?
And, if so
>Hello, I know this is an easy question, not much of a challenge, but...I
>am going to update on my linux server the Glibc from 2.2 to 2.3. Does
>anybody know of any issues I may face with this upgrade? I am using the
>Glibc 2.3 rpm to do the upgrade.
Well, I killed my system by
Hello everyone
(I tried to post some time before but I was not subscribed to the list so I'm
not sure it worked).
I am working on a Redhat 7.2 system with "kernel 2.4.19 #2 SMP". I think I
broke everything by installing a new version of glibc using the --nodeps
option of r
Aeryn wrote:
Hello, I know this is an easy question, not much of a challenge, but...I am
going to update on my linux server the Glibc from 2.2 to 2.3. Does anybody
know of any issues I may face with this upgrade? I am using the Glibc 2.3
rpm to do the upgrade.
Don't try to use the i386 rpm i
Hello, I know this is an easy question, not much of a challenge, but...I am
going to update on my linux server the Glibc from 2.2 to 2.3. Does anybody
know of any issues I may face with this upgrade? I am using the Glibc 2.3
rpm to do the upgrade.
Thanks.
A
--
redhat-list mailing list
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Thu, 17 Jul 2003 01:14:04 -0700, Big Chuck wrote:
> I noticed that when upgrading glibc (I had to downgrade to link some
> legacy code) that it restarted the sshd server. Where exactly was this
> called from? rpm itself or is there a w
I noticed that when upgrading glibc (I had to downgrade to link some
legacy code) that it restarted the sshd server. Where exactly was this
called from? rpm itself or is there a wrapper in the mix somewhere or
what? Did Red Hat actually cross-reference new libraries with running
services and
console if I was to go to the
building where the server is ?
many thanks
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Behalf Of Jonathan Bartlett
Sent: Tuesday, July 15, 2003 7:35 PM
To: [EMAIL PROTECTED]
Subject: RE: glibc compilation--Help needed!
>
> I installed glibc-2.2.4 and the configuration, make & make install said that
> the installation was successful.
> However, now whe I run any commands such as ls-l, su etc.. all I get is a
> segmentation fault.
> Is there a way of fixing this or reversing it as I can't
Hi,
I installed glibc-2.2.4 and the configuration, make & make install said that
the installation was successful.
However, now whe I run any commands such as ls-l, su etc.. all I get is a
segmentation fault.
Is there a way of fixing this or reversing it as I can't leave it as it is
now
Hi snort bsd,
> actually there are very few glibc packages marked with
> i686; most of them are marked them with i386. i am
> wondering whether i could installed them together and
> disregard the lables "i386" and "i686"
If you have a i686 machine get the i
Hi Lisa,
> I'm doing it as a last resort as I'm having problems with java threads using up
> a lot of memory. The glib that I had didn't have the linuxthreads added onto
> it, so I downloaded a newer glibc with the linuxthreads add-on and that's why
> I'm tryi
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Wed, 16 Jul 2003 02:35:33 +1000 (EST), snort bsd wrote:
> tring to upgrate glibc and failed:
>
> warning: glibc-2.3.2-4.80.6.i686.rpm: V3 DSA
> signature: NOKEY, key ID db42a60e
> error: Failed dependencies:
> glibc-com
thanks bill.
actually there are very few glibc packages marked with
i686; most of them are marked them with i386. i am
wondering whether i could installed them together and
disregard the lables "i386" and "i686"
tia
_ming
--- Bill Tangren <[EMAIL PROTECTED]>
snort bsd wrote:
hi all:
tring to upgrate glibc and failed:
warning: glibc-2.3.2-4.80.6.i686.rpm: V3 DSA
signature: NOKEY, key ID db42a60e
error: Failed dependencies:
glibc-common = 2.3.2-4.80.6 is needed by
glibc-2.3.2-4.80.6
glibc = 2.2.93 is needed by (installed)
glibc-devel
I Know, I hate messing with this stuff..
I'm doing it as a last resort as I'm having problems with java threads using
up a lot of memory. The glib that I had didn't have the linuxthreads added
onto it, so I downloaded a newer glibc with the linuxthreads add-on and
that'
hi all:
tring to upgrate glibc and failed:
warning: glibc-2.3.2-4.80.6.i686.rpm: V3 DSA
signature: NOKEY, key ID db42a60e
error: Failed dependencies:
glibc-common = 2.3.2-4.80.6 is needed by
glibc-2.3.2-4.80.6
glibc = 2.2.93 is needed by (installed)
glibc-devel-2.2.93-5
where I
Is there a reason you are compiling glibc? I've always put that on my
official "bad idea" list because of how intrusive it is.
It looks like the file is missing an #include statement.
Jon
On Tue, 15 Jul 2003, Lisa Ryan wrote:
> Hi,
>
> I am configuring glibc-2.2. Wh
Hi,
I am configuring glibc-2.2. When I do a mak, I get the following error:
Can anyone tell me what the problem could be ?
thanks
Lisa
-I../sysdeps/wordsize-32 -I../sysdeps/ieee754/ldbl-96 -I../sysdeps/ieee754/
dbl-64 -I../sysdeps/ieee754/flt-32 -I../sysdeps/ieee754 -I../sysdeps/generic
Updating glibc*-2.3.2-27.9.i386.rpm on an i686 or Athlon system seems to
be a common way of killing a system... and by some reports it may even
happen if you're using up2date.
Here are some interesting threads on the topic:
http://www.linuxquestions.org/questions/archive/5/2003/05/4/57607
I have found the solution for this. It's quite simple, just do:
[EMAIL PROTECTED] glibc]# export LD_ASSUME_KERNEL=2.2.5
[EMAIL PROTECTED] glibc]# rpm -Uvh
ftp://ftp.redhat.com/pub/redhat/linux/updates/9/en/os/i686/glibc-2.3.2-27.9.i686.rpm -
-force
or you can do
rpm -Uvh --replac
Before updating the glibc, you please check the architecture the glibc
RPM .
All other glibc RPMS(Ex: glibc-common) have i383 architecture set, but
only
the glibc RPM is set to i686 architecture. So even while downloading
from redhat
updates, download GLIBC from i686 folder.Then everything will
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Fri, 11 Jul 2003 15:20:18 +0300, Alex wrote:
> Preparing...###
> [100%]
> 1:glibc-common ### [
> 17%]
)" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Friday, July 11, 2003 3:40 PM
Subject: Re: Glibc update & dead redhat - HLLLPPP !!!
> start from redhat-cdrom into rescue-mode and install the last working
> version you got.
> maybe you have to use chroot to get
ing...###
> [100%]
> 1:glibc-common ### [
> 17%]
>2:glibc ### [
> 33%]
> error: %post(glibc-2.3.2-27.9) scriptlet failed, exit status 1
Download your old rpm package and "rpm -ivh --force --allfiles x.rpm"
it should work.
Leo
Alex wrote:
Preparing...###
[100%]
1:glibc-common ### [
17%]
Preparing...###
[100%]
1:glibc-common ### [
17%]
2:glibc ### [
33%]
error: %post(glibc-2.3.2-27.9) scriptlet failed, exit status
I have installed on my linux box the glibc-2.3.2-4.80.6 version, and I'd
like to go back to glibc-2.2.4-31. However, when I try to install it
using rpm I get all kind of errors. Is there a way to unistall the newer
version and go back to the previous one without compromising anything?
gio
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Mon, 30 Jun 2003 10:54:14, Lancer wrote:
> I have a new install of AS 2.1 which I understand is based on RH 8.0 for RPM
> purposes. I have new RPMs which are dependent on libc.so.6 so I am trying to
> upgrade glibc. As shown below this se
I have a new install of AS 2.1 which I understand is based on RH 8.0 for RPM
purposes. I have new RPMs which are dependent on libc.so.6 so I am trying to
upgrade glibc. As shown below this seems to be a chicken/egg thing. How do I
upgrade glibc?
[EMAIL PROTECTED] rpms]# uname -a
Linux host 2.4.9
I was trying to update my gLibc library last night, due to an
incompatablility with my version(stock lib for RH9) and Mysql, when the rpm
upgrade went sorrow. Unfortunately I have lost all connections to the box.
Is it possible to boot into single user mode and re-compile or replace the
corrupt
Hi All,
Whenever I upgrade glibc to 2.3.2... my app starts to crash.
Everything works fine until I relink a specific shared library. I am
using RH8 but we had the same problem on a new RH9 system.
What bugs me is that all the other applications seem very stable. The
only app affected by this
I just installed RH9.0 and compiled a c++ extension to TCL w/
the 'gcc296' compiler. I'm on RH 9.0. All built fine and then
I tried to run it and got the following error.
libAnotherDependentLib.so.7: symbol __pthread_atfork, version
GLIBC_2.0 not defined in file libpthread.so.0 with link time
refe
Hi,
I recently setup a new machine with RH 8 and I've been experiencing
weird problems with an application we are currently developing since
I've installed a security patch to the glibc package.
For your information, RH 8 ships we glibc-2.2.93-5. upgrading glibc to
package 2.3.2 wil
I have done a fresh install on a system, that has
matlab 6.1 R12.1 and matlab 6.5 R13. However the
install of 9.0 broke the older verion of matlab.
Here is the error I receive.
[EMAIL PROTECTED] root]# matlab
> Opening Log file: /root/java.log.
> Warning: Failed to start the Java Virtual ma
Hello,
i just ran into sth weird.
I manually applied the glibc update and
replaced:
glibc-2.2.93-5.i686.rpm
glibc-common-2.2.93-5.i386.rpm
glibc-devel-2.2.93-5.i386.rpm
with the updates:
glibc-2.3.2-4.80.i686.rpm
glibc-common-2.3.2-4.80.i386.rpm
glibc-devel-2.3.2-4.80.i386.rpm
Simply
Hello,
I update my RedHat 8.0 today, and there was an update for the glibc
packages. So I also updated that one.
Now I discovered some problems after updated the glibc packagesome
programs fails to start since that update.
Now I want to 'roll back' the glibcis there any way
On Sat, 2003-03-22 at 00:18, Ed Wilts wrote:
> On Sat, Mar 22, 2003 at 12:03:05AM +, David Holden wrote:
> > ok i'll try this. With regard to glibc updates from redhat network, I
> > think this should be in default list of things (i.e. with kernel) not to
> > au
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Friday 21 March 2003 07:18 pm, Ed Wilts wrote:
> On Sat, Mar 22, 2003 at 12:03:05AM +, David Holden wrote:
> > ok i'll try this. With regard to glibc updates from redhat network, I
> > think this should be in default list
On Sat, Mar 22, 2003 at 12:03:05AM +, David Holden wrote:
> ok i'll try this. With regard to glibc updates from redhat network, I
> think this should be in default list of things (i.e. with kernel) not to
> automatically update.
I disagree. When used with Red Hat application
> >>
> >> Dave.
> >
> >
> > Bugger - I was going to tell you after your original post not to mess with
> > this. Glibc is so vital to system operations, I only EVER get the RedHat
> > RPMs for the RedHat operating system. Then I read this post and
I downloaded glibc-2.3.2-4.80.src.rpm and proceeded to build RPMS on my
system. After a lot of churning around (around 2 days - it is a slow
system!), I obtained the binary RPMs. However, I noticed that it only
produced glibc-2.3.2-4.80.i586.rpm and glibc-debug-2.3.2-4.80.i586.rpm.
Other RPMs
wine: relocation error: /usr/lib/wine/libntdll.dll.so: symbol __fork,
version GLIBC_2.0 not defined in file libc.so.6 with link time reference
:-(
Rebuilding wine should fix this, huh?
Krum
--
redhat-list mailing list
unsubscribe mailto:[EMAIL PROTECTED]
https://listman.redhat.com/mailman/li
Edward Dekkers wrote:
Well I can't do that now because it seems to have left my machine in a
state where it has *two* glibc's and everything is now failing, can't
even boot!
Dave.
Bugger - I was going to tell you after your original post not to mess with
this. Glibc is so
; Dave.
Bugger - I was going to tell you after your original post not to mess with
this. Glibc is so vital to system operations, I only EVER get the RedHat
RPMs for the RedHat operating system. Then I read this post and saw it was
too late.
Shame I got onto this only this morning our time.
Har
On Thu, 2003-03-20 at 12:00, Stephen Kuhn wrote:
> On Thu, 2003-03-20 at 22:54, David Holden wrote:
> > Hi, trying to "up2date" a RH7.2 system glibc and I get the following
> > failure
> > up2date glibc
> > /usr/bin/python: /lib/ld-linux.so.2: version `GLIB
On Thu, 2003-03-20 at 22:54, David Holden wrote:
> Hi, trying to "up2date" a RH7.2 system glibc and I get the following
> failure
> up2date glibc
> /usr/bin/python: /lib/ld-linux.so.2: version `GLIBC_PRIVATE' not found
> (required by /lib/i686/libc.so.6)
&g
Hi, trying to "up2date" a RH7.2 system glibc and I get the following
failure
up2date glibc
/usr/bin/python: /lib/ld-linux.so.2: version `GLIBC_PRIVATE' not found
(required by /lib/i686/libc.so.6)
anyone know what this is about.
Dave.
--
Dr. David Holden. (Systems De
That page is very out of date for RH8. it talks about version 2.1.3-28
and my stock RH8 came with
[root@daevid root]# rpm -qa | grep "glibc"
glibc-2.2.93-5
glibc-kernheaders-2.4-7.20
glibc-utils-2.2.93-5
glibc-common-2.2.93-5
glibc-devel-2.2.93-5
> -Original Message-
&
Hello Robert,
Saturday, December 7, 2002, 11:18:32 AM, you textually orated:
RC> The last Glibc updates killed connections to MySql.
Actually, the "last" glibc updates were specifically released to fix that
problem. ;)
RC> Anyone know yet if the new updates have the same iss
The last Glibc updates killed connections to MySql.
Anyone know yet if the new updates have the same issues? Or will we
have to do something to the MySql?
Thanks inadvance :-)
--
robert canary
system services
OhioCounty.Net
[EMAIL PROTECTED]
(270)298-9331 Office
(270)298-7449 Fax
It has been standard practice with Red Hat as long as I have been using
linux (MKLinux DR3 was my first distro - and that was Red Hat 5.1 except
with the Mach 3 mikrokernel and ppc binaries) to create a package
containing just the stuff the user needs to use the software (binary,
config files, docu
Hi,
The reason the program didn't compile had something to do with
bzip2. If I installed the rpm bzip2-development it worked like
a charm... same thing if I downloaded the bzip2 source code
and compiled that. I think it's stupid that the bzip2-development
package wasn't installed in the first plac
Hi,
My problems are now addressed to the source code of the
software I tried to compile, so I guess it's not really glibc's
fault. But I'll keep my eyes open! :-)
Thanks for all your answers.
/dahonk
--
redhat-list mailing list
unsubscribe mailto:[EMAIL PROTECTED]?subject=unsubscribe
https:/
1 - 100 of 324 matches
Mail list logo
