David wrote
> I've been having problems with ld-linux-2.0.7.so and libc-2.0.7.so
> getting corrupted (apparently). Previously, insmod SegFaulted (right
> away). Now, more SegFaults after about 3-6 pages of display (though the
> number seems to vary).
>
> I'm using busybox 0.50pre, and glibc-2.0.7 from Debian with the last
> security fix (Sep 2000).
>
> What's it take to ensure that these don't get corrupted? I'm always
> making a tar.gz out of the system, including all files in /lib; would
> this do it?
I had a similar problem with Busybox 0.49.
Root.lrp tar.gz on the debian system. Functioned like a dream after
i made a change, and backed up using busybox tar and gzip, I
couldn't boot anymore, and system stopped with segfault.
copying the root.lrp back to the system. Can this have something
to do with busybox tarring files if linked. not links.
did you use the busybox tar ( remembering our previous
discussion), as i told that it functioned, it did, root.lrp was the only
package i didn't check.
>
> I originally thought this was a problem with busybox, but then busybox
> does practically everything in my system, and when libc and ld-linux was
> replaced, the symptoms changed....
>
> I tried using gdb but it SegFaults as soon as the program runs. Did
> that with insmod and (I think) with more.
>
Eric Wolzak
_______________________________________________
Leaf-devel mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/leaf-devel
