Sponsored Content
Operating Systems Linux Create a bootable PXE image from build kernel source code Post 302737425 by h0ujun on Thursday 29th of November 2012 02:54:03 AM
Old 11-29-2012
Linux Create a bootable PXE image from build kernel source code

Hi,

Can i just ask how I can create a bootable PXE image from the built kernel source.

What files do I need to get?

Thanks!
 

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
MKRESCUE(8)						      System Manager's Manual						       MKRESCUE(8)

NAME
mkrescue - make rescue floppy or CD SYNOPSIS
/sbin/mkrescue makes a bootable rescue floppy or CD using the default kernel specified in lilo.conf. DESCRIPTION
mkrescue takes its specifation for the kernel from the default image specified in /etc/lilo.conf. If the actual default is an other= spec- ification, then use the first image= specification. Any associated initial ramdisk (initrd=), and append= options will also be used. The root directory will be taken to be the current root. A bootable floppy or CD-image will be created using LILO version 22.5.5 or later. mkrescue normally requires no options, unless a CD-image is desired (--iso). OPTIONS
--append <string> Override any append= options taken from the default image. If there is any doubt about whether the lilo.conf options are correct, then specify no kernel parameters by providing the null string (--append ""). --debug Provide verbose output of the operation of mkrescue, pausing to allow the setting of internal operating parameters to be viewed. <CR> must be hit to proceed from these pauses. --device <device> Make the floppy on a device other than /dev/fd0. The floppy disk will always be made to boot on BIOS device code 0x00 (A: drive), without regard to the drive on which it is created. --fast Use a faster method of creating the boot floppy. This involves first creating a file of --size 1k blocks (default is 1440) mounted using a loopback device, creating the bootable floppy, then copying the entire file to the disk. --fs [ ext2 | msdos | minix ] Specify the type of filesystem to create on the drive. ext2 is the default, but msdos and minix allow slightly more disk sectors for really big kernels. --help Print a short usage synopsis, including a list of command options. --image <label> Specifies the label or alias of the particular image from which the append, initial ramdisk, root, keytable, and kernel information is to be taken. --initrd <filepath> and --kernel <filepath> These options, which must be used together, allow specification of an arbitrary kernel file and initial ramdisk file to be used on the created boot floppy. Be sure you know what you are doing before you use these options. If no inital ramdisk is needed with a particular kernel, then you MUST specify --initrd "", meaning a null pathname. --install [ text | menu ] Allows overriding the default human interface used with the rescue bootloader (configuration file "install=" option). text is the default on 1.2MB and 1.44MB floppy disks, and menu is the default on 2.88MB floppies and HD emulation on CD-R media. --iso Create an ISO-9660 bootable CD image (El Torito Format) suitable for burning to a CD-R or CD-RW. The --device specification defaults to the filename rescue.iso, and the --size defaults to 2880. A utility such as "wodim" may be used to burn the ISO file to a recordable CD medium. With this ISO option, the --size HD option is allowed. --nocompact For faster kernel loading from a floppy, LILO map compaction is normally enabled. This option will disable map compaction by omit- ting the lilo -c switch. --noformat Suppresses creation of a new filesystem on the boot floppy. This option may be used ONLY when you know that the floppy you will be writing upon is formatted with the same filesystem as specified by --fs XXX (default is ext2). --root <device> Specify the root filesystem for the kernel on the boot floppy. The currently mounted root is taken as the default specification. --size [ 1440 | 1200 | 2880 | HD ] The default floppy disk size is 1440, meaning a 1.44MB floppy. When --iso is specified, the default size is 2880. Allowed specifi- cations are 1200, 1440, or 2880, meaning a 1.2MB, 1.44MB or 2.88MB floppy, respectively. No other floppy disk sizes are supported. The HD specification, meaning "hard disk", may only be used with the --iso option, to indicate a 16MB hard disk is to be generated for emulation. This allows for very large kernel/initial ramdisk combinations on CD-R. The hard disk image is created using loop- back devices /dev/loop0 and /dev/loop1, which must be free to utilize this size option. --version Print the version number of mkrescue, then terminate. SEE ALSO
cdrecord(1), dd(1), wodim(1), lilo.conf(5), lilo(8), mkfs(8), mkinitrd(8), mkisofs(8), mount(8) 6 Mar 2011 MKRESCUE(8)
All times are GMT -4. The time now is 07:11 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy