Bryan Cantrill

Yeah, so I'm going to try to make RFD 82 public while we're in the podcast. So RFD 82 is not currently public, but I think it's a very good one to make public because that really captures, I think, an important aspect of your own approach and you're thinking about the way we ask different questions of different parts of the system.

Yeah, so I'm going to try to make RFD 82 public while we're in the podcast. So RFD 82 is not currently public, but I think it's a very good one to make public because that really captures, I think, an important aspect of your own approach and you're thinking about the way we ask different questions of different parts of the system.

So it's not, you know. I think I've just made it too public. Sorry.

So it's not, you know. I think I've just made it too public. Sorry.

Definitely made something public. So let's hope it's RFD 82. So you may or may not, it may take a second for the, this is like us, this is a terrific RFD API. So that may take a second, but hopefully people will be able to see that at some point real soon. Okay, so the... And I think, Robert, 82 is a great one in terms of your, again, your own kind of disposition. So maybe to kind of...

Definitely made something public. So let's hope it's RFD 82. So you may or may not, it may take a second for the, this is like us, this is a terrific RFD API. So that may take a second, but hopefully people will be able to see that at some point real soon. Okay, so the... And I think, Robert, 82 is a great one in terms of your, again, your own kind of disposition. So maybe to kind of...

just dive back down into some of these specific technical details of things that you've been dealing with recently. I mean, the T6 issue is a really interesting issue. I'm not sure if you're willing to get into the weeds on that one, but I do think that it's very concrete. How much do you know about this one, Adam? Have you...

just dive back down into some of these specific technical details of things that you've been dealing with recently. I mean, the T6 issue is a really interesting issue. I'm not sure if you're willing to get into the weeds on that one, but I do think that it's very concrete. How much do you know about this one, Adam? Have you...

Uh, in the current generation, current generation, part of me. So this is, um, in, in Gilmour.

Uh, in the current generation, current generation, part of me. So this is, um, in, in Gilmour.

So there's something... In stark contrast to the rest of the system where we are just like... Down the fairway. Down the fairway, exactly. It's like we also are a little weird with the neck. So welcome to Oxide.

So there's something... In stark contrast to the rest of the system where we are just like... Down the fairway. Down the fairway, exactly. It's like we also are a little weird with the neck. So welcome to Oxide.

Importantly, this means we're able to do this. This is not the SP running in some context before the host CPU is up. This is the host CPU is able to do this while it itself is up.

Importantly, this means we're able to do this. This is not the SP running in some context before the host CPU is up. This is the host CPU is able to do this while it itself is up.

Right. And this is like having the recovery path be the primary path, Adam. It's like this is so you don't you don't have this kind of path that you rarely execute that when you needed to execute doesn't work. And it also because this is a real problem with like Nix have gotten really, really complicated. And it's like, oh, by the way, there's another computer over there.

Right. And this is like having the recovery path be the primary path, Adam. It's like this is so you don't you don't have this kind of path that you rarely execute that when you needed to execute doesn't work. And it also because this is a real problem with like Nix have gotten really, really complicated. And it's like, oh, by the way, there's another computer over there.

I mean, it's not really clear like who's in charge of the system anyway. And especially with like, you know, smart necks, they're being pretty overt about like, no, I've got my own CPU. I've got like, I load my own OS image. And it's like, no, no, no, we don't want any of that.

I mean, it's not really clear like who's in charge of the system anyway. And especially with like, you know, smart necks, they're being pretty overt about like, no, I've got my own CPU. I've got like, I load my own OS image. And it's like, no, no, no, we don't want any of that.

We want to actually be, we want to have all this information flow in a way that it's attestable, that we know exactly what we're putting out there, where we're So we don't want that level of autonomy out of the system. We don't want this thing for a bunch of reasons. Security, reliability, a bunch of things. So...

We want to actually be, we want to have all this information flow in a way that it's attestable, that we know exactly what we're putting out there, where we're So we don't want that level of autonomy out of the system. We don't want this thing for a bunch of reasons. Security, reliability, a bunch of things. So...