Lines Matching full:operating
57 * Operating systems::
60 * Convenience to operating systems::
69 Every operating system ever created tends to have its own boot loader.
70 Installing a new operating system on a machine generally involves
73 operating systems to coexist reliably on one machine through typical
75 of boot loaders for a particular operating system -- if the one that
76 comes with the operating system doesn't do exactly what you want, or
80 operating systems, it shouldn't be too difficult for a few people in the
81 free operating system communities to put their heads together and solve
82 this problem for the popular free operating systems. That's what this
84 boot loader and a operating system, such that any complying boot loader
85 should be able to load any complying operating system. This
87 how they must interface with the operating system being loaded.
90 File: multiboot.info, Node: Architecture, Next: Operating systems, Prev: Motivation, Up: Overvi…
96 common and have the largest variety of operating systems and boot
103 File: multiboot.info, Node: Operating systems, Next: Boot sources, Prev: Architecture, Up: Over…
105 1.3 The target operating systems
108 This specification is targeted toward free 32-bit operating systems
111 operating systems that this specification is being primarily designed
113 emerging free operating systems will adopt it from the start, and thus
115 be nice if commercial operating system vendors eventually adopted this
119 File: multiboot.info, Node: Boot sources, Next: Boot-time configuration, Prev: Operating systems…
133 operating system (e.g. the VSTa boot code, which loads from DOS).
142 File: multiboot.info, Node: Boot-time configuration, Next: Convenience to operating systems, Pre…
144 1.5 Configure an operating system at boot-time
148 to provide some configuration information to an operating system
152 information to the operating system.
155 File: multiboot.info, Node: Convenience to operating systems, Next: Boot modules, Prev: Boot-tim…
162 operating system normally uses. It should be possible to `nm' or
165 If this means shifting some work from the operating system to a boot
169 typically has to remain in memory forever. The operating system should
172 to load operating system data above the 1MB boundary, and forcing the
173 operating system to do this makes creation of OS images much more
177 formats even among free Unix-like PC-based operating systems --
178 generally a different format for each operating system. Most of the
179 relevant free operating systems use some variant of a.out format, but
183 boot loader effectively becomes operating system specific again.
194 File: multiboot.info, Node: Boot modules, Prev: Convenience to operating systems, Up: Overview
199 Many modern operating system kernels, such as those of VSTa and Mach, do
205 by the operating system when it receives control, it is often more
206 flexible, more space-efficient, and more convenient to the operating
211 loader to indicate to the operating system what auxiliary boot modules
214 because some operating systems will be unable to boot without them.
238 operating system to be run on the machine. The boot loader may
242 to an operating system -- must follow the rules specified in this
248 transfers control to start an operating system. The OS image is
249 typically an executable containing the operating system kernel.
254 passing their locations to the operating system when it is invoked.
287 2. The state of a machine when a boot loader starts an operating
290 3. The format of information passed by a boot loader to an operating
306 format for that particular operating system, except that it may be
377 along with the operating system must be aligned on page (4KB)
378 boundaries. Some operating systems expect to be able to map the
444 to the operating system in that area. If this field is zero, the
449 to start running the operating system.
492 When the boot loader invokes the 32-bit operating system, the machine
497 value indicates to the operating system that it was loaded by a
499 boot loader that the operating system can also be loaded from).
547 that's what the boot loader runs from). In other words, the operating
562 Upon entry to the operating system, the `EBX' register contains the
564 which the boot loader communicates vital information to the operating
565 system. The operating system can use or ignore any parts of the
572 is the operating system's responsibility to avoid overwriting this
617 operating system does not understand should be ignored. Thus, the
633 this field must not be present (bit 3 must be clear). The operating
694 string might be a command line (e.g. if the operating system treats boot
695 modules as executable programs), or a pathname (e.g. if the operating
697 is specific to the operating system. The `reserved' field must be set
698 to 0 by the boot loader and ignored by the operating system.
889 document, but are included for prospective operating system and boot
914 BIOS drive maps to which device driver in an operating system is
915 non-trivial, at best. Many kludges have been made to various operating
928 passing along any extra data to be interpreted by the operating system
937 Both of these techniques should be usable from any PC operating system,
948 of the remaining BIOS devices when not all of them have operating system
967 using the operating system drivers. This should hopefully be sufficient
1611 * Clasification of machine state passed to an operating system.
1634 Node: Operating systems3724
1637 Node: Convenience to operating systems6096