xCAT/xcat-core
2
0
Fork 0
mirror of https://github.com/xcat2/xcat-core.git synced 2025-06-12 00:00:12 +00:00
Code Issues Releases Wiki Activity

Merge pull request #1262 from xuweibj/I846

Browse Source 
Fix issue 846, update mknb doc
This commit is contained in:
Victor Hu
2016-06-08 19:47:40 -04:00
parent d55964407f c519024679
commit 62a2dd804d
2 changed files with 12 additions and 13 deletions
Download Patch File Download Diff File Expand all files Collapse all files

12
docs/source/guides/admin-guides/references/man8/mknb.8.rst
View File

@ -27,14 +27,14 @@ DESCRIPTION
***********
The \ **mknb**\ command is run by xCAT automatically, when xCAT is installed on the management node.
The \ **mknb**\ command is run by xCAT automatically when xCAT is installed on the management node.
It creates a network boot root image (used for node discovery, BMC programming, and flashing)
for the same architecture that the management node is. So you normally do not need to run the \ **mknb**\
command yourself.
for the same architecture that the management node is. So you normally do not need to run the
\ **mknb**\ command yourself.
If you do run \ **mknb**\ to add custom utilities to your boot root image, and you have an xCAT Hierarchical Cluster with service nodes that each have a local /tftpboot directory (site sharedtftp=0), you will also need to copy the generated root image to each service node.
If you make custom changes to the network boot root image, you will need to run \ **mknb**\ again to regenerate the diskless image to include your changes. If you have an xCAT Hierarchical Cluster with Service Nodes having local /tftpboot directories (site.sharedtftp=0), you will need to copy the generated root image to each Service Node.
Presently, only the arch x86_64 is supported.
Presently, the architectures x86_64 and ppc64 are supported. For ppc64le, use the ppc64 architecture.
*******
@ -45,7 +45,7 @@ OPTIONS
\ *arch*\
The hardware architecture for which to build the boot image: x86_64
The hardware architecture for which to build the boot image.

13
xCAT-client/pods/man8/mknb.8.pod
View File

@ -9,15 +9,14 @@ B<mknb> I<arch>
=head1 DESCRIPTION
The B<mknb> command is run by xCAT automatically, when xCAT is installed on the management node.
The B<mknb> command is run by xCAT automatically when xCAT is installed on the management node.
It creates a network boot root image (used for node discovery, BMC programming, and flashing)
for the same architecture that the management node is. So you normally do not need to run the B<mknb>
command yourself.
for the same architecture that the management node is. So you normally do not need to run the
B<mknb> command yourself.
If you do run B<mknb> to add custom utilities to your boot root image, and you have an xCAT Hierarchical Cluster with service nodes that each have a local /tftpboot directory (site sharedtftp=0), you will also need to copy the generated root image to each service node.
If you make custom changes to the network boot root image, you will need to run B<mknb> again to regenerate the diskless image to include your changes. If you have an xCAT Hierarchical Cluster with Service Nodes having local /tftpboot directories (site.sharedtftp=0), you will need to copy the generated root image to each Service Node.
Presently, only the arch x86_64 is supported.
Presently, the architectures x86_64 and ppc64 are supported. For ppc64le, use the ppc64 architecture.
=head1 OPTIONS
@ -25,7 +24,7 @@ Presently, only the arch x86_64 is supported.
=item I<arch>
The hardware architecture for which to build the boot image: x86_64
The hardware architecture for which to build the boot image.
=back