RE: [Cooker] Non-working cooker after latest glibc-upgrade
> > Wesley J Landaker wrote on Sat, Jun 22, 2002 at 04:27:41PM -0600 : > > > > I ran into this same issue on my laptop, which is a i586 -- after > > updating to the latest glibc, I got all sorts of illegal instruction > > errors as above. (A monsterous pain to clean up, I might add, since > > things like "cp" and "ls" aren't statically linked, so won't help in > > fixing glibc problems.) > After giving it some more thought I consider it to be highly dangerous "feature" that must NEVER BE DONE AUTOMATICALLY. Linking your default libraries to any specific process type makes it impossible to (ex-)change CPU as part of system changeover or to restore backup on different system. What os worse, because use has no idea what happens (s)he has no idea how to fix it. The only case when such CPU-specific library tuning can be done automatically is when you recheck it on every startup ... but here you are trapped. It must be done very early before anything else runs ... but at this point root is usually read-only yet ... -andrej
Re: [Cooker] Non-working cooker after latest glibc-upgrade
Wesley J Landaker wrote on Sun, Jun 23, 2002 at 01:20:53PM -0600 : > > Unfortunately, sash would help fix things only if I was already logged > in and running at the time of the failure. Certainly not if I'd LILO: linux init=/bin/sash root=/dev/ More than one way to skin a cat :) Blue skies... Todd -- Todd Lyons -- MandrakeSoft, Inc. http://www.mandrakesoft.com/ UNIX was not designed to stop you from doing stupid things, because that would also stop you from doing clever things. -- Doug Gwyn Cooker Version mandrake-release-8.3-0.2mdk Kernel 2.4.18-20mdk msg66505/pgp0.pgp Description: PGP signature
Re: [Cooker] Non-working cooker after latest glibc-upgrade
On Sunday 23 June 2002 12:52 pm, Todd Lyons wrote: > Wesley J Landaker wrote on Sat, Jun 22, 2002 at 04:27:41PM -0600 : > > I ran into this same issue on my laptop, which is a i586 -- after > > updating to the latest glibc, I got all sorts of illegal > > instruction errors as above. (A monsterous pain to clean up, I > > might add, since things like "cp" and "ls" aren't statically > > linked, so won't help in fixing glibc problems.) > If you come across that problem again, use the sash shell. It is > statically linked and has built in cp, ls, rm, tar, mount, dd, chmod, > etc. It does not support all the features of each of the commands, > but it supports enough to get you through whatever problems you might > be encountering. Thanks for the suggestion. On all of my "real" machines (i.e. ones that aren't running cooker all the time and can't afford to crash often ;) I actually have staticly linked versions of those commands as well as a staticlly linked bash, login, init and so forth. Unfortunately, sash would help fix things only if I was already logged in and running at the time of the failure. Certainly not if I'd rebooted in the meantime, since init can't run. (Apparently /sbin doesn't mean what it used to; almost everything in /sbin is dynamically linked; 20 out of 134 files are actually staticly linked.) $ ldd /sbin/init libc.so.6 => /lib/i686/libc.so.6 (0x40022000) /lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x4000) Anyway, I've got it working now by carefully NOT updating to the latest glibc RPM. Hopefully it will get fixed up and work with my i586 and the OP's K6 ... =) -- Wesley J. Landaker - [EMAIL PROTECTED] OpenPGP FP: C99E DF40 54F6 B625 FD48 B509 A3DE 8D79 541F F830
Re: [Cooker] Non-working cooker after latest glibc-upgrade
Wesley J Landaker wrote on Sat, Jun 22, 2002 at 04:27:41PM -0600 : > > I ran into this same issue on my laptop, which is a i586 -- after > updating to the latest glibc, I got all sorts of illegal instruction > errors as above. (A monsterous pain to clean up, I might add, since > things like "cp" and "ls" aren't statically linked, so won't help in > fixing glibc problems.) If you come across that problem again, use the sash shell. It is statically linked and has built in cp, ls, rm, tar, mount, dd, chmod, etc. It does not support all the features of each of the commands, but it supports enough to get you through whatever problems you might be encountering. Blue skies... Todd -- Todd Lyons -- MandrakeSoft, Inc. http://www.mandrakesoft.com/ UNIX was not designed to stop you from doing stupid things, because that would also stop you from doing clever things. -- Doug Gwyn Cooker Version mandrake-release-8.3-0.2mdk Kernel 2.4.18-19mdk msg66502/pgp0.pgp Description: PGP signature
Re: [Cooker] Non-working cooker after latest glibc-upgrade
On Saturday 22 June 2002 12:18 pm, Oliver Lemke wrote: > Hi! > > Upgrading my K6-200 to the latest glibc lead to these errors: > > glibc > ## > /var/tmp/rpm-tmp.12229: line 18: 8749 Illegal instruction (core > dumped) rm -f /lib/glibc.upgraded error: execution of %post scriptlet > from glibc-2.2.5-7mdk failed, exit status 132 > > After that all commands segfault. After reboot it hangs while trying > to load init daemon. It seems to be a problem with the new i686 > version of glibc. I put the harddrive in another PC with Athlon > processor and it booted flawlessly. > > ldconfig -v revealed that it used the glibc from /lib/686 although it > was not specified in ld.so.conf. After removing that directory and > putting the harddrive back to the K6-200 system everything worked > fine again. > > *puh* I ran into this same issue on my laptop, which is a i586 -- after updating to the latest glibc, I got all sorts of illegal instruction errors as above. (A monsterous pain to clean up, I might add, since things like "cp" and "ls" aren't statically linked, so won't help in fixing glibc problems.) -- Wesley J. Landaker - [EMAIL PROTECTED] OpenPGP FP: C99E DF40 54F6 B625 FD48 B509 A3DE 8D79 541F F830
Re: [Cooker] Non-working cooker after latest glibc-upgrade
Hi, > ldconfig -v revealed that it used the glibc from /lib/686 although it > was not specified in ld.so.conf. That's normal, an i686-class processor was detected and it uses libs it finds in /lib/i686. > After removing that directory and putting the harddrive back to the > K6-200 system everything worked fine again. However, the problem is here. It should not have used /lib/i686 things on a K6. Thanks for the report. I will investigate more that issue. At the very least, there will be a completely separate package. Bye, Gwenole.
[Cooker] Non-working cooker after latest glibc-upgrade
Hi! Upgrading my K6-200 to the latest glibc lead to these errors: glibc ## /var/tmp/rpm-tmp.12229: line 18: 8749 Illegal instruction (core dumped) rm -f /lib/glibc.upgraded error: execution of %post scriptlet from glibc-2.2.5-7mdk failed, exit status 132 After that all commands segfault. After reboot it hangs while trying to load init daemon. It seems to be a problem with the new i686 version of glibc. I put the harddrive in another PC with Athlon processor and it booted flawlessly. ldconfig -v revealed that it used the glibc from /lib/686 although it was not specified in ld.so.conf. After removing that directory and putting the harddrive back to the K6-200 system everything worked fine again. *puh* -- Oliver Lemke University of Bremen - Institute of Environmental Physics Satellite Microwave Atmospheric Sounding Group http://www.sat.uni-bremen.de/
