On 02/ 3/10 02:20 AM, Brian Ruthven - Solaris Network Sustaining - Sun 
UK wrote:
>
>
> On 01/29/10 07:52 PM, Garrett D'Amore wrote:
>> On 01/29/10 11:46 AM, Hitendra Zhangada wrote:
>>> On 1/28/2010 10:55 AM, chris kiick wrote:
>>>> Here is a diff for the proposed man page change:
>>>>
>>>> ***************
>>>> *** 297,307 ****
>>>>             Stop the  operating  system  and  reboot  to  the  state
>>>>             defined by the initdefault entry in /etc/inittab.
>>>>
>>>> !          Service  svc:/system/boot-config:default is  enabled  by
>>>> !        default.    On       x86        systems,   when      the
>>>>             config/fastreboot_default property is set to true,  init
>>>> !          6 will bypass the firmware.  On a SPARC system some POST
>>>> !        tests will be skipped.
>>>
>>>
>>> Just wondering if it is necessary to say what "-f" option does for 
>>> SPARC.
>>> As Chris mentioned, more changes are in pipe and enhancement will do
>>> more than just skipping POST tests.  Do we have to change man page
>>> for each phase of the fast-boot project?
>>>
>>> Also, saying SPARC systems implies both CMT and non-CMT SPARC
>>> systems.  I believe the changes that are coming are only for non-CMT
>>> SPARC systems only.  Do we need to make that distinction in the man 
>>> page?
>>
>> I think I'd rather say something like:
>>
>> "When config/fastreboot_default property is set to true, init 6 will 
>> bypass certain firmware initialization and test steps, depending on 
>> the specific capabilities of the system."
>>
>> This covers everything, and leaves the door open.
>
> I like the idea of unifying the text for all platforms, but I think 
> there is an obvious question as a consumer:
>
> How do I tell if my system has the "specific capabilities" required 
> for fast reboot? Is there a command which can be run, or a particular 
> line in prtconf, prtdiag or the like which tells me whether the system 
> is capable of fast reboot?

reboot -f dryrun shows whether your system is capable at all.

As far as what the precise meaning of of fast reboot is for your 
platform (how much of POST, firmware, etc, is skipped?) -- the end user 
simply should not care.

     - Garrett

>
> Regards,
> Brian
>
>>
>>     - Garrett
>>>
>>>
>>>>
>>>>         a,b,c
>>>> --- 297,306 ----
>>>>             Stop the  operating  system  and  reboot  to  the  state
>>>>             defined by the initdefault entry in /etc/inittab.
>>>>
>>>> !          On x86 systems, service  svc:/system/boot-config:default
>>>> !          is      enabled      by      default.      When      the
>>>>             config/fastreboot_default property is set to true,  init
>>>> !          6 will bypass the firmware. more than just skipping POST 
>>>> tests.  Do we have to change man page
>>>> for each phase of the fast-boot project?
>>>>
>>>> Also, saying SPARC systems implies both CMT and non-CMT SPARC
>>>> systems.  I believe the changes that are coming are only for non-CMT
>>>> SPARC systems only.  Do we need to make that distinction in the man 
>>>> page?
>>>>
>>>>
>>>>         a,b,c
>>>> ***************
>>>>
>>>>
>>>> On Wed, Jan 27, 2010 at 01:44:29PM -0800, Huay-Yong Wang wrote:
>>>>>   I spoke to Chris and the case is amended for
>>>>>   minor binding only. Chris will send
>>>>>   out an update to the init(1M) manpage shortly.
>>>>>   Thanks.
>>>>>
>>>
>>>
>>
>

Reply via email to