!pbdtvoHxUGLhcEvnlu:nixos.org

Exotic Nix Targets

353 Members
111 Servers

Load older messages


SenderMessageTime
25 Mar 2023
@matthewcroughan:defenestrate.itmatthewcroughan - nix.howthat systemd timer could even pop up a UI object that says "Do you wan to update" and wait for a dbus response or something12:47:44
@matthewcroughan:defenestrate.itmatthewcroughan - nix.how * that systemd timer could even pop up a UI object that says "Do you want to update" and wait for a dbus response or something12:47:48
@7c6f434c:nitro.chat7c6f434c
In reply to @matthewcroughan:defenestrate.it
Is it a good idea to nixos-rebuild on a raspberry pi? It's kind of up to the user, for sure
I think RPi is easier to cool, though…
12:47:51
@matthewcroughan:defenestrate.itmatthewcroughan - nix.howI mean, one of the benefits for me of running Mobile NixOS was going to be the CPU control12:48:09
@matthewcroughan:defenestrate.itmatthewcroughan - nix.howrunning at low MHz always, to get the best possible battery12:48:33
@matthewcroughan:defenestrate.itmatthewcroughan - nix.howI don't need much CPU!12:48:35
@7c6f434c:nitro.chat7c6f434cHm OK, if you have a ton of RAM and just do the rebuilds at slow rates in background and you can have the cache just for the big packages…12:49:20
@matthewcroughan:defenestrate.itmatthewcroughan - nix.how yeah you could even have the rebuild switch happen in a systemd service with very very very low resources in a slice 12:49:58
@7c6f434c:nitro.chat7c6f434c
In reply to @matthewcroughan:defenestrate.it
running at low MHz always, to get the best possible battery
Pretty sure that CPUs are designed to make this is not the best possible battery, but nothing has enough load control to make the design come true
12:50:06
@matthewcroughan:defenestrate.itmatthewcroughan - nix.how1cpu 512M memory12:50:08
@7c6f434c:nitro.chat7c6f434cUhm, let me count the ways 512MiB is not enough for nixos-rebuild12:50:30
@matthewcroughan:defenestrate.itmatthewcroughan - nix.hownix evaluation right?12:50:37
@matthewcroughan:defenestrate.itmatthewcroughan - nix.howIt would be enough if we could share the eval cache, something I know is not secure at the moment 12:50:49
@matthewcroughan:defenestrate.itmatthewcroughan - nix.howAnd that is a design proposal, to be able to share eval cache12:51:13
@7c6f434c:nitro.chat7c6f434cNot sure how well NixOS module system would work for sharing eval caches between non-identical systems 12:51:22
@matthewcroughan:defenestrate.itmatthewcroughan - nix.howYeah me neither, I'm just thinking there are no limitations and what the design would look like without limitations 12:51:41
@7c6f434c:nitro.chat7c6f434cI mean, I don't like NixOS modules for any of the other reasons either…12:51:59
@matthewcroughan:defenestrate.itmatthewcroughan - nix.how to me, the perfect setup is nix running everywhere for every purpose, to keep everything isomorphic 12:52:00
@7c6f434c:nitro.chat7c6f434cI kind of want enough RAM to run Nix evaluation on almost everything, that's true…12:52:52
@7c6f434c:nitro.chat7c6f434cBut for many purposes I am mostly fine with Nix-on-whatever12:53:15
@7c6f434c:nitro.chat7c6f434c(Assuming a somewhat clueless but not too malicious and already platform-adapted carrier system)12:53:53
@matthewcroughan:defenestrate.itmatthewcroughan - nix.how
In reply to @7c6f434c:nitro.chat
I kind of want enough RAM to run Nix evaluation on almost everything, that's true…
No I mean sharing eval cache would prevent that from being a problem, optionally
12:56:19
@matthewcroughan:defenestrate.itmatthewcroughan - nix.howthere are ways we can keep it isomorphic just by messing around with caches and stuff, and fix these problems just like that 12:56:39
@7c6f434c:nitro.chat7c6f434cIf you give up on «actually can eval anywhere», I won't call Nix the ideal setup. Maybe looking at what Guix did, noticing it is still not the best direction, and designing a new Nix-like-tolerable-on-low-RAM without giving up on data-crunching-completeness…12:58:39
@matthewcroughan:defenestrate.itmatthewcroughan - nix.howI quite like the idea of hosting the top level closures somewhere like latest.mysytem.com and then having systemd pull it down on a regular basis and activate it13:01:24
@7c6f434c:nitro.chat7c6f434c(I am not saying I have a coherent vision how it would be, not yet)13:01:26
@matthewcroughan:defenestrate.itmatthewcroughan - nix.howThere's no nix involved in that13:01:29
@7c6f434c:nitro.chat7c6f434cWell, without Nix usable for configuration…13:01:42
@7c6f434c:nitro.chat7c6f434cI guess the next level is a cheap subscription service where you can fine-tune your system and add the closure to the update service… Given Nix deduplication, it won't scale too badly13:03:45
@matthewcroughan:defenestrate.itmatthewcroughan - nix.howI don't really get it, you can self host all this super easy13:04:59

Show newer messages


Back to Room ListRoom Version: 6