Thanks for the information on this, Martin as it is helpful.

I am working my way through the Genode manual after having gone through the Sculpt documentation recently and little-by-little things become clearer.

I actually saw the part in Sculpt about making things permanent, but since I am having troubles getting all of the components in place, in particular with the Virtualbox setup which is referenced in Section 5 of Sculpt 20.02 where it give you the link to follow setting up VM's (https://genodians.org/m-stein/2019-03-07-vm-with-sculpt-ce-preview), I wanted to investigate the possibility of setting it up pre-configured since the "+" component configurations are off-screen in Qemu and have already tried to reduce the Sculpt Font sizes to small (as was recently suggested "Nobody III" from the mailing list) in an attempt to get those components on-screen to configure.

Also, I have looked at changing the Qemu resolution but that did not help as well.

Maybe in the next iteration of Sculpt, the "+" component system could be scrollable or movable on the Sculpt desktop so that there could be an easier way for users to complete component selection and configurations as the components have submenus that seem to go off-screen when expanded to configure.

I'll keep reading up on things to see if I can get it to work, though.

Cheers

Lonnie

On Mon, Apr 13, 2020 at 5:25 AM Martin Stein <martin.stein@genode-labs.com> wrote:

Hi Lonnie,

El 11/4/20 a las 15:52, Lonnie Cumberland escribió:
> I am particularly interested in starting up VirtualBox to see how that
> works but with the "off screen" problem persistent to select the options
> needed for "vm-with-sculpt-ce-preview" directions, I started to wonder
> if it might be possible to have some type of "script" that I could add
> in during the img/iso builds for Sculpt that would automatically select
> and add in all of the components needed so that I could just boot up
> this new modified img/iso and have the VirtualBox frontend GUI started
> up by default?

The sculpt manager is doing the deployment using the file
'config/managed/deploy'. This file always contains a complete
description of the deployment in your runtime. See the Sculpt
documentation [1]:

"... The content of the deploy file is taken as the starting point for
the interactive use via the + menu. All interactive changes to the
deployment are reflected in the managed/deploy file ..."

Once you used GUI and sculpt manager to populate this file with your
individual static setup, you can make the changes permant as the Sculpt
documentation says:

"... To make it permanent, copy the current state of
/config/managed/deploy to /<DISK>/config/<VERSION>/deploy where <DISK>
corresponds to your Sculpt partition ..." (<VERSION> would be 20.02 here)

For sub-systems that you'd like to use often with the same configuration
but that shall not be started automatically, launchers exist:

"... Additionally, the deployment can be controlled by ... and the
so-called launchers located at the launcher/ sub directory. ...
Launchers appear at the top level of the + menu. ..."

Launchers can also be made permanent by copying them to
/<DISK>/config/<VERSION>/launcher/<LAUNCHER_NAME>.

All this is described in more detail in the documentation.

However, if you really want to have your deployment shipped with the
boot image, AFAIK, you'd have to modify the sculpt manager code to
generate different default configs.

Cheers,
Martin

[1] https://genode.org/documentation/articles/sculpt-20-02

_______________________________________________
Genode users mailing list
users@lists.genode.org
https://lists.genode.org/listinfo/users