dav@NORTHSTAR.DARTMOUTH.EDU (William David Haas) (05/10/91)
Currently there are two ways of setting preferences for the Andrew software. The first is to compile the preference into the code during installation and the second is for the user to have a preferences file. How hard would it be to add a global preferences file as a third alternative? We would like to set the default printing commond (amungst other things) for our users. If we put it in the code we have to edit the Andrew software every time we do an installation and anytime we find a bug we have to wonder if it was because we made a bad change. What we have done is to automatically give each user a preferences file when we create an account. This works ok but there are always users who delete or compress the file to save space in their account. Since they didn't create it they don't know what it is for. So, how hard would it be to add an global preferences file that is reference anytime the user's file is read? -dav P.S. I am hoping someone will tell me its already in there.
wdc@ATHENA.MIT.EDU (Bill Cattey) (05/12/91)
Excerpts from mail: 10-May-91 preferences William David Haas@north (1003) > So, how hard would it be to add an global preferences file that is > reference anytime the user's file is read? > -dav > P.S. I am hoping someone will tell me its already in there. As the person who lobbied for it's creation, I am qualified to tell you: It's already there! Put your global preferences into a file named global.pref in the same place you've configured to hold your global.ezinit. We aim to please. -wdc
gk5g+@ANDREW.CMU.EDU (Gary Keim) (05/13/91)
Excerpts from misc: 11-May-91 Re: preferences Bill Cattey@ATHENA.MIT.E (497+0) > Put your global preferences into a file named global.pref in the same > place you've configured to hold your global.ezinit. Actually, the name of the file is ${ANDREWDIR/lib/global.prf.
druid@uk.co.gec-avionics.tsrl (Mark D Templeton - Senior Systems Engineer - TSRL - GEC Avionics) (05/13/91)
Excerpts from mail: 10-May-91 preferences William David Haas@north (1004) > Currently there are two ways of setting preferences for the Andrew > software. The first is to compile the preference into the code during > installation and the second is for the user to have a preferences file. > How hard would it be to add a global preferences file as a third > alternative? We would like to set the default printing commond (amungst > other things) for our users. If we put it in the code we have to edit > the Andrew software every time we do an installation and anytime we find > a bug we have to wonder if it was because we made a bad change. What we > have done is to automatically give each user a preferences file when we > create an account. This works ok but there are always users who delete > or compress the file to save space in their account. Since they didn't > create it they don't know what it is for. > So, how hard would it be to add an global preferences file that is > reference anytime the user's file is read? > -dav > P.S. I am hoping someone will tell me its already in there. Try reading README or README.ez in the andrew root. This lists the setup files: /AndrewSetup /etc/AndrewSetup $(LOCAL_ANDREW_SETUP_ENV) /usr/vice/etc/AndrewSetup $(DEFAULT_ANDREWDIR_ENV)/etc/AndrewSetup /usr/andrew/etc/AndrewSetup Regards, Mark.