| 23 Mar 2026 |
 boop-north | Doesn't exist | 17:00:23 |
 K900 | And systemctl status nix-daemon? | 17:00:47 |
| boop-north | I don't think that exists either I'll have to check in a few minutes | 17:01:37 |
| boop-north | I'm AFK rn | 17:01:39 |
 toinux | 
Download image.png | 18:02:02 |
| toinux | This one seems more readable :|
| 18:02:04 |
| toinux | * This one seems more readable :D | 18:02:08 |
|  Display Name joined the room. | 18:22:30 |
| Display Name | Is Lix planning to support multi-user without systemd (just asking)? | 18:32:05 |
| Display Name | Sorry if it was too common of a question or I have misinterpreted the docs for the Lix installer | 18:33:10 |
 raitobezarius | That's not a goal we pursue but the features we may be using for multi-user are reasonably support-able, if you care about this, I suggest being in touch with Lix development to get a hang of which features we plan to depend on | 18:35:06 |
| Display Name | Okay | 18:35:32 |
| raitobezarius | OTOH: cgroup delegation xattrs, socket activation, nsresourced-like delegation of sub-uids (probably will take some time until it is required) | 18:35:34 |
| raitobezarius | Also: putting the daemon in a supervisor cgroup (we don't do it ourselves, so an init system would need to run the right dance to move things in the right hierarchy) | 18:36:01 |
| Display Name | May I ask, your an developer or part of the Lix team? (Just curious) | 18:37:23 |
| raitobezarius | I am part of the Lix core team | 18:37:32 |
| Display Name | Okay | 18:38:04 |
 neindochoh! / Seti (they/them) | sounds like a variant of https://git.lix.systems/lix-project/lix/issues/1112 perhaps? | 21:18:02 |
| 24 Mar 2026 |
| boop-north | btw I checked, neither of the services exist | 07:57:23 |
| boop-north | at all | 07:57:24 |
| boop-north | nix store ping ──(Tue,Mar24)─┘
Store URL: daemon
Version: 2.95.1
Trusted: 0
not sure if this is the issue or not | 08:00:01 |
| boop-north | it outputs this with and without the daemon running funnily enoıgh | 08:00:18 |
|  ralismark joined the room. | 10:57:10 |
|  Lotte (it/its)/Cinny (she/her) θΔ& changed their profile picture. | 12:14:57 |
| 25 Mar 2026 |
 adobo | hi! i've been trying to install Lix on an existing Nix installation, but I'm on MacOS 12, so I don't have /usr/lib/libc++.1.dylib, which makes the installation fail. I tried downloading libcxx through Nix and MacPorts to supply the libs, but I don't know how to point the installer to where those are | 04:12:56 |
 emily | it's normal to not have libraries in /usr/lib, those have been virtual for many releases. the problem is rather that Nixpkgs no longer supports macOS < 13 (and nor does Apple, even for security updates) | 04:19:27 |
| adobo | yeah, i know my version isn't supported anymore, but i was hoping i could still get some things to work | 04:23:08 |
| emily | OCLP is probably your best bet. (but note that x86_64-darwin support is being dropped by the end of the year too, and ofc every aarch64-darwin machine can run newer macOS) | 04:37:33 |
| adobo | ah okay, thank you! i'll look into it. unfortch i do have the intel chip 🫠 | 05:40:38 |
 niko | In reply to @raitobezarius:matrix.org
Also: putting the daemon in a supervisor cgroup (we don't do it ourselves, so an init system would need to run the right dance to move things in the right hierarchy) Are all of those required for the daemon or just nice to have and to guarantee everything runs as expected? E.g. uid delegation I guess would risk conflicts or something, or would Lix refuse to run without knowing about the delegates ranges? And I’d expect socket activation to not be required if someone is willing to just have the daemon running always. I know nothing about the daemon implementation | 17:45:16 |
