If you like BoxMatrix then please contribute Supportdata, Supportdata2, Firmware and/or Hardware (get in touch).
My metamonk@yahoo.com is not reachable by me since years. Please use hippie2000@webnmail.de instead.
0
U
Property:POSIXLY CORRECT
From BoxMatrix
(Redirected from POSIXLY CORRECT)
| BoxMatrix >> Environment >> POSIXLY_CORRECT | @ BoxMatrix - IRC-Chat - Translate: de es fr it nl pl |
| News | Selectors | Models | Accessories | Components | Environment | Config | Commands | System | Webif | Software | Develop | Lexicon | Community | Project | Media |
| Bootloader-Env | Brandings | TIATM-Env | Linux-Env | AVM-Env | Config-Env | CGI-Env | WebCM-Env | Kernel-Cfg | Research |
Linux-Variable
| Variable: | POSIXLY_CORRECT - type Text | Wiki | Freetz | IPPF | whmf | AVM | Web |
| Location: | Environment >> Linux-Environment - Origin: busybox, uClibc | ||||||
| Source: | busybox, uClibc | ||||||
| Values: | Release: <any> Lab+Rel: <any> | ||||||
| Properties: | Firmware: 1.63 - 8.00 | ||||||
| Defines: | If present: Try to behave according to the POSIX standard. | ||||||
Goto: Dependencies - Model-Matrix - SMW-Browser
Details
Excerpt from: bashref.info >> Bash Variables >> POSIXLY_CORRECT variable
POSIXLY_CORRECT
If this variable is in the environment when Bash starts, the shell
enters POSIX mode (*note Bash POSIX Mode::) before reading the
startup files, as if the '--posix' invocation option had been
supplied. If it is set while the shell is running, Bash enables
POSIX mode, as if the command
set -o posix
had been executed.
Excerpt from: bashref.info >> Bash POSIX Mode >> POSIXLY_CORRECT variable
POSIXLY_CORRECT
Bash POSIX Mode
Starting Bash with the '--posix' command-line option or executing 'set
-o posix' while Bash is running will cause Bash to conform more closely
to the POSIX standard by changing the behavior to match that specified
by POSIX in areas where the Bash default differs.
When invoked as 'sh', Bash enters POSIX mode after reading the
startup files.
The following list is what's changed when 'POSIX mode' is in effect:
1. When a command in the hash table no longer exists, Bash will
re-search '$PATH' to find the new location. This is also available
with 'shopt -s checkhash'.
2. The message printed by the job control code and builtins when a job
exits with a non-zero status is 'Done(status)'.
3. The message printed by the job control code and builtins when a job
is stopped is 'Stopped(SIGNAME)', where SIGNAME is, for example,
'SIGTSTP'.
4. Alias expansion is always enabled, even in non-interactive shells.
5. Reserved words appearing in a context where reserved words are
recognized do not undergo alias expansion.
6. The POSIX 'PS1' and 'PS2' expansions of '!' to the history number
and '!!' to '!' are enabled, and parameter expansion is performed
on the values of 'PS1' and 'PS2' regardless of the setting of the
'promptvars' option.
7. The POSIX startup files are executed ('$ENV') rather than the
normal Bash files.
8. Tilde expansion is only performed on assignments preceding a
command name, rather than on all assignment statements on the line.
9. The default history file is '~/.sh_history' (this is the default
value of '$HISTFILE').
10. Redirection operators do not perform filename expansion on the
word in the redirection unless the shell is interactive.
11. Redirection operators do not perform word splitting on the word in
the redirection.
12. Function names must be valid shell 'name's. That is, they may not
contain characters other than letters, digits, and underscores, and
may not start with a digit. Declaring a function with an invalid
name causes a fatal syntax error in non-interactive shells.
13. Function names may not be the same as one of the POSIX special
builtins.
14. POSIX special builtins are found before shell functions during
command lookup.
15. When printing shell function definitions (e.g., by 'type'), Bash
does not print the 'function' keyword.
16. Literal tildes that appear as the first character in elements of
the 'PATH' variable are not expanded as described above under *note
Tilde Expansion::.
17. The 'time' reserved word may be used by itself as a command. When
used in this way, it displays timing statistics for the shell and
its completed children. The 'TIMEFORMAT' variable controls the
format of the timing information.
18. When parsing and expanding a ${...} expansion that appears within
double quotes, single quotes are no longer special and cannot be
used to quote a closing brace or other special character, unless
the operator is one of those defined to perform pattern removal.
In this case, they do not have to appear as matched pairs.
19. The parser does not recognize 'time' as a reserved word if the
next token begins with a '-'.
20. The '!' character does not introduce history expansion within a
double-quoted string, even if the 'histexpand' option is enabled.
21. If a POSIX special builtin returns an error status, a
non-interactive shell exits. The fatal errors are those listed in
the POSIX standard, and include things like passing incorrect
options, redirection errors, variable assignment errors for
assignments preceding the command name, and so on.
22. A non-interactive shell exits with an error status if a variable
assignment error occurs when no command name follows the assignment
statements. A variable assignment error occurs, for example, when
trying to assign a value to a readonly variable.
23. A non-interactive shell exits with an error status if a variable
assignment error occurs in an assignment statement preceding a
special builtin, but not with any other simple command.
24. A non-interactive shell exits with an error status if the
iteration variable in a 'for' statement or the selection variable
in a 'select' statement is a readonly variable.
25. Non-interactive shells exit if FILENAME in '.' FILENAME is not
found.
26. Non-interactive shells exit if a syntax error in an arithmetic
expansion results in an invalid expression.
27. Non-interactive shells exit if a parameter expansion error occurs.
28. Non-interactive shells exit if there is a syntax error in a script
read with the '.' or 'source' builtins, or in a string processed by
the 'eval' builtin.
29. Process substitution is not available.
30. While variable indirection is available, it may not be applied to
the '#' and '?' special parameters.
31. When expanding the '*' special parameter in a pattern context
where the expansion is double-quoted does not treat the '$*' as if
it were double-quoted.
32. Assignment statements preceding POSIX special builtins persist in
the shell environment after the builtin completes.
33. Assignment statements preceding shell function calls persist in
the shell environment after the function returns, as if a POSIX
special builtin command had been executed.
34. The 'command' builtin does not prevent builtins that take
assignment statements as arguments from expanding them as
assignment statements; when not in POSIX mode, assignment builtins
lose their assignment statement expansion properties when preceded
by 'command'.
35. The 'bg' builtin uses the required format to describe each job
placed in the background, which does not include an indication of
whether the job is the current or previous job.
36. The output of 'kill -l' prints all the signal names on a single
line, separated by spaces, without the 'SIG' prefix.
37. The 'kill' builtin does not accept signal names with a 'SIG'
prefix.
38. The 'export' and 'readonly' builtin commands display their output
in the format required by POSIX.
39. The 'trap' builtin displays signal names without the leading
'SIG'.
40. The 'trap' builtin doesn't check the first argument for a possible
signal specification and revert the signal handling to the original
disposition if it is, unless that argument consists solely of
digits and is a valid signal number. If users want to reset the
handler for a given signal to the original disposition, they should
use '-' as the first argument.
41. The '.' and 'source' builtins do not search the current directory
for the filename argument if it is not found by searching 'PATH'.
42. Enabling POSIX mode has the effect of setting the
'inherit_errexit' option, so subshells spawned to execute command
substitutions inherit the value of the '-e' option from the parent
shell. When the 'inherit_errexit' option is not enabled, Bash
clears the '-e' option in such subshells.
43. When the 'alias' builtin displays alias definitions, it does not
display them with a leading 'alias ' unless the '-p' option is
supplied.
44. When the 'set' builtin is invoked without options, it does not
display shell function names and definitions.
45. When the 'set' builtin is invoked without options, it displays
variable values without quotes, unless they contain shell
metacharacters, even if the result contains nonprinting characters.
46. When the 'cd' builtin is invoked in LOGICAL mode, and the pathname
constructed from '$PWD' and the directory name supplied as an
argument does not refer to an existing directory, 'cd' will fail
instead of falling back to PHYSICAL mode.
47. The 'pwd' builtin verifies that the value it prints is the same as
the current directory, even if it is not asked to check the file
system with the '-P' option.
48. When listing the history, the 'fc' builtin does not include an
indication of whether or not a history entry has been modified.
49. The default editor used by 'fc' is 'ed'.
50. The 'type' and 'command' builtins will not report a non-executable
file as having been found, though the shell will attempt to execute
such a file if it is the only so-named file found in '$PATH'.
51. The 'vi' editing mode will invoke the 'vi' editor directly when
the 'v' command is run, instead of checking '$VISUAL' and
'$EDITOR'.
52. When the 'xpg_echo' option is enabled, Bash does not attempt to
interpret any arguments to 'echo' as options. Each argument is
displayed, after escape characters are converted.
53. The 'ulimit' builtin uses a block size of 512 bytes for the '-c'
and '-f' options.
54. The arrival of 'SIGCHLD' when a trap is set on 'SIGCHLD' does not
interrupt the 'wait' builtin and cause it to return immediately.
The trap command is run once for each child that exits.
55. The 'read' builtin may be interrupted by a signal for which a trap
has been set. If Bash receives a trapped signal while executing
'read', the trap handler executes and 'read' returns an exit status
greater than 128.
56. Bash removes an exited background process's status from the list
of such statuses after the 'wait' builtin is used to obtain it.
There is other POSIX behavior that Bash does not implement by default
even when in POSIX mode. Specifically:
1. The 'fc' builtin checks '$EDITOR' as a program to edit history
entries if 'FCEDIT' is unset, rather than defaulting directly to
'ed'. 'fc' uses 'ed' if 'EDITOR' is unset.
2. As noted above, Bash requires the 'xpg_echo' option to be enabled
for the 'echo' builtin to be fully conformant.
Bash can be configured to be POSIX-conformant by default, by
specifying the '--enable-strict-posix-default' to 'configure' when
building (*note Optional Features::).
Model-Matrix
Daily updated index of the presence and value of this variable for each model. Last update: 2024-11-05 07:03 GMT.
Showing all models using this variable. Click any column header (click-wait-click) to sort the list by the respective data.
The (main/scrpn/boot/arm/prx/atom/rtl) label in the Model column shows which CPU is meant for Multi-Linux models.
Note that this list is merged from Firmware-Probes of all known AVM firmware for a model, including Recovery.exe 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.
