From: woods@weird.com (Greg A. Woods)
To: rc@hawkwind.utcs.toronto.edu
Subject: Re: non login "rc" needs customized environment
Date: Thu, 14 Feb 2002 19:37:26 -0500 [thread overview]
Message-ID: <20020215003726.3C159B5@proven.weird.com> (raw)
In-Reply-To: <m16bM2t-000grCC@shell.vex.net>
[ On Thursday, February 14, 2002 at 08:35:31 (-0500), Smarasderagd wrote: ]
> Subject: Re: non login "rc" needs customized environment
>
> rsh should really be called rcsh; it fails miserably with any other
> shell.
Rsh works perfectly well with any and every shell.
With ksh and its clones though there are better ways of setting up a
per-user specified environment, just as with csh....
The reason is of course that csh and ksh have a default way of reading a
script specified by the environment variable ENV, which has a default
value specified at compile time....
(in pdksh you have to define DEFAULT_ENV at compile time to enable a
default ENV script....)
Perhaps 'rc' could use a similar technique.
--
Greg A. Woods
+1 416 218-0098; <gwoods@acm.org>; <g.a.woods@ieee.org>; <woods@robohack.ca>
Planix, Inc. <woods@planix.com>; VE3TCP; Secrets of the Weird <woods@weird.com>
next prev parent reply other threads:[~2002-02-15 3:07 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-14 13:35 Smarasderagd
2002-02-15 0:37 ` Greg A. Woods [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-02-27 6:29 Byron Rakitzis
2002-02-27 6:26 Russ Cox
2002-02-27 0:52 Byron Rakitzis
2002-02-15 4:11 Byron Rakitzis
2002-02-15 14:04 ` Tim Goodwin
2002-02-27 1:46 ` callum.gibson
2002-02-27 2:16 ` Chris Siebenmann
2002-02-27 13:32 ` Carlo Strozzi
2002-02-27 13:29 ` Carlo Strozzi
2002-02-27 22:24 ` Matt H
2002-02-27 6:13 ` Derek Fawcus
2002-02-14 17:44 Byron Rakitzis
2002-02-15 0:18 ` Dave Mason
2002-02-15 3:21 ` Scott Schwartz
[not found] <chet@nike.ins.cwru.edu>
2002-02-13 20:36 ` Chet Ramey
2002-02-14 2:16 ` Scott Schwartz
2002-02-14 23:35 ` Markus Friedl
2002-02-15 3:05 ` Scott Schwartz
2002-02-13 19:21 Peter Koch
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=20020215003726.3C159B5@proven.weird.com \
--to=woods@weird.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).