Вы не можете выбрать более 25 тем Темы должны начинаться с буквы или цифры, могут содержать дефисы(-) и должны содержать не более 35 символов.

branding.h 5.7KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174
  1. #ifndef CONFIG_BRANDING_H
  2. #define CONFIG_BRANDING_H
  3. /** @file
  4. *
  5. * Branding configuration
  6. *
  7. */
  8. FILE_LICENCE ( GPL2_OR_LATER_OR_UBDL );
  9. #include <config/defaults.h>
  10. /*
  11. * Branding
  12. *
  13. * Vendors may use these strings to add their own branding to iPXE.
  14. * PRODUCT_NAME is displayed prior to any iPXE branding in startup
  15. * messages, and PRODUCT_SHORT_NAME is used where a brief product
  16. * label is required (e.g. in BIOS boot selection menus).
  17. *
  18. * To minimise end-user confusion, it's probably a good idea to either
  19. * make PRODUCT_SHORT_NAME a substring of PRODUCT_NAME or leave it as
  20. * "iPXE".
  21. *
  22. */
  23. #define PRODUCT_NAME ""
  24. #define PRODUCT_SHORT_NAME "iPXE"
  25. #define PRODUCT_URI "http://ipxe.org"
  26. /*
  27. * Tag line
  28. *
  29. * If your PRODUCT_SHORT_NAME is longer than the four characters used
  30. * by "iPXE", then the standard tag line "Open Source Network Boot
  31. * Firmware" is unlikely to fit neatly onto the screen.
  32. */
  33. #define PRODUCT_TAG_LINE "Open Source Network Boot Firmware"
  34. /*
  35. * Error messages
  36. *
  37. * iPXE error messages comprise a summary error message
  38. * (e.g. "Permission denied") and a 32-bit error number. This number
  39. * is incorporated into an error URI such as
  40. *
  41. * "No such file or directory (http://ipxe.org/2d0c613b)"
  42. *
  43. * or
  44. *
  45. * "Operation not supported (http://ipxe.org/3c092003)"
  46. *
  47. * Users may browse to the URI within the error message, which is
  48. * provided by a database running on the iPXE web site
  49. * (http://ipxe.org). This database provides details for all possible
  50. * errors generated by iPXE, including:
  51. *
  52. * - the detailed error message (e.g. "Not an OCSP signing
  53. * certificate") to complement the summary message (e.g. "Permission
  54. * denied") which is compiled into the iPXE binary.
  55. *
  56. * - an instruction to the user to upgrade, if the error cannot be
  57. * generated by the latest version of iPXE.
  58. *
  59. * - hints on how to fix the error (e.g. "This error indicates that
  60. * the file was not found on the TFTP server. Check that you can
  61. * retrieve the file using an alternative TFTP client, such as
  62. * tftp-hpa on Linux.")
  63. *
  64. * - details of which source file within the iPXE codebase generated
  65. * the error.
  66. *
  67. * - a direct link to the line(s) of code which generated the error.
  68. *
  69. * If you have a customer support team and would like your customers
  70. * to contact your support team for all problems, instead of using the
  71. * existing support infrastructure provided by http://ipxe.org, then
  72. * you may define a custom URI to be included within error messages.
  73. *
  74. * Note that the custom URI is a printf() format string which must
  75. * include a format specifier for the 32-bit error number.
  76. */
  77. #define PRODUCT_ERROR_URI "http://ipxe.org/%08x"
  78. /*
  79. * Command help messages
  80. *
  81. * iPXE command help messages include a URI constructed from the
  82. * command name, such as
  83. *
  84. * "See http://ipxe.org/cmd/vcreate for further information"
  85. *
  86. * The iPXE web site includes documentation for the commands provided
  87. * by the iPXE shell, including:
  88. *
  89. * - details of the command syntax (e.g. "vcreate --tag <tag>
  90. * [--priority <priority>] <trunk interface>").
  91. *
  92. * - example usages of the command (e.g. "vcreate --tag 123 net0")
  93. *
  94. * - a formal description of the command (e.g. "Create a VLAN network
  95. * interface on an existing trunk network interface. The new network
  96. * interface will be named by appending a hyphen and the VLAN tag
  97. * value to the trunk network interface name.")
  98. *
  99. * - details of the possible exit statuses from the command.
  100. *
  101. * - links to documentation for related commands (e.g. "vdestroy")
  102. *
  103. * - links to documentation for relevant build options (e.g. "VLAN_CMD").
  104. *
  105. * - general hints and tips on using the command.
  106. *
  107. * If you want to provide your own documentation for all of the
  108. * commands provided by the iPXE shell, rather than using the existing
  109. * support infrastructure provided by http://ipxe.org, then you may
  110. * define a custom URI to be included within command help messages.
  111. *
  112. * Note that the custom URI is a printf() format string which must
  113. * include a format specifier for the command name.
  114. *
  115. * [ Please also note that the existing documentation is licensed
  116. * under Creative Commons terms which require attribution to the
  117. * iPXE project and prohibit the alteration or removal of any
  118. * references to "iPXE". ]
  119. */
  120. #define PRODUCT_COMMAND_URI "http://ipxe.org/cmd/%s"
  121. /*
  122. * Setting help messages
  123. *
  124. * iPXE setting help messages include a URI constructed from the
  125. * setting name, such as
  126. *
  127. * "http://ipxe.org/cfg/initiator-iqn"
  128. *
  129. * The iPXE web site includes documentation for the settings used by
  130. * iPXE, including:
  131. *
  132. * - details of the corresponding DHCP option number.
  133. *
  134. * - details of the corresponding ISC dhcpd option name.
  135. *
  136. * - examples of using the setting from the iPXE command line, or in
  137. * iPXE scripts.
  138. *
  139. * - examples of configuring the setting via a DHCP server.
  140. *
  141. * - a formal description of the setting.
  142. *
  143. * - links to documentation for related settings.
  144. *
  145. * - links to documentation for relevant build options.
  146. *
  147. * - general notes about the setting.
  148. *
  149. * If you want to provide your own documentation for all of the
  150. * settings used by iPXE, rather than using the existing support
  151. * infrastructure provided by http://ipxe.org, then you may define a
  152. * custom URI to be included within setting help messages.
  153. *
  154. * Note that the custom URI is a printf() format string which must
  155. * include a format specifier for the setting name.
  156. *
  157. * [ Please also note that the existing documentation is licensed
  158. * under Creative Commons terms which require attribution to the
  159. * iPXE project and prohibit the alteration or removal of any
  160. * references to "iPXE". ]
  161. */
  162. #define PRODUCT_SETTING_URI "http://ipxe.org/cfg/%s"
  163. #include <config/local/branding.h>
  164. #endif /* CONFIG_BRANDING_H */