That’s right. The problem is in the original image, since it does not make any sense that a system defined as “NomadBSD is a persistent live system for USB flash drives, based on FreeBSD®” forces, to avoid the reported error, to install it on another USB or HDD.
Until version 131R (December '22) this error did not occur, and the system could be updated on the USB itself without problems. It was from version 132R (October '23), when hardlink errors began to appear and version 140R (November '23, only 43 days after!) was created, in my opinion hastily.
Today I installed NomadBSD on an HDD with Settler as the user and it worked well, according to Mauro. However, once installed and completely updated (about 400 packages), I tried to create a new user and apparently it did well, but then it did not allow me to start the system from this new user, even though I had the same permissions and accesses as Settler, unable to log in reporting an “xterm definition error”.
These are the user definition screens
The error that appears when trying to start NomadBSD with this user is: “There is no user-session or usable default with xterm”.
As I said before, until version 131R I was able to use NomadBSD normally, and it was from 132R onwards that it stopped working as expected, so in view of the errors and in my opinion poor configuration or compilation of version 140R, I will not use NomadBSD again.
As they say, it was nice while it lasted.
Greetings to all users.