ctlmp/ctlconvert_txt EOF request [PSARC/2007/365 closed approved fast-track 09/26/2007]

[Suresh Chandrasekharan]

Sorry for the incorrect approval date of 10/05/2007, right one should be 
09/26/2007.
Also pl. read "specification changes" for TCR's.

Thanks much for James Carlson for pointing these out.

Regards,
Suresh

Suresh Chandrasekharan wrote:
> This is timed out and approved on 10/05/2007 with the following TCRs.
>
> Following mechanisms will be used for alerting the customers of the  EOF.
>
> 1. The EOF notice a message "ctlmp: This utility will be removed from 
> future Solaris release. Please use mp(1) print filter or another 
> suitable printing mechanism instead" will output to stderr for each 
> invocation of ctlmp.
>
> For ctlconvert_txt
> "ctlconvert-txt: This utility will be removed from future Solaris 
> release. Please use mp(1) print filter or another suitable printing 
> mechanism instead".
>
> 2. For ctlmp user can prepare for the upgrade by making use of mp(1) 
> print filter in places where ctlmp is used inside a script. For 
> ctlconvert-txt the part of the script which converts text to 
> presentation forms and then piping to a print filter need to be 
> replaced by mp(1) filter. Will be documented in the release notes.
>
> Regards,
> Suresh
>
>
> James Carlson wrote:
>> Suresh Chandrasekharan writes:
>>  
>>>>>> 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?
>>>>
>>>>         
>>> For ctlmp user can prepare for the upgrade by making use of mp(1) 
>>> print filter in places where ctlmp is used inside a script. For 
>>> ctlconvert-txt the part of the script which converts text to 
>>> presentation forms and then piping to a print filter need to be 
>>> replaced by mp(1) filter. Will be documented in the release notes.
>>>     
>>
>> OK; thanks.  That's what I was looking for.
>>
>>   
>
>