ChanServ changed the topic of #nixos-systemd to: NixOS <3 systemd | https://jitsi.nixcon.net/systemd | Next meeting 08.12.2020 14:00 UTC (every two weeks)
pbb has quit [Quit: http://quassel-irc.org - Chat comfortably. Anywhere.]
<colemickens> do we have an over-arching tracking issue for this?
<colemickens> or at least that looks like a pretty recent update
lukegb has quit [Quit: ~~lukegb out~~]
lukegb has joined #nixos-systemd
pbb has joined #nixos-systemd
{^_^} has quit [Remote host closed the connection]
<flokli> colemickens: define "this"
<flokli> #72401 is the "tracking issue" for systemd in initramfs
<flokli> or it kinda became
<flokli> I think most of the work now is looking at everything doing stuff with out initrd, what can be removed, and what still needs to be supported
<flokli> … whether we can use something like plymouth for it, or reuse some of the unit writing logic from NixOS proper to produce in-initrd systemd unitds
julm has quit [*.net *.split]
julm has joined #nixos-systemd
{^_^} has joined #nixos-systemd
<jtojnar> or do we just use /etc/modprobe.d
<Mic92> I get `A dependency job for remote-fs.target failed. See 'journalctl -xe' for details.` on nixos-rebuild for now reason
<Mic92> on 20.09
<Mic92> I checked the dependencies for remote-fs.target
<Mic92> There is one nfs mount and it is fine
<Mic92> mhm. now that I fixed my a docker container service it works.
<Mic92> Not sure how remote-fs.target depends on that
<flokli> Mic92: I think systemd has a per-fstype list and uses this to add mountpoints to remote-fs vs local-fs
<flokli> And nfs is on the "remote-fs" list.
<Mic92> flokli: yeah, but nfs was fine, which surprised me.
<flokli> huh?
<Mic92> flokli: docker-localAttestation.service failed. After fixing it also remote-fs.target was fixed
<Mic92> so someone remote-fs.target depends on multi-user.target?
<Mic92> docker-localAttestation.service is from our oci-container module