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!
Happy Sunday! Happy Fathers Day to fellow fathers!
For the last year, going on two now, NetBSD-current updates and recompiles, almost always flawlessly, sometimes while I am sleeping. The setup here is mostly generic and unmodified, just to track what's going on in the neighborhood, and to have the sources handy and available.
This brings back memories of running and rebuilding NetBSD-current -- was it thirty years ago?
When I shut down the VPS, usually it is because I want to make a backup. Usually what I do is shut down the VPS internally and then also run shutdown from the control panel. The idea being that the control panel shutdown possibly is less likely to mess up the backup or even harm the VPS file system internally if the VPS already is shutdown internally and in the control panel when the backup starts. Maybe there really is no danger, so that I am taking unnecessary steps.
I haven't generally been using the control panel restart button. Just Shutdown and Boot.
Yesterday, there was, for the first time, a control panel shutdown failure (as usual, following an internal NetBSD shutdown). This failure manifested as stuck at 73% completion in the control panel log for a long time, about an hour. I did start a backup, after allowing what usually would be enough time (30 sec) for the control panel shutdown to complete, but without checking the shutdown log. The backup seemed to complete, and I received the email confirming the backup as completed. Later, when I checked the control panel log again, the control panel log reported the shutdown as FAILED.
Throughout the hour while the control panel shutdown seemed stuck at 73%, there seemed no way to reset the control panel. I tried reloading the page and logging out and logging in.
I imagined that installing Qemu-guest-agent might facilitate the control panel shutdown.
I never before saw the "power button pressed" message in this exact context. When I saw that message I assumed it was from Qemu-guest-agent. I didn't think about ACPI. There doesn't seem to be a "power button pressed" message in /var/log/messages:
netbsd# cd /var/log
netbsd# grep pressed messages
netbsd#
I am guessing that ACPI messages might not be included in /var/log/messages.
Maybe I should test the Shutdown from the control panel next? Any additional ideas for me, please?
Thanks for your question! I really, really appreciate your kind help!
netbsd# date
Sun Jul 5 22:02:07 UTC 2026
netbsd# # Trying control panel Shutdown
netbsd#
*** FINAL System shutdown message from [email protected] ***
System going down IMMEDIATELY
power button pressed # Don't recall seeing this message before installing Qemu-guest-agent
Connection to xxx.xxx.xxx.xxx closed by remote host.
Connection to xxx.xxx.xxx.xxx closed.
chronos@penguin:~/2026/netbsd$
@cmeerw said: I don't have qemu-guest-agent installed and I also get "power button pressed" when restarting from the control panel. I think that's using ACPI.
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. . . .
Happy Sunday! Happy Fathers Day to fellow fathers!
For the last year, going on two now, NetBSD-current updates and recompiles, almost always flawlessly, sometimes while I am sleeping. The setup here is mostly generic and unmodified, just to track what's going on in the neighborhood, and to have the sources handy and available.
This brings back memories of running and rebuilding NetBSD-current -- was it thirty years ago?
Thanks to Linveo for sponsoring the build VPS.
If someone wants to share this fine, free VPS . . . teach me something . . . please ask.
July 4 edition, everything renewed! Thanks to @linveo!
Free share of this fine, fast, Ryzen VPS is still available!
Best wishes!
Qemu-guest-agent installed! Can now reboot from the web Control Panel! Thanks @linveo!
Couldn't you do that before already without qemu-guest-agent?
I don't have qemu-guest-agent installed and I also get "power button pressed" when restarting from the control panel. I think that's using ACPI.
@cmeerw
When I shut down the VPS, usually it is because I want to make a backup. Usually what I do is shut down the VPS internally and then also run shutdown from the control panel. The idea being that the control panel shutdown possibly is less likely to mess up the backup or even harm the VPS file system internally if the VPS already is shutdown internally and in the control panel when the backup starts. Maybe there really is no danger, so that I am taking unnecessary steps.
I haven't generally been using the control panel restart button. Just Shutdown and Boot.
Yesterday, there was, for the first time, a control panel shutdown failure (as usual, following an internal NetBSD shutdown). This failure manifested as stuck at 73% completion in the control panel log for a long time, about an hour. I did start a backup, after allowing what usually would be enough time (30 sec) for the control panel shutdown to complete, but without checking the shutdown log. The backup seemed to complete, and I received the email confirming the backup as completed. Later, when I checked the control panel log again, the control panel log reported the shutdown as FAILED.
Throughout the hour while the control panel shutdown seemed stuck at 73%, there seemed no way to reset the control panel. I tried reloading the page and logging out and logging in.
I imagined that installing Qemu-guest-agent might facilitate the control panel shutdown.
I never before saw the "power button pressed" message in this exact context. When I saw that message I assumed it was from Qemu-guest-agent. I didn't think about ACPI. There doesn't seem to be a "power button pressed" message in /var/log/messages:
I am guessing that ACPI messages might not be included in /var/log/messages.
Maybe I should test the Shutdown from the control panel next? Any additional ideas for me, please?
Thanks for your question! I really, really appreciate your kind help!
From control panel log:
Task Requested Duration Progress
Shutdown Sunday, July 5, 2026 3:02 PM 17 sec 100% Complete
Worked okay to Boot from control panel:
As usual it seems like @cmeerw is right!
The single log entry below seems consistent with the use of ACPI when I pushed the Restart button on the Control Panel.
Qemu-guest-agent doesn't seem to be doing much. Tagging @linveo in case he might be interested.