Sorry this might be an extremely stupid question, but can you please explain the benefits of this and what other (larger?) alternatives are?
I understand that this "exokernel" provides more performant hardware access for software and it seems to be written from scratch in assembler.
Does this mean that one should expect a lot of security and robustness issues, which means it should only be used for internal services and never be exposed to untrusted networks?
Does look alien. When Going to http://baremetal.returninfinity.com/ one can only see some b0rken plaintext in the browser:
GET / HTTP/1HTTP/1.0 404 Not Found
Server: BareMetal
Content-type: text/html
<!DOCTYPE html>
<html>
<head>
<title>404</title>
</head>
<body>
<p>404 - Not found</p>
</boGET / HTTP/1Wow, that's some nostalgia for me. I remember encountering BareMetalOS and its bootloader Pure64 back when I still lurked the OSDev.org forums, probably more than 15 years ago at this point. Glad to see you're still at it!
Given that this is (AFAICT) a way to efficiently run exactly one program on a machine (probably a VM), I would have liked to see more time spent on the particulars of getting a program running on it. Like, can you easily run existing software on BareMetal? Could you compile nginx to run on it? Or does software have to be written specifically for this environment? And either way, how exactly do you actually build your software for/into(?) the image?