<dtz>
lol yeah musl-cross-make is goodness. Are you doing something re:musl -- and having problems?
<dtz>
oh, some problems where setting localSystem or crossSystem isn't viable? hmm
<angerman>
?
mbrgm has quit [Ping timeout: 256 seconds]
mbrgm has joined #nixos-dev
<dtz>
oh sounded like y'all were interested in MCM and sounded like something I could help with--or would like to be aware of problems at the least :)
tomberek has joined #nixos-dev
<tomberek>
has anyone managed a NixOS machine using nixops itself? (deployment.targetHost = "localhost";)
<tomberek>
does that work?
<gchristensen>
I wouldn't recommend it
<gchristensen>
makes it hard to do `nixos-rebuild boot` like things
<tomberek>
gchristensen: my alternative is to just copy my .nix files over to /etc/nixos seems kludgey
<simpson>
tomberek: Sounds risky. Once a machine is managed by nixops, it is no longer a pet, but cattle.
<tomberek>
simpson: what do you mean?
<simpson>
I mean that the machine is not suitable for use as, say, a development laptop. IMO.
<tomberek>
simpson: what abilities do you lose? can't you perform a `nixos-rebuild` to bring it back? perform `nix-env`?
<simpson>
Yeah, but then what was the original point?
<simpson>
(Some nix-env stuff still works under nixops-created users, in particular for root.)
<simpson>
(...well, not by default, but it can be made to work, especially when debugging/rescuing)
<tomberek>
simpson: my particular use case is a collection of TinkerBoards (basically a powerful RPi). I started managing them one by one, but after a few that only differ in a few slight settings and hostnames, I'm starting to try to manage them centrally.
<tomberek>
sometimes they are disconnected and would have to be managed individually, hence my interest in if it would work (or what difficulties would come up) if i just had the state shared with them, and then manage themselves on occasion.
<simpson>
Oh. Totally, that's a possibility. I've been thinking about this kind of thing; I want something more meshy. clever's got some tech too for managing embedded boards.
<tomberek>
simpson: I'm using tinc to mesh-VPN them, it has worked out very well. I can move them around networks, wifi, etc. and as long as you have a single publicly accessible node, the mesh punches through LANs as well as discovering local neighbors
<simpson>
tinc is pretty cool. I want the next level; I want content-addressed stuff.
<tomberek>
simpson: I've seen a few steps in nix to do content-addressing, but i'm not sure how to make good use of it. What were you thinking of?
<simpson>
tomberek: Ultimately, NDN directly over the mesh topology, at the level of Ethernet frames. I hear there's research into it.
adisbladis has joined #nixos-dev
pxc1 has joined #nixos-dev
pxc1 has quit [Ping timeout: 265 seconds]
orivej has quit [Ping timeout: 248 seconds]
tomberek has quit [Quit: Page closed]
adisbladis has quit [Read error: Connection reset by peer]
Synthetica has joined #nixos-dev
pxc has quit [Ping timeout: 256 seconds]
pxc1 has joined #nixos-dev
__Sander__ has joined #nixos-dev
pxc1 has quit [Ping timeout: 276 seconds]
goibhniu has joined #nixos-dev
jtojnar has quit [Read error: Connection reset by peer]
jtojnar has joined #nixos-dev
jtojnar has quit [Read error: Connection reset by peer]
jtojnar has joined #nixos-dev
tv has joined #nixos-dev
jtojnar has quit [Read error: Connection reset by peer]
jtojnar_ has joined #nixos-dev
jtojnar_ has quit [Quit: jtojnar_]
jtojnar has joined #nixos-dev
ckauhaus has joined #nixos-dev
aminechikhaoui has quit [Ping timeout: 240 seconds]
<gchristensen>
from a user: "fyi: I :heart_eyes: that nixos/nixpkgs is up on github as one project. that was one of the deciding factors for switching from Arch :smile:"
<LnL>
ou:w
__Sander__ has quit [Quit: Konversation terminated!]
<dtz>
:D
JosW has joined #nixos-dev
<Sonarpulse>
peti: see my ping on --extra-framework-dirs?
infinisil has quit [Quit: Configuring ZNC, sorry for the joins/quits!]
infinisil has joined #nixos-dev
Synthetica has quit [Quit: Connection closed for inactivity]
JosW has quit [Quit: Konversation terminated!]
<dtz>
Sonarpulse: is there a preference re:setting "platforms" to something, as opposed to omitting it if "should" work everywhere?
<Sonarpulse>
dtz: maybe? :)
<Sonarpulse>
what are you thinking?
<Sonarpulse>
I thankfully got rid of everything but system, config, parsed, platform, and a few things of my own creation (like useAndroidPrebuilt)
<dtz>
just wondering if it's "bad" to leave it out
<dtz>
sounds like it's not obviously the worst idea, lol
<Sonarpulse>
if you are not building linux kernels, it's fine :D
<dtz>
oh! I mean in a package's meta
<dtz>
lol
<Sonarpulse>
dtz: oh platformsS
<Sonarpulse>
dtz: well does it work on windows? :D
<Sonarpulse>
there is an `all` thinggy
<dtz>
idk! I don't have knowledge that it doesn't!
<Sonarpulse>
dtz: yeah use the "all" thinggy
<dtz>
well so I know this has been discussed--mostly just double-checking it's okay to omit before submitting a PR doing so :P
<Sonarpulse>
dtz: if one doesn't do a platforms, I think hydra only builds on linux
<Sonarpulse>
it's unfortunate
<dtz>
oh, okay! great
MichaelRaskin has joined #nixos-dev
jtojnar has joined #nixos-dev
Lisanna has quit [Ping timeout: 240 seconds]
Synthetica has joined #nixos-dev
orivej_ has joined #nixos-dev
orivej has quit [Ping timeout: 260 seconds]
phreedom has quit [Remote host closed the connection]
phreedom has joined #nixos-dev
xeji has joined #nixos-dev
phreedom has quit [Remote host closed the connection]
phreedom has joined #nixos-dev
lassulus has quit [Quit: WeeChat 2.0]
lassulus has joined #nixos-dev
Lisanna has joined #nixos-dev
pxc has joined #nixos-dev
pxc has quit [Ping timeout: 276 seconds]
pxc has joined #nixos-dev
pxc has quit [Ping timeout: 255 seconds]
xeji has quit [Quit: WeeChat 2.0]
<gchristensen>
good news -- I think I'll be releasing new NixOS installers for Packet.net, with lots of improvements and a bump to 18.03