rc-list - mailing list for the rc(1) shell
 help / color / mirror / Atom feed
From: byron@netapp.com (Byron Rakitzis)
To: rc@hawkwind.utcs.toronto.edu
Subject: autoconfig
Date: Tue, 1 Apr 1997 14:28:39 -0500	[thread overview]
Message-ID: <9704011928.AA27920@netapp.com> (raw)

Ok, I've been thinking some more about this and I went through
rc's config.h to see what could be done about it all. Here's
a walk through the list of options in config.h, I wanted to see
if I could get rid of most or all of them:

> #define DEFAULTPATH "/usr/ucb", "/usr/bin", "/bin", "."

I think this can be deduced by running /bin/sh as a login shell
with $PATH unset, and snarfing the output of "echo $PATH".

> #define NODIRENT
> #define SVSIGS

Handled by GNU autoconf.

> #define NOCMDARG
> #define DEVFD
> #define TMPDIR "/var/tmp"

I am sorely tempted to remove named pipe support. It never worked
properly. So something is needed to auto-sense the particular
encoding for /dev/fd (systems encode this differently), which I
doubt is supplied by GNU autoconf.

> #define NOLIMITS

Should be handled by autoconf, or can be extended to do so.

> #define NOSIGCLD

Handled by autoconf.

> #define READLINE

Leave this as-is.

> #define NOEXECVE

I think I should bundle my fake execve; it is a very small amount
of code and will only cause extra file opens and the like on an
exec failure, which is out of the "performance loop".

> #define DEFAULTINTERP "/bin/sh"

Ditto, this should just be a standard feature.

> #define PROTECT_ENV

Given that every /bin/sh I have tried croaks on rc-native environment
variable representation in some way or other, PROTECT_ENV should
be the only method for encoding env. variable names.

> #define NOECHO

rc's echo should be built in.

> #define NOJOB

Does anyone use this? It forces sh-like semantics for backgrounding.
Why should it be an option? I haven't found a use for it, but I think
I put it in in self-defense early on.

My conclusion: It seems that rc + an autoconfig script could take
out all the configuration options. I don't see the point of going
with Posix, then.

             reply	other threads:[~1997-04-01 22:58 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1997-04-01 19:28 Byron Rakitzis [this message]
1997-04-02  1:11 ` autoconfig Greg A. Woods
1997-04-02  8:32   ` autoconfig Stefan Dalibor
1997-04-02  2:20 ` autoconfig Scott Schwartz
1997-04-02 15:10   ` autoconfig Mark K. Gardner
1997-04-02  2:59 ` autoconfig David Luyer
1997-04-02 16:32 ` autoconfig Chet Ramey
1997-04-01 23:52 autoconfig Alan Watson
1997-04-02  9:38 autoconfig Bengt Kleberg
1997-04-03  0:15 ` autoconfig Scott Merrilees
1997-04-03  3:14   ` autoconfig Warren Toomey
1997-04-02 17:30 autoconfig Rich Salz
1997-04-02 20:24 autoconfig Byron Rakitzis
1997-04-05 18:38 autoconfig Bengt Kleberg

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=9704011928.AA27920@netapp.com \
    --to=byron@netapp.com \
    --cc=rc@hawkwind.utcs.toronto.edu \


* 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).