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.
Property:environ
| BoxMatrix >> System >> environ | @ 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 |
| Devices | Filesystems | Partitions | Sockets | Netlink | Pipes | Interfaces | Bridges | Ports | Events | Sources | Sinks | AVMIPC | Processes | Watchdogs | Memory | Slab | Vmalloc | ProcFS | SysFS | Research |
Procfs-Object
| Procfs-Object: | environ - type File | Wiki | Freetz | IPPF | whmf | AVM | Web |
| Location: | System >> Proc-Filesystem - Origin: Linux | ||||||
| Path: | /proc/1 | ||||||
| Properties: | Firmware: 4.07 - 7.90 - Kernel (perm): 2.4.17 (r), 2.6.13.1 (r), 2.6.28.10 (r), 2.6.32.60 (r), 2.6.32.61 (r), 2.6.39.4 (r), 3.10.107 (r), 3.10.73 (r), 4.1.38 (r), 4.1.52 (r), 4.19.183 (r), 4.4.271 (r), 4.4.60 (r), 4.9.198 (r), 4.9.218 (r), 4.9.250 (r), 4.9.325 (r) | ||||||
| Function: | Initial shell Environment of a process when it was launched. | ||||||
Goto: Examples - Dependencies - Model-Matrix - Help Supportdata2 - SMW-Browser
Details
environ contains the initial shell Environment of a process when it was launched.
This is what env prints, but each line is zero terminated instead of a line feed.
Excerpt from the proc(5) man page:
/proc/[pid]/environ
This file contains the initial environment that was set
when the currently executing program was started via
execve(2). The entries are separated by null bytes
('\0'), and there may be a null byte at the end. Thus, to
print out the environment of process 1, you would do:
$ cat /proc/1/environ | tr '\000' '\n'
If, after an execve(2), the process modifies its
environment (e.g., by calling functions such as putenv(3)
or modifying the environ(7) variable directly), this file
will not reflect those changes.
Furthermore, a process may change the memory location that
this file refers via prctl(2) operations such as
PR_SET_MM_ENV_START.
Permission to access this file is governed by a ptrace
access mode PTRACE_MODE_READ_FSCREDS check; see ptrace(2).
Examples
Fw 7.29 examples:
root@fritz1:/var/mod/root# hexdump -n 128 -C /proc/self/environ 00000000 43 4f 4e 46 49 47 5f 46 4f 4e 5f 48 44 3d 79 00 |CONFIG_FON_HD=y.| 00000010 43 4f 4e 46 49 47 5f 54 49 4d 45 52 43 4f 4e 54 |CONFIG_TIMERCONT| 00000020 52 4f 4c 3d 79 00 43 4f 4e 46 49 47 5f 55 53 42 |ROL=y.CONFIG_USB| 00000030 5f 53 54 4f 52 41 47 45 5f 55 53 45 52 53 3d 6e |_STORAGE_USERS=n| 00000040 00 43 4f 4e 46 49 47 5f 57 4c 41 4e 3d 79 00 43 |.CONFIG_WLAN=y.C| 00000050 4f 4e 46 49 47 5f 57 4c 41 4e 5f 52 41 44 49 4f |ONFIG_WLAN_RADIO| 00000060 53 45 4e 53 4f 52 3d 79 00 43 4f 4e 46 49 47 5f |SENSOR=y.CONFIG_| 00000070 41 42 5f 43 4f 55 4e 54 3d 31 00 43 4f 4e 46 49 |AB_COUNT=1.CONFI| 00000080 root@fritz1:/var/mod/root# strings /proc/self/environ | head CONFIG_FON_HD=y CONFIG_TIMERCONTROL=y CONFIG_USB_STORAGE_USERS=n CONFIG_WLAN=y CONFIG_WLAN_RADIOSENSOR=y CONFIG_AB_COUNT=1 CONFIG_DSL_VRX518=y CONFIG_EWETEL_SMARTMETER=n CONFIG_FON_IPPHONE=y CONFIG_I2C=n root@fritz1:/var/mod/root# env | head CONFIG_FON_HD=y CONFIG_TIMERCONTROL=y CONFIG_USB_STORAGE_USERS=n CONFIG_WLAN=y CONFIG_WLAN_RADIOSENSOR=y CONFIG_AB_COUNT=1 CONFIG_DSL_VRX518=y CONFIG_EWETEL_SMARTMETER=n CONFIG_FON_IPPHONE=y CONFIG_I2C=n
Dependencies
Daily updated index of all dependencies of this object. Last update: GMT.
A ** in the Mod column marks info from Supportdata2 probes, which will always stay incomplete.
A - in the Mod column marks manual research, the Firmware then shows where the Object occurs, not the Relation.
| Relation | Typ | Object | Mod | Firmware | Info | Origin |
|---|---|---|---|---|---|---|
| 0 dependencies for this object | ||||||
Model-Matrix
Daily updated index of the presence, path and size of this object for each model. Last update: 2024-04-18 04:27 GMT.
Showing all models using this object. Click any column header (click-wait-click) to sort the list by the respective data.
The (main/scrpn/boot/arm/prx/atom) label in the Model column shows which CPU is meant for models with multiple Linux instances.
Note that this list comes from Supportdata2 probes, which can have arbitrary settings and come from different firmware versions.
It doesn't say much if a model is not listed here. It may be a missing supportdata2 file or just a disabled feature.
| Model | Firmware | Path | Kernel (perm) |
|---|---|---|---|
| FRITZ!Box SL WLAN | 4.34 | /proc/1 | 2.6.13.1 (r) |
| FRITZ!Box WLAN 3020 | 4.34 | /proc/1 | 2.6.13.1 (r) |
| FRITZ!Box WLAN 3050 | 4.07 | /proc/1 | 2.4.17 (r) |
| FRITZ!Box WLAN 3070 | 4.15 | /proc/1 | 2.4.17 (r) |
| FRITZ!Box 3490 | 7.30 | /proc/1 | 3.10.107 (r) |
| FRITZ!Box 4020 | 7.01 | /proc/1 | 4.4.60 (r) |
| FRITZ!Box 4060 | 7.30 - 7.39 | /proc/1 | 4.4.271 (r), 4.4.60 (r) |
| FRITZ!Box 5490 | 7.29 | /proc/1 | 3.10.107 (r) |
| FRITZ!Box 5590 Fiber (arm) | 7.29 | /proc/1 | 4.4.60 (r) |
| FRITZ!Box 6360 Cable | 5.20 | /proc/1 | 2.6.28.10 (r) |
| FRITZ!Box 6430 Cable (arm) | 7.29 | /proc/1 | 2.6.39.4 (r) |
| FRITZ!Box 6430 Cable (atom) | 7.29 | /proc/1 | 2.6.39.4 (r) |
| FRITZ!Box 6490 Cable (arm) | 7.29 - 7.39 | /proc/1 | 2.6.39.4 (r) |
| FRITZ!Box 6490 Cable (atom) | 7.29 - 7.39 | /proc/1 | 2.6.39.4 (r) |
| FRITZ!Box 6660 Cable (atom) | 7.29 | /proc/1 | 4.9.250 (r) |
| FRITZ!Box 6850 LTE | 7.39 | /proc/1 | 4.4.60 (r) |
| FRITZ!Box 6850 5G | 7.39 | /proc/1 | 4.4.60 (r) |
| FRITZ!Box Fon WLAN 7050 | 4.33 | /proc/1 | 2.6.13.1 (r) |
| FRITZ!Box Fon WLAN 7140 | 4.33 | /proc/1 | 2.6.13.1 (r) |
| FRITZ!Fon 7150 | 4.72 | /proc/1 | 2.6.13.1 (r) |
| FRITZ!Box Fon WLAN 7240 | 6.06 | /proc/1 | 2.6.32.60 (r) |
| FRITZ!Box 7272 | 6.88 | /proc/1 | 2.6.32.61 (r) |
| FRITZ!Box Fon WLAN 7320 | 6.55 | /proc/1 | 2.6.32.61 (r) |
| FRITZ!Box 7362 SL | 7.12 | /proc/1 | 3.10.107 (r) |
| FRITZ!Box Fon WLAN 7390 | 6.04 | /proc/1 | 2.6.28.10 (r) |
| FRITZ!Box 7412 | 6.87 | /proc/1 | 3.10.73 (r) |
| FRITZ!Box 7430 | 7.29 | /proc/1 | 3.10.107 (r) |
| FRITZ!Box 7490 | 7.29 - 7.51 | /proc/1 | 3.10.107 (r) |
| FRITZ!Box 7510 | 7.30 | /proc/1 | 4.4.60 (r) |
| FRITZ!Box 7520 | 7.29 - 7.50 | /proc/1 | 4.4.271 (r), 4.4.60 (r) |
| FRITZ!Box 7520 v2 | 7.31 | /proc/1 | 4.4.60 (r) |
| FRITZ!Box 7530 | 7.39 | /proc/1 | 4.4.271 (r) |
| FRITZ!Box 7530 AX | 7.31 - 7.51 | /proc/1 | 4.1.52 (r), 4.19.183 (r) |
| FRITZ!Box 7581 | 7.17 | /proc/1 | 4.1.38 (r) |
| FRITZ!Box 7590 | 7.57 - 7.90 | /proc/1 | 4.9.325 (r) |
| FRITZ!Box 7590 AX | 7.31 - 7.39 | /proc/1 | 4.9.198 (r), 4.9.218 (r) |
| FRITZ!Smart Gateway | 7.57 - 7.58 | /proc/1 | 4.4.271 (r) |
| FRITZ!Repeater 1200 AX | 7.30 - 7.39 | /proc/1 | 4.4.60 (r) |
| FRITZ!WLAN Repeater 1750E | 7.29 | /proc/1 | 4.4.60 (r) |
| FRITZ!Repeater 6000 | 7.29 - 7.39 | /proc/1 | 4.4.60 (r) |
| 40 models use this object | |||
Help Supportdata2
The data in this article is incomplete since it was manually collected using the Supportdata2 project.
Unlike the Supportdata-Probes which have been collected for years Supportdata2 is brand new and only has a few probes.
If you have access to a shell then please help to extend the Supportdata2 collection to improve this data.
It's easy and it's done in minutes. Please send created data as an Email attachment to the address listed here. Thanks!
