In my Chromebook's Linux container's servers directory, each provider has its own subdirectory, inside of which each server has its own directory.
The individual server directories each have a file named login. The first line of each login file (output by head -n 1) is the IPv4 ssh login command and the last line of each login file (output by tail -n 1) is the IPv6 ssh login command.
As long as I am in the right directory, and using sh or bash, I almost always can log in by ssh to any server with the same two keystrokes: Ctrl+r (reverse search through previous commands) and then backtick (`).
As you know, the backticks tell sh and bash to run as a command the output of what is between the backticks.
Of course, as you know, ssh has it's own built-in shortcut procedure that can be set up in a configuration file.
The new pcc seems to bootstrap successfully on NetBSD-current. The Github pcc sources were compiled first using NetBSD's native gcc, and then compiled again using the gcc-built pcc as the compiler to get a pcc-compiled, bootstrapped pcc.
netbsd$ date
Sun Apr 5 16:33:42 UTC 2026
netbsd$ pwd
/home/tom/PortableCC-compiles-itself/bin
netbsd$ ls
hello.c p++ pcc pcpp
netbsd$ cat hello.c
#include <stdio.h>
int main() {
printf("Hello from bootstrapped PCC!\n");
return 0;
}
netbsd$ ./pcc -o hello hello.c
netbsd$ ./hello
Hello from bootstrapped PCC!
netbsd$ ./pcc -v
Portable C Compiler 1.2.0.DEVEL 20231021 for x86_64-unknown-netbsd11.99
error: no input files
netbsd$
Thanks to Anders Magnusson, the recent main pcc developer! Thanks to Linveo for sponsoring my NetBSD-current VPS!
My sponsored Linveo VPS continues to compile NetBSD-current every few days. No issues, certainly no problems!
I like Linveo so much that I actually bought and continue to pay for two additional VPSes from them, one for FreeBSD-current and another for OpenBSD-current.
This thread's offer of a free share of this thread's sponsored NetBSD-current VPS remains open. Please check the OP for details!
Comments
Wow, that
got me confused for a bit. Had never thought you could use it in that context.
Hi @cmeerw!
In my Chromebook's Linux container's servers directory, each provider has its own subdirectory, inside of which each server has its own directory.
The individual server directories each have a file named login. The first line of each login file (output by head -n 1) is the IPv4 ssh login command and the last line of each login file (output by tail -n 1) is the IPv6 ssh login command.
As long as I am in the right directory, and using sh or bash, I almost always can log in by ssh to any server with the same two keystrokes: Ctrl+r (reverse search through previous commands) and then backtick (`).
As you know, the backticks tell sh and bash to run as a command the output of what is between the backticks.
Of course, as you know, ssh has it's own built-in shortcut procedure that can be set up in a configuration file.
Thanks!
Tom
Hopefully cmeerw's fix gets into NetBSD 11 so I could finally see a login prompt on my Linveo Intel VM
It is working amazingly on FreeBSD though and the uptime has been impeccable.
There seems to be a new version of the venerable pcc compiler available on Github at https://github.com/PortableCC.
The new pcc seems to bootstrap successfully on NetBSD-current. The Github pcc sources were compiled first using NetBSD's native gcc, and then compiled again using the gcc-built pcc as the compiler to get a pcc-compiled, bootstrapped pcc.
Thanks to Anders Magnusson, the recent main pcc developer!
Thanks to Linveo for sponsoring my NetBSD-current VPS! 
My sponsored Linveo VPS continues to compile NetBSD-current every few days. No issues, certainly no problems!
I like Linveo so much that I actually bought and continue to pay for two additional VPSes from them, one for FreeBSD-current and another for OpenBSD-current.
This thread's offer of a free share of this thread's sponsored NetBSD-current VPS remains open. Please check the OP for details!
Looks like my sponsored Linveo NetBSD-current VPS has the wapbl(4) journal that @cmeerw mentioned in the BSD thread:
It's been longer than usual since I updated and recompiled.
A little more up to date now. . . .