Lines Matching full:operating

105 * Operating systems::           
108 * Convenience to operating systems::  
116 Every operating system ever created tends to have its own boot loader.
117 Installing a new operating system on a machine generally involves
120 operating systems to coexist reliably on one machine through typical
122 choice of boot loaders for a particular operating system --- if the one
123 that comes with the operating system doesn't do exactly what you want,
127 operating systems, it shouldn't be too difficult for a few people in the
128 free operating system communities to put their heads together and solve
129 this problem for the popular free operating systems. That's what this
131 boot loader and a operating system, such that any complying boot loader
132 should be able to load any complying operating system. This
134 only how they must interface with the operating system being loaded.
141 most common and have the largest variety of operating systems and boot
148 @node Operating systems
149 @section The target operating systems
151 This specification is targeted toward free 32-bit operating systems
154 operating systems that this specification is being primarily designed
156 emerging free operating systems will adopt it from the start, and thus
158 be nice if commercial operating system vendors eventually adopted this
174 another operating system (e.g. the VSTa boot code, which loads from
184 @section Configure an operating system at boot-time
187 to provide some configuration information to an operating system
191 information to the operating system.
194 @node Convenience to operating systems
199 operating system normally uses. It should be possible to @code{nm} or
202 format. If this means shifting some work from the operating system to
206 typically has to remain in memory forever. The operating system should
209 to load operating system data above the 1MB boundary, and forcing the
210 operating system to do this makes creation of OS images much more
214 even among free Unix-like @sc{pc}-based operating systems --- generally
215 a different format for each operating system. Most of the relevant free
216 operating systems use some variant of a.out format, but some are moving
220 effectively becomes operating system specific again.
235 Many modern operating system kernels, such as those of VSTa and Mach, do
241 by the operating system when it receives control, it is often more
242 flexible, more space-efficient, and more convenient to the operating
247 loader to indicate to the operating system what auxiliary boot modules
250 because some operating systems will be unable to boot without them.
272 operating system to be run on the machine. The boot loader may itself
275 loader --- the stage that eventually transfers control to an operating
282 transfers control to start an operating system. The OS image is
283 typically an executable containing the operating system kernel.
288 locations to the operating system when it is invoked.
323 The state of a machine when a boot loader starts an operating
327 The format of information passed by a boot loader to an operating
342 format for that particular operating system, except that it may be
413 along with the operating system must be aligned on page (4KB)
414 boundaries. Some operating systems expect to be able to map the pages
477 operating system in that area. If this field is zero, the boot loader
482 start running the operating system.
524 When the boot loader invokes the 32-bit operating system, the machine
530 value indicates to the operating system that it was loaded by a
532 boot loader that the operating system can also be loaded from).
584 operating system should be able to make @sc{bios} calls and such after
596 Upon entry to the operating system, the @code{EBX} register contains the
599 operating system. The operating system can use or ignore any parts of
606 operating system's responsibility to avoid overwriting this memory until
654 be set to zero by the boot loader. Any set bits that the operating
672 clear). The operating system may use this field as a hint for
741 string might be a command line (e.g. if the operating system treats boot
742 modules as executable programs), or a pathname (e.g. if the operating
744 is specific to the operating system. The @samp{reserved} field must be
745 set to 0 by the boot loader and ignored by the operating system.
959 document, but are included for prospective operating system and boot
982 @sc{bios} drive maps to which device driver in an operating system is
983 non-trivial, at best. Many kludges have been made to various operating
997 the operating system as desired.
1003 Both of these techniques should be usable from any PC operating system,
1014 remaining @sc{bios} devices when not all of them have operating system
1031 the operating system drivers. This should hopefully be sufficient to
1211 Clasification of machine state passed to an operating system.