From: Scott Schwartz <schwartz@cse.psu.edu>
To: byron@netapp.com (Byron Rakitzis)
Cc: rc@hawkwind.utcs.toronto.edu
Subject: Re: autoconfig
Date: Tue, 1 Apr 1997 21:20:32 -0500 [thread overview]
Message-ID: <199704020220.VAA14000@cse.psu.edu> (raw)
In-Reply-To: Your message of "Tue, 01 Apr 1997 14:28:39 EST." <9704011928.AA27920@netapp.com>
byron@netapp.com (Byron Rakitzis) writes:
| > #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".
I like adding /usr/local/bin to defaultpath, something /bin/sh
doesn't do, because rc doesn't source .rcrc unless it is a login shell
and more localized defaults makes rsh work better.
| I am sorely tempted to remove named pipe support. It never worked
| properly.
But it works just barely well enough for SunOS, which has no /dev/fd
(unless you install a nonstandard modloaded device, or override open().)
| > #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.
If anyone ever ports it to Plan 9, it might be handy.
(I get an urge to do this every time I hit a feature that your
shell does better than the original, most often multi line lists.)
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 ` autoconfig Greg A. Woods
1997-04-02 8:32 ` autoconfig Stefan Dalibor
1997-04-02 2:20 ` Scott Schwartz [this message]
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:
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=199704020220.VAA14000@cse.psu.edu \
--to=schwartz@cse.psu.edu \
--cc=byron@netapp.com \
--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).