Boot folder
Page Module:Message box/ambox.css has no content.Page Template:Multiple issues/styles.css has no content.
 | This article has multiple issues. Please help improve it or discuss these issues on the talk page. (Learn how and when to remove these messages)
Page Module:Message box/ambox.css has no content.
|
In Unix-like operating systems, a boot folder is the directory which holds files used in booting the operating system, typically Page Template:Mono/styles.css has no content./boot. The usage is standardized within Linux in the Filesystem Hierarchy Standard.[1]
Contents
The contents are mostly Linux kernel files or boot loader files, depending on the boot loader, most commonly (on Linux) LILO or GRUB.
Linux
vmlinux– the Linux kernel[2]initrd.img– a temporary file system, used prior to loading the kernel[3]System.map– a symbol lookup table[4]
LILO
LILO creates and uses the following files:
map– a key file, which records where files needed by LILO during boot are stored. Following kernel upgrades, this file must be regenerated by running the "map installer", which is Page Template:Mono/styles.css has no content./sbin/lilo otherwise the system will not boot.boot.xxyy– these 512-byte files are backups of boot sectors, either the master boot record (MBR) or volume boot record (VBR), created when LILO overwrites a boot sector. xx and yy are the major and minor device numbers in hex;[5] for example, the drive Page Template:Mono/styles.css has no content.sda has numbers 8, 0, hence its MBR is backed up to Page Template:Mono/styles.css has no content.boot.0800 while the partition Page Template:Mono/styles.css has no content.sda3 has numbers 8,3, hence its VBR is backed up to Page Template:Mono/styles.css has no content.boot.0803.
LILO may also use other files, such as Page Template:Mono/styles.css has no content.message and also stores a non-boot configuration file in Page Template:Mono/styles.css has no content./etc/lilo.conf.
GRUB
GRUB stores its files in the subdirectory Page Template:Mono/styles.css has no content.grub/ (i.e. Page Template:Mono/styles.css has no content./boot/grub/). These files are mostly modules (Page Template:Mono/styles.css has no content..mod), with configuration stored in Page Template:Mono/styles.css has no content.grub.cfg.
Location
Page Template:Mono/styles.css has no content./boot/ is often simply a directory on the main (or only) hard drive partition. However, it may be a separate partition. A separate partition is generally only used when bootloaders are incapable of reading the main filesystem (e.g. LILO does not recognize XFS) or other problems not easily resolvable by users.[citation needed]
On UEFI systems, including most modern PCs, the EFI system partition is often mounted at Page Template:Mono/styles.css has no content./boot/, Page Template:Mono/styles.css has no content./efi/ or Page Template:Mono/styles.css has no content./boot/efi/.[6][7]
References
Page Template:Reflist/styles.css has no content.
- ^ Lua error in package.lua at line 80: module 'Module:Citation/CS1/Utilities' not found.
- ^ Lua error in package.lua at line 80: module 'Module:Citation/CS1/Utilities' not found.
- ^ Lua error in package.lua at line 80: module 'Module:Citation/CS1/Utilities' not found.
- ^ Lua error in package.lua at line 80: module 'Module:Citation/CS1/Utilities' not found.
- ^ Lua error in package.lua at line 80: module 'Module:Citation/CS1/Utilities' not found.
- ^ Lua error in package.lua at line 80: module 'Module:Citation/CS1/Utilities' not found.
- ^ Lua error in package.lua at line 80: module 'Module:Citation/CS1/Utilities' not found.
