Page MenuHomeFreeBSD

Allow loader to boot from a device containing an ISO image

Authored by benno on Mar 30 2018, 11:04 PM.
Referenced Files
Unknown Object (File)
Thu, Apr 11, 6:15 PM
Unknown Object (File)
Thu, Apr 11, 4:02 PM
Unknown Object (File)
Thu, Apr 11, 4:02 PM
Unknown Object (File)
Thu, Apr 11, 3:59 PM
Unknown Object (File)
Thu, Apr 11, 3:58 PM
Unknown Object (File)
Thu, Apr 11, 3:19 PM
Unknown Object (File)
Mar 23 2024, 4:08 AM
Unknown Object (File)
Mar 7 2024, 10:28 AM



When booted using isoboot (see D14914) loader gets a bit confused because it can't work out where to boot from. This change teaches loader about ISO images and treats them as a partition format a-la GPT et al.

Test Plan

Boot an image using isoboot under BIOS and watch loader manage to find things like, y'know, the kernel.

Diff Detail

rS FreeBSD src repository - subversion
Lint Not Applicable
Tests Not Applicable

Event Timeline

I'm going to have to think about this. It seems like it's mixing up two different layers (filesystem and partition) in much the same way that ZFS is currently doing, but in a more annoying way.

Well an ISO image doesn't have a partition format per se. On top of that GPT doesn't have an established partition type for an ISO image. We could roll our own and plant it in there and go looking for that instead but it'd also imply that we had overlapping partition entries given that we're going to have the ESP entry pointing within the El Torito catalog and any ISO partition entry would be covering the entire disk including the GPT itself. I'm not sure whether that's going to make things complain or not.

This revision is now accepted and ready to land.Apr 2 2018, 1:16 AM
This revision was automatically updated to reflect the committed changes.