This message does not appear to have gone out so I'll attempt
to resend it.
Lloyd
------ Forwarded by Lloyd Young on 08/06/98 12:28 AM ------
Lloyd Young
08/05/98 02:00 PM
To: pmp at pwg.org
cc:
Subject: Re: PMP> Re: COnfig Changes (Document link not converted)
There are two questions on the table:
1. Should these conditions be added to the FAQ on what constitues a
config change? They seem reasonably to me to be added to the list.
2. Should this list of conditions that cause a config change be an
"only" list or "at least" list? The answer to me should be "at least".
Unless I hear objections by Wednesday August 12th, I will tell Gail
to make the above changes to the FAQ.
Lloyd
Gail Songer <gsonger%tsoft.com at interlock.lexmark.com> on 08/04/98 11:14:11
PM
To: pmp%pwg.org at interlock.lexmark.com
cc: (bcc: Lloyd Young)
Subject: Re: PMP> Re: COnfig Changes
Hey!
As keeper of the FAQ I am more than happy to add these variables
and have a new version ready to go as soon I hear the word.
The only comment that I have is that this was not intended to be a
complete list but was to give a flavor of the things that could cause
a config change. Should this intent change? Do we want to state ALL
those things that an ideal implementation would count as config
changes? Should the list be an "only" list or an "at least" list?
Gail
Ira Mcdonald x10962 wrote:
> I agree with Harry and Jay that all of these MIB variables should
> be added to what constitutes a config change
>> Cheers,
> - Ira McDonald (High North Inc)
>> ------------------------------------------------------
> [Harry's note]
> From: Harry Lewis <harryl at us.ibm.com>
> To: <pmp at pwg.org>
> Subject: PMP> COnfig Changes
> Message-Id: <5030100024028591000002L012*@MHS>
> Date: Mon, 3 Aug 1998 09:58:39 PDT
> Mime-Version: 1.0
> Content-Type: text/plain; charset=iso-8859-1
> Content-Transfer-Encoding: quoted-printable
> Sender: pmp-owner at pwg.org> Status: R
>> There is a FAQ (#7) - that explains what constitutes a config change.
> We have some questions...
>> 1) The following variables weren't included:
>> prtGeneralInputDefaultIndex
> prtGeneralOutputDefaultIndex
> prtGeneralMarkerDefaultIndex
> prtGeneralMediaPathDefaultIndex
>> This seems inconsistent with other listed 'default' settings --
> prtChannelDefaultPageDescLangIndex, prtInterpreterDefaultOrientation,
> prtInterpreterDefaultCharSetIn, prtInterpreterDefaultCharSetOut.
>> 2) These variables were also not included but could be considered chang=
> es
> to the configuration although they do not effect operations.
>> prtGeneralCurrentLocalization
> prtConsoleLocalization
>> Harry Lewis - IBM Printing Systems
> =