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 (0x40000000)
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
