Suresh Chandrasekharan writes:
> Pl. view this request as an EOF announcement for print filter
> consolidation similar to we did for PSARC/2001/754.
OK.
> James Carlson wrote:
> > If so, then what must they do on upgrade to a Nevada-based release?
> > Does the upgrade process itself automatically adjust the print filters
> > to the new mechanism, or is there a document that explains the
> > necessary customer action?
> >
> The following is the mechanism used for alerting the customers about the
> EOF.
>
> The EOF notice a message "ctlmp: This utility will be removed from next
> Solaris Major release. Please use mp(1) print filter or another suitable
Given that we're not planning any Major releases, and haven't had one
for 15+ years, that's probably not the right wording.
It should say instead:
This utility may be removed from a future Solaris release.
> printing mechanism instead" will output to stderr for each invocation of
> ctlmp.
Who would see that message? Isn't this something that is likely to be
buried under either lots of scripting or a GUI for most users?
I think there needs to be at least a release note for this.
> Pl. see the reasons for EOFing ctlconvert-txt in the OVERVIEW
> section of the fasttrack one pager submitted. "ctlconvert-txt: This
> utility will be removed from next Solaris Major release. Please use
> mp(1) print filter or another suitable printing mechanism instead".
Also inaccurate wording -- Solaris 10, for example, was a Minor
release. Solaris Nevada hasn't been released yet (so doesn't formally
have a binding yet), but currently admits only Minor-binding projects.
(Modulo the mind-bending confusion over consolidations ...)
> > If there's customer action required, is this something that customers
> > can do (prior to upgrade) on existing S10 and S9 systems when the EOF
> > notice is released? Or is it an upgrade-break-fix cycle?
Is there an answer to these questions? Can the user prepare for this
change, or does the system just break on upgrade?
--
James Carlson, Solaris Networking <james.d.carlson at sun.com>
Sun Microsystems / 35 Network Drive 71.232W Vox +1 781 442 2084
MS UBUR02-212 / Burlington MA 01803-2757 42.496N Fax +1 781 442 1677
