Information AboutBoot Image |
| CATEGORIES ABOUT BOOT IMAGE | |
| booting | |
| disk images | |
|
However, once built, the boot image can be simply copied onto devices, patched within reasonable limits, and remains disposable in case of any problems ( Computer Virus es in particular). This is possible because: Unlike other hard drive images (which may contain any data at all), pure boot images contain no mission-critical data. By definition a pure boot image contains no data that cannot be reproduced from configurations or off-the-shelf executables. In particular end user data is not part of a boot image, although some operating systems require that a copy of user preferences or configuration files be kept within the boot image itself, e.g. Microsoft Windows Registry . Utilities like Norton Ghost keep a backup copy of the boot image, for quick re-imaging (often called '''re-installation''') in case of problems, to avoid diagnosing specific problems with the '''image''' itself." And so on. By keeping the boot image entirely separate and disposable, and mandating Boot Image Control , organizations seek to keep their Total Cost Of Operations (including its Total Cost Of Ownership component) low. Often such organizations look at Uptime As A Service . One goal of Boot Image Control is to minimize the number of boot images used by an organization to reduce support costs. It includes at least:
Many organizations use thin clients for applications which require high security, involve unreliable users or repurpose older machines for continued use: A cascading strategy involves re-imaging older, off-spec machines to thin client boot images so that they may continue in use for some less demanding or more access-controlled applications. This is one context in which Linux often replaces Microsoft Windows , as Linux will run fast on older machines with better Computer Security and technical support. Also almost any Linux Boot Image fits on a CD-ROM - while a current Windows XP Boot Image requires DVD-ROM . |
|
|