Open TooDumbForAName opened 2 years ago
copy
commented
2 years ago Interesting idea, will probably do it just for the fun of it.
That said, the websockproxy is intentionally rate-limited, so most payloads will take too long to load. You can, however, point to third-party servers using url parameters (the server needs to send CORS headers), e.g.: https://copy.sh/v86/?fda.url=//builds.kolibrios.org/eng/data/data/kolibri.img&profile=custom
hello-smile6
commented
2 years ago Interesting idea, will probably do it just for the fun of it.
That said, the websockproxy is intentionally rate-limited, so most payloads will take too long to load. You can, however, point to third-party servers using url parameters (the server needs to send CORS headers), e.g.: https://copy.sh/v86/?fda.url=//builds.kolibrios.org/eng/data/data/kolibri.img&profile=custom
Could you parse ipxe disk images and find the URLs, then load them and boot using a custom config?
Adding an iPXE boot ROM might make testing operating systems easier, now or in the future. The user could point to their own files/script, or chainload netboot.xyz's script.
iPXE still supports the NE2000. There is some sort of warning message (a "read/write mishap"), but it does work...slowly.