Scribd
Upload
9 views3 pages

Word

Uploaded by

herunxonji
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as TXT, PDF, TXT or read online on Scribd
9 views3 pages

Word

Uploaded by

herunxonji
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as TXT, PDF, TXT or read online on Scribd
You are on page 1/ 3

On system with BIOS firmware, the BIOS invokes MBR boot code from a hard disk

drive at startup. The MBR boot code and the VBR boot code are OS-specific. In
Microsoft Windows, the MBR boot code tries to find an active partition (the MBR is
only 512 bytes), then executes the VBR boot code of an active partition. The VBR
boot code tries to find and execute the bootmgr file from an active partition.[3]

On systems with UEFI firmware, UEFI invokes bootmgfw.efi from an EFI system
partition at startup, starting the Windows Boot Manager.

Operation

edit

Once launched the Windows Boot Manager reads the Boot Configuration Data to
determine what operating systems are present and if it should present the user with
a menu allowing them to select which operating system to boot. Before Windows
Vista, this data was contained in boot.ini.

These menu entries can include:

Options to boot Windows Vista and later by invoking winload.exe.

Options to resume Windows Vista and later from hibernation by invoking


winresume.exe.

Options to boot a prior version of the Windows NT family by invoking its NTLDR.

Options to load and to execute a volume boot record.

Operating system loading

edit

Further information: Booting process of Windows NT

The operating system is loaded by individual boot loaders for each install of
Windows, called the Windows Boot Loader.

winload.exe

edit

The Windows Boot Manager invokes winload.exe—the operating system boot loader—to
load the operating system kernel executive (ntoskrnl.exe) and core device drivers.
In that respect, winload.exe is functionally equivalent to the operating system
loader function of NTLDR in prior versions of Windows NT. In UEFI systems, the file
is called winload.efi and the file is always located at \windows\system32 or \
windows\system32\boot.

winresume.exe

edit

If the computer has recently hibernated, then bootmgr will instead


invoke winresume.exe. In UEFI systems, the file is called winresume.efi and is
always located at \windows\system32 or \windows\system32\boot.[4]
The Linux booting process involves multiple stages and is in many ways similar to
the BSD and other Unix-style boot processes, from which it derives. Although the
Linux booting process depends very much on the computer architecture, those
architectures share similar stages and software components,[1] including system
startup, bootloader execution, loading and startup of a Linux kernel image, and
execution of various startup scripts and daemons.[2] Those are grouped into 4
steps: system startup, bootloader stage, kernel stage, and init process.[3] When a
Linux system is powered up or reset, its processor will execute a specific
firmware/program for system initialization, such as the power-on self-test,
invoking the reset vector to start a program at a known address in flash/ROM (in
embedded Linux devices), then load the bootloader into RAM for later execution.[2]
In IBM PC–compatible personal computers (PCs), this firmware/program is either a
BIOS or a UEFI monitor, and is stored in the mainboard.[2] In embedded Linux
systems, this firmware/program is called boot ROM.[4][5] After being loaded into
RAM, the bootloader (also called first-stage bootloader or primary bootloader) will
execute to load the second-stage bootloader[2] (also called secondary bootloader).
[6] The second-stage bootloader will load the kernel image into memory, decompress
and initialize it, and then pass control to this kernel image.[2] The second-stage
bootloader also performs several operation on the system such as system hardware
check, mounting the root device, loading the necessary kernel modules, etc.[2]
Finally, the first user-space process (init process) starts, and other high-level
system initializations are performed (which involve with startup scripts).[2]

For each of these stages and components, there are different variations and
approaches; for example, GRUB, coreboot or Das U-Boot can be used as bootloaders
(historical examples are LILO, SYSLINUX or Loadlin), while the startup scripts can
be either traditional init-style, or the system configuration can be performed
through modern alternatives such as systemd or Upstart.

A Linux file system is a structured collection of files on a disk drive or a


partition. A partition is a segment of memory and contains some specific data. In
our machine, there can be various partitions of the memory. Generally, every
partition contains a file system.
The general-purpose computer system needs to store data systematically so that we
can easily access the files in less time. It stores the data on hard disks (HDD) or
some equivalent storage type. There may be below reasons for maintaining the file
system:

Primarily the computer saves data to the RAM storage; it may lose the data if it
gets turned off. However, there is non-volatile RAM (Flash RAM and SSD) that is
available to maintain the data after the power interruption.
Data storage is preferred on hard drives as compared to standard RAM as RAM costs
more than disk space. The hard disks costs are dropping gradually comparatively the
RAM.
ADVERTISEMENT
Advertisement

The Linux file system contains the following sections:

The root directory (/)


A specific data storage format (EXT3, EXT4, BTRFS, XFS and so on)
A partition or logical volume having a particular file system.

You might also like