Currently, if both a filename and root-path are present, iPXE will hook the SAN device but will only attempt to boot from the filename. Change this behaviour so that both are attempted. Users who want to avoid booting from the SAN as a fallback can do so via the existing "skip-san-boot" setting. This allows for seamless deployment to a SAN target using Windows Deployment Services (and similar products). A user simply has to define the root-path option in DHCP and then use WDS to deploy the system. No further configuration should be required. Signed-off-by: Michael Brown <mcb30@ipxe.org>tags/v1.20.1
|
|
||
150 |
|
150 |
|
151 |
|
151 |
|
152 |
|
152 |
|
|
153 |
|
|
|
154 |
|
|
|
155 |
|
|
|
156 |
|
|
|
157 |
|
|
|
158 |
|
|
|
159 |
|
|
153 |
|
160 |
|
154 |
|
161 |
|
155 |
|
162 |
|
|
|
||
171 |
|
178 |
|
172 |
|
179 |
|
173 |
|
180 |
|
174 |
|
|
|
|
181 |
|
|
|
182 |
|
|
|
183 |
|
|
|
184 |
|
|
175 |
|
185 |
|
176 |
|
186 |
|
177 |
|
187 |
|
178 |
|
188 |
|
179 |
|
189 |
|
|
190 |
|
|
|
191 |
|
|
|
192 |
|
|
|
193 |
|
|
180 |
|
194 |
|
181 |
|
195 |
|
182 |
|
196 |
|
|
|
||
184 |
|
198 |
|
185 |
|
199 |
|
186 |
|
200 |
|
187 |
|
|
|
|
201 |
|
|
|
202 |
|
|
|
203 |
|
|
|
204 |
|
|
188 |
|
205 |
|
189 |
|
206 |
|
190 |
|
207 |
|
|
|
||
193 |
|
210 |
|
194 |
|
211 |
|
195 |
|
212 |
|
196 |
|
|
|
|
213 |
|
|
|
214 |
|
|
|
215 |
|
|
197 |
|
216 |
|
198 |
|
|
|
199 |
|
|
|
200 |
|
|
|
201 |
|
217 |
|
202 |
|
218 |
|
203 |
|
219 |
|
|
|
||
212 |
|
228 |
|
213 |
|
229 |
|
214 |
|
230 |
|
|
231 |
|
|
215 |
|
232 |
|
216 |
|
233 |
|
217 |
|
234 |
|