qyliss changed the topic of #spectrum to: A compartmentalized operating system | https://spectrum-os.org/ | Logs: https://logs.spectrum-os.org/spectrum/
nicoo has quit [Remote host closed the connection]
nicoo has joined #spectrum
nicoo has quit [Remote host closed the connection]
nicoo has joined #spectrum
maxdevjs has quit [Ping timeout: 265 seconds]
cole-h has quit [Quit: Goodbye]
<Profpatsch> qyliss: if you haven’t seen solo5, you should take a look at solo5 https://github.com/Solo5/solo5/blob/master/include/solo5/solo5.h
<Profpatsch> it defines a <10 “syscall” interface for *kernels to run on, basically main, write, read, net_read and net_write
<Shell> it's used under the hood by Mirage primarily, right?
<Profpatsch> plus yield
<Shell> I'm not really sure where you see this being used in Spectrum.
<Profpatsch> Shell: It’s one compilation target of Mirage, yes.
<Profpatsch> I don’t, I just want to mention it
<Shell> ah :)
<Profpatsch> It’s a general interface to run such kernels on, so if you want to add “native” support for *kernels to spectrum you probably want to use it
<Profpatsch> Also the authors are cool people
<ehmry> solo5 is cool because its super portable, if you can make it work with your application
cole-h has joined #spectrum
cole-h_ has joined #spectrum
cole-h_ has quit [Client Quit]
cole-h_ has joined #spectrum
Shell has left #spectrum ["WeeChat 2.8"]
cole-h_ has quit [Quit: Goodbye]
tilpner has quit [Remote host closed the connection]
tilpner has joined #spectrum
<cole-h> That last line... ;^)
<qyliss> :)
<cole-h> Will I finish setting up NixOS before the chromiumOS update comes out? Tune in on 19 May 2020 to find out!
<MichaelRaskin> No, setting up NixOS is a continuous process
<MichaelRaskin> But you do not need to have finished, just have it in a good enough state
<cole-h> *Will I get my system on-par with my old Arch setup before the chromiumOS update comes out?
<cole-h> :P
<hyperfekt> qyliss> Most VMs should not be able to give themselves extra memory this way -- really only the Wayland compositor should be using it. < does this mean that the host compositor goes into a VM, too? isn't it totally trusted anyway in all local administrator setups?
<MichaelRaskin> Well, it does raise the bar if the compositor only has access to rendered window contents and not directly to the tasty files. And Spectrum seems to be about raising the attack cost more than about optimising the TCB.
<MichaelRaskin> And as wl_roots simultaneously have fun tricks with pointers _in the API_, and segfaults, every bit matters.
<hyperfekt> less talking about window contents than being the arbiter of input. or is that not the case anymore with wayland?
<MichaelRaskin> Well, you only get the input until the next segfault!
<cole-h> My keywords went down :(
<MichaelRaskin> keywords?
<cole-h> Spam mail from devel@
<cole-h> "Re: re: my keywords went down" lol
<qyliss> cole-h: on it
<qyliss> that was actually caught by the spam filter hooked up to public-inbox, but not by mailman, heh
<cole-h> Yeah, swing that banhammer!
<qyliss> so let's make sure those are both using the same spamassassin thingy
<hyperfekt> MichaelRaskin: getting the input? more like giving the input.
<hyperfekt> MichaelRaskin: as long as i don't have a separate interface for administrating the system there's little point in isolating the one i do have
<MichaelRaskin> Well, you can switch VTs