>>>>> "liw" == Lars Wirzenius <liw_at_iki.fi> wrote:
liw> I think it may be a mistake to force a global config file to be
liw> read. Or at least it will mean that the system admin can't put
liw> too much of an environment there. For instance, he can't start
liw> modules there, because not everyone will want them. A user
liw> should be able to completely avoid a system.fvwmrc, IMHO.
That's my HO too.
Let me say what I do with shell initialization files (~/.bashrc and
~/.bash_profile) in the workstations I take care of. These files, as
they're put in the user home dir by adduser, have something like:
## This is "~/.bashrc". This file is execute by bash for non-login
## interactive shells.
## Everything is handled by a cluster-wide file. Feel free to copy it
## to your home directory and make the changes you want, but be ware
## that eventual changes done to the system will not be reflected to
## your environment! If you want to make small changes, do them
## *after* the indicated line.
SHRC=/usr/local/cetc/sh.shrc
if [ -r $SHRC ]; then
. $SHRC
fi
unset SHRC
## Put your local customizations after this line.
I think the same scheme can be done with fvwm2: the ~/.fvwm2rc can
"Read" some system-wide file and the user can them do some
"overloading" after the "Read". This works only with version 2, where
the order of the "sections" is no more important.
Emilio.
--
Emilio C. Lopes <mailto:ecl_at_if.usp.br>
FINPE, Instituto de Fisica E-mail: ecl_at_if.usp.br
Universidade de Sao Paulo Phone : (+55 11) 818-6724 (Voice)
Caixa Postal 66318 (+55 11) 818-6715 (Fax)
05389-970 Sao Paulo - SP
BRAZIL
--
Visit the official FVWM web page at <URL:http://www.hpc.uh.edu/fvwm/>.
To unsubscribe from the list, send "unsubscribe fvwm" in the body of a
message to majordomo_at_hpc.uh.edu.
To report problems, send mail to fvwm-owner_at_hpc.uh.edu.
Received on Wed May 29 1996 - 09:37:06 BST