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