mknbi.1

linux下从网卡远程启动

These can be used to modify the kernel loading process at runtime. To
use these options with \s-1ISC\s0 \s-1DHCPD\s0 v3, a popular \s-1DHCP\s0 daemon, the syntax
is as below. You will need to adjust the syntax for other \s-1DHCP\s0 or \s-1BOOTP\s0
daemons.
.PP
option etherboot-signature code 128 = string;
.PP
option kernel-parameters code 129 = text;
.PP
\&...
.PP
.Vb 1
\&                option etherboot-signature E4:45:74:68:00:00;
.Ve
.PP
.Vb 1
\&                option kernel-parameters "INITRD_DBG=6 NIC=3c509";
.Ve
.PP
Option 128 is required to be the six byte signature above. See the
vendortags appendix of the Etherboot user manual for details.
.PP
The following option is presently supported by \fBmkelf-linux\fR:
.PP
\&\fB129\fR The \fIstring\fR value given with this option is appended verbatim to
the end of the kernel command line.  It can be used to specify arguments
like I/O addresses or \s-1DMA\s0 channels required for special hardware
like \s-1SCSI\s0 adapters, network cards etc. Please consult the Linux kernel
documentation about the syntax required by those options. It is the same
as the \fB\-\-append\fR command line option to \fBmkelf-linux\fR, but works at
boot time instead of image build time.
.PP
\&\fB130\fR With this option it is possible to the select the network adapter
used for mounting root via \s-1NFS\s0 on a multihomed diskless client. The
syntax for the \fIstring\fR value is the same as for the \f(CW\*(C`dev\*(C'\fR entry used
with the \fB\-\-ip=\fR option as described above. However note that the
\&\fBmkelf-linux\fR runtime setup routine does not check the syntax of the
string.
.SH "MKNBI-ROM"
.IX Header "MKNBI-ROM"
\&\fBmknbi-rom\fR makes a boot image from an Etherboot \f(CW\*(C`.rom\*(C'\fR or \f(CW\*(C`.zrom\*(C'\fR
boot \s-1ROM\s0 image.  This allows it to be netbooted using an existing
\&\s-1ROM\s0. This is useful for developing Etherboot drivers or to load a newer
version of Etherboot with an older one.
.PP
Run mknbi-rom like this:
.PP
mknbi-rom nic.zrom > nic.nb
.PP
Move \fInic.nb\fR to where the network booting process expects to find it.
The boot \s-1ROM\s0 will load this as the \fIoperating system\fR and execute the
\&\s-1ROM\s0 image.
.SH "MKELF-IMG"
.IX Header "MKELF-IMG"
\&\fBmkelf-img\fR makes a boot image from an Etherboot \f(CW\*(C`.img\*(C'\fR or \f(CW\*(C`.zimg\*(C'\fR
image.  This allows it to be netbooted using an existing \s-1ROM\s0. This is
useful for developing Etherboot drivers or to load a newer version of
Etherboot with an older one.
.PP
Run mkelf-img like this:
.PP
mkelf-img nic.zimg > nic.nb
.PP
Move \fInic.nb\fR to where the network booting process expects to find it.
The boot \s-1ROM\s0 will load this as the \fIoperating system\fR and execute the
image.
.PP
Note that this does not test the \s-1ROM\s0 loader portion that's in a \f(CW\*(C`.z?rom\*(C'\fR
image, but not in a \f(CW\*(C`.z?img\*(C'\fR.
.SH "MKELF-MENU"
.IX Header "MKELF-MENU"
\&\fBmkelf-menu\fR and \fBmknbi-menu\fR make a boot image from an auxiliary menu
program. Etherboot has the ability to load an auxiliary program which
can interact with the user, modify the \s-1DHCP\s0 structure, and return a
status.  Based on the status, Etherboot can load another binary, restart
or exit.  This makes it possible to have elaborate user interface
programs without having to modify Etherboot. The specification for
auxiliary program is documented in the Etherboot Developer's Manual.
.PP
\&\fBmkelf-menu\fR and \fBmknbi-menu\fR take a binary named \f(CW\*(C`menu\*(C'\fR from the
library directory, which is assumed to have an entry point of 0x60000.
An optional argument is accepted, and this is loaded at 0x80000. This
can be a data file used by the menu program.
.PP
Currently, the menu binary provided duplicates the builtin menu facility
of Etherboot with the exception of a couple of small differences: no
server or gateway specifications are used and nested \s-1TFTP\s0 loads don't
work. You should not have \s-1MOTD\s0 or \s-1IMAGE_MENU\s0 defined in your Etherboot
build to be able to use this external menu binary. The specifications of
the \s-1DHCP\s0 option required is in the vendortags document in the Etherboot
user manual.
.PP
Typical usage is like this:
.PP
mkelf-menu > menu.nb
.PP
Then put menu.nb in the \s-1TFTP\s0 boot directory and edit your \s-1DHCP\s0 options
according to the documentation.
.PP
Alternate user interface programs are highly encouraged.
.SH "MKELF-NFL"
.IX Header "MKELF-NFL"
\&\fBmkelf-nfl\fR and \fBmknbi-nfl\fR make a boot image from the \s-1NFL\s0 menu
program. This menu program takes the names of images from a
menu-text-file file which just contains lines with the filenames
(relative to the tftpd root directory) of images to load. The
user-interface is a light\-bar, similar to that used in \s-1GRUB\s0.  There is a
sample menu-text-file in \f(CW\*(C`menu\-nfl.eg\*(C'\fR. The special entry \*(L"Quit
Etherboot\*(R" (without quotes, of course) can be used in menu-text-files
as an entry that causes Etherboot to quit and return to the invoking
environment, which is the \s-1BIOS\s0 in the case of ROMs.
.PP
Typical usage is:
.PP
mkelf-nfl \fImenu-text-file\fR > nfl.nb
.PP
Then put nfl.nb in the \s-1TFTP\s0 boot directory and specify as the boot
image. Chaining to other menus works.
.PP
Enhancements to the menu format accepted to specify other features such
as titles, timeout, colours, and so forth are highly encouraged.
.SH "MKELF-LUA"
.IX Header "MKELF-LUA"
\&\fBmkelf-lua\fR makes an \s-1ELF\s0 image from a precompiled Lua
(\f(CW\*(C`http://www.tecgraf.puc\-rio.br/lua/\*(C'\fR) program.
.PP
Typical usage is:
.PP
mkelf-lua hello.lb > luaprog.nb
.PP
where \f(CW\*(C`hello.lb\*(C'\fR was generated from a Lua program by:
.PP
luac \-o hello.lb hello.lua
.PP
The functions available to Lua programs in this environment is described
in a separate document.
.SH "MKNBI-FDOS"
.IX Header "MKNBI-FDOS"
\&\fBmknbi-fdos\fR makes a boot image from a FreeDOS kernel file and a floppy
image.  Note that the kernel image is not read from the floppy section
of the boot image, but is a separate section in the boot image. The
bootloader has been adjusted to jump to it directly. This means the
space that would be taken up on the \fIfloppy\fR by the kernel image file
can now be used for applications and data.
.PP
Obtain a distribution of FreeDOS with a recent kernel, probably at least
2006. It has been tested with 2012 but nothing older. You can get the
FreeDOS kernel here:
.PP
\&\f(CW\*(C`http://freedos.sourceforge.net/\*(C'\fR
.PP
Follow the instructions to make a bootable floppy. Then get an image
of the floppy with:
.PP
dd if=/dev/fd0 of=/tmp/floppyimage
.PP
Also extract \fIkernel.sys\fR from the floppy. You can do this from the
image using the mtools package, by specifying a file as a \fIdrive\fR
with a declaration like this in \fI~/.mtoolsrc\fR:
.PP
drive x: file=\*(L"/tmp/floppyimage\*(R"
.PP
Then run:
.PP
mcopy x:kernel.sys .
.PP
Then run mknbi by:
.PP
mknbi-fdos kernel.sys /tmp/floppyimage > freedos.nb
.PP
where \fIkernel.sys\fR and \fI/tmp/floppyimage\fR are the files extracted above.
Then move \fIfreedos.nb\fR to where the network booting process expects to
find it.
.PP
If you have got it to netboot successfully, then you can go back and
add your files to the floppy image. You can delete \fIkernel.sys\fR in
the floppy image to save space, that is not needed. Note that you can
create a floppy image of any size you desire with the mformat program
from mtools, you are not restricted to the actual size of the boot floppy.
.SH "MKNBI-FDOS OPTIONS"
.IX Header "MKNBI-FDOS OPTIONS"
\&\fB\-\-harddisk\fR Make the boot ramdisk the first hard disk, i.e. C:. One
reason you might want to do this is because you want to use the real
floppy. The limit on \*(L"disk size\*(R" in the boot image is not raised by this
option so that is not a reason to use this option. This option is
incompatible with \-\-disableharddisk.
.PP
\&\fB\-\-disableharddisk\fR When the ramdisk is simulating a floppy disk drive,
this switch will disable hard disk accesses.  This is necessary if the
client should use a network file system as drive C:, which is only
possible if there are no hard disks found by \s-1DOS\s0. This option is
incompatible with \-\-harddisk.
.PP
\&\fB\-\-nosquash\fR Do not try to chop unused sectors from the end of the
floppy image. This increases the boot image size and hence loading
time if the \s-1FAT\s0 filesystem on the floppy is mostly empty but you may
wish to use this option if you have doubts as to whether the squashing
algorithm is working correctly.
.PP
\&\fB\-\-rdbase=\fR\fI0xNNNNNNNN\fR Set the ramdisk load address. The default
load address for the ramdisk is 0x110000. It can be moved higher
(lower will not work) if for some reason you need to load other stuff
at the address it currently occupies. As this is a linear address and
not a segment address, the last 4 bits are not used and should be 0.
.SH "MKNBI-DOS"
.IX Header "MKNBI-DOS"
\&\fBmknbi-dos\fR makes a boot image from a floppy image containing a
bootable \s-1DOS\s0 filesystem.  It is not necessary to build the filesystem on
a physical floppy if you have the mtools package, but you need a
bootable floppy of any size to start with. First extract the boot block
from the floppy, this boot block must match the \s-1DOS\s0 kernel files you
will copy in the next step:
.PP
dd if=/dev/fd0 of=bootblock bs=512 count=1
.PP
Then get the \s-1DOS\s0 kernel files (this is correct for \s-1DR\-DOS\s0, the names
are different in \s-1MS\-DOS\s0, \s-1IO\s0.SYS and \s-1MSDOS\s0.SYS):
.PP
mcopy a:IBMBIO.COM a:IBMDOS.COM a:COMMAND.COM .
.PP
Next make an entry in \fI~/.mtoolsrc\fR to declare a floppy to be mapped
to a file:
.PP
drive x: file=\*(L"/tmp/floppyimage\*(R"
.PP
Now format a floppy of the desired size, in this example a 2.88 \s-1MB\s0 floppy,
at the same time writing the bootblock onto it:
.PP
mformat \-C \-t 80 \-s 36 \-h 2 \-B bootblock x:
.PP
The size of the \*(L"floppy\*(R" is only limited by the limits on the number of
cylinders, sectors and heads, which are 1023, 63 and 255 respectively,
and the amount of \s-1RAM\s0 you are willing to allocate to the \*(L"floppy\*(R" in
memory. As \s-1RAM\s0 is precious, choose a size slightly bigger than what is
needed to hold your \*(L"floppy\*(R" files.
.PP
Finally, copy all your desired files onto the floppy:
.PP
mcopy \s-1IBMBIO\s0.COM x:
.PP
mcopy \s-1IBMDOS\s0.COM x:
.PP
mcopy \s-1COMMAND\s0.COM x:
.PP
mcopy \s-1CONFIG\s0.SYS \s-1AUTOEXEC\s0.BAT \s-1APP\s0.EXE \s-1APP\s0.DAT ... x:
.PP
For MS-DOS substitute \s-1IO\s0.SYS for \s-1IBMIO\s0.COM, and \s-1MSDOS\s0.SYS for
\&\s-1IBMDOS\s0.COM.  The case of the files must be preserved, it may not work if
\&\s-1VFAT\s0 lower case names are generated in the floppy image.  Pay attention
to the order of copying as the boot block may expect the first two
entries on a newly formatted disk to be \s-1IO\s0.SYS, \s-1MSDOS\s0.SYS.  Possibly too
\&\s-1COMMAND\s0.COM has to be the third entry so we play safe.  Thanks to Phil
Davey and Phillip Roa for these tips.
.PP
I have reports that the bootblock of MS-DOS 6.22 sometimes fails to boot
the ramdisk.  You could try using the boot block from Netboot instead of
getting the boot block off the floppy. I have provided this boot block
in the distribution as altboot.bin, and in source form as altboot.S and
boot.inc. One essential thing is to make \s-1IO\s0.SYS the first file on the
disk, or this bootblock will not work.
.PP
If you happen to have a media of the same size you could test if the
image is bootable by copying it onto the media, and then booting it:
.PP
dd if=/tmp/floppyimage of=/dev/fd0
.PP
Then run mknbi-dos over the image \fI/tmp/floppyimage\fR to create a
boot image:
.PP
mknbi-dos /tmp/floppyimage > dos.nb
.PP
Move \fIdos.nb\fR to where the network booting process expects to find it.
.SH "MKNBI-DOS OPTIONS"
.IX Header "MKNBI-DOS OPTIONS"
\&\fB\-\-harddisk\fR Make the boot ramdisk the first hard disk, i.e. C:. One
reason you might want to do this is because you want to use the real
floppy. The limit on \*(L"disk size\*(R" in the boot image is not raised by this
option so that is not a reason to use this option. This option is
incompatible with \-\-disableharddisk.
.PP
\&\fB\-\-disableharddisk\fR When the ramdisk is simulating a floppy disk drive,
this switch will disable hard disk accesses.  This is necessary if the
client should use a network file system as drive C:, which is only
possible if there are no hard disks found by \s-1DOS\s0. This option is
incompatible with \-\-harddisk.
.PP
\&\fB\-\-nosquash\fR Do not try to chop unused sectors from the end of the
floppy image. This increases the boot image size and hence loading
time if the \s-1FAT\s0 filesystem on the floppy is mostly empty but you may
wish to use this option if you have doubts as to whether the squashing
algorithm is working correctly.
.PP
\&\fB\-\-rdbase=\fR\fI0xNNNNNNNN\fR Set the ramdisk load address. The default
load address for the ramdisk is 0x110000. It can be moved higher
(lower will not work) if for some reason you need to load other stuff
at the address it currently occupies. As this is a linear address and
not a segment address, the last 4 bits are not used and should be 0.
.SH "BUGS"
.IX Header "BUGS"
Please report all bugs to Etherboot users mailing list:
<https://sourceforge.net/mail/?group_id=4233>
.SH "SEE ALSO"
.IX Header "SEE ALSO"
Etherboot tutorial at \f(CW\*(C`http://etherboot.sourceforge.net/\*(C'\fR Mtools package
is at \f(CW\*(C`http://wauug.erols.com/pub/knaff/mtools/\*(C'\fR Make sure you have a
recent version, the ability to map a drive to a file is not present in
old versions.
.SH "COPYRIGHT"
.IX Header "COPYRIGHT"
\&\fBmknbi\fR is under the \s-1GNU\s0 Public License
.SH "AUTHOR"
.IX Header "AUTHOR"
Ken Yap
.PP
mk{elf,nbi}\-nfl was contributed by Robb Main of Genedyne.
.SH "DATE"
.IX Header "DATE"
See man page footer for date and version. Sorry, not available in the
\&\s-1HTML\s0 version.