<Mic92>
My laptop is now converted to nix-sops: https://github.com/Mic92/sops-nix documentation to be written, but I think you get the idea from this commit
<gchristensen>
anyone know why udev might be unable to configure /dev/ttyS0 when this config is applied: systemd.services.systemd-udevd.serviceConfig.NetworkNamespacePath = "/var/run/netns/foobar";
<flokli>
gchristensen: what are you doing? oO
<flokli>
running systemd-udevd (and only it) in a separate network namespace sounds scary
<gchristensen>
why do you say that? (it has a few other things in there ...)
<gchristensen>
flokli: I've started systemd in a separate netns, leaving all the physical devices in the original one
<gchristensen>
but then dhcpcd, even when running in the original netns, doesn't seem to worke for udev reasons
<flokli>
hmmm… I'd probably run an entire system inside an nspawn container then, not just individual system units…
<flokli>
I'd assume systemd-udevd and pid1 do some sort of communication, and might have some assumptions on seeing similar things
<flokli>
but :shrug:
<gchristensen>
well I need certain pieces to run in the original namespace
<gchristensen>
because I need them to talk to the physical devices
<gchristensen>
right now that is dhcpcd and ssh's .socket unit, though dhcpcd doesn't work yet
<flokli>
I'd just solve this with some routing probably and a veth pair
<flokli>
I'd just leave my main system in the main network namespace
<gchristensen>
yeah... I don't really want to do that, but I know that is the prevailing solution
<gchristensen>
so your concern is systemd-udev and pid1 wanting to talk over a network socket of some sort, causing trouble? might be
<flokli>
gchristensen: I just mean, you're chartering unexplored waters :-)