
	Where results make sense

Topic: Multiboot Specification

	Multiboot Specification: Scope and requirements
		While this specification should not dictate how this configuration information is obtained by the boot loader, it should provide a standard means for the boot loader to pass such information to the operating system.
		Multiboot compliant boot images always contain a magic Multiboot header (see section 4.1 OS image format), which allows the boot loader to load the image without having to understand numerous a.out variants or other executable formats.
		Thus, this specification should provide a standard method for a boot loader to indicate to the operating system what auxiliary boot modules were loaded, and where they can be found.
	odin-os.sourceforge.net /guides/multiboot_3.html (729 words)

	Multiboot Specification: Specification (Site not responding. Last check: 2007-10-08)
		The Multiboot header must be contained completely within the first 8192 bytes of the OS image, and must be longword (32-bit) aligned.
		Contains the address corresponding to the beginning of the Multiboot header -- the physical memory location at which the magic value is supposed to be loaded.
		The Multiboot information structure and its related substructures may be placed anywhere in memory by the boot loader (with the exception of the memory reserved for the kernel and boot modules, of course).
	www.nada.kth.se /projects/proj03/EOS/doc-ext/replicated/grub/multiboot_3.html (2833 words)

	MultibootDraft - GRUB Wiki
		This documents Multiboot Specification, the proposal for the boot sequence standard.
		The Multiboot header must be contained completely within the first 8192 bytes of the OS image, and must be 32-bit aligned.
		The address corresponding to the beginning of the Multiboot header -- the physical memory location at which the magic value is supposed to be loaded.
	grub.enbug.org /MultibootDraft (747 words)

	[No title]
		Check for the format of a Multiboot kernel @end direntry @setchapternewpage off @@ -151,23 +151,28 @@ One of the important features in GRUB is flexibility; GRUB understands filesystems and kernel executable formats, so you can load an arbitrary operating system the way you like, without recording the physical -position of your kernel on the disk.
		Specification}), because they were determined not to add to the large number of mutually-incompatible PC boot methods.
		Multiboot Specification, Motivation, multiboot, The Multiboot Specification}), not all kernels make use of this information, but GRUB provides it for those who do.
	lists.gnu.org /archive/html/bug-grub/2003-10/txtcdRa6rRVMZ.txt (8166 words)

	Multiboot Specification
		Multiboot compliant boot images always contain a magic Multiboot header (see section OS image format), which allows the boot loader to load the image without having to understand numerous a.out variants or other executable formats.
		Therefore, this specification requires that an additional header, known as a Multiboot header, appear somewhere near the beginning of the executable file.
		word is set, then the fields at offsets 8-24 in the Multiboot header are valid, and the boot loader should use them instead of the fields in the actual executable header to calculate where to load the OS image.
	www.pvv.ntnu.no /~steinarh/grub/multiboot.html (5807 words)

	SourceForge.net: etherboot-developers
		(That is, a Multiboot OS looks at every "size+4" bytes for mmap entries, but with Etherboot, the mmap entries are at every "size" bytes.) The Multiboot Specification may be ambiguous and misleading, but the example code in the Specification and the implementation in GRUB are different from Etherboot.
		Hello list, > The Multiboot Specification may be ambiguous and misleading, > but the example code in the Specification and the implementation > in GRUB are different from Etherboot.
		Anselm Martin Hoffmeister writes: > Hello list, > > > The Multiboot Specification may be ambiguous and misleading, > > but the example code in the Specification and the implementation > > in GRUB are different from Etherboot.
	sourceforge.net /mailarchive/forum.php?thread_id=2692270&forum_id=6402 (1267 words)

	Sysenter: Writing multiboot PE kernels using Visual C++
		Because it is one of the bootloaders that implements the âMultibootâ specification (correctly?).
		In very simple terms, multiboot compliant operating systems need to have a 48 byte structure called the Multiboot header (in its entirety), somewhere within the first 8192 bytes of the kernel image, longword aligned.
		This means that the fields at offsets 8-24 in the Multiboot header are valid, and the boot loader should use them instead of the fields in the actual executable header to calculate where to load the OS image.
	ksrenevasan.blogspot.com /2005/10/writing-multiboot-pe-kernels-using.html (972 words)

	Multiboot Standard
		MultiBoot compliant boot images always either (a) are in ELF format, or (b) contain a "magic MultiBoot header", described below, which allows the boot loader to load the image without having to understand numerous a.out variants or other executable formats.
		Thus, this standard should provide a standard method for a boot loader to indicate to the OS what auxiliary boot modules were loaded, and where they can be found.
		A final release has not been made, but both the GRUB beta release (which is quite stable) and a patch for Multiboot version 0.6 for Mach4 UK22 are available in the GRUB public release area.
	www.nilo.org /multiboot.html (4128 words)

	Multiboot Specification: Terminology (Site not responding. Last check: 2007-10-08)
		Whatever program or set of programs loads the image of the final operating system to be run on the machine.
		The boot loader may itself consist of several stages, but that is an implementation detail not relevant to this specification.
		When this specification specifies a rule as should or may, a Multiboot-complaint boot loader/OS image doesn't need to follow the rule.
	transpatent.com /doc/grub-doc/html/multiboot_2.html (314 words)

	Multiboot Specification:
		It is often necessary for one reason or another for the user to be able to provide some configuration information to an operating system dynamically at boot time.
		Multiboot-compliant OS images always contain a magic Multiboot header (see section 3.1 OS image format), which allows the boot loader to load the image without having to understand numerous a.out variants or other executable formats.
		' parameter in the Multiboot information structure, if the bootloader in question uses older BIOS interfaces, or the newest ones are not available (see description about bit 6), then a maximum of either 15 or 63 megabytes of memory may be reported.
	ftp.sunet.se /pub/gnu/Manuals/grub-0.92/html_mono/multiboot.html (5025 words)

	OS-FAQ Wiki - Bare Bones (Site not responding. Last check: 2007-10-08)
		This spec requires the multiboot header to be present, so providing it in your kernel image is highly recommended.
		GRUB is capable of loading many other kernel formats other than Multiboot compliant ones, like Linux or *BSD, so you might want to provide your kernel in those formats instead.
		A: The multiboot header must be in the first 8kb of the kernel file for GRUB to find it.
	www.mega-tokyo.com /osfaq2/index.php/BareBones?version=18 (646 words)

	[No title] (Site not responding. Last check: 2007-10-08)
		Multiboot Specification Here is the HTML version of the Multiboot Specification.
		The current version of the specification is 0.7.
		HTML (56KB) Note: Multiboot Standard was renamed to Multiboot Specification.
	distro.ibiblio.org /pub/linux/distributions/uos/production/descr/grub (764 words)

	MultibootRequirements - GNU GRUB Wiki (Site not responding. Last check: 2007-10-08)
		We need to understand required information for Multiboot Specification, common information and arch-specific information.
		In Multiboot Specification, the former is called "Multiboot Information", while the latter is "Multiboot Header".
		Multiboot is neutral to any executable format, so it must work with, for example, ELF, variants of a.out and PE.
	www1.autistici.org /grub/moin.cgi/MultibootRequirements (95 words)

	Sysenter
		This is a good place to put the multiboot header (which anyways needs to be present in its entirety within the first 8192 bytes)
		This is important because we want the multiboot header to start at offset 4096.
		Because of this the multiboot header would be pushed to offset 4099 and Grub would refuse to load the kernel because the multiboot header isnât
	ksrenevasan.blogspot.com (1758 words)

	GRUB Manual: Introduction
		Using the command-line interface, you type the drive specification and file name of the kernel manually.
		The primary requirement for GRUB is that it be compliant with the Multiboot Specification, which is described in section `Motivation' in
		Except for specific compatibility modes (chain-loading and the Linux piggyback format), all kernels will be started in much the same state as in the Multiboot Specification.
	jamesthornton.com /gnu/grub/grub_1.html (1409 words)

	Multiboot plan (Site not responding. Last check: 2007-10-08)
		First, a Multiboot header must be included near the beginning of the kernel image.
		The Multiboot specification provides some, but not all, of the information the kernel currently gets in the BootInfo structure.
		bootDrive: The Multiboot specification provides the boot_device, but it is the partition containing the OS image, which is in the /boot file system, not the CapROS partition.
	www.capros.org /design-notes/Multiboot.html (495 words)

	MultibootIdeas - GRUB Wiki
		Random notes about the next version of Multiboot Specification.
		There are some discussions about redesigning the Multiboot Specification.
		But I don't know if this should be applied to Multiboot Header as well.
	grub.enbug.org /MultibootIdeas (183 words)

	[No title]
		Erich and Brian Ford designed the Multiboot Specification (note Multiboot* Specification: (multiboot)Top.), because they were determined not to add to the large number of mutually-incompatible PC boot methods.
		PART is a partition specification in GRUB syntax (*note Naming convention::); TYPE is the partition type and must be a number in the range `0-0xff'; FROM and TO are the starting and ending sectors, expressed as an absolute sector number.
		PART is a partition specification in GRUB syntax (*note Naming convention::); TYPE is the new partition type and must be a number in the range 0-0xff.
	gd.tuwien.ac.at /gnu/gnudoc/grub-0.92/text/grub.txt (16842 words)

	dwww: www - All documents
		This specification describes a method for generating a physical representation, the canonical form, of an XML document that accounts for the permissible changes.
		This specification defines a new XML Signature transform to facilitate the development of efficient document subsetting implementations that interoperate under similar performance profiles.
		This specification defines the syntax and semantics of XSLT, which is a language for transforming XML documents into other XML documents.
	www.gr.ssr.upm.es /dwww/menu/all.html (4385 words)

	Info: (multiboot) Terminology (Site not responding. Last check: 2007-10-08)
		The definitions of terms used through the specification ******************************************************* "must" We use the term "must", when any boot loader or OS image needs to follow a rule -- otherwise, the boot loader or OS image is _not_ Multiboot-compliant.
		Only the _final_ stage of the boot loader -- the stage that eventually transfers control to an operating system -- must follow the rules specified in this document in order to be "Multiboot-compliant"; earlier boot loader stages may be designed in whatever way is most convenient.
		Because the target architecture is little-endian, u64 is coded in little-endian.
	www.cit.gu.edu.au /teaching/2105CIT/cgi-bin/info2html.cgi?(multiboot)Terminology (313 words)

	Untitled Document
		Probe the Intel Multiprocessor Specification 1.1 or 1.4 configuration table and boot the various CPUs which are found into a tight loop.
		for a Multiboot format boot image (no interpretation of the file contents are made, so that user of this command must know what the kernel in question expects).
		This error is returned when the Multiboot features word in the Multiboot header requires a feature that is not recognized.
	www.pvv.ntnu.no /~steinarh/grub/user-ref.html (6505 words)

	ModulOS - Boot process (Site not responding. Last check: 2007-10-08)
		The boot process of ModulOS is compatible with the Multiboot specification (GRUB is an example of boot loader that implements this specification) and is made in three stages:
		The starter is a program compatible with the Multiboot specification, that is, it has an header of the Multiboot specification and is responsible for loading all modules necessary to the initialization of the system.
		The starter must be loaded by a boot loader compatible with the Multiboot specification or, at least, that uses the Multiboot header of the starter do load it.
	modulos.sourceforge.net /docs/bootproc.html (284 words)

	SourceForge.net: etherboot-developers
		Anselm Martin Hoffmeister writes: > Hello list, > > > The Multiboot Specification may be ambiguous and misleading, > > but the example code in the Specification and the implementation > > in GRUB are different from Etherboot.
		It based on the assumption you are using a.out.
		I have been busy lately so I haven"t had a chance to really look at that stuff yet.
	sourceforge.net /mailarchive/message.php?msg_id=5417999 (180 words)

	Re: Multiboot specification for PowerPC
		This seems to be somewhat like the original multiboot, > only more consistent; but since I have no experience at all with multiboot, > I'm > not sure how well it would work.
		The idea people had for the portable multiboot spec is to have a tagged item list.
		Of course it is much nicer to use multiboot for >> this.
	lists.gnu.org /archive/html/bug-grub/2004-08/msg00004.html (633 words)

	Booting from GRUB...
		IIRC the multiboot specification (or Grub) requires this header to be word aligned.
		IIRC = the multiboot specification (or Grub) requires this header to be = word aligned.
		I ran the multiboot check program on the file and it passed.
	www.software-one.org /new-555721-4686.html (984 words)

	Multiboot Specification
		An OS image may be an ordinary 32-bit executable file in the standard format for that particular operating system, except that it may be linked at a non-default load address to avoid loading on top of the
		format or contain the load address information embedded in the Multiboot header; they may also directly support other executable formats, such as particular a.out variants, but are not required to.
		Must contain the 32-bit physical address of the Multiboot information structure provided by the boot loader (see Boot information format).
	www.gnu.org /software/grub/manual/multiboot/multiboot.html (6106 words)

	Info Node: (multiboot.info)Motivation (Site not responding. Last check: 2007-10-08)
		1.1 The background of Multiboot Specification ============================================= Every operating system ever created tends to have its own boot loader.
		Installing a new operating system on a machine generally involves installing a whole new set of boot mechanisms, each with completely different install-time and boot-time user interfaces.
		This specification does _not_ specify how boot loaders should work -- only how they must interface with the operating system being loaded.
	jonas.liljegren.org /cgi-bin/info2www?(multiboot)Motivation (197 words)

	[cap-talk] Moving to multiboot (Site not responding. Last check: 2007-10-08)
		At the time I wrote it, the multiboot > standard did not yet exist and Brian and Erich had not yet created the > Grub boot loader.
		Grub is unarguably superior to the EROS boot loader, > and much of the work that the current boot loader does is handled better > by grub.
		> > The multiboot specification, which describes the kernel entry > environment, can be found at: > > http://www.gnu.org/software/grub/manual/multiboot/multiboot.pdf > > _______________________________________________ > cap-talk mailing list > cap-talk at mail.eros-os.org > http://www.eros-os.org/mailman/listinfo/cap-talk
	www.eros-os.org /pipermail/cap-talk/2005-May/003567.html (159 words)

	PXE multiboot FreeBSD and other OSes? (Site not responding. Last check: 2007-10-08)
		My goal is to be able to multiboot FreeBSD, Linux and some other OSes and different versions using PXE.
		I don't want to install boot loaders on hard disks because I want to boot several different machines to different OSes every now and then.
		Pxegrub claims to conform to the Multiboot Specification, would it be sensible (and easy?) to make FreeBSD loader and/or kernel Multiboot compliant as well?
	lists.freebsd.org /pipermail/freebsd-questions/2004-December/067974.html (312 words)

Try your search on: Qwika (all wikis)