From 0423f0ef38b56c02f31eb4302bb9696b3d678c60 Mon Sep 17 00:00:00 2001 From: Jade Lovelace Date: Mon, 10 Nov 2025 01:22:53 -0800 Subject: [PATCH] docs typo: ssh-keyscan takes a hostname not user@host Change-Id: Ib823165bcababed2808a602368d6ab57762a49b3 --- doc/manual/src/advanced-topics/distributed-builds.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/manual/src/advanced-topics/distributed-builds.md b/doc/manual/src/advanced-topics/distributed-builds.md index e88c0490d..6781e672d 100644 --- a/doc/manual/src/advanced-topics/distributed-builds.md +++ b/doc/manual/src/advanced-topics/distributed-builds.md @@ -41,7 +41,7 @@ contains Nix. > If you are building via the Lix daemon (default on Linux and macOS), it is the Lix daemon user account (that is, `root`) that should have SSH access to a user (not necessarily `root`) on the remote machine. > > Furthermore, `root` needs to have the public host keys for the remote system in its `.ssh/known_hosts`. -> To add them to `known_hosts` for root, do `ssh-keyscan USER@HOST | sudo tee -a ~root/.ssh/known_hosts`. +> To add them to `known_hosts` for root, do `ssh-keyscan HOST | sudo tee -a ~root/.ssh/known_hosts`. > > If you can’t or don’t want to configure `root` to be able to access the remote machine, you can use a private Nix store instead by passing e.g. `--store ~/my-nix` when running a Nix command from the local machine.