-
Improvement
-
Resolution: Invalid
-
Minor
-
None
-
None
-
boot from livecd, there is no indication that the environment is a live environment vs an installed system
-
HWSurvery.py produces some ultimately misleading data when run from live/fchroot environment. We do not want this data in the CPU database in this case.
-
there is currently no immediately obvious means to discriminate between a live environment or an installed environment
-
HWSurvey.py makes calls to 'epro get subarch' and 'epro get mix-ins'. In a live environment this data will be representative of the livecd, not the final installed system.
Since I submitted my HWSurvery script (FL-11399) I have seen discussions on discord mentioning possible expansion of said script, and specifically, running it from the live environment. This is not what it has been designed for and should it be run from the live environment, the Funtoo environment specific data will be misleading (reporting the live environment subarch/mix-in configuration rather than the actual system). Nevertheless, as it may well be run from such an environment, we as recipients of the report need to know if it has come from said environment so that the misleading data can be ignored.
Therefore I am suggesting that the shell prompt string of the livecd be modified to contain the string 'livecd' in much the same way that fchroot does. The HWSurvey script can then detect this and place appropriate warnings in the report.
never mind, was working from old data.
- relates to
-
-
- Work Queue
-
