Looking to upgrade from an old Latitude, curious as to what mobile hardware you folks use for writing your open source projects?

    • jet@hackertalks.comEnglish
      4·
      8 months ago

      It’s an open source operating system, that looks for the best level of practical paranoia using virtual machines as a form of isolation between processes

      Because of virtual machine workloads, and the security requirements, it can be quite demanding on hardware, and also open source support. So if a laptop supports qubes it’ll support anything else

      • GolfNovemberUniform
        11·
        8 months ago

        Qubes is not fully FOSS afaik. Try something FSF-recommended to really test the compatibility

            • jet@hackertalks.comEnglish
              7·
              8 months ago

              I admire your level of purity, but your distinction is not helpful in laptop selection.

              I’m not aware of any FOSS operating system that only uses totally open source hardware drivers. even GNU HERD would run proprietary drivers if they actually ever finished.

              For Qubes, I’m not sure how you can have a better approach to isolating binary drivers, then running them in a totally contained virtual machine.

              Which operating system are you referring to without drivers?

              • Telorand@reddthat.com
                2·
                8 months ago

                I’m not super informed about the kernel layer, so forgive me if this is a silly question, but how does that approach compare to atomic distros like Fedora Kinoite, UniversalBlue, or NixOS?

                • jet@hackertalks.comEnglish
                  1·
                  8 months ago

                  It’s all about where you draw the abstraction layer in the hardware stack.

                  For Qubes / Xen its done at the Virtual Machine layer (pretending to be totally independent CPUs/RAM/Networks)

                  For Nix et al I believe they are using containers which draws the line of abstraction inside the Kernel (pretending to be different clean name spaces, but the same kernel is aware of what is running everywhere).

                  There are tradeoffs and different efficiencies for every different level of abstraction, for the most security sensitive applications you would want to run them on physically different computers, then the next step would be inside of different virtual machines (Xen/Qubes), then next step would be in different kernel name spaces (Containers/Nix), then process isolation with different virtual memory spaces (standard linux type processes you know and love)