On 6/4/23 17:30, Chris Adams wrote:
Again, the DHCP request that gets a response "use this file" comes from
the firmware, not the OS.
It goes something like:
- BIOS/UEFI configured for network boot sends DHCP request
- DHCP server says "use this file (aka shim)"
- BIOS/UEFI loads that file and
On 6/4/23 17:12, Samuel Sieb wrote:
The part you're missing is that it isn't the OS that's sending the
DHCP request. It's the BIOS. There's no OS loaded yet, that's what
you're trying to boot.
The hardware definitely sends a DHCP request when it tries to PXE boot.
But when the OS actually lo
Once upon a time, Thomas Cameron said:
> I really wish that there was something in the OS that would identify
> itself when it sends a DHCP broadcast.
Again, the DHCP request that gets a response "use this file" comes from
the firmware, not the OS.
It goes something like:
- BIOS/UEFI configured
On 6/4/23 15:00, Thomas Cameron wrote:
I really wish that there was something in the OS that would identify
itself when it sends a DHCP broadcast. I've read up
The part you're missing is that it isn't the OS that's sending the DHCP
request. It's the BIOS. There's no OS loaded yet, that's wh
On 6/4/23 16:25, Barry wrote:
I have always seen this done by having tooling that read a database of hardware
mac addresses mapped to config.
With that setup you “just” edit the database to switch the os you want and
rebuild
your dhcpd/tftpd config.
Unfortunately, the vast majority of my syste
> On 4 Jun 2023, at 19:43, Thomas Cameron
> wrote:
>
> Or am I going about this the wrong way?
I have always seen this done by having tooling that read a database of hardware
mac addresses mapped to config.
With that setup you “just” edit the database to switch the os you want and
rebuild
Once upon a time, Joe Zeff said:
> On 06/04/2023 01:40 PM, Chris Adams wrote:
> >It'd be nice if there was a way to chainload one shim from another
>
> If memory serves, you could have GRUB boot Windows by giving it the
> command chainload +X, where X represented the number of sectors to
> load.
On 06/04/2023 01:40 PM, Chris Adams wrote:
It'd be nice if there was a way to chainload one shim from another
If memory serves, you could have GRUB boot Windows by giving it the
command chainload +X, where X represented the number of sectors to load.
I've no idea if GRUB2 still does this, b
Once upon a time, Thomas Cameron 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
On 6/4/23 14:40, Chris Adams wrote:
As far as I can tell, you cannot configure network boot for different
OSes in a UEFI Secure Boot environment. The shim is loaded first,
before you get to the point of choosing which kernel to boot, and a
given distribution's shim will only load other Linux thi
Once upon a time, Thomas Cameron said:
> Is it that the shim.efi file is signed for UEFI environments, and
> the RHEL kernel is expecting the signature for the RHEL shim.efi
> file? If so, how do I specify which shim.efi file I want to use
> based on the kernel? I would assume I'd need to add the
I am trying to kickstart multiple versions of Linux. Some of my systems
are BIOS based, and some are UEFI based.
I have a stanza in my dhcpd.conf file that looks like this:
class "pxeclients" {
match if substring (option vendor-class-identifier, 0, 9) =
"PXEClient";
ne
12 matches
Mail list logo
