06-28-2020, 05:33 PM
Maybe there's a middle ground here.
What if the ISO included a "moodecfg.txt.dist" flle in the boot partition filesystem?
If the user ignored it, then moOde would go through its first boot with the parameter values already built into the code.
If the user copied it (or renamed it) to moodecfg.txt and edited it, then moOde incorporate the parameter values from the file as it goes through the first boot.
Used or not, the file(s) could be deleted after the first boot, as is done now, to avoid confusion later on.
This compromise would require little additional work on @Tim Curtis's part while, it seems to me, providing the boost to the user that @normand is looking for.
What I like best about this scheme is that it would make more visible any changes which might occur in future moOde releases to the structure or content of the moodecfg.txt file without me having to go find the prototype in the rootfs or in the repo.
Just a thought.
Regards,
Kent
What if the ISO included a "moodecfg.txt.dist" flle in the boot partition filesystem?
If the user ignored it, then moOde would go through its first boot with the parameter values already built into the code.
If the user copied it (or renamed it) to moodecfg.txt and edited it, then moOde incorporate the parameter values from the file as it goes through the first boot.
Used or not, the file(s) could be deleted after the first boot, as is done now, to avoid confusion later on.
This compromise would require little additional work on @Tim Curtis's part while, it seems to me, providing the boost to the user that @normand is looking for.
What I like best about this scheme is that it would make more visible any changes which might occur in future moOde releases to the structure or content of the moodecfg.txt file without me having to go find the prototype in the rootfs or in the repo.
Just a thought.
Regards,
Kent
