Talk:Glossary: Difference between revisions

From OLPC
Jump to navigation Jump to search
No edit summary
No edit summary
Line 7: Line 7:
*suspend (semi-stub added to OS and firmware section) (User: Nicabod)
*suspend (semi-stub added to OS and firmware section) (User: Nicabod)
*resume (ditto) (User: Nicabod) 03:22, 9 June 2K8
*resume (ditto) (User: Nicabod) 03:22, 9 June 2K8
*RT (Nicabod, 04:28 9 Je 2K8)


[[User:Cjl|Cjl]] 22:50, 31 March 2008 (EDT)
[[User:Cjl|Cjl]] 22:50, 31 March 2008 (EDT)

Revision as of 08:29, 9 June 2008

additional terms for consideration

  • telepathy
  • salut
  • mesh view as synonym for group view?
  • rpm / yum
  • suspend (semi-stub added to OS and firmware section) (User: Nicabod)
  • resume (ditto) (User: Nicabod) 03:22, 9 June 2K8

Cjl 22:50, 31 March 2008 (EDT)

Although I've been reading about Suspend and Resume for months, in Walter Bender's weeklies, where details of trying to improve its performance were detailed, I've never learned just what these terms mean precisely. Plainly, to suspend means, loosely, to set aside or put away, figuratively, to stop work with the intent of resuming it later. However:

When the XO is suspended, what suspends it? Timeout? User action (likely), but what kind? Button press? Selecting an icon or menu item? Closing up the machine? Command from the mesh (unlikely)? None, or several of those? Others? What does the user do to resume, or does a signal on the mesh do it (very unlikely to be the only way to resume), or both?

When suspended, what is the internal state of the XO? Low power, likely, but is the XO powered down except for the clock/calendar?

What happens to the OS when the XO is suspended? Does it go into standby -- what runlevels as it suspends? Resume must be the reversal, of course.

Are these questions mostly answered implicitly in online documentation? If so, where?