Not done yet

joe Linux is in beta. This is what is missing, so you know before you install it.

Installing

  • No Secure Boot. Turn it off in your firmware to start the medium.
  • No resizing, no encryption. The installer uses free space beside another system, or erases a whole disk. It does not shrink other systems’ partitions (make the room in that system first), and does not encrypt the disk.
  • No initramfs. joe starts without one, which is enough for internal disks but not for encrypted roots or roots spread over several devices.

Real hardware

Firmware, processor microcode, Wi-Fi (through NetworkManager and wpa_supplicant) and the Intel, AMD and NVIDIA graphics drivers are there, but have been tried on few machines. The hardware list has the ones it has run on.

Mesa supplies Vulkan drivers for Intel, AMD, virtio and software rendering. The software path has been tried; hardware Vulkan has not. Video is decoded on the GPU through VA-API with Mesa’s drivers (AMD, nouveau, virtual machines), but Intel’s VA-API driver is not packaged.

The desktop

  • No graphical front end to dave: upgrades are sudo dave upgrade and a restart.
  • Only the English (US) locale is built, so it is the one language the first-run setup offers.
  • No mail client. LibreOffice is in the repository but not installed by default.
  • Not built yet: WebKitGTK and its applications, Chromium, QtWebEngine and Thunderbird.

The security model

  • Declarations beyond the desktop. The desktop’s privileged services and set-uid programs declare their own operations, but the services of the rest of the repository (web servers, databases and the like) and the one-shot services of boot are still undeclared and receive all from systemd. Printing, Bluetooth, modems and ssh logins are declared from their upstream units but not yet tested.
  • D-Bus services without a unit. A system bus service that systemd does not start, cups-pk-helper among them, cannot be started over D-Bus.
  • The rest of the trust chain. Kernel modules are checked by the security module but not by the kernel’s own signature enforcement. There is no kernel lockdown and no Secure Boot, so root can still replace the kernel or its command line.
  • Software built on the machine cannot be signed yet.
  • Other interpreters. awk, sed and perl do not ask the module before running a script; bash and Python do.

Packages and builds

  • No split packages. A package is everything its upstream installs, so the base system carries the compiler.
  • Builds are not isolated from each other. Every recipe builds in one shared build root. A fresh, minimal build root per package, chosen by the solver, comes later.
  • Not every build is offline. Some recipes still fetch their locked Rust, Go, Haskell, JavaScript or Java dependencies from the network while building, until those are kept as sources of their own.
  • dave is not yet built by joe. joe packages Zig 0.17.1 now, but the dave package is still the static binary built on the build machine.
  • No virtual packages (provides), and no changing the kernel on a running system: that is what dave upgrade is for.