Zsh Mailing List Archive
Messages sorted by:
Reverse Date,
Date,
Thread,
Author
Re: stuff
- X-seq: zsh-users 1083
- From: Tim Writer <Tim.Writer@xxxxxxxxxx>
- To: Andrew Main <zefram@xxxxxxxxx>
- Subject: Re: stuff
- Date: 14 Oct 1997 17:17:28 -0400
- Cc: quinn@xxxxxxxxxxxxxxxxxxxxx, zsh-users@xxxxxxxxxxxxxxx
- In-reply-to: Andrew Main's message of Fri, 10 Oct 1997 18:27:53 +0100 (BST)
- References: <199710101727.SAA13977@xxxxxxxxxxxxxxxx>
- Sender: tim@xxxxxxxxxx
Andrew Main <zefram@xxxxxxxxx> writes:
> Tim Writer wrote:
> >> No, that's what /etc/skel is for.
> >
> >I disagree. The purpose of /etc/skel is to provide an INITIAL environment.
> >It doesn't solve the (much more difficult) problem of MAITAINING a
> >consistent, friendly environment for those users that don't have the skills
> >to do it themselves.
>
> I see what you mean. You need to have one single set of shell setup
> files, that will be used by any user that makes no attempt to change eir
> setup. However, I disagree that these need to be called /etc/zshenv etc..
> It would be much better to have an /etc/skel setup with files that just
> source your master files, which you can keep anywhere you want (say,
> /usr/local/lib/skel).
Actually, that's what I do in practice. But I set up some basic machinery in
/etc/zshenv.
Messages sorted by:
Reverse Date,
Date,
Thread,
Author