On Mon, Apr 1, 2013 at 4:08 PM, Linda Walsh
I had a problem a few weeks ago where I was having libc problems booting off a rescue disk -- used to be I could usually boot from a rescue disk, mount root on /mnt, chroot /mnt, mount the rest, and look at startup scripts 1-by-1.
Now that doesn't come close to working. But even when I got the paths set right (LDLLIBPATH) etc... BASH/DASH/SH/ were still having problems loading due to suse's adding OW's patches that make linked binaries incompat with standard libc/glibc I.e. -- instead of a dynamic load of OW, and giving reduced functionality, it was hardcoded in to prevent anything from working. Ok... so I thought -- AH
Standalone shell... it doesn't depend on anything.
SURPRISE -- it's now dynamically linked with a custom libc as well...so it wouldn't work either!
Um...
FAIL!!!!
SASH is called SASH because it is supposed to be Stand-Alone and need no libs to link as well as having builtin basic commands:
Manpage: DESCRIPTION The sash program is a stand-alone shell which is useful for recovering from certain types of system failures. In particular, it was created in order to cope with the problem of missing shared libraries or impor- tant executables. ^^^^^^^^^^^^^^^^^^^^^^^^
Um...HELLO... breaking basic functionality?
Had a bitch of a time recovering since xfsdump bumped it's version num to '3' to correct several kernel bugs. For some reason my xfsrestore's even from the disk kept saying '2'... Well it appears I couldn't run xfsrestore from any repair disk as they all had v2 of the libs (v3 appeared in mid Jan). But I couldn't link with the new versions on disk due to libc problems.
Finally was able to rebuild xfs from git running on the repair disk and install xfsrestore onto the repair disk where the libc wasn't corrupted with a non-standard OW extension.
But, that was an aside. Um...main beef .. NOT EVEN SASH?!?! statically linked?
system recovery tools like xfsrestore likely should be too (as an afterthough/aside)...
Linda, Can't say I've ever worked with sash, but per the changes file it has to dynamically link with libc: == Wed May 6 15:44:12 CEST 2009 - crrodriguez@suse.de - while using static libz will work, using static libc wont, due to the use of getgrgid, getgrnam, getpwnam and getpwuid. == That's from 4 years ago, so maybe upstream has a fix for that by now. I checked and Fedora doesn't have sash package, so maybe they dropped it since it doesn't build statically anymore. The home page for the project is http://members.tip.net.au/~dbell/ It doesn't look like there has been an update in 6 years or so. As it stands, I don't see a value in the project, so it seems someone needs to either fix it to be static or drop it. Greg -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org