9 More Discussions You Might Find Interesting
1. Solaris
I understand the OBP program looks for the boot-device, loads the bootblk (located on physical disk sectors 1 through 15). Then the secondary boot program, /platform/`arch -k`/ufsboot is run. This program loads the kernel core image files (genunix and unix).
So how does it uses the ufsboot and... (1 Reply)
Discussion started by: MR.bean
1 Replies
2. Red Hat
Hello,
Sometime i see that the boot process hangs.
I am using rhel 6.2.
At that time in the console i see
Probing EDD (edd=off to disable)...
SSH service seems to be started but i can't login...
ssh logs (last lines) in verbose mode level 3:
debug2: we did not send a packet,... (3 Replies)
Discussion started by: @dagio
3 Replies
3. UNIX for Advanced & Expert Users
Hey guys,
I am working on a security module which checks signatures of binarys/shared libs. The Linux security framework (and thus my module) gets loaded early in the bootprocess.
Right now all my module does is - whenever a binary gets mmap'ed for execution - print out a message using printk()... (1 Reply)
Discussion started by: disaster
1 Replies
4. Red Hat
Hi Folks,
Initially I had vista and redhat 9 .. due to some reasons i had to re instal my vista again.. since then the dual boot menu disappeared.. i tried to re install redhat and changing the boot configuration of redhat 9 but i am not getting both the OS back .. I am not aboe to boot linux... (2 Replies)
Discussion started by: subhotech
2 Replies
5. Filesystems, Disks and Memory
I have 40GB HD with mepis8, swap, MBR and under flags word boot.
I also have a 160 GB external with a few Linux OS, no swaps, no extended etc. I am total Linux no MS
I would feel more secure by resizing that sda1 partition and creating a /boot partition with the MBR housed there. Is that a... (1 Reply)
Discussion started by: worthamtx
1 Replies
6. Programming
what would happen if a process wrote to its own stdin?
#include<unistd.h>
#include<fcntl.h>
int main()
{
if((write(STDIN_FILENO,"arrgh!",6))==-1)
{
perror("error writing to file");
}
}
output:
$ gcc temp.c
$ ./a.out
arrgh!$ (9 Replies)
Discussion started by: c_d
9 Replies
7. UNIX for Dummies Questions & Answers
Hi all,
I am newbie here.I want to know what is MBR,boot loader & boot strap programe.
What is procedure of loading OS in to memory.
Thanx in advance:) (1 Reply)
Discussion started by: vishwasrao
1 Replies
8. UNIX for Advanced & Expert Users
I have an unix id (AIX system) which is used to run a couple of processes. They also write some log files into a file system (that is not in the home directory of the user id, but in different location).
One bad day, the id was deleted accidentally. But the home directory, files and everything... (1 Reply)
Discussion started by: cmgreat
1 Replies
9. Red Hat
Hi ,
I have two disk installed with Linux(disk 1) and WinXP(disk 2) .Now i am changing Hardisk jumbper manualy to get in to Linux/Windows .I want to configure my REDHAT linux boot manager to list Linux and WindowXP and wanna boot according to my choice .
Here is what my fdisk -l shows (Only... (2 Replies)
Discussion started by: gkrishn
2 Replies
UEFI(8) BSD System Manager's Manual UEFI(8)
NAME
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 <benno@FreeBSD.org>, Ed Maste <emaste@FreeBSD.org>, and Nathan Whitehorn
<nwhitehorn@FreeBSD.org>. 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
