|BoxMatrix >> Environment >> BASH_COMPAT||@|
|Variable:||BASH_COMPAT - type Text||Wiki||Freetz||IPPF||whmf||AVM||Web|
|Location:||Environment >> TODO-Environment - Origin: '|
|Values:||Release: - All:|
|Defines:||The value to set the shell's compatibility level.|
Excerpt from: bashref.info >> Bash Variables >> BASH_COMPAT variable
The value is used to set the shell's compatibility level. *Note
The Shopt Builtin::, for a description of the various compatibility
levels and their effects. The value may be a decimal number (e.g.,
4.2) or an integer (e.g., 42) corresponding to the desired
compatibility level. If 'BASH_COMPAT' is unset or set to the empty
string, the compatibility level is set to the default for the
current version. If 'BASH_COMPAT' is set to a value that is not
one of the valid compatibility levels, the shell prints an error
message and sets the compatibility level to the default for the
current version. The valid compatibility levels correspond to the
compatibility options accepted by the 'shopt' builtin described
above (for example, COMPAT42 means that 4.2 and 42 are valid
values). The current version is also a valid value.
Daily updated index of the presence and value of this variable for each model. Last update: 2020-10-23 03:52 GMT.
Showing all models using this variable. Click any column header (click-wait-click) to sort the list by the respective data.
(main/scrpn/arm/atom) label in the
Model column shows which CPU is meant for models with multiple Linux instances.
Note that this list is merged from Firmware-Scans of all AVM currently has online for a model, including Downgrades and Labor-Files.
If the 'Value' column contains '<comp>' the variable is computed at runtime. '<empty>' means the variable is present but empty (rare).
Multiple values typically show a conditional static assignment or different values in different firmware.
|0 models use this variable|
Showing 1 related property.