27 ms·

If I understand correctly, it just wraps an existing Linux driver in a container. You can hardly call that writing a driver.

• ncr100 2mo ago
  Would calling it a "driver adapter" fit more accurately .. ?
  • unregistereddev 2mo ago
    I don't think so, no. It does not appear to be functioning as an OSX device driver. It's just hosting a network print server in docker.
    • happyPersonR 2mo ago
      Tbh I actually like this even more than writing a driver … Makes it so if there’s an issue I don’t get a kernel panic Maybe it could write something CUPS compliant though ?
      • 05 2mo ago
        To be fair print drivers have mostly been user mode. On Windows since win2000, and on macOS - since macOS 10 Cheetah.
    • kuberwastaken 2mo ago
      It works with Cmd + P https://x.com/kuberwastaken/status/2089961185047437729 https://x.com/kuberwastaken/status/2089961185047437729
  • ASalazarMX 2mo ago
    Why not call it a containerized driver?