From: firstname.lastname@example.org (Greg A. Woods)
Subject: Re: autoconfig
Date: Tue, 1 Apr 1997 20:11:13 -0500 [thread overview]
Message-ID: <m0wCEa1-00076zC@most.weird.com> (raw)
In-Reply-To: Byron Rakitzis's message of "Tue, April 1, 1997 14:28:39 -0500" regarding "autoconfig" id <9704011928.AA27920@netapp.com>
[ On Tue, April 1, 1997 at 14:28:39 (-0500), Byron Rakitzis wrote: ]
> Subject: autoconfig
> > #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".
Ssh (which also uses GNU autoconf) adds a special option to the
autoconf generated configure script:
--with-path=PATH Default path passed to user shell by sshd.
(autoconf has an AC_ARG_WITH() macro to support such features....)
> 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.
It would be sad to lose it, though of course if it doesn't wrok right (I
admit I've not tried it in a very long time),
> > #define DEFAULTINTERP "/bin/sh"
> Ditto, this should just be a standard feature.
Though of course autoconf can tell for sure. (Note that many modern
systems don't have a /bin directory, eg. SunOS-4 & 5, though of course
they do usually have a symlink there pointing at /usr/bin)
> > #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.
What if DEFAULTINTERP isn't /bin/sh? ;-)
Greg A. Woods
+1 416 443-1734 VE3TCP robohack!woods
Planix, Inc. <email@example.com>; Secrets of the Weird <firstname.lastname@example.org>
next prev parent reply other threads:[~1997-04-02 4:34 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-04-01 19:28 autoconfig Byron Rakitzis
1997-04-02 1:11 ` Greg A. Woods [this message]
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
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 \
* 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).