Sponsored Content
Operating Systems Linux Create a bootable PXE image from build kernel source code Post 302738857 by boethius on Monday 3rd of December 2012 02:55:12 AM
Old 12-03-2012
Quote:
Originally Posted by h0ujun
Hi,
Can i just ask how I can create a bootable PXE image from the built kernel source.
!
You're saying you want to build a custom Linux kernel that also supports PXE booting?

Here are some guides, both RHEL/CentOS-specific however it's not a big stretch to use the same basic guidelines for other distributions:

Since I can't post URLs, Google this: Building a RHEL kernel with the intention of PXE-booting a machine

How to properly compile a PXE/NFSRoot kernel for CentOS 5.x
 

9 More Discussions You Might Find Interesting

1. BSD

Am searching for source code of openBSD kernel..

Hello Friends, Am lakshma reddy, doing my masters, i had some interest in exploring the source code of any open LINUX/UNIX, i searched for that i know i can get it but this time am finding it difficult in doing that. To be frank am new to this UNIX?LINUX platform. I need it since i want to... (1 Reply)
Discussion started by: luckyy
1 Replies

2. AIX

How do I create a bootable mksysb image file

I have several systems which require software maintenance several times a year. After the software maintenance, it is required that we make two system tapes for DR purposes. The creation of these system tapes takes anywhere from 1-1.5 hours because of the performance of the tape drives. What I... (7 Replies)
Discussion started by: acascianelli
7 Replies

3. AIX

check whether a mksysb image is bootable or not?

Hi, Can any one please tell me the method to check whether a mksysb image which is in the server is bootable or not. :confused: Thanks in advance, Anoop (1 Reply)
Discussion started by: anoopraok
1 Replies

4. BSD

BSD Kernel Source Code

Hi I need the BSD core (kernel) operating system Please let me download link I'm from Iran Please help me Thank you very much (1 Reply)
Discussion started by: sepadl71
1 Replies

5. Solaris

ffmpeg build - Sorais 10 x86: source code?

Hi I am trying to build ffmpeg on Solaris 10 from source as per the main downloads page on the ffmpeg site, howver I am running into various errors. I then came across this posting chrismiles: Building ffmpeg on Solaris 10 after some judicious googling. Unfortunately, the patch does not... (0 Replies)
Discussion started by: skewbie
0 Replies

6. Red Hat

Need help to create netboot image for EL6 kernel

We use netboot to boot our RedHat Linux kernels. We usually use mknbi tool to create netboot image from Red Hat Linux kernel. However, I can't get this to work with the new Red Hat EL6 kernel. One online document I found seems to say mknbi should not be used for Linux 2.6 or newer kernels any... (1 Reply)
Discussion started by: jyao02459
1 Replies

7. AIX

bootable mksysb image on

i have been given a bootable cd/dvd, that i install a ibm aix 185 workstation with, i want to make a nim mksysb resource from that, the following is a listing for the root file structure of the cd/dvd, seems someone took a mksysb of a built ibm aix machine and did mkcd -L -S -I and setup the... (2 Replies)
Discussion started by: asyed123
2 Replies

8. UNIX for Dummies Questions & Answers

how to make pxe file bootable

hi, i recently built a pxe file the problem is I don't know how to add it in the pxe server. I was wondering if you guys know how to add my pxe file in the pxe server so that when I run the device we're using, I can go lan boot then at boot: I will just type a text and it will boot the built... (0 Replies)
Discussion started by: h0ujun
0 Replies

9. UNIX for Dummies Questions & Answers

Adding SDK Build on Kernel Source Build

Hi, So I downloaded this kernel source and was able to build it successfully. But I want to add this SDK source code inside, can anyone help me how to do this? Note that the SDK source can be built by itself. I added the SDK in the main Makefile: init-y := init/ #added SDK... (0 Replies)
Discussion started by: h0ujun
0 Replies
BOOT0CFG(8)						    BSD System Manager's Manual 					       BOOT0CFG(8)

NAME
boot0cfg -- boot manager installation/configuration utility SYNOPSIS
boot0cfg [-Bv] [-b boot0] [-d drive] [-e bell character] [-f file] [-i volume-id] [-m mask] [-o options] [-s slice] [-t ticks] disk DESCRIPTION
The FreeBSD 'boot0' boot manager permits the operator to select from which disk and slice an i386 machine (PC) is booted. Note that what are referred to here as ``slices'' are typically called ``partitions'' in non-BSD documentation relating to the PC. Typi- cally, only non-removable disks are sliced. The boot0cfg utility optionally installs the 'boot0' boot manager on the specified disk; and allows various operational parameters to be con- figured. On PCs, a boot manager typically occupies sector 0 of a disk, which is known as the Master Boot Record (MBR). The MBR contains both code (to which control is passed by the PC BIOS) and data (an embedded table of defined slices). The options are: -B Install the 'boot0' boot manager. This option causes MBR code to be replaced, without affecting the embedded slice table. -b boot0 Specify which 'boot0' image to use. The default is /boot/boot0 which will use the video card as output, alternatively /boot/boot0sio can be used for output to the COM1 port. (Be aware that nothing will be output to the COM1 port unless the modem signals DSR and CTS are active.) -d drive Specify the drive number used by the PC BIOS in referencing the drive which contains the specified disk. Typically this will be 0x80 for the first hard drive, 0x81 for the second hard drive, and so on; however any integer between 0 and 0xff is acceptable here. -e bell character Set the character to be printed in case of input error. -f file Specify that a backup copy of the preexisting MBR should be written to file. This file is created if it does not exist, and replaced if it does. -i volume-id Specifies a volume-id (in the form XXXX-XXXX) to be saved at location 0x1b8 in the MBR. This information is sometimes used by NT, XP and Vista to identify the disk drive. The option is only compatible with version 2.00 of the 512-byte boot block. -m mask Specify slices to be enabled/disabled, where mask is an integer between 0 (no slices enabled) and 0xf (all four slices enabled). Each mask bit enables corresponding slice if set to 1. The least significant bit of the mask corresponds to slice 1, the most sig- nificant bit of the mask corresponds to slice 4. -o options A comma-separated string of any of the following options may be specified (with ``no'' prepended as necessary): packet Use the disk packet (BIOS INT 0x13 extensions) interface, as opposed to the legacy (CHS) interface, when doing disk I/O. This allows booting above cylinder 1023, but requires specific BIOS support. The default is 'packet'. setdrv Forces the drive containing the disk to be referenced using drive number definable by means of the -d option. The default is 'nosetdrv'. update Allow the MBR to be updated by the boot manager. (The MBR may be updated to flag slices as 'active', and to save slice selection information.) This is the default; a 'noupdate' option causes the MBR to be treated as read-only. -s slice Set the default boot selection to slice. Values between 1 and 4 refer to slices; a value of 5 refers to the option of booting from a second disk. The special string ``PXE'' or a value of 6 can be used to boot via PXE. -t ticks Set the timeout value to ticks. (There are approximately 18.2 ticks per second.) -v Verbose: display information about the slices defined, etc. FILES
/boot/boot0 The default 'boot0' image /boot/boot0sio Image for serial consoles (COM1,9600,8,N,1,MODEM) EXIT STATUS
The boot0cfg utility exits 0 on success, and >0 if an error occurs. EXAMPLES
To boot slice 2 on the next boot: boot0cfg -s 2 ada0 To enable just slices 1 and 3 in the menu: boot0cfg -m 0x5 ada0 To go back to non-interactive booting, use fdisk(8) to install the default MBR: fdisk -B ada0 SEE ALSO
geom(4), boot(8), fdisk(8), gpart(8) AUTHORS
Robert Nordier <rnordier@FreeBSD.org> BUGS
Use of the 'packet' option may cause 'boot0' to fail, depending on the nature of BIOS support. Use of the 'setdrv' option with an incorrect -d operand may cause the boot0 code to write the MBR to the wrong disk, thus trashing its previ- ous content. Be careful. BSD
October 1, 2013 BSD
All times are GMT -4. The time now is 07:26 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy