<abathur>
is that enough, or do you need the full log?
<Mic92>
abathur: I think I can work with that, thanks
contrapumpkin is now known as copumpkin
__monty__ has joined #nix-darwin
<hhes>
__monty__ abathur: sorry, I had to go AFK. I used sh <(curl -L https://nixos.org/nix/install) --darwin-use-unencrypted-nix-store-volume for nix and then nix-build https://github.com/LnL7/nix-darwin/archive/master.tar.gz -A installer for Nix-Darwin. the place where I might have screwed up was the Darwin-installer process: I answered 'no' to Would you like to create /run? (wasn't explained why it would need that so I wanted to cancel the process and do
<hhes>
some research). then I reran it and answered 'yes' to that
<abathur>
I found those prompts a little daunting myself; may be worthwhile to mention the confusion in LnL7/nix-darwin#2
<abathur>
I suspect the main thing here is that it sounds like you're mixing a single-user Nix install with some daemon-oriented nix-darwin settings; if you saw the two issues I linked before, they both touch on aspects of this
philr has quit [Ping timeout: 246 seconds]
<hhes>
yeah, it sounds like that from my research too. as far as I know, while using Big Sur I'd rather want multi-user. is that true?
<abathur>
I think you'd probably stop having problems if you make sure those aren't enabled in your darwin config (at least the daemon and gc settings, iirc?) and take ownership of the store after any daemons are dead--or perhaps the inverse if you go back and start with a daemon install
<abathur>
not sure what the research indicated; it may depend a little on the why
<abathur>
my PR in nix#4289 is slated to end support for new single user installs, but that's mostly just because people felt like the installs were getting too complex to be ~ideologically in-line with how simple a single-user install is intended to be
<abathur>
I can't swear it'll land like that, since it hasn't; there's nothing particularly wrong with existing single-user installs (I'm using one on Catalina myself)
<hhes>
hm
<hhes>
okay, that makes sense. I disabled the daemon but now I'm getting 'error: The daemon is not enabled but this is a multi-user install, aborting activation'. I'd like to switch to a single-user installation but, honestly, I don't even know when I opted into a multiuser one (what step does that?)
<abathur>
ah, I forgot there was a line in your message before about it being a multi-user; LnL may know how it decides this but I'll go peek in the source
<hhes>
if you think it'd be easier to just fix a multi-user installation, then I could do that; I don't really have a preference (as far as I know, it doesn't change much besides the fact that the daemon executes all the operations, hence allowing me to setup an autoupdate)
<abathur>
I think I might see what it is doing, at least, but that's also a valid option
<abathur>
do you recall if you added useDaemon to a nix config file?
<hhes>
makes sense, I saw it creating a bunch of users
<abathur>
so if useDaemon got set once, it looks like it might be able to get into a bugged state
<hhes>
btw. is there a way to apply e.g. 'system.defaults.dock.autohide = false;' without rebooting the system?
<hhes>
abathur: yes, I was playing with the configs and I think the services.nix-daemon.enable = true wasn't there by default and I must have enabled it
<abathur>
not sure, re: autohide; if it isn't, there may be a process you can kill
<abathur>
there's a reboot at the end of my system bootstrap script, so I guess I wouldn't notice
eraserhd has joined #nix-darwin
eraserhd has quit [Ping timeout: 240 seconds]
<emily>
`killall Dock` should suffice for such things