Re: dselect wigged out and everything's seg-faulting!
On Tue, 29 Jul 1997, Brandon Mitchell wrote:
> [snip]
> > when it tries to run a shell script. At this point, I'd like to motion
> > that the Debian policy be changed so that the shell pointed to by /bin/sh
> > be compiled with *static* libraries?). If I go to the (S)elect screen, I
> [snip]
Well, I think I've narrowed it down to a problem with libreadline and
libreadlineg overwriting each other. I tried the same upgrade on another
Debian machine and had almost the same thing happen. Dselect installed
libreadline fine, then libreadlineg fine, and then proceeded to seg-fault
on everything else. I looked on a machine that did NOT have libreadlineG
installed (we'll call it machine B) and noticed that it had a different
libreadline than machine A that had just installed libreadline and then
libreadlineg. Figuring that libreadlineg was overwriting the
libreadline.so.2.1 from the libreadline package (on machine A), I copied
machine B's libreadline.so.2.1 ober to machine A and things started
working again. Even bash works... which was the only thing that claims to
depend on libreadlineg.
So, my advice to anyone upgrading from unstable would be, if upgrading
bash, to deselect libreadlineg and then use "Q" to force dselect to grin
and bear it. Bash seems to be working fine without it.
Now, the only problem is that there's apparently *another* library that
got hosed in the process. smail hangs up on me when telnetting to port 25
and perl seg-faults. I've copied over libdl, libdb, ldso, libgdbm, libm,
and libc from a Debian machine that perl is *working* on and still no
luck. However, those are the only libraries I could find when doing a
strings perl | grep "\.so\."
Does anyone know of any other libraries Perl needs or what else could be
making it segfault?
> A better solution is to have an /sbin/sh which has static libraries. This
> keeps dynamic libraries for everything else. In a crisis, you can just
> make a symlink from /bin/sh to /sbin/sh.
And lastly, perhaps some scripts to handle all of the symlinks. "ohshit"
could point the links to the /sbin versions and "whew" could point them
back to the dyn-linked ones. :)
> I've been avoiding unstable till it seems more
> stable.
Well, I once asked if "unstable" meant that the *software* itself was
unstable or if it was mainly that the version numbers weren't stable (in
other words, that new packages and new builds of existing ones could show
up in there without notice). The impression I got from the responses was
that it was mostly the latter, but some of the former in that it wasn't
necessarily beta tested very much if at all.
But what else can you do? I've been itching for Apache 1.2 and I'm gonna
just burst if I have to wait much longer for mSQL 2.x. Don't wanna wait
for a whole new Debian release.
> P.S. This problem probably belongs in debian-devel.
Okay, I'll forward it along to them.
- Joe
--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
debian-devel-request@lists.debian.org .
Trouble? e-mail to templin@bucknell.edu .
Reply to: