bud is unable to detect hostname on macOS

[divnix]

bud is unable to detect hostname on macOS

[KarolisL]

I think that hostname -f works on both BSD (at least on Darwin) and Linux. Wouldn't that work?

[nrdxp]

are you trying to deploy NixOS systems from darwin, or what is the usecase here? Unfortunately we still don't have great nix-darwin support in general since we don't have any MacOS users on the core team.

[blaggacao]

The particular implementation is towards the end of:

bud/module.nix

Lines 75 to 88 in 26ba276

	host =
	let
	partitionString = sep: s:
	builtins.filter (v: builtins.isString v) (builtins.split "${sep}" s);
	reversePartition = s: lib.reverseList (partitionString "\\." s);
	rebake = l: builtins.concatStringsSep "." l;
	in
	if (hostConfig != null && hostConfig.networking.domain != null) then
	rebake (reversePartition hostConfig.networking.domain + [ hostConfig.networking.hostName ])
	else if hostConfig != null then
	hostConfig.networking.hostName
	# fall back to reverse dns from hostname --fqdn command
	else "$(IFS='.'; parts=($(hostname --fqdn)); IFS=' '; HOST=$(for (( idx=\${#parts[@]}-1 ; idx>=0 ; idx-- )) ; do printf \"\${parts[idx]}.\"; done); echo \${HOST:: -1})"
	;

We internally need to work with reverse DNS of the fqdn to "reliably" match hosts's to the host raking contract: nested folders are raked as reverse DNS, like so:

com
  example
    host1
    host2
net
  example
    host1
    host2

(sorry for that bash sequence)

[montchr]

are you trying to deploy NixOS systems from darwin, or what is the usecase here?

@nrdxp use case is working with a flake providing an output matching my current darwin host's hostname. The flake provides a set of configurations for nix-darwin and home-manager. Essentially just dotfiles. But I'd like to reuse these profiles on NixOS systems as I build them out (via VMs or Linodes). So at least on darwin, I'd only be using the commands that aren't NixOS-specific (e.g. bud repl or bud switch if it could be used with darwin-rebuild)

@blaggacao Thanks, that points me in the right direction. I'm going to assume I'm doing something kind of wrong in the process of setting up this darwin host, as I don't think I should have ended up hitting that call to hostname at all.

[blaggacao]

@montchr It should alwasy hit hostname unless you'd be running already from within the host that you (still) want to build.

That is: in the devshell, it should always try to figure out your current host via hostname.

Could you think of a BSD compatible implementation?