From: Paul Haahr <haahr@netcom.com>
To: Tom Culliton <culliton@clark.net>
Cc: Russell Davies <c9415019@cs.newcastle.edu.au>,
rc@hawkwind.utcs.toronto.edu
Subject: Re: rc,linux,signal,readline
Date: Tue, 12 Aug 1997 17:24:34 -0400 [thread overview]
Message-ID: <8PZdii2+2@localhost.localdomain.netcom.com> (raw)
In-Reply-To: <199708121359.JAA05316@clark.net>
> > I have been trying for a while now to get the following
> > working under linux..without success..
> >
> > a _dynamically linked_ rc shell with;
>
> I have sent patches to the list which take care of all the rest of
> your requests, but for some reason the shared/dynamic version of GNU
> readline doesn't work like the static version. At least thats my
> first guess as to the problem. Without readline it works "properly"
> and trips clean when linked dynamically. With readline it doesn't.
Could it be that you're getting the wrong readline.so? There were real
changes between the 1.x and 2.x versions, as I remember.
> The size of the statically linked image is with readline unde RedHat
> Linux 4.2 is 308264 bytes, actually slighty bigger than dynamically
> linked bash at 300668. On the other hand I think it was Chris (cks)
> (or maybe Paul) who once gave some good reasons why a shell should be
> statically linked.
I probably said something along those lines, back in the days when we
worried about the startup time. 10x performance improvement moots the
issue for me.
You should have *some* shell, typically lying around in /sbin these
days, which is not dynamically linked, for those times when everything
else is broken. If rc is your root shell, then making it statically
linked is probably a good idea.
--p
next prev parent reply other threads:[~1997-08-12 22:05 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-08-12 8:19 rc,linux,signal,readline Russell Davies
1997-08-12 9:42 ` rc,linux,signal,readline Tim Goodwin
1997-08-12 13:59 ` rc,linux,signal,readline Tom Culliton
1997-08-12 21:24 ` Paul Haahr [this message]
1997-08-12 21:55 ` rc,linux,signal,readline Tom Culliton
1997-08-13 13:33 ` rc,linux,signal,readline Tim Goodwin
1997-08-13 14:20 ` rc,linux,signal,readline Tom Culliton
1997-08-13 17:57 ` rc,linux,signal,readline Tom Culliton
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8PZdii2+2@localhost.localdomain.netcom.com \
--to=haahr@netcom.com \
--cc=c9415019@cs.newcastle.edu.au \
--cc=culliton@clark.net \
--cc=rc@hawkwind.utcs.toronto.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).