You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I know it is wrong to report this at this repo 😄, but…
At the moment, the boot-to-emulator config options are distributed among different configuration files. For example, forced display resolution is defined via grub, the desired boot environment is defined via enviroment-id.txt in the root of the emil-data partition, there is another ini-style formatted settings file for chosing developer or temper-proof mode, the inactivity timeout is part of an XML file yet somewhere else.
It would be nice to have a single configuration file in the emil-data root, XML or YAML, that would contain all the possible configuration options.
The text was updated successfully, but these errors were encountered:
Seems like a not-so-straightforward thing to do. We can unify all our configuration stuff, but the grub configuration is far outside the reach of bwFLA/EaaS/emil.
One possibility is to abuse the kernel command line for some things. This way we can use the grub config to make all the changes. But I would rather not put too much information into kcmd as it is intended for short key=value pairs, not complex XML settings.
CC'ed Oleg as he designed all this live-system stuff.
I know it is wrong to report this at this repo 😄, but…
At the moment, the boot-to-emulator config options are distributed among different configuration files. For example, forced display resolution is defined via grub, the desired boot environment is defined via enviroment-id.txt in the root of the emil-data partition, there is another ini-style formatted settings file for chosing developer or temper-proof mode, the inactivity timeout is part of an XML file yet somewhere else.
It would be nice to have a single configuration file in the emil-data root, XML or YAML, that would contain all the possible configuration options.
The text was updated successfully, but these errors were encountered: