Implement console ioctl with com = 0x20007461

[SuchAFuriousDeath]

Now that we know what it is, it should be fairly easy.

[SuchAFuriousDeath]

@ultimaweapon Actually, do we really need to implement this? Probably not, right?

[ultimaweapon]

We should implement everything that we can.

[SuchAFuriousDeath]

Right. But currently this just mutates some sort of an internal state and then nothing touches that state again (at least yet). So right now, implementing this doesn't help us at all.

[ultimaweapon]

If there are other things we can do and it has more priority than this one then do that one first.

[SuchAFuriousDeath]

@ultimaweapon Now that we know what the console is... maybe we should create a separate window with a terminal for it?

[ultimaweapon]

If you are willing to work with Qt.

[SuchAFuriousDeath]

Maybe later :D

[SuchAFuriousDeath]

And what if just the kernel were running?

[ultimaweapon]

It's just a normal stderr.

[SuchAFuriousDeath]

By the way, wouldn't it be better to create sort of a wrapper type for all the strings that are actually arrays in FreeBSD? We could use const generics. It would be faster and more explicit and may even prevent us from making some mistake in the future.

[ultimaweapon]

Good idea. I think there should be a crate for this so better to check first.

[SuchAFuriousDeath]

I found arraystring, but the documentation says that it's not using const generics.

[ultimaweapon]

Seems like we need to implement this by our self.

[SuchAFuriousDeath]

By the way, after syscall 602, what's the game doing for you? The same as before? Mine is doing this:

[ultimaweapon]

That is an expected behavior.

[SuchAFuriousDeath]

I thought so, just making sure

[SuchAFuriousDeath]

By the way, is there a reason or threads don't have a proc field, like FreeBSD?

[ultimaweapon]

Because we only have one proc so no point to put it there.

[SuchAFuriousDeath]

The reason I'm asking is that passing a &Arc to Dmem1 felt really weird

[SuchAFuriousDeath]

Superseded by #795