Visit The New, Modern Unix Linux Community

Linux and UNIX Man Pages

Test Your Knowledge in Computers #65
Difficulty: Easy
In the TCP/IP model, end-to-end connectivity is provided from host-to-host in the transport layer.
True or False?
Linux & Unix Commands - Search Man Pages

boot(1m) [hpux man page]

boot(1M)																  boot(1M)

boot - bootstrap process DESCRIPTION
Itanium-based System Hardware An system's bootstrap process involves the execution of four software components: o CMOS o option ROM o EFI o Boot Manager o (see hpux.efi(1M)). After the processor is reset, firmware initializes and tests processors and platform. During initialization, the firmware lets a user interrupt and configure CMOS and option ROMs. It then transfers control to EFI, the Extensible Firmware Interface. EFI, in turn, initial- izes EFI boot and runtime services and launches the Boot Manager. The Boot Manager, which allows loading of EFI application or drivers from EFI defined file system, loads and transfers control to the HP-UX-specific bootstrap loader. then loads the HP-UX kernel object file from the HP-UX file system to memory and transfers control to the loaded kernel image. PA-RISC Hardware The PA-RSIC bootstrap process involves the execution of three software components: o (see pdc(1M), o (see isl(1M), and o (see hpux(1M). After the processor is RESET, the (firmware), performs a self-test and initializes the processor. It then loads and transfers control to the operating-system-independent in turn, loads and transfers control to the utility, the HP-UX-specific bootstrap loader. then downloads the HP-UX kernel object file from an HP-UX file system and transfers control to the loaded kernel image. SEE ALSO
hpux(1M), hpux.efi(1M), isl(1M), pdc(1M), efi(4). boot(1M)

Check Out this Related Man Page

UEFI(8) 						    BSD System Manager's Manual 						   UEFI(8)

UEFI -- Unified Extensible Firmware Interface bootstrapping procedures DESCRIPTION
The UEFI Unified Extensible Firmware Interface provides boot- and run-time services to operating systems. UEFI is a replacement for the legacy BIOS on the i386 and amd64 CPU architectures, and is also used on arm64 and ia64. The UEFI boot process loads system bootstrap code located in an EFI System Partition (ESP). The ESP is a GPT or MBR partition with a spe- cific identifier that contains an msdosfs(5) FAT file system with a specified file hierarchy. Partition Scheme ESP Identifier GPT C12A7328-F81F-11D2-BA4B-00A0C93EC93B MBR 0xEF The UEFI boot process proceeds as follows: 1. UEFI firmware runs at power up and searches for an OS loader in the EFI system partition. The path to the loader may be set by an EFI environment variable. If not set, the default is /EFI/BOOT/BOOTX64.EFI. The default UEFI boot configuration for FreeBSD installs boot1.efi as /EFI/BOOT/BOOTX64.EFI. 2. boot1.efi locates the first partition with the type freebsd-ufs, and from it loads loader.efi. 3. loader.efi loads and boots the kernel, as described in loader(8). The vt(4) system console is automatically selected when booting via UEFI. FILES
/boot/boot1.efi First stage UEFI bootstrap /boot/boot1.efifat msdosfs(5) FAT file system image containing boot1.efi for use by bsdinstall(8) and the bootcode argument to gpart(8). /boot/loader.efi Final stage bootstrap /boot/kernel/kernel default kernel /boot/kernel.old/kernel typical non-default kernel (optional) SEE ALSO
vt(4), msdosfs(5), boot(8), gpart(8) HISTORY
UEFI boot support first appeared in FreeBSD 10.1. AUTHORS
UEFI boot support was developed by Benno Rice <>, Ed Maste <>, and Nathan Whitehorn <>. The FreeBSD Foundation sponsored portions of the work. CAVEATS
EFI environment variables are not supported by loader(8) or the kernel. boot1.efi loads loader.efi from the first FreeBSD-UFS file system it locates, even if it is on a different disk. boot1.efi cannot load loader.efi from a ZFS(8) file system. As a result, UEFI does not support a typical root file system on ZFS configura- tion. BSD
October 17, 2014 BSD

Featured Tech Videos