You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I see in the other newbie question issue that cpud -d -init may be necessary when running outside of system startup. That helped me quite a bit to get a server started.
Once that server is started, I get a message cpuns not found which seems to imply that I need an executable called cpuns on either the server or the client side. It makes sense if cpu is trying to do namespacey things.
I don't, however, see anything with that name around.
Running cpu -ssh appears to work well which corroborates the idea that some sort of namespace executable or config is missing.
What is it that I don't know enough to ask?
Here is a transcript from the client side
tdunning@nodec:~/cpu$ cpu -key ~/.ssh/id_rsa nodea
bash: line 25: cpuns: command not found
2025/04/03 01:31:25 SSH error Process exited with status 127
tdunning@nodec:~/cpu$ cpu -ssh -key ~/.ssh/id_rsa nodea
2025/04/03 01:31:39 Running basic ssh protocol; no mounts
tdunning@nodea:~$ exit
tdunning@nodec:~/cpu$
And here are the outputs from the client and server sides with debug prints on
Second, you should not need to run cpud with -init unless you are really init. If I have a board with a shell prompt, meaning it ran init, I only run cpud or cpud -d.
cpud needs to be in $PATH, and a file named key.pub has to somewhere it will find it, or you can name it something else and use the -pk switch.
the cpu command (not cpud, cpu) checks to see if it is on port 22. If so, it will try to just run a cpuns command. If you have a working ssh on the target system, it's frequently easier to install cpuns in some standard place, so:
cd u-root/cpu/cmds/cpuns
CGO_ENABLED=0 GOARCH=arm5 go build . # or other arm stuff here
scp cpuns rpi:/usr/bin # or whatever your rpi is named
My test for whether to use cpud or cpuns: If I have to run the cpud by hand, by ssh'ing in to a system, cpuns makes more sense to use. If I want to build an initramfs from scratch, with u-root, then I'll use cpud. If I have something like a milk duo s, which uses sysv-like scripts, then install the script from the cpu repo, reboot, and you have cpud and sshd.
here's an example .ssh/config for milkv galaxy or whatever they call it:
host milkv
HostName 192.168.42.1
IdentityFile ~/.ssh/cpu_rsa
User root
Port 17010
here is for an ip6 host, running cpud
Host k10
User root
HostName fe80::fcfe:feff:fe1e:319b%enx00e04c6800ee
IdentityFile ~/.ssh/cpu_rsa
Port 17010
I see in the other newbie question issue that
cpud -d -init
may be necessary when running outside of system startup. That helped me quite a bit to get a server started.Once that server is started, I get a message
cpuns not found
which seems to imply that I need an executable calledcpuns
on either the server or the client side. It makes sense if cpu is trying to do namespacey things.I don't, however, see anything with that name around.
Running
cpu -ssh
appears to work well which corroborates the idea that some sort of namespace executable or config is missing.What is it that I don't know enough to ask?
Here is a transcript from the client side
And here are the outputs from the client and server sides with debug prints on
The text was updated successfully, but these errors were encountered: