How to reboot Cubic's "virtual environment" using the CLE on the Terminal page? about cubic HOT 2 CLOSED

The Cubic Terminal environment is not a "running" OS.
It is just a secure, isolated file system that you have root access to, in order to edit, add, or delete files.
Any changes you make to the file system are applied immediately.

There are no active services, as you would find in an actual running OS.
Therefore, do not expect systemd to be running.
Likewise, other services such as snapd do not run in this environment.

With this in mind, the concept of "rebooting" does not apply.

By executing dist-upgrade, you simply ran a program (not a service!) that downloaded a bunch of files (i.e. packages) and copied them into this secure file system. Thus, you do not need to "reboot".

However, if you really want to exit and re-enter the Cubic Terminal environment, you have four choices:

1. Simply type exit in the Terminal and press Enter.
   You will exit the Terminal environment, and Cubic will automatically reenter the environment within a few miliseconds.
2. Alternatively, you can click the Back button in Cubic's header bar, and then click the Customize button in the header bar to return to the Cubic Terminal page.
3. Another option is to click the Next button in Cubic's header bar, and then click the Back button in the header bar to return to the Cubic Terminal page.
4. The last option is to just quit Cubic, restart Cubic, and chose your existing project to continue customizing it.

All of these options are the same. They have no effect on the file system you are updating. No new services will run and the changes applied to your customized OS will not be any different than if you had stayed in the Terminal environment.

from cubic.

(By the way, don't use sudo, you are already root!)

from cubic.