Once upon a time, Thomas Cameron <thomas.cameron@xxxxxxxxxxxxxxx> said: > Yeah, that's why I was hoping there was maybe some magic in the > vendor-class-identifier response that I could use. It would make > life a LOT easier. All the DHCP communication happens before shim is loaded (and then it's too late to change), so all you can see is the base hardware info. If you know your hardware, you could configure MAC addresses in your DHCP config to control the response, pointing to a different shim/config depending on which MAC is requesting. Otherwise, I suppose you might be able to do something odd like serve up one shim/config via TFTP and a different one via HTTP, so you could choose UEFI PXE for one OS and UEFI HTTP for the other. It would probably be confusing after the fact though. -- Chris Adams <linux@xxxxxxxxxxx> _______________________________________________ users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
