GNU GRUB (short for GNU GRand Unified Bootloader, commonly referred to as GRUB) is a boot loader package from the GNU Project. GRUB is the reference implementation of the Free Software Foundation's Multiboot Specification, which provides a user the choice to boot one of multiple operating systems installed on a computer or select a specific kernel configuration available on a particular operating system's partitions.
(Redirected from Grub4Dos)
GNU GRUB was developed from a package called the Grand Unified Bootloader (a play on Grand Unified Theory[5]). It is predominantly used for Unix-like systems. The GNU operating system uses GNU GRUB as its boot loader, as do most Linux distributions and the Solaris operating system on x86 systems, starting with the Solaris 10 1/06 release.
Operation[edit]
GRUB2 on MBR-partitioned hard drive; stage 1 (
boot.img ) can alternatively be written into one of the partition boot sectors.
GRUB2 on a GPT-partitioned hard drive, booting on BIOS firmware, or UEFI compatibility mode (CSM)
Booting[edit]
When a computer is turned on, BIOS finds the configured primary bootable device (usually the computer's hard disk) and loads and executes the initial bootstrap program from the master boot record (MBR). The MBR is the first sector of the hard disk, with zero as its offset (sectors counting starts at zero). For a long time, the size of a sector has been 512 bytes, but since 2009 there are hard disks available with a sector size of 4096 bytes, called Advanced Format disks. As of October 2013, such hard disks are still accessed in 512-byte sectors, by utilizing the 512e emulation.[6]
The legacy MBR partition table supports a maximum of four partitions and occupies 64 bytes. Together with the optional disk signature (four bytes) and disk timestamp (six bytes), this leaves between 434 and 446 bytes available for the machine code of a boot loader. Although such a small space can be sufficient for very simple boot loaders,[7] it is not big enough to contain a boot loader supporting complex and multiple file systems, menu-driven selection of boot choices, etc. Boot loaders with bigger footprints are thus split into pieces, where the smallest piece fits into and resides within the MBR, while larger piece(s) are stored in other locations (for example, into empty sectors between the MBR and the first partition) and invoked by the boot loader's MBR code.
Operating system kernel images are in most cases files residing on appropriate file systems, but the concept of a file system is unknown to the BIOS. Thus, in BIOS-based systems, the duty of a boot loader is to access the content of those files, so it can be loaded into the RAM and executed.
One possible approach for boot loaders to load kernel images is by directly accessing hard disk sectors without understanding the underlying file system. Usually, an additional level of indirection is required, in form of maps or map files – auxiliary files that contain a list of physical sectors occupied by kernel images. Such maps need to be updated each time a kernel image changes its physical location on disk, due to installing new kernel images, file system defragmentation etc. Also, in case of the maps changing their physical location, their locations need to be updated within the boot loader's MBR code, so the sectors indirection mechanism continues to work. This is not only cumbersome, but it also leaves the system in need of manual repairs in case something goes wrong during system updates.[8]
Another approach is to make a boot loader aware of the underlying file systems, so kernel images are configured and accessed using their actual file paths. That requires a boot loader to contain a driver for each of the supported file systems, so they can be understood and accessed by the boot loader itself. This approach eliminates the need for hardcoded locations of hard disk sectors and existence of map files, and does not require MBR updates after the kernel images are added or moved around. Winning eleven for pc. Configuration of a boot loader is stored in a regular file, which is also accessed in a file system-aware way to obtain boot configurations before the actual booting of any kernel images. As a result, the possibility for things to go wrong during various system updates is significantly reduced. As a downside, such boot loaders have increased internal complexity and even bigger footprints.[8]
GNU GRUB uses the second approach, by understanding the underlying file systems. The boot loader itself is split into multiple stages, allowing for itself to fit within the MBR boot scheme.
Two major versions of GRUB are in common use: GRUB version 1, called GRUB legacy, is only prevalent in older releases of Linux distributions, some of which are still in use and supported, for example CentOS 5. GRUB 2 was written from scratch and intended to replace its predecessor, and is now used by a majority of Linux distributions.
Version 0 (GRUB Legacy)[edit]
GRUB v1 menu (running as part of Ubuntu 8.04 installation)
GRUB 0.x follows a two-stage approach. The master boot record (MBR) usually contains GRUB stage 1, or can contain a standard MBR implementation which chainloads GRUB stage 1 from the active partition's boot sector. Given the small size of a boot sector (512 bytes), stage 1 can do little more than load the next stage of GRUB by loading a few disk sectors from a fixed location near the start of the disk (within its first 1024 cylinders).
Stage 1 can load stage 2 directly, but it is normally set up to load the stage 1.5., located in the first 30 KiB of hard disk immediately following the MBR and before the first partition. In case this space is not available (unusual partition table, special disk drivers, GPT or LVM disk) the install of stage 1.5 will fail. The stage 1.5 image contains file system drivers, enabling it to directly load stage 2 from any known location in the filesystem, for example from
/boot/grub . Stage 2 will then load the default configuration file and any other modules needed.
Version 2 (GRUB 2)[edit]
GRUB 2 - MBR vs. GPT partitioning and boot sequence visualized (systems using BIOS firmware).
Startup on systems using BIOS firmware[edit]
Startup on systems using UEFI firmware[edit]
After startup[edit]
Grub presents a menu where the user can choose from operating systems (OS) found by grub-install. Grub can be configured to automatically load a specified OS after a user-defined timeout. If the timeout is set to zero seconds, pressing and holding ⇧ Shift while the computer is booting makes it possible to access the boot menu.[9]
Logic is like the lungs ofmy studio, allowing everything to breath no matter where i am. Logic pro x free download.
In the operating system selection menu GRUB accepts a couple of commands:
Once boot options have been selected, GRUB loads the selected kernel into memory and passes control to the kernel. Alternatively, GRUB can pass control of the boot process to another boot loader, using chain loading. This is the method used to load operating systems that do not support the Multiboot Specification or are not supported directly by GRUB.
History[edit]
GRUB was initially developed by Erich Boleyn as part of work on booting the operating systemGNU/Hurd, developed by the Free Software Foundation.[11] In 1999, Gordon Matzigkeit and Yoshinori K. Okuji made GRUB an official software package of the GNU Project and opened the development process to the public.[11] As of 2014, the majority of Linux distributions have adopted GNU GRUB 2, as well as other systems such as Sony's PlayStation 4.[12]
Development[edit]
GRUB version 1 (also known as 'GRUB Legacy') is no longer under development and is being phased out.[13] The GNU GRUB developers have switched their focus to GRUB 2,[14] a complete rewrite with goals including making GNU GRUB cleaner, more robust, more portable and more powerful. GRUB 2 started under the name PUPA. PUPA was supported by the Information-technology Promotion Agency (IPA) in Japan. PUPA was integrated into GRUB 2 development around 2002, when GRUB version 0.9x was renamed GRUB Legacy.
Some of the goals of the GRUB 2 project include support for non-x86 platforms, internationalization and localization, non-ASCII characters, dynamic modules, memory management, a scripting mini-language, migrating platform specific (x86) code to platform specific modules, and an object-oriented framework. GNU GRUB version 2.00 was officially released on June 26, 2012.[15][16]
Three of the most widely used Linux distributions use GRUB 2 as their mainstream boot loader.[17][18][19]Ubuntu adopted it as the default boot loader in its 9.10 version of October 2009.[20]Fedora followed suit with Fedora 16 released in November 2011.[21]OpenSUSE adopted GRUB 2 as the default boot loader with its 12.2 release of September 2012.[22]Solaris also adopted GRUB 2 on the x86 platform in the Solaris 11.1 release.[23]
In late 2015, the exploit of pressing backspace 28 times to bypass the login password was found and quickly fixed.[24][25]
Variants[edit]
GNU GRUB is free and open-source software, so several variants have been created. Some notable ones, which have not been merged into GRUB mainline:
Utilities[edit]GRUB configuration tools[edit]
StartUp-Manager, a program used to configure GRUB
Grub4dos User Guide
The setup tools in use by various distributions often include modules to set up GRUB. For example, YaST2 on SUSE Linux and openSUSE distributions and Anaconda on Fedora/RHEL distributions. StartUp-Manager and GRUB Customizer are graphical configuration editors for Debian-based distributions.
For GRUB 2 there are KDE Control Modules.[34][35]
GRLDR ICE is a tiny tool for modifying the default configuration of grldr file for GRUB4DOS.[36]
Boot repair utilities[edit]
Super Grub2 Disk helps you to boot into most any Operating System (OS) even if you cannot boot into it by normal means. It's built in Grub2's bash-like script. A 20MB ISO image that can be booted from USB or CD. Download
Boot-Repair is a simple graphical tool for recovering from frequent boot-related problems with GRUB and Microsoft Windows bootloader. This application is available under GNU GPL license. Boot-Repair can repair GRUB on multiple Linux distributions including, but not limited to, Debian, Ubuntu, Mint, Fedora, openSUSE, and Arch Linux.
GRUB Customizer
Installer for Windows[edit]
Grub2Win is a Windows open-source software package. It allows GNU Grub to boot from a Windows directory. The setup program installs GNU Grub version 2.02 to an NTFS partition. A Windows GUI application is then used to customize the Grub boot menu, themes, UEFI boot order, scripts etc. All GNU Grub scripts and commands are supported for both UEFI and legacy systems. Grub2Win can configure Grub for multiboot of Windows, Ubuntu, openSuse, Fedora and many other Linux distributions. It is freely available under GNU GPL License at SourceForge.
Alternative boot-managers[edit]
The strength of Grub is the wide range of supported platforms, file-systems, operating systems, making it the default choice for distributions and embedded systems.
However, there are boot-managers targeted at the end user that gives more friendly user experience, graphical OS selector and simpler configuration:
Non-graphical alternative, that's simpler to configure:
External links[edit]How-Tos and troubleshooting[edit]
Distribution wikis have many solutions for common issues and custom setups, that might help you:
Documentation[edit]
Introductory articles[edit]
Technicalities[edit]
See also[edit]
References[edit]
Retrieved from 'https://en.wikipedia.org/w/index.php?title=GNU_GRUB&oldid=898885333#Variants'
is there Gui for grub4dos i think if this found will help all people to make bootable cd without to learn or know or write any code or line
so is there any Gui for it?
“Nothing,” Mr Miyagi replies, “Just monks having a good time.” Then the old sage joins in with the dancing, no doubt thinking “Was it really only 10 years ago that I got an Oscar nomination for playing this character?” Julie’s already quite good at karate. “What’s going on?” Julie asks, possibly as horrified as we are. Karate kid movies list.
Mahmoud20070
Mahmoud20070Mahmoud20070
closed as not a real question by slhck, Tom Wijsman, Sathyajith Bhat♦Mar 27 '12 at 7:40
It's difficult to tell what is being asked here. This question is ambiguous, vague, incomplete, overly broad, or rhetorical and cannot be reasonably answered in its current form. For help clarifying this question so that it can be reopened, visit the help center. If this question can be reworded to fit the rules in the help center, please edit the question.
1 Answer
Diddy-Boot-Land has a few that you might like (as @slhck pointed out): 1; 2; 3 in English
Google is your friend on this one as well, asking specific questions in google will give you some good results.
I couldn't find any Arabic documentation, but even if I did I wouldn't know if it's helpful. Perhaps try Google Arabic
also be sure to read the README file that comes with the program
Community♦
RaystafarianRaystafarian
Not the answer you're looking for? Browse other questions tagged command-linegrubgrub4dos or ask your own question.GRUB for DOS - Bridging DOS/Windows to Unix/LinuxGRUB4DOS is an universal boot loader based on GNU GRUB. It can boot off DOS/LINUX, or via Windows boot manager/syslinux/lilo, or from MBR/CD. It also has builtin BIOS disk emulation, ATAPI CDROM driver, etc.GRUB for DOS is free and open-source software, released under the GNU General Public License.News: This project now has yet another new home at https://gna.org/projects/grub4dos/.View the source code: http://svn.gna.org/viewcvs/grub4dos/trunk/.Download the binary build: http://download.gna.org/grub4dos/. (Note: chs is for Chinese Simplified Edition.)View or contribute DOCs at: http://grub4dos.sourceforge.net/wiki![]()
New Our support forumin English has been set up at http://www.boot-land.net/forums/?showforum=66
![]() You can boot the GRUB4DOS boot-loader/boot-manager in different manners:
(1) Run GRUB.EXE at the DOS prompt or in AUTOEXEC.BAT
(2) In CONFIG.SYS of DOS/Windows9x, use DEVICE=GRUB.EXE or INSTALL=GRUB.EXE or SHELL=GRUB.EXE (3) In BOOT.INI of Windows NT/2K/XP, use C:GRLDR='GRUB' (there should be a backslash between C: and GRLDR) (4) Under Linux, use 'kexec -l grub.exe' and then 'kexec -e' (5) In syslinux.cfg, use 'kernel grub.exe' (6) Under GNU GRUB, use 'kernel (DEVICE)/PATH/grub.exe' (7) In lilo.conf, use 'image=/boot/grub.exe' All above methods won't touch the MBR nor the boot area of any partition. (8) Boot from MBR(or floppy) by installing boot sectors onto it with the DOS/LINUX utility bootlace.com. When GRUB4DOS gets running, you can boot other OSes:
(1) Boot Linux kernel with 'kernel (DEVICE)/PATH/vmlinuz'
(2) Boot MS-DOS7+ kernel with 'chainloader (DEVICE)/io.sys' (3) Boot FreeDOS kernel with 'chainloader (DEVICE)/kernel.sys' (4) Boot NTLDR of Windows NT/2K/XP with 'chainloader (DEVICE)/ntldr' (5) Boot CMLDR of Windows NT/2K/XP with 'chainloader (DEVICE)/cmldr' (6) Boot other OSes with 'chainloader (DEVICE)+1' (7) Boot DOS/Windows9x disk image files with the memdrive feature. (8) Boot Smart Boot Manager with the memdrive feature(SBM can boot CD-ROMs).
README.txt has more details.
Download
See Attachments below. Under Linux, the unzip utility can do:
unzip grub4dos-*.zip
Under DOS/Windows, any unzip utility will do.
Useful LinksHere are some useful resources about GRUB for DOS and WINGRUB.
Here are some documentations for GRUB for DOS.
Other Download Sites
Grub4dos GuiOther Resources
Ralf Brown's Interrupt List: It's cool http://www.ctyme.com/rbrown.htm
A Disk Editor View of the NTFS Boot Sector and 'Bootstrap Code' http://www.therdcom.com/asm/mbr/NTFSbrHexEd.htm The Second Extended File System(Internal Layout) http://www.nongnu.org/ext2-doc/ext2.html OSD: PC bootstrap http://my.execpc.com/CE/AC/geezer/osd/boot/ eXtended Memory Specification: http://freedos.sourceforge.net/freedos/news/press/1991-xms30.html High-res high-speed VESA tutorial http://www.monstersoft.com/tutorial1/ BIOS Data Area http://www.bioscentral.com/misc/bda.htm Hardware and Software Documentation http://www.o3one.org/hwdocs.html Screen shot showing the new featuresGrub4dos Gui Installer DownloadsComments are closed.
|
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |