Content deleted Content added
ClueBot NG (talk | contribs) m Reverting possible vandalism by 2.111.85.127 to version by Cotton2. Report False Positive? Thanks, ClueBot NG. (3234911) (Bot) |
|||
Line 4:
[[Hibernate (OS feature)|Hibernation]] is an example that uses an image of the entire machine's [[Random-access memory|RAM]].
==Disk images==
{{Main article|Disk image}}
If a system has all its state written to a disk, then a system image can be produced by simply copying that disk to a file elsewhere, often with [[disk cloning]] applications. On many systems a complete system image cannot be created by a disk cloning program running within that system because information can be held outside of disks and volatile memory, for example in non-volatile memory like boot ROMs.
==Process images==
A [[Process (computing)|process]] image is a copy of its [[State (computer science)|state]] at a given point in time. It is often used for [[persistence (computer science)|persistence]]. A common example is a [[database management system]] (DBMS). Most DBMS can store the state of its [[database]] or databases to a file before being closed down (see [[database dump]]). The DBMS can then be restarted later with the information in the database intact and proceed as though the software had never stopped. Another example would be the [[Hibernate (OS feature)|hibernate]] feature of many operating systems. Here, the state of all [[RAM]] memory is stored to disk, the computer is brought into an energy saving mode, then later restored to normal operation.
Some [[emulator]]s provide a facility to save an image of the system being emulated. This is often called a [[savestate]].
Another use is [[code mobility]]: a [[mobile agent]] can migrate between machines by having its state saved, then copying the data to another machine and restarting there.
===Programming language support===
Some [[programming language]]s provide a command to take a system image of a program. This is normally a standard feature in [[Smalltalk]] (inspired by [http://www.mprove.de/diplom/gui/kay68.html FLEX]) and [[Lisp (programming language)|Lisp]], among other languages. Development in these languages is often quite different from many other programming languages. For example, in Lisp the programmer may load packages or other code into a running Lisp [[implementation]] using the [[read-eval-print loop]], which usually compiles the programs. Data is loaded into the running Lisp system. The programmer may then [[ROM image|dump]] a system image, containing that pre-compiled and possibly customized code - and also all loaded application data.
<!--
It's to avoid the time penalty of recompiling that software like Emacs use images, and modern Common Lisp interpreters, anyway, compile packages as a matter of course (See SBCL, CMUCL, etc.)
-->
Often this image is an executable, and can be run on other machines. This system image can be the form in which executable programs are distributed — this method has often been used by programs (such as [[TeX]] and [[Emacs]]) largely implemented in Lisp, Smalltalk, or [[idiosyncratic]] languages to avoid spending time repeating the same initialization work every time they start up.
Similar, [[Lisp Machine]]s were booted from Lisp images, called Worlds. The World contains the complete operating system, its applications and its data in a single file. It was also possible to save incremental Worlds, that contain only the changes from some base World. Before saving the World, the Lisp Machine operating system could optimize the contents of memory (better memory layout, compacting data structures, sorting data, ...).
Although its purpose is different, a "system image" is often similar in structure to a [[core dump]].
== See also ==
| |||